Privacy Policy

This policy describes how DenialPath ("we", "us") collects, uses and protects information when you use our website, API and MCP server (the "Service"). DenialPath checks a claim against published CMSNCCI procedure-to-procedure and medically unlikely edits, and explains X12 CARC and RARC denial codes, citing the source behind every verdict. It is not a law firm, a clearinghouse, a payer, or a provider of medical advice, and provides no coverage determination or guarantee of payment.

A claim you scrub for free is never sent to us

The free single-claim scrubber runs entirely in your browser. The payer, date of service, procedure codes, modifiers and units you enter for a free scrub are processed on your device and are never transmitted to our servers. There is no record of that scrub anywhere in our systems.

What a saved claim holds, on a paid plan

If you save a claim on a paid plan, we store the procedure codes, modifiers, units and payer you billed, together with the verdict returned and the CMS edit quarter it was checked against. That is the complete list of fields. There is no name, date of birth, member ID, account number, or any other patient identifier column in our schema, so none is stored even if one appeared in text you typed elsewhere, such as a practice note on an appeal letter.

Information we collect

• Account information, your name and email address (or sign-in provider identifier) when you create an account.
• Plan and billing references, your plan, its status, and the Stripe customer and subscription identifiers that correspond to it. Payment is processed by Stripe; we never see or store your card details.
• API keys, stored as a sha-256 hash plus a short display prefix so you can tell one key from another in your dashboard. The key value itself is never stored. It is shown once, at creation, and you can revoke it at any time.
• An API and MCP request log, the endpoint, method, response status, timing and request identifier for calls made with your key. This is what powers quota accounting, rate limits and the inspectable log in your dashboard, so you can see what your own integrations and agents did.
• Saved claims and scrub runs, on a paid plan: procedure codes, modifiers, units, payer, the verdict, and the CMS edit quarter it was checked against for each claim you choose to save.
• Appeal letters, on a paid plan: the CARC and RARC codes, payer, claim number, date of service and procedure codes you supply to generate a letter, along with any free-text practice note you add. We generate the letter from cited facts; we do not verify anything you type into the practice note field, and you are responsible for what it contains.

That is the complete list. There is no file storage on this Service; Supabase Storage is disabled in our configuration, and there is nothing to submit beyond the typed fields above.

No model provider is in the request path

No part of the Service sends your claim data to a model or AI provider. Every verdict is a deterministic lookup and computation against the cited CMS and X12 datasets, run in code. Nothing you enter is used to train any model, ours or anyone else's. Our MCP server lets an AI agent you control call the same deterministic engine; that agent is yours, and we do not pass your account data to it beyond what your key requests.

How we use your information

• To operate the Service: scrub claims, explain denials, save your claim history and generate appeal letters, and enforce plan quotas and rate limits.
• To send account and billing notifications, such as a password reset or a receipt.
• To process payments for paid plans via Stripe.
• To diagnose and fix faults, and to see which features are worth keeping.
• To keep the Service secure and prevent abuse, including by automated and agent traffic.

We do not sell your personal information.

Data storage and security

Account, API key, request log, saved claim and appeal letter records are stored in Supabase (Postgres) and the Service is hosted on Vercel. Every user table is owner-scoped by Postgres Row Level Security, so a row is readable only by the account that owns it and there is no world-readable user data. All traffic runs over HTTPS. See our Security page for what we do and do not have.

Data retention and your choices

You can delete a saved claim, remove an appeal letter, revoke an API key, or delete your account at any time. If you close your account we honour deletion requests and remove your records within a reasonable period, except where we are required to retain billing records for tax or legal purposes.

Cookies and analytics

We use a small number of cookies required to keep you signed in. That is all. There is no analytics script on this site, no session recording, no advertising tracker, and no third-party tag of any kind. The free scrubber runs entirely in your browser and sends us nothing.

Third parties

We share data with the vendors that operate the Service on our behalf: Supabase for the database, Vercel for hosting, and Stripe for billing, each bound to use it only to provide their service to us.

Accuracy of what we publish

DenialPath provides billing and administrative guidance based on published CMS and X12 sources. It is not medical advice, not a coverage determination, and not a guarantee of payment. NCCI and MUE edits are republished quarterly and payer policies vary by contract. Always confirm against the payer's own current policy before submitting or appealing.

Children

The Service is intended for medical billers, billing companies, and the businesses and agents building on top of them, and is not directed to, or knowingly used by, children under 16.

Changes to this policy

If we make a material change to this policy, we will update the date above and, where appropriate, notify you by email.

Contact

Questions about this policy or your data, including requests to access, export or delete it, can be sent to hello@denialpath.com.