Privacy Policy

1. Who operates the service

MedicalBillReader.com is operated by Jason Ramirez. For privacy questions or requests, email privacy@medicalbillreader.com. Do not send medical bills, diagnoses, member IDs, account numbers, or other sensitive documents through ordinary email.

The service is intended and offered only to people located in the United States and U.S. territories. It is not offered or marketed to people in the European Economic Area, United Kingdom, or Switzerland. If you are located outside the United States or its territories, do not use the analyzer or submit personal data. This geographic scope does not waive rights under a law that otherwise applies.

2. Information processed

• Uploads: the image or PDF you choose, which may contain names, dates, providers, diagnoses, procedure codes, insurance details, account identifiers, and charges.
• Generated report: the AI response derived from the submitted document.
• Request and security data: IP address and other request metadata processed by hosting infrastructure, plus HMAC-protected rate-limit and entitlement tokens stored in Upstash. The application does not put bill content or report text in those keys.
• Payments: payment, customer, subscription, and transaction information processed by Stripe. Full card numbers go directly to Stripe and are not handled by our application.
• Support and privacy requests: the email address and message content you choose to send.
• Third-party analytics: disabled site-wide. The current site does not load Google Analytics or send page views, device or referral information, upload activity, analysis activity, report content, payment state, or conversion events to Google.

3. How information is used

• Generate and display the bill or EOB report you request.
• Enforce free, paid, and subscription usage limits.
• Process payments, refunds, and subscription management.
• Prevent abuse, investigate failures, and secure the service.
• Respond to support, correction, and privacy requests.

4. Health data and the analyzer

The analyzer is a direct-to-consumer service, not a HIPAA covered entity or business associate service. It does not offer a business associate agreement for public use. Before uploading, remove names, addresses, dates of birth, member IDs, account numbers, barcodes, and other identifiers that are not needed for the explanation.

See the prominently linked Consumer Health Data Privacy Notice for data categories, processors, retention, and rights specific to consumer health data.

5. Service providers and disclosures

• Anthropic:receives the supported document and returns the report through its commercial API. Anthropic states that standard API inputs and outputs are automatically deleted from its backend within 30 days, except when a service has longer customer-controlled retention, different agreed terms apply, or retention is needed for policy enforcement or law. Anthropic's published policy says inputs and outputs flagged by its automated trust and safety systems may be retained for up to two years and associated classification scores for up to seven years. By default, Anthropic says commercial API inputs and outputs are not used to train its models unless the customer opts in or submits feedback. Medical Bill Reader does not claim a zero-data-retention agreement or Business Associate Agreement. See Anthropic's published retention policy.
• Vercel: hosts and routes the application and may process request metadata and operational logs. Application logs use fixed event categories and are designed not to include bill content, base64 data, filenames, report text, Stripe IDs, or raw provider error objects.
• Upstash: stores pseudonymous security, rate-limit, and entitlement keys, not the document or report. The current code creates no new webhook-deduplication keys; legacy keys from the prior design may remain until their expiration.
• Stripe: processes hosted Checkout, payment, subscription, refund, and billing-portal data.
• Third-party analytics: disabled. Google Analytics is not a current service provider for site-usage measurement, and the application does not send analytics data to it.

We may also disclose information when required by law, to protect the service or users, or as part of a business transaction subject to applicable safeguards and notice requirements.

6. Retention

• Document and report in our application: held in memory for the request and active browser page; not intentionally written to our database.
• Anthropic API: up to 30 days under the standard policy, subject to the longer policy-enforcement, legal, customer-controlled-service, and agreed-term exceptions described above. Policy-flagged inputs and outputs may be retained for up to two years and associated classification scores for up to seven years. We do not claim that this public service has zero data retention or a Business Associate Agreement.
• Rate-limit and entitlement keys: generally one minute to 40 days. A pseudonymous pay-per-use replay-prevention key may be retained for up to 370 days. Temporary reservations expire after about 10 minutes. No new webhook-deduplication keys are created; legacy keys may remain for up to 30 days after their last creation.
• Payment records: retained by Stripe and, where applicable, by us for payment, accounting, refund, dispute, fraud-prevention, and legal obligations.
• Analytics: third-party analytics is disabled, so the current site sends no new site-usage data to Google Analytics.
• Provider metadata and logs: follows the active provider configuration, plan, contract, and legal obligations.

7. Cookies and controls

Essential cookies carry signed free-use authorization, an authenticated browser binding, and encrypted paid or subscription entitlement tokens. The paid tokens are bound to the browser-binding cookie and do not expose raw Stripe identifiers. A theme choice may be stored in localStorage. Third-party analytics is disabled, so the current site does not load Google Analytics, set Google Analytics cookies, or display an analytics-consent banner. See the Cookie Policy and Do Not Sell or Share page.

8. Advertising

Google AdSense code is not currently loaded by the site. If advertising is introduced later, this policy and any legally required consent tooling must be updated before activation. Ads may not appear on the analyzer, checkout, pricing, account-management, report, contact, or privacy pages, and document content or sensitive activity may not be used for ad targeting.

9. Privacy rights

Depending on where you live and whether a law applies, you may have rights to know, access, correct, delete, or receive a copy of personal data, withdraw consent, limit certain uses of sensitive data, or appeal a denied request. We do not sell personal data or use bill data for targeted advertising. Email the privacy address above with the subject “Privacy Request.” We may need to verify your identity. To appeal, reply with the subject “Privacy Request Appeal.” Response timing and exceptions follow applicable law.

10. Security and incidents

Safeguards include HTTPS, restrictive response headers, upload type and size validation, rate limiting, signed free-use authorization, browser-bound authenticated paid and subscription entitlement tokens, Stripe webhook signature verification, and category-only security logs. No service can promise absolute security. We will investigate incidents and provide notices when required by applicable breach-notification law.

11. Children and changes

The service is not directed to children under 13. A parent or guardian should manage a minor's bill and remove unnecessary identifiers before upload. We will update the effective date when this policy changes materially and provide additional notice when required.