Privacy policy

Searching without an account

You can search for facility prices, insurance plans, and coverage options without creating an account. Nothing about your search is required to identify you.

If you create an account, we authenticate you with a signed token (JWT) stored in an httpOnly cookie: a cookie your browser holds but that page scripts cannot read. The session stays valid for 7 days before you need to sign in again.

Pricing-estimate logging

We may keep a server-side log of pricing estimates for observability, to understand whether the estimates we're showing are accurate and useful. This logging is optional and controlled by a deployment setting (ENABLE_ESTIMATE_LOGGING); when it is on, we salt and hash any session identifier before it is stored, so the log entry cannot be reversed back to your session.

Consumer health records

If you use an account, you can choose to save estimates, procedure-price watches, insurance claim facts, denial notes, service dates, claim numbers, and HSA/FSA balances. These records can reveal health and financial activity even when they do not contain a diagnosis. Claim rows can be deleted individually. An account can be deleted in Settings, though no universal retention or backup-deletion schedule has been ratified.

Bills and EOB documents

Rede does not currently accept, store, or send real bill or Explanation of Benefits document files to an AI processor. The bill checker receives only the line facts you type for that request; application code has no bill-document table or object store.

AI and external services

Two features send what you write to AI companies, and each names every company, in order, before anything is sent. Ask rede.ai, on the Find a price page, sends only the words in its box, up to 500 characters, after obvious identifiers such as email addresses, phone numbers, dates and long numbers are removed; words typed while searching by service or code are never sent. The care navigator (the Care guide and Ask Rede on the Code lookup and care guide page), for signed-in accounts, sends your messages with the same obvious identifiers removed. Names cannot be found that way, so leave them out. In this release the companies are OpenAI, then Anthropic, then Google (the Gemini API, on a paid Cloud Billing project); the next one is asked only when the one before it cannot answer. No health-privacy agreement or business associate agreement (BAA) covers it: it runs on the founder's interim decision during Rede's demo period, under each company's standard terms for API customers, as recorded in Rede's interim AI policy (docs/legal/ai-health-data-interim-policy-2026-09-17.md and its addenda). No account identifier, IP address or session id is sent with it, and Rede does not store the text. Nothing from document uploads (Rede accepts no real bill or EOB files) or from the bill and claim letter helpers is sent to an AI company, and no page offers web search, so none sends text to SerpAPI. Google Maps/Places receives location searches when Maps is enabled, but not the procedure, plan, or computed price held in Rede's search state. Optional distributed rate limiting sends only HMAC-pseudonymized limiter keys to Upstash, not raw account IDs or IP-address keys.

Page analytics

Rede uses Google Analytics to count visits to rede.care, with its enhanced measurement features on. Google therefore receives the full address of the pages you visit and move between, and the searches you make here. On rede.care an address can include what you searched for, a billing code, the insurance plan you chose, a place, the location you searched from (a ZIP code, a city or map coordinates) and a deductible amount. Google Analytics also records scrolling, clicks on links to other sites, form use and where a visit came from. Google signals and ad personalization are off, and Google Analytics sets its own cookies in your browser to count visits.

Visit counts and error reports

Cloudflare Web Analytics counts visits to rede.care and how fast pages load, without cookies and without following you across sites. When a page fails in your browser, Rede receives the error message, where in the code it happened, the page's path (not what you searched for) and your browser and operating system (for example, Safari 18 on iOS), and keeps them in its server logs.

What you send through the sign-up form on rede.care's home page is stored by Rede with Cloudflare, one of its service providers, and a copy goes to Rede's own inbox. Rede uses it only to confirm your sign-up and to email you about Rede, which you can stop at any time from the link in any of those emails, and never sells or shares it.

Provider assessment requests

When you request a provider assessment, we collect your name, work email and practice name. You may also provide your role, specialty, state, approximate monthly billing-question volume, system names and a note. We use this information to respond to your request. Your request is stored by Rede with a service provider, and a copy goes to Rede's own inbox. We send you a confirmation email when you submit your request. Do not include patient information.

Coverage-options answers

The Coverage Options tool asks questions to help you find a coverage pathway, including about immigration status. Those answers are never sent to our servers. By design, the page makes no network requests, writes nothing to cookies or browser storage, and puts nothing in the URL. Your answers live only in your browser's memory for that page visit, and are gone the moment you close or navigate away from the tab.

Where our pricing data comes from

The prices and facility information we show are built from public CMS (Centers for Medicare & Medicaid Services) datasets and hospitals' own published machine-readable price files, which federal price-transparency rules require hospitals to make public.

We do not sell your data

We do not sell personal data to third parties.

Questions

This is a draft policy for a product still in development. If you have questions about how your information is handled, reach out through the provider portal contact channel.