Privacy Policy
Last updated: November 2, 2026
This Privacy Policy describes how Tilden Software LLC ("we", "us", or "our") collects, uses, and shares information when you visit our website, create an account, subscribe to a paid plan, or use our API (together, the "Service"). It explains what we collect, why, and the choices available to you. If you do not agree with these practices, please do not use the Service.
1. Information we collect
Information you provide
- Account information. When you register we collect your name, email address, and authentication credentials (a hashed password or passkey public key). We never store plaintext passwords.
- Billing information. Payments are processed by Stripe, our payment processor. We do not receive or store full payment card numbers. We retain billing records such as your plan, invoices, billing address, and the last four digits and brand of your card as provided to us by Stripe.
- Your workspace. When you're signed in, we keep what you put in your workspace—bookmarked codes, tracked localities, and saved calculations—and your recent calculations: the inputs of each calculation you run and the result we showed, so you can return to them without saving. We keep your 50 most recent. You can remove any of them from your workspace, and they are deleted with your account. Because they are part of the product rather than measurement, the measurement opt-out does not turn them off.
- Alert preferences. If you sign up for rate-change alerts, we collect the email address and preferences (for example, a specialty filter) you provide.
- Waitlists. If you join a waitlist, we collect your email address and the answers you give on the form, such as your role, organization size, specialty, ZIP code, the insurers you're interested in, and what you'd use the product for.
- Communications. If you contact us, we keep the correspondence and any information you choose to include in it.
Information collected automatically
- API usage records. We log API requests, including the endpoint, the parameters you send (such as procedure codes, localities, and dates of service), the API token used and who created it, the time, and the response we returned. We use these records to meter usage, enforce rate limits, bill correctly, prevent abuse, and improve the Service, and to catch mistakes in our answers so we can tell you about them.
- Server logs. Like most websites, our servers record technical information such as IP address, browser type, requested pages, and timestamps.
- Cookies. We use essential cookies for sign-in, security, and session management. After you sign in, our product analytics provider (Mixpanel) may set a first-party cookie. On public pages we set one other cookie, which records the first page you visited and the site that referred you; we read it only if you create an account, to note how you found us, and it expires after 60 days. If you turn off measurement, a cookie remembers that choice. We do not use advertising or cross-site tracking cookies.
- Analytics. We use Fathom Analytics, a privacy-focused analytics service that does not use cookies or track visitors across sites, for aggregate traffic statistics. Public marketing, tool, sign-in, and registration pages do not initialize Mixpanel or send Mixpanel browser events. Mixpanel receives server-side account milestones and reviewed interactions inside the authenticated product; autocapture, automatic pageviews, and session replay are disabled there.
- Traffic measurement. We measure how public pages are used in aggregate, using request statistics from our network provider (Cloudflare), short-lived server records, and limited signals from your browser—for example, whether a page loaded, roughly how long it was visible and how far it was scrolled, which sections were viewed, and whether a tool was completed. These signals never include full URLs, query strings, or anything you type; they store no identifier in your browser; and they are not linked to your account. Your IP address and browser details are used briefly to derive a same-day pseudonymous key for counting daily visitors, then discarded. We keep only aggregate totals, such as views by page type or by code, not individual visits.
- Product activity log. Separately, we keep a log of how the product is used—for example, running the fee calculator, copying a result, or asking a question through the "Ask" box. Unlike traffic measurement, this log can include what you entered or looked up, such as the text of a question or the codes, dates of service, and amounts in a calculation, along with the page it happened on (never the page's query string). To group this activity, your browser keeps two random identifiers, neither a cookie nor derived from your IP address or device: one for the current visit, and one that tells us whether you have visited before. The second resets after 90 days without a visit, and turning off measurement deletes it. If you sign in, earlier activity from the same browser may be linked to your account. We also note how each visit began: the page you arrived on, the site that linked you there (its domain only), and any campaign tags in that link. When you use one of our calculators, the log also keeps what you entered and the result we showed you, tied to your account if you're signed in. That way, if we find a mistake in a result, we can tell the people who received it. On Charge Check and Contract Check, you can select “Don't save this check” to leave that check out of the log. We use this log to understand and improve the product, to diagnose problems, and to make sure our results are right. It honors the opt-out choices described below, and we keep it for no longer than twelve months. When you delete your account, we delete the activity associated with it.
2. Protected health information—do not submit it
The Service is a fee-schedule data tool. It works with procedure codes, localities, dates, and dollar amounts—it does not need, and is not designed to receive, patient information. Do not submit protected health information (PHI) or any patient-identifying information to the Service, including in API requests, calculator inputs, or support messages. We are not a "covered entity" or "business associate" as defined by HIPAA, we do not enter into Business Associate Agreements, and the Service must not be used to store or transmit PHI. Free-text fields such as the "Ask" box are stored and read by our staff, so treat them like an email to us. If we become aware that PHI has been submitted, we may delete it without notice.
3. How we use information
- To provide, operate, and maintain the Service, including authenticating you and responding to API requests.
- To meter usage, enforce plan limits, and process payments and invoices.
- To send transactional emails (account verification, receipts, security notices). If you opted in, we also send rate-change alerts and product updates, which are occasional announcements and requests for feedback. If you joined a waitlist, we email you when what you signed up for is ready and may ask you about what you need. Every non-essential email includes a way to unsubscribe.
- To secure the Service, prevent fraud and abuse, and enforce our Terms of Service.
- To understand aggregate usage and improve the Service.
- To review individual product interactions recorded in the product activity log so we can diagnose problems, answer questions you submit, and decide which features to build.
- To comply with legal obligations, such as tax and accounting requirements.
We do not sell your personal information, and we do not share it with third parties for their own advertising or marketing purposes.
4. How we share information
We share personal information only in the following circumstances:
- Service providers. With vendors who process data on our behalf and only as needed to run the Service—for example, Stripe (payments), our hosting and infrastructure providers, our transactional email provider, Fathom Analytics, and Mixpanel (product analytics). These providers are bound by their own contractual and legal obligations regarding your data.
- Legal requirements. When we believe in good faith that disclosure is required by law, regulation, legal process, or an enforceable governmental request, or to protect the rights, property, or safety of Tilden Software LLC, our users, or the public.
- Business transfers. In connection with a merger, acquisition, financing, or sale of assets, in which case we will notify you before your personal information becomes subject to a different privacy policy.
- With your consent. In any other case, only with your direction or consent.
5. Data retention
We keep account information for as long as your account is active and for a reasonable period afterward. We keep billing records for as long as required by tax, accounting, and other legal obligations. Server logs and API usage records are retained for a limited period for security, metering, and billing-dispute purposes and are then deleted or aggregated. You may request deletion of your account at any time (see "Your rights" below); some records may be retained where the law requires or permits it.
Traffic request staging is deleted two hours after successful aggregation and always within 24 hours. Compact daily summaries used to finalize unique counts are deleted the next day and always within 30 hours. Aggregate traffic statistics may be retained to compare trends; they contain no IP, daily pseudonymous key, pageview identifier, or individual timeline.
Product activity log records are deleted automatically twelve months after they are recorded. When you delete your account, we delete the product activity associated with it, including activity from before you signed in. We may keep information that no longer identifies you.
6. Security
We use reasonable technical and organizational safeguards to protect your information, including encryption in transit (HTTPS), hashed credentials, scoped API tokens, and access controls. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for keeping your password, passkeys, and API tokens confidential.
7. Your rights and choices
Depending on where you live, you may have rights under applicable privacy laws (such as the EU/UK GDPR or the California Consumer Privacy Act), including the right to access, correct, export, or delete your personal information, to object to or restrict certain processing, and to not be discriminated against for exercising these rights. We honor such rights as required by the laws that apply to you.
To exercise any of these rights, email us at [email protected]. We will verify your request and respond within the time required by applicable law. You can also update account details and unsubscribe from alerts directly in the Service. If you are in the EEA or UK, you may also have the right to lodge a complaint with your local supervisory authority.
You can turn off first-party traffic measurement and the product activity log for your browser at any time through Privacy Choices. We also treat Global Privacy Control and Do Not Track signals as objections to both automatically.
8. International transfers
The Service is operated from the United States and information we collect is processed and stored in the United States, which may have data-protection laws different from those in your jurisdiction. By using the Service, you understand that your information will be transferred to and processed in the United States.
9. Children
The Service is a professional tool intended for adults. It is not directed to children under 16, and we do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.
10. Third-party links
The Service links to third-party sites (for example, CMS.gov). We are not responsible for the privacy practices of those sites, and this policy does not apply to them.
11. Changes to this policy
We may update this policy from time to time. We will post the updated policy on this page and revise the "Last updated" date above. For material changes, we will provide additional notice, such as an email to account holders or a prominent notice in the Service, before the change takes effect.
12. Contact us
Questions about this policy or our data practices? Email [email protected].
See also our Terms of Service.