Privacy Policy
Plain English. We collect the minimum we need to operate the service. We don't sell your data. We don't track you across the web.
Effective: 2026-05-18 · Last updated: 2026-11-14
Change on 2026-11-12: we corrected how account deletion is described. It previously described book and account deletion alike as taking effect on request; it now separates the request, the deletion while it is in progress, and its completion, and names the three records kept after deletion and what each one does. The retention periods and your rights are unchanged. See Data retention.
Change on 2026-10-15: we expanded the account-deletion retention summary below to name every category of record the account-deletion feature actually covers, including decision/outcome-review, research-session, filing-watch and workspace-collaboration records added since this policy was last written. It previously listed a shorter, incomplete set. See Data retention.
Change on 2026-10-14: we corrected where your data is hosted. Our application servers and database are in the United States (Ashburn, Virginia), and filing documents are stored in Finland (Helsinki). This policy previously said all data was hosted in Germany and Finland. See International transfers.
1. Who we are
RateFileAI is operated by RateFileAI, LLC, a Florida limited liability company, as an independent research and intelligence platform for U.S. property & casualty insurance professionals. This policy explains what personal information we collect about you when you visit ratefileai.com or use the service, why we collect it, and your rights.
2. What we collect
| Category | Examples | Purpose |
|---|---|---|
| Account info | Name, email address, company, ZIP code, phone number (company, ZIP and phone are optional profile fields collected at onboarding) | Authenticate you; deliver alerts and digests; reach you about account or service changes |
| Billing info | Payment method (handled by Stripe — we do not see your card number), billing address as provided to Stripe, subscription tier and status | Process subscription payments and confirm your tier |
| Usage analytics | Pages visited, time on page, anonymized IP address, browser/OS family | Understand which features get used; debug issues; improve product |
| Saved preferences | Saved alert scope (carriers/states/LOBs), alert rules you create, email delivery toggles | Deliver the alerts and digests you've configured |
| Saved renewal book (Renewal Defender) | Only if you save a renewal book to your account in the app: the policy rows you upload — which may include a customer name, ZIP, and policy number — plus the renewal-risk scores and talking points we generate from them | Deliver and persist your renewal-defense analysis across sessions, so your filing intelligence and talking points are there when you sign back in. Stored only for your agency; not sold; not used for any other customer; deletable at any time (see §3 and §7) |
| Search history | Filing searches and queries you run | Make the platform faster for you (caching); aggregate, anonymous trend analysis |
| Team workspace and collaboration records | Team membership and roles; decisions, outcome reviews, briefs, tasks, comments and activity you create or take part in inside a shared team workspace | Run shared team workspaces: show who did what and keep the team's shared records intact for its other members |
| Support and referral records | Support requests you send us and their messages; referral clicks and sign-ups | Answer your support requests; count referral clicks and sign-ups |
| Security, deletion and service records | Sign-in and plan-change records, access and document-delivery records, the previous sign-in and deletion records described in §7, replay-protection keys, internal work queues and locks | Keep the service secure and recoverable; stop a deleted sign-in from coming back; honor opt-outs; prove that a deletion was carried out |
The personal information described above covers what we collect about you as a subscriber. The platform separately aggregates and displays publicly available regulatory filing data — including rate filing records, carrier-state-line-of-business data, and state regulatory filing reference identifiers sourced from state insurance departments' public filing systems. That public regulatory data is not personal information of any subscriber and is not covered by this Privacy Policy.
3. What we don't collect
- Insureds' PII we don't need. Our research platform runs on public regulatory filings; using it does not require your customers' personal information. The only personal information about your customers that we process is the portfolio data you choose to upload. It is used solely to power your portfolio-analysis tools — Renewal Defender and the related renewal, retention, leakage, and prospecting views it feeds — and is not shared with or sold to third parties, or combined across customers. The rest of the platform runs on public regulatory filings and requires no customer personal information.
- Saved renewal books (in a paid account) are stored — and you control them. This is the one case where customer data is stored on our servers, and only because you chose to save it. When you save a renewal book to your account, the policy rows, scores, and talking points are stored (in the United States, on our own database server; access is restricted and backups of it are encrypted) so your filing intelligence is there next time you sign in. This data is used only to deliver your own analysis, is not sold, not shared with other customers, and not used to train our AI models or any third-party model. You can delete any saved book — or your whole account — at any time (see Data retention and Your rights).
- Holding rule for uploads. If a RateFileAI surface does not explicitly say it is the public in-browser demo, treat uploaded or saved Renewal Defender books as account data processed server-side for your workspace and retained until you delete the book or account. The original file you uploaded is deleted 90 days after upload; the book itself — the rows, scores and filed-rate context — stays until you delete it.. Demo-only browser parsing does not apply to signed-in upload, save, Team Scorecard, or Revenue-Leakage workflows.
- Credit card numbers, CVV, or full payment data. All payment data is collected and stored by Stripe under their PCI-compliant systems; we receive only a token and subscription status from Stripe.
- Cross-site tracking or third-party advertising cookies. We don't run ads on the platform.
4. How we use your information
- To provide, maintain, and improve the service
- To authenticate you and prevent account fraud
- To send transactional emails (account verification, alerts you've enabled, weekly digest, billing receipts, service announcements)
- To detect abuse (rate-limit anomalies, scraping, credential stuffing)
- To aggregate anonymized product analytics for product decisions
We do not sell your personal information. We do not share your personal information with advertisers. We do not let third parties use our system to track you across other sites.
5. Sub-processors
We use the following third-party services to operate the platform. Each receives only the data necessary to perform its function:
| Provider | Purpose | Data shared |
|---|---|---|
| Clerk | Authentication, session management, user identity | Email, name, hashed password (if used), OAuth tokens (if you sign in with Google) |
| Stripe | Payment processing, subscription management | Email, billing address (collected by Stripe), payment method (handled by Stripe) |
| Plausible | Privacy-friendly product analytics | Anonymized IP, page path, referrer, browser/OS family — no cookies, no cross-site tracking |
| Anthropic (Claude) | Generating genuine AI summaries for some public filing PDFs (server-side, not user-driven) | Excerpts of public filing PDFs only; no user-identifiable content is sent. Anthropic does not use API inputs or outputs to train its models (confirmed by Anthropic's API usage policy and our account-level zero-retention configuration). Your renewal book data is not sent to Anthropic and is not used to train any model. |
| Google Workspace (Gmail) | Internal and transactional email (CEO mailbox, account communications) | Recipient email, message body |
| Resend | Transactional email delivery (account alerts, weekly digest, billing notifications, account lifecycle email) | Recipient email address and message content delivered on our behalf; no persistent storage of content by Resend beyond transient delivery |
| Hetzner | Server and database hosting (United States: Ashburn, Virginia); filing-document storage (Finland: Helsinki) | Application data at rest and in transit |
| 2Captcha | Automated processing of publicly available challenge-response prompts encountered when accessing public regulatory portals (does not touch user data) | Public challenge-response data from regulatory portals — no user data |
6. Cookies
We use cookies only for:
- Authentication (Clerk session cookies) — strictly necessary; the service can't function without these
- CSRF protection — strictly necessary
We do not use advertising cookies, social-media tracking pixels, or third-party analytics cookies. Our analytics (Plausible) is cookieless — it sets no cookies and stores no identifier on your device. Your browser's local storage is used only for functional preferences you set yourself (such as saved favorites) and is not shared with third parties.
Because the only cookies we set are strictly necessary for the service to function, and our analytics operates without cookies or persistent identifiers, no cookie-consent banner is required — strictly necessary cookies are exempt from consent requirements under applicable privacy law (including the EU ePrivacy Directive). If we ever introduce non-essential cookies, a consent mechanism will be added before non-essential cookies are set.
7. Data retention
- Account data: kept while your account is active. On deletion, your profile, uploaded books and policies, scores, alerts and saved searches, queued work, and any decision, outcome-review, research-session, filing-watch or workspace-collaboration records tied to your account are deleted or, where the record also belongs to another customer's workspace, kept with your name removed from it. Billing records are retained separately as described below. Account settings → Delete account → “What’s deleted and what we keep” lists every category by name, including the small number of records kept on purpose and why.
- Billing records: retained at least as long as applicable U.S. tax law requires (typically 7 years). After you delete your account the billing history is kept without your identity, with no scheduled deletion date; the table below says so record by record.
- Saved renewal books (Renewal Defender): kept until you delete the book or your account; there is no fixed time limit while a book is saved. Deleting a single book in the app removes it, with its policies, scores and talking points, when you delete it; deleting your whole account removes your books as part of the account deletion described below
- Original uploaded files (Renewal Defender source CSVs): deleted 90 days after upload. This is the raw file you uploaded, not your book — the rows, scores and filed-rate context derived from it are kept under the line above until you delete the book or your account.
- Backups: encrypted backups are retained offsite for 30 days, and four weekly full database base backups are kept for disaster recovery. Data you delete may therefore persist inside a backup for up to 30 days after deletion, after which the backup containing it is pruned automatically. Backups exist to restore the service after a failure, not to look up individual records.
- Operational data (including email delivery logs and product analytics): retained for the period necessary to fulfil the purpose for which the data was collected, consistent with our documented data-retention schedule.
- Server access logs (Caddy web server): our web server records structured access logs that include your IP address, the URL path requested, HTTP status code, timestamp, and browser/client information for each request to ratefileai.com and api.ratefileai.com. These logs are retained for 90 days on a rolling basis (older entries are automatically overwritten). Purpose: security monitoring, abuse detection, and forensic investigation of unauthorized access or service incidents. The logs are stored on our Hetzner servers in the United States (Ashburn, Virginia), are not shared with third parties except as required by applicable law, and are not used for marketing or analytics profiling. IP address constitutes personal data under GDPR; if you wish to exercise a right of access, erasure, or restriction with respect to these logs, contact us at the address below (note that erasure of specific IP records from rolling logs may not be technically feasible, in which case processing will be restricted).
You can request deletion of your account and personal data at any time, from Account settings → Delete account or by emailing us at the address below; requests are processed within 30 days unless we are required to retain data for legal compliance.
Account deletion happens in three distinct stages. Request: you ask for it in Account settings or by email. In progress: the deletion runs in the background, your account settings show that it has started, and your sign-in keeps working until it finishes. Complete: your account settings show that it has finished, your old sign-in stops working and cannot be restored, and your saved work and billing access are not recovered. After completion you may create a new, separate account with the same verified email.
After deletion we keep three separate records about the deletion itself, each for one purpose. Every other record we keep, and every record we delete, is listed in the table that follows:
- Prior-identity block: your old sign-in identifier and verified email, kept so the deleted identity cannot quietly reappear. It stops anyone signing in as the old identity, and stops the email being reused while deletion is pending or unresolved. It does not stop a new, separate account with the same email once deletion is complete.
- Do-not-contact record: kept only if you opted out of marketing email, so we keep honoring that opt-out. It suppresses marketing email; it does not block sign-in or a new account.
- Deletion audit record: an entry showing that a deletion was carried out. It carries no name, email or sign-in identifier.
What account deletion removes and what we keep
This is the same list Account settings shows under “What’s deleted and what we keep”, grouped by the categories in section 2, with each group’s purpose. Backups and server logs follow the rules in the last two rows.
| Category | What happens when your account is deleted | How long it is kept | Detail |
|---|---|---|---|
| Account info — Authenticate you; deliver alerts and digests; reach you about account or service changes | |||
| API keys and integrations | Deleted | Deleted when your account deletion completes | |
| Do-not-contact record | Kept, still naming you | No scheduled end | Your email address is kept on a do-not-contact list so the system continues to suppress messages covered by your opt-out. This is separate from sign-in and does not prevent a new account. Deleting the suppression would allow contact covered by the opt-out to resume. |
| Email and lifecycle history | Deleted | Deleted when your account deletion completes | |
| Marketing subscription | Deleted | Deleted when your account deletion completes | |
| Profile and login | Deleted | Deleted when your account deletion completes | |
| Billing info — Process subscription payments and confirm your tier | |||
| Billing and subscription records | Deleted | Deleted when your account deletion completes; billing history is kept separately (see Billing history) | |
| Billing history (de-identified) | Kept without your identity | No scheduled end; kept without your identity. U.S. tax law requires billing records for typically 7 years, and we set no earlier deletion date | Add-on billing history is kept for accounting; your email and Stripe identifiers are removed. Billing change history is kept for accounting; the address identifying you is replaced. |
| Team billing link | Kept without your identity | No scheduled end; kept without your identity | If you were the billing owner of a team that other members still use, the team's billing link is kept so the team survives; your reference as owner is removed. |
| Usage analytics — Understand which features get used; debug issues; improve product | |||
| Product analytics | Kept without your identity | No scheduled end; kept without your identity | Product usage counts are kept; the row no longer points to you. Signup and activation counts are kept; your identity is replaced by a one-way token. |
| Saved preferences — Deliver the alerts and digests you've configured | |||
| AI research sessions and signal watches | Deleted | Deleted when your account deletion completes | |
| Alerts, watchlists and saved searches | Deleted | Deleted when your account deletion completes | |
| Historical alerts snapshot | Kept, still naming you | Expires with the 30-day backup cycle | A pre-change snapshot of alerts from a specific data-repair event. It is not exported or looked up per customer; it expires under the standard backup retention cycle. |
| Queued and scheduled work | Deleted | Deleted when your account deletion completes | |
| Saved renewal book (Renewal Defender) — Deliver and persist your renewal-defense analysis across sessions, so your filing intelligence and talking points are there when you sign back in. Stored only for your agency; not sold; not used for any other customer; deletable at any time (see §3 and §7) | |||
| Renewal scores and talking points | Deleted | Deleted when your account deletion completes | |
| Uploaded book and policy data | Deleted | Deleted when your account deletion completes; the original uploaded file is deleted 90 days after upload even if you never delete your account | |
| Search history — Make the platform faster for you (caching); aggregate, anonymous trend analysis | |||
| Search history | Deleted | Deleted when your account deletion completes | |
| Team workspace and collaboration records — Run shared team workspaces: show who did what and keep the team's shared records intact for its other members | |||
| Comments and reviews on shared records | Kept without your identity | No scheduled end; kept without your identity | A comment you posted on a brief belonging to a different customer's workspace is kept as that brief's record; your identity is replaced by the same "Deleted user" placeholder used for decisions and outcome reviews. A review action you performed, or a reviewer assignment naming you, on a brief belonging to a different customer's workspace is kept as that brief's history; your identity is replaced by the same placeholder. |
| Decisions, outcome reviews and workspace briefs | Deleted | Deleted when your account deletion completes | |
| Team activity log | Kept without your identity | No scheduled end; kept without your identity | A team activity event you triggered, or that named you (an invite, a role change, a removal), is kept as that team's history for the other members; your identity and the hashed reference to an invited email are removed. |
| Workspace and organization membership | Deleted | Deleted when your account deletion completes | |
| Workspace and task activity | Kept without your identity | No scheduled end; kept without your identity | A workspace notification you triggered is kept for the other recipients who were notified; the actor reference is cleared. A checklist item you owned or created inside a surviving task is kept; the owner and creator references are cleared. A task status-change event you triggered is kept as the task's history; the actor reference is cleared. An activity-feed entry you triggered inside a workspace that survives you is kept so other members retain that history; the actor reference is cleared. A comment you posted inside a workspace that survives you is kept for the team; your identity is replaced by the placeholder. |
| Workspace and task ownership | Kept without your identity | No scheduled end; kept without your identity | A task you requested inside a workspace that survives you is kept for that workspace's record, with your reference as requester replaced by the placeholder; an assignment or approval naming you is cleared instead. Ownership of a workspace you created that other teammates still use is reassigned to the "Deleted user" placeholder so the workspace survives for them. |
| Support and referral records — Answer your support requests; count referral clicks and sign-ups | |||
| Referral records | Kept without your identity | No scheduled end; kept without your identity | Referral clicks and signups are kept as counts, with your link to them removed. Records naming someone who invited you, or whom you invited, belong to that person and are left intact. |
| Support history | Kept without your identity | No scheduled end; kept without your identity | Support cases are kept as a service record. Your email address, login id and owner reference are removed. Anything you typed into the message itself is NOT removed — if you included personal details in a support message, they stay in that record. A message you posted on a teammate's support request inside your organization is kept as part of that request's record; your identity is removed. Anything you typed into the message itself is NOT removed. |
| Security, deletion and service records — Keep the service secure and recoverable; stop a deleted sign-in from coming back; honor opt-outs; prove that a deletion was carried out | |||
| API request de-duplication keys | Deleted | Deleted when your account deletion completes | |
| Access and audit records | Kept without your identity | No scheduled end; kept without your identity | Records of which data was accessed are kept as an audit trail, with your identity replaced by a one-way token. Records of which filing documents were delivered to you, and whether delivery completed or was interrupted, are kept as dispute evidence, with your identity replaced by a one-way token. |
| Deletion record | Kept without your identity | No scheduled end | A record that a deletion completed, with counts and a hashed agency reference. It carries no name, email or login id. |
| Internal backup lock | Kept without your identity | Until the backup upload finishes | An internal lock that keeps two database backup uploads from running at once. Its actor field names the backup host or operator, never a customer, so it holds nothing about you. |
| Internal filing workflow | Kept, still naming you | No scheduled end | An internal queue recording which login asked for a filing to be analysed. The filing work is the product's own record, not your data; only the authorship stamp refers to you. Filing update records carry the login that created them, as provenance for regulatory filing work. The filing content is the product's record. |
| Pre-migration table copies | Kept, still naming you | Removed within 30 days of account deletion | A June 2026 pre-migration copy of the users table. It holds the login id and email of the accounts it copied, so it still names you until its row for your account is removed, within 30 days of your account deletion. A June 2026 pre-migration copy of the subscriptions table. A June 2026 pre-migration copy of marketing subscribers. A June 2026 pre-migration copy of lifecycle events. |
| Previous sign-in and deletion record | Kept, still naming you | No scheduled end | This record keeps the previous sign-in id and email so the old account cannot be restored and an unfinished deletion stays blocked. After deletion completes, a distinct new sign-in may use the same verified email to create a separate account. The new account does not inherit the old account's saved data or billing access. It also holds per-step evidence that deletion ran to completion. The separate hashed deletion audit below contains no name, email, or login id. The sign-in id and email are kept as they are, not replaced by a one-way token, because the check that stops the old account returning compares them directly. |
| Replay-protection keys | Kept, still naming you | Until the key expires, then swept automatically | Short-lived replay-protection keys stamped with the sign-in that made the request. Expired keys are swept automatically. Operational de-duplication keys for decision outcomes; they carry no customer content. |
| Sign-in and plan change records | Kept, still naming you | No scheduled end; kept after account deletion and not removed today | A security record that your sign-in identity was moved to a new login for the same verified email (the old and new login ids, when, and the checks that allowed it). The deletion process does not remove it today. RateFileAI's record of a plan or team-seat change its audit tooling applied to an account, kept so the change can be checked and reversed exactly. It names the account and its email. The deletion process does not remove it today. |
| Backups (all categories) | Applies to every category above | Encrypted backups are kept for 30 days; data you delete may remain inside a backup for up to 30 days, then the backup is pruned automatically | |
| Server access logs (all categories) | Applies to every category above | Kept for 90 days on a rolling basis; individual IP records cannot be erased from rolling logs, so processing is restricted instead | |
These retention periods follow a documented data-retention schedule, and deletion requests are fulfilled under a documented deletion procedure (aligned to CCPA/CPRA and GDPR Article 17) within the timeline above. Business customers can review the per-category processing and retention summary in our Data Processing Addendum (Schedule A).
8. Your rights
Subject to applicable law, you have the right to:
- Access — request a copy of the personal information we hold about you
- Correct — fix inaccurate personal data; you can update most of this directly from your account page
- Delete — request deletion of your account and associated data
- Object / restrict — opt out of non-transactional emails; you can also disable specific alert categories from your account page
- Portability — request your data in a portable format
- Withdraw consent — at any time, by deleting your account
8a. Your U.S. state privacy rights
Depending on your state of residence, you may have additional rights under your state’s consumer-privacy law — including California (CCPA/CPRA), Virginia (VCDPA), Colorado (CPA), Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Indiana, Kentucky, and Rhode Island. Subject to your state’s law, these may include the right to confirm whether we process your personal data and to access it; to correct inaccuracies; to delete it; to obtain a portable copy; and to opt out of the “sale” of personal data, “targeted advertising,” or certain “profiling.” We do not sell your personal data, we do not share it for cross-context behavioral or targeted advertising, and we do not use it for profiling that produces legal or similarly significant effects — so for most residents these opt-out rights have no applicable processing to suppress.
Opt-out preference controls. Because we do not sell or share personal data or process it for targeted advertising, browser opt-out preference controls such as Global Privacy Control (GPC) have no applicable processing for us to suppress; we honor the no-sale / no-targeted-advertising posture above for all visitors regardless of signal.
How to exercise / verification. Email info@ratefileai.com. We verify requests against account information on file and respond within the timeframe your state’s law requires (generally 45 days, extendable once where permitted). You may use an authorized agent where your state’s law allows.
Right to appeal. If we decline your request, you may appeal by replying to our decision email; we respond within the period your state’s law requires (typically 45–60 days). If your appeal is denied, you may contact your state Attorney General.
Non-discrimination. We do not discriminate against you for exercising any of these rights.
9. Security
We use industry-standard security measures: TLS everywhere, encrypted backups (the live database disk itself is not yet encrypted at rest; that work is scheduled), hashed-not-stored credentials (via Clerk), short-lived authentication tokens, principle-of-least-privilege access controls internally. No system is 100% secure; affected users are notified without undue delay if a breach involving personal information occurs.
10. International transfers
Our application servers and database are located in the United States (Hetzner — Ashburn, Virginia); filing documents are stored in Finland (Hetzner — Helsinki). Your account information is stored in the United States, and several of our service providers listed above are also based there. If you access the service from outside the United States, your personal information will be transferred to and stored in the United States. We rely on standard contractual clauses and equivalent legal mechanisms where required.
11. Children
RateFileAI is a B2B service intended for licensed insurance professionals. It is not directed at children under 16, and we do not knowingly collect personal information from children.
12. Changes to this policy
We may update this policy from time to time. Material changes will be communicated by email or by prominent notice in the product. The "Last updated" date at the top of this page reflects the current version.
13. Contact
For privacy questions, deletion requests, or any data-rights exercise: