Skip to main content
Noxport Labs

TRUST & PRIVACY SPECIFICATION

Privacy Policy

Effective date: 2026-10-22 · Zero third-party analytics · Local-first data boundaries

1. Data Controller & Contact Information

This privacy policy governs the public website and software documentation for Noxport Labs (https://noxportlabs.com). No personal user accounts or tracking cookies are required to browse or evaluate our interactive workbenches. Noxport AI Exporter Pro license purchases on /pricing#checkout are processed via our PCI-DSS encrypted payment gateway without storing payment card numbers on Noxport Labs servers. Customer support & privacy inquiries: [email protected].

2. What This Website Processes vs. Infrastructure Delivery Logs

Application-Layer Behaviour: This website ships with zero third-party analytics trackers, zero advertising pixels, zero session-replay scripts, and zero marketing cookies. Interactive product fixtures on / and /products/* execute deterministically inside your local browser memory using pre-recorded sample vectors.

Infrastructure & CDN Delivery Logs: Like any website served over HTTPS, the hosting edge or content delivery network (CDN) that delivers static HTML, CSS, SVG, and JavaScript files necessarily processes standard HTTP request metadata (IP address, request timestamp, requested path, and User-Agent header) for routing, DDoS mitigation, and security logging. Noxport Labs does not combine infrastructure delivery logs with behavioral profiling.

3. Product-by-Product Processing Matrix & Data Boundaries

Below is the explicit data boundary for each software project in the Noxport Labs portfolio:

Product-by-product processing matrix comparing website behavior and local-first product runtime architecture
ProductCurrent StatusOn-Site Interactive WorkbenchLocal-First Runtime Data Boundary
Noxport AI ExporterAvailable · v3.0.4.226 · Instant Offline NOX1 KeyStatic in-browser fixture using pre-recorded sample inputs; zero network transmission of user data.Website demonstration runs purely on built-in synthetic sample turns. In the extension, parsing, redaction, and document generation run locally in browser memory after explicit consent (#consentDialog) without uploading chat transcripts to Noxport Labs servers.
AnswerBell AIIn development (Proof-Carrying State Receipt & Attention Layer)Static in-browser fixture using pre-recorded sample inputs; zero network transmission of user data.Content-Redacted Zero-Prompt Privacy: this website monitors no real browser tabs and plays no background audio without explicit user interaction. State Receipt V2 records contain zero prompt text or response payloads.
YouTube → Gemini GemPreview (Verified Evidence Operations Core)Static in-browser fixture using pre-recorded sample inputs; zero network transmission of user data.Static demonstration uses 7 original synthetic transcript segments (SYNTHETIC-ONLY). No YouTube player iframe, external API call, or user playlist URL is requested.
Vitalis Health StudioResearch preview (Personal Health Data Plane & Scoped MCP Gateway)Static in-browser fixture using pre-recorded sample inputs; zero network transmission of user data.Marketing website never accepts health export files. All sleep and heart-rate trend numbers in the inspector are synthetic illustrative values.
CardioLab WorkstationIn development (Physiology Data Integrity & Signal QC Workbench)Static in-browser fixture using pre-recorded sample inputs; zero network transmission of user data.All waveforms and ledger rows are generated from a deterministic built-in mathematical array. The website requests no Web Bluetooth permissions and accepts no biometric uploads.

CWS LIMITED USE POLICY COMPLIANCE · NOXPORT AI EXPORTER (v3.0.4.226 / M2R8)

4. Chrome Web Store User Data Policy & Limited Use Alignment (Noxport M2R8)

The use of information received from Google APIs and active browser tabs by Noxport AI Exporter v3.0.4.226 (M2R8) adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements:

  1. 01. Scoped Active-Tab InvocationDOM access occurs strictly upon explicit user export action after accepting #consentDialog. Zero background tab polling or silent history scraping.
  2. 02. No Sale or TransferZero sale, rental, licensing, or transfer of user conversation data or exported artifacts to third parties, analytics platforms, or data brokers.
  3. 03. No Advertising or Creditworthiness UseZero use of user data or DOM content for personalized, retargeted, or interest-based advertising or for creditworthiness / lending decisions.
  4. 04. Zero Human Access to ConversationsAll AST compilation runs locally in client RAM; the local History registry stores metadata for up to 100 files with zero conversation text transmitted or readable by Noxport Labs personnel.

30-Second Chrome DevTools (`F12`) Zero-Upload Verification Protocol

Self-Audit for CISOs & Enterprise Security Teams
  1. 01. Open any AI conversation tab alongside Chrome DevTools (F12 or Cmd+Option+I → Network tab).
  2. 02. In the DevTools Network filter bar, enter Fetch/XHR and click the Clear networking log (🚫) button.
  3. 03. Trigger any Noxport export (Word .docx, Vector Text PDF, or Professional Pack .zip) or paste your NOX1 license key in the side panel.
  4. 04. Confirm 0 outbound HTTP requests (0 B payload egress). Even Vector PDF glyph subsetting (pdf-font-vectors.js) and NOX1 Ed25519 signature verification (crypto.subtle.verify) execute 100% offline in local memory.
  5. 05. Open DevTools → Application → Local Storage / Extension Storage and verify that the 100-item History registry stores only file metadata (timestamp, format, turn_count, status_badge) and zero raw conversation text.

5. Biometric & Physiological Signal Demonstrations (Vitalis & CardioLab)

The Vitalis and CardioLab pages on this website display synthetic, pre-recorded JSON-RPC payloads and simulated ECG/PPG waveforms for engineering demonstration only. Neither this website nor preview builds of Vitalis or CardioLab are medical devices, covered healthcare entities, or clinical diagnostic services. Users must not upload protected health information (PHI) or rely on these tools for medical decisions.