Privacy Policy

What data is collected

Veridax collects the clinical note text that you paste into the Veridax web app. That text is used to generate a Medicare LCD compliance audit, and is discarded immediately after the response is returned. During the current design-partner pilot, submitted text should be synthetic or de-identified — real PHI is in scope only after a signed BAA, partner security review, and PHI-authorized hosting/subprocessor review. Appeal drafting is disabled in the current pilot.

Before any clinical text leaves your browser, a first-pass redaction runs in your browser and removes structured identifiers — specifically:

• Patient and provider names
• Dates of birth (DOBs)
• Medical Record Numbers (MRNs)
• Social Security Numbers (SSNs)
• Insurance IDs and policy numbers
• Phone numbers
• Street addresses
• National Provider Identifiers (NPIs)

Because this scrubbing is automated and pattern-based, it targets identifiers in structured or labeled form (e.g. 'DOB: 01/01/1980', 'Patient: Jane Doe'); identifiers embedded in free-narrative text may not be caught. Veridax therefore does not represent that clinical text is fully de-identified, and treats all processed clinical text as potentially containing PHI. The client-redacted text is then sent to Veridax's serverless functions, which run a second, server-side PHI-redaction pass and the coverage analysis using Anthropic's Claude API. The text is processed in-memory during transient function invocations and is not retained in any Veridax database. Do not enter PHI unless Veridax has enabled a PHI-authorized pilot environment for your organization.

If you create an account, the authentication provider (Clerk) stores your email address and sign-in credential. If you subscribe, the payment processor (Stripe) receives the payment details you enter at checkout — Veridax itself never sees or stores credit card numbers or bank account numbers.

How data is used

Client-redacted clinical text is transmitted over TLS to Veridax's serverless functions, which apply a second, server-side PHI-redaction pass and then run the coverage analysis using the Anthropic Claude API. The output is:

• A structured compliance audit against the selected 2026 Medicare Local Coverage Determination (LCD). (Appeal drafting is disabled in the current pilot; while disabled, no appeal output is generated from your text.)

The response is returned to your browser and displayed to you. Scrubbed text is used solely for the purpose of providing the audit service you requested. It is not used for advertising, analytics, profiling, marketing, or training AI models.

How data is stored

Veridax does not persistently store submitted clinical notes on its servers. Clinical notes submitted for audit are processed in-memory by transient serverless function invocations and discarded the moment the response is returned. Veridax has no patient database, no note archive, and no backup copies of submitted clinical text.

Appeal outcome tracking data — payer name (Medicare, UHC, BCBS, Cigna, or Aetna), outcome status (won, denied, or pending), a timestamp, and the word count of the generated letter — is stored only locally in your own browser via chrome.storage.local. Note text, denial text, and free-text notes are not persisted. This data never leaves your device and is never transmitted to Veridax servers.

Web-app local storage (saved drafts, free-tier audit counter, and the signed access token you receive after payment) is stored in your browser's localStorage for the domain veridax.ai. This is also local-only.

Account records are retained by Clerk. Billing records are retained by Stripe. Standard request metadata (IP address, user agent, timestamp, response status) is logged by our hosting provider, Netlify, for reliability and abuse prevention. None of these logs contain the contents of your clinical notes.

Who data is shared with

Client-redacted clinical text is shared with one external AI processor, Anthropic, for redaction and coverage analysis via the Claude API. Anthropic's API terms prohibit using API inputs to train its models.

Information is handled by these service processors strictly to operate the service:

• Stripe — payment processing
• Clerk — user authentication
• Netlify — hosting and serverless function execution
• Anthropic — AI processing of clinical text

Stripe and Clerk receive only non-clinical account and payment information, never clinical note content. Netlify hosts the serverless functions that process the client-redacted clinical text in-memory during a request, and Anthropic's Claude API processes that text to perform redaction and coverage analysis. Veridax does not store or retain the clinical text.

Veridax does not share your data with any other third parties. Veridax does not sell your data to anyone, ever. There is no advertising network, no analytics broker, no data resale, and no marketing partner.

Your rights

You can clear all locally stored Veridax data at any time:

Uninstall the Chrome extension — removes all chrome.storage.local data (appeal outcome history, license key, saved extension state).

Clear your browser storage for veridax.ai — removes all localStorage data (drafts, audit counters, access tokens).

Delete your account — email the address below to request deletion of account records (Clerk) and billing records (Stripe).

Because Veridax does not store clinical notes on its servers, there is no stored clinical content for us to return, correct, or delete on request — it was discarded at the moment of processing.

Contact

For privacy questions, to exercise any of the rights above, or to report a concern, email oscar@veridax.ai.