1. Executive Plain-English Summary
The Bottom Line: ClaimHive Inc. ("ClaimHive", "we", "our") is designed specifically for licensed USA Public Adjusters. We do not sell your personal information, monetize your client lists, broker leads to third parties, or train public AI foundation models on your claim documentation. Your files belong exclusively to your firm and your clients.
We operate under the fundamental understanding that property claim documentation—including fee agreements, proof of loss filings, estimates, expert causation reports, and carrier correspondence—constitutes sensitive, often legally privileged work product. This policy explains clearly and without obscure legal jargon how we handle and protect that information.
2. Information We Collect
We only collect data necessary to provide and secure the ClaimHive operating system:
- Account & Adjuster Credentials: Full name, firm name, state adjuster license number(s), work email address, phone number, and seat allocation counts.
- Billing & Payment Information: Payment processing is handled directly via PCI-DSS Level 1 compliant processors (Stripe). We do not store raw credit card numbers or bank account passwords on our servers.
- Claim Work Product (Uploaded by You): Insurance policies, declaration pages, scope notes, inspection photos, repair estimates, statutory notices, and client contact details entered into your firm's workspace. Each firm's data is separated at the database level for firm users.
- Operational Audit Logs: Tamper-evident audit logs, login timestamps, IP addresses, and document action events used for security and regulatory compliance.
3. How We Use Your Information
Your information is used strictly to power your firm’s operations:
- Executing file docketing, automatic policy limits extraction, and photo sorting.
- Calculating and monitoring state-specific statutory deadlines (e.g., 60-day Proof of Loss statutory clocks).
- Generating pre-drafted carrier letters and scheduling the daily Next Action morning docket.
- Providing policyholders with a private, read-only status view of their ongoing claim.
- Diagnosing software bugs, preventing malicious access, and verifying system uptime.
What we will NEVER do: We will never sell, lease, or distribute your claim files, policyholder contact info, or estimate line items to insurance carriers, lead brokers, roofing contractors, or marketing aggregators.
4. AI Processing & Model Training
Privileged Work Product Clause: ClaimHive does not use customer claim documents, estimates, photos, or messages to train public AI models or models shared across firms.
Some features (for example, sorting email, drafting replies, and reading documents) send content, including email content, to Fireworks AI through our LiteLLM proxy so the model can return a result. Fireworks processes the content under its own terms; we do not make a retention guarantee on its behalf. AI requests and responses may be logged for debugging by our observability provider, Langfuse.
5. Data Sharing & Third-Party Infrastructure
We use the following service providers to run ClaimHive:
- File Storage & Authentication: Firebase Authentication (for sign-in). Uploaded files and filed attachments are stored with Firebase Storage or local server storage.
- Database & Application Hosting: Cloud infrastructure providers. Data is encrypted in transit using TLS; Google OAuth tokens are encrypted with AES-256-GCM.
- Billing Gateway: Stripe Inc. for encrypted payment transactions.
- SMS & Calls: Twilio, for policyholder and adjuster text messages and calls.
- Email: Google (Gmail API), when you connect a Gmail account.
- AI Models: Fireworks AI, reached through our LiteLLM proxy (see Section 4).
- AI Observability: Langfuse, which may log AI requests and responses for debugging.
- Error Monitoring: Sentry, which receives application error reports.
Subpoenas & Legal Process: In the event that ClaimHive receives a court order, administrative subpoena, or regulatory demand requesting customer files, we will promptly notify your firm administrator unless prohibited by applicable law, enabling you to assert appropriate work-product privileges or file protective motions.
6. Analytics & Cookies
This public website loads two analytics tools so we can see which pages are useful and whether the site is working. We do not sell this information, and we do not load advertising pixels. These tools run on claimhive.app. They are separate from the claim files inside a firm workspace.
- Google Analytics 4. We load Google’s gtag.js library. It records page views (the page address and title) and a few actions: viewing the pricing page, and submitting the access request form. A request submission can include the firm name, seat count, cohort, and referral text you entered. Google Analytics sets cookies to tell browsers apart and collects standard technical details that come with that script, such as browser, device, and approximate location. We use it to understand traffic on this site. We do not use it to run ads.
- Microsoft Clarity. We load Clarity’s script. Clarity records how visitors use public pages — clicks, scrolling, and mouse movement — and turns that into session recordings and heatmaps so we can see where the layout is confusing. The same page-view and form actions above are also sent to Clarity as event names. Clarity sets its own cookies. By default, the Clarity script masks text typed into form fields. We use it to improve the site, not to sell visits.
How to opt out: You can block cookies and scripts in your browser settings. You can install the Google Analytics Opt-out Browser Add-on. You can also use an ad blocker or privacy extension that blocks requests to googletagmanager.com and clarity.ms. Blocking those requests stops both tools on this site.
7. Ownership & Export
You own your data. To request a copy of your firm's data, contact privacy@claimhive.app.
8. State Insurance Department Compliance Alignment
Our platform controls and data audit mechanisms are structured to support Public Adjuster compliance under state insurance regulatory frameworks, including the Florida Office of Insurance Regulation (OIR), the Texas Department of Insurance (TDI), the Georgia Insurance and Safety Fire Commissioner, and corresponding regulatory bodies across all 50 states.
9. Contact & Data Protection Escalation
If you have any questions, wish to execute a custom Business Associate or Confidentiality Agreement, or need immediate assistance regarding claim file custody:
10. Google User Data
This section explains what ClaimHive does with information it gets from Google when you sign in with Google or connect a Gmail account. It adds to the rest of this policy. Where they differ, this section controls for Google user data.
What we access
- Google sign-in. When you sign in with Google, we ask for your basic profile: your name, email address and profile picture (scopes
openid, userinfo.email, userinfo.profile). We use this only to create and sign in to your ClaimHive account.
- Gmail (optional). If you choose to connect a Gmail account, we ask for the following scopes:
gmail.readonly — reads your email messages, threads, attachments, and send-as settings. ClaimHive uses it to show your email inside ClaimHive, match messages to claims and leads, and file attachments into claim documents.
gmail.compose — creates, updates, deletes, and sends drafts. ClaimHive uses it to prepare reply drafts for you to review.
gmail.send — sends email on your behalf. ClaimHive uses it to send the emails and replies you choose to send.
userinfo.email — accesses the email address of the connected account. ClaimHive uses it to identify which mailbox is connected.
How we use it
We use Gmail data only to provide the email features you see in ClaimHive:
- show your email inside ClaimHive and open threads and attachments;
- match an email to a claim or a lead, add the sender as a contact, and file attachments into the claim's documents;
- prepare reply drafts for you to review, and send the emails and replies you choose to send;
- keep the connected mailbox in sync so new claim email appears in ClaimHive.
To match and sort email and to prepare drafts, ClaimHive sends parts of a message (sender, recipients, subject, date, up to the first 3,000 characters of the body, and attachment names) to Fireworks AI through our LiteLLM proxy. Fireworks processes the content under its own terms; we do not make a retention guarantee on its behalf. AI requests and responses may be logged for debugging by our observability provider, Langfuse. We do not use Gmail data to train generalized AI models. We do not use Gmail data for advertising.
What we store
- Your Google access and refresh tokens, encrypted with AES-256-GCM.
- For email ClaimHive processes: the Gmail message and thread IDs, sender, recipients, subject, date, a short snippet of the body, the matched claim or lead, and the result of the AI sorting.
- Email you link to a claim is saved in the claim's communication history, including the message text. Attachments you file to a claim are saved as claim documents.
- Drafts you create in ClaimHive and their Gmail draft IDs.
- Uploaded files and filed attachments are stored with Firebase Storage or local server storage.
We keep Gmail data for up to 90 days, except emails you link to a claim or lead, which are kept as part of that record until you delete it or ask us to. You can ask us to delete your data at any time by emailing privacy@claimhive.app.
Who we share it with
We do not sell Google user data. We do not share it with advertisers, data brokers or information resellers, and we do not use it to decide credit or lending. Google user data is shared only:
- within your firm's ClaimHive workspace, with the users who have access to the claim, lead or shared mailbox;
- with the service providers listed in Section 5 (file storage, hosting, and the AI proxy and AI model subprocessors), only to provide the features you use;
- when the law requires it, to protect security, or as part of a merger or sale of the business with your prior consent.
Our policy is that ClaimHive staff do not read customers' email content.
Disconnecting and deleting
Limited Use
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Learn more in Google's Google Workspace API User Data and Developer Policy.
See the Google API Services User Data Policy.