This policy explains exactly what ClaimsGap collects, why, who it is shared with, and how to get rid of it. It is written to be read, not to be survived. Insurance claim data is sensitive, so this one is more specific than most.
ClaimsGap is operated by Blue Tide Exteriors LLC, 1780 E. Bert Kouns Industrial Loop, Suite 907, Shreveport, LA 71105, United States.
ClaimsGap is used by contractors, and most of what goes into it is somebody else’s information — the homeowner’s name, their address, their claim, photographs of their damaged property. This policy covers both: the contractor whose account it is, and the homeowner whose claim is in it.
- What we collect
- Photographs of property
- Why we collect it
- Reading an estimate with AI
- Gmail correspondence
- Homeowner share pages
- What stays on your phone
- Email, calendar, reminders and dictation
- Automated follow-up (not active)
- Who we share data with
- How long we keep it
- Security and isolation
- If you are the homeowner
- Your rights
- Visiting this website
- Children
- Changes to this policy
- Contact
1. What we collect
Everything below is either something you typed into the app, something you photographed or scanned, or something you explicitly connected. There is no hidden collection: ClaimsGap contains no analytics, no advertising SDK, no crash reporter and no tracking of any kind — not a single event is logged about how you use the app.
| Category | What it is |
|---|---|
| Account | Your email address and a password, held by our authentication provider as an encrypted hash. We never store your password in readable form. We do not ask for your name, phone number or company at signup. |
| The property and the people | The homeowner or insured’s name, the loss address, and where you enter them, the homeowner’s email address and phone number. |
| Claim identifiers | The carrier name, the carrier claim number, and the type of loss. Where a mortgage company is involved, the servicer’s name, contact name, email, phone and the loan number. |
| Policy numbers | We do not collect these. There is no policy-number field anywhere in ClaimsGap, by design — the claim number is what the app actually needs. |
| Adjuster details | The adjuster’s name, email address and phone number, as you enter them. |
| Money | Carrier replacement-cost value, your contract total, depreciation, approved amounts, recovered depreciation, and the amount and stage of insurance checks — including whether one needs mortgage endorsement. |
| Scope and gaps | Line items detected on the carrier estimate, and each gap finding: its category, rationale, dollar amount, trade code and any statutory or code citation attached to it. |
| Correspondence you send | The full text of follow-up letters and demand letters generated in the app, with their subject line, recipient and CC addresses, and when they were sent. |
| Notes, tasks and calls | Free-text notes on a claim, task titles and due dates, and call-log entries — the contact’s name and your written summary of the conversation. |
| Documents | For each photograph or PDF you attach: its file name, its label, its kind and when it was added. The file itself is not uploaded — see section 2. |
| Gmail connection | If you connect Gmail: the refresh and access tokens Google issues, and the address of the connected Google account. See section 5. |
We do not collect your location, your contacts, advertising identifiers, your browsing activity, or any usage analytics. We do not use tracking cookies. We do not sell data to anyone, ever, and there is nobody we could sell it to — there are no advertising or data partners in this product.
2. Photographs of property
Damage photographs and imported PDFs are stored on your device only, in the app’s own storage. The image bytes are never uploaded to our servers. What syncs to the cloud is the file’s name, label, type and date — a record that a photo exists, not the photo.
Photographs of a damaged home are sensitive in a way a line item is not: they show where somebody lives, the condition it is in, and sometimes their possessions. Keeping them off our servers is a deliberate choice, and it has a consequence you should plan for — if you lose the phone or delete the app, we cannot restore them.
Two details about photo metadata, stated plainly because they cut in opposite directions:
- Photos you take in the app carry no location. ClaimsGap never asks for location permission and never attaches GPS coordinates. The camera photo does keep ordinary EXIF data — capture time, device model, exposure settings.
- Photos you import from your library are stored exactly as they are. If that file already carries GPS coordinates from whatever took it, that stays in the file. We do not strip it. Since the file never leaves your device, that metadata does not reach us — but it will travel with the photo if you attach it to something and send it.
Photographs leave the device only when you send them: embedded as photo exhibits in a supplement package PDF you email, or shared through the iOS share sheet. At that point they go wherever you sent them, through your own email account or messaging app, and this policy no longer controls what happens to them.
3. Why we collect it
- To run your account — authenticate you, and keep your claims separate from every other contractor’s.
- To find scope gaps — the detected line items are compared against a gap library for your trade to produce the findings.
- To run the deadline clock — the property’s state, taken from the address, determines which prompt-pay statute applies.
- To organise adjuster correspondence — the adjuster’s email address and the claim number are what match a Gmail thread to the right claim.
- To produce the documents you send — supplement packages, follow-up letters, demand letters and call recaps are built from the claim file.
- To keep the homeowner informed — the status page is built from a subset of the claim, described in section 6.
We do not use your claim data to train any AI model, we do not pool it across customers, and we do not build a benchmark or an industry dataset out of it.
4. Reading an estimate with AI
When you scan a carrier estimate rather than typing it in, ClaimsGap sends an image of that page to an AI model so it can read the fields off it. The model used is Anthropic’s Claude, reached through a third-party API gateway.
Be clear about what that image contains: it is a picture of an insurance document, and it typically shows the insured’s name, the loss address, the carrier, the claim number, the replacement-cost value and the depreciation. The prompt asks the model to extract exactly those fields. Nothing else from your account — your login, other claims, your photographs, your Gmail — is sent with it.
Scanning is a shortcut, not the only way in. Every field the scanner fills can be typed by hand on the same screen. If a particular estimate should not go through an AI service, enter it manually and no image is sent anywhere.
The extracted values land in an editable form for you to correct before they become part of the claim. AI extraction can misread a number or miss a field, so check it.
5. Gmail correspondence
Connecting Gmail is optional and the app works without it. If you connect it, you log in through Google’s own login window — your password is entered on their site, not ours, and we never see it.
We request exactly one permission: gmail.readonly. ClaimsGap can
read mail; it cannot send, delete, or modify anything, and it can never send email as you.
What we actually read
Not your whole mailbox. For a given claim, ClaimsGap asks Gmail a narrow question built from that claim’s adjuster email address and claim number — roughly “messages to or from this adjuster mentioning this claim number, from the last year” — and takes at most twenty results. For each one it requests only the Subject, From, To and Date headers, plus Gmail’s own short preview of the message. It does not download message bodies or attachments.
What we store
Nothing. Message subjects, senders and previews pass through our server to your phone and are never written to a database. They are held in the screen you are looking at and are gone when you leave it. The only thing kept is a note of when you last viewed a claim’s correspondence, stored on your device so new replies can be flagged.
The Google tokens themselves are stored server-side, in an isolated per-user store, and are never exposed to the app on your phone. Disconnecting deletes them immediately — see the data deletion instructions, which also cover removing the grant from your Google account.
6. Homeowner share pages
A homeowner status page is a link you generate and send. It is worth understanding exactly how it works, because it behaves differently from most “share” features.
What is on the page
| Included | Deliberately not included |
|---|---|
| The homeowner’s first name only | Their surname |
| The property address | The claim number |
| The carrier name | Any dollar amount — RCV, contract total, depreciation, checks |
| The claim status and a six-step timeline | The adjuster’s name, email or phone |
| Your company name and the rep’s name | The homeowner’s email or phone number |
| A plain-language next step, and the date the snapshot was made | Photographs, notes, gap findings, correspondence |
How the link works
The status information is encoded into the link itself rather than stored in a database. That means anyone holding the link can read the page, the encoding is not encryption and offers no protection to someone who has the URL, and a link cannot currently be expired or revoked. It keeps working, showing the snapshot as it was when you generated it.
Practical consequences, stated rather than buried:
- Forwarding the link works as well as receiving it. Anyone the homeowner sends it to can open it.
- The link will sit in whatever carried it — a text message thread, an email, browser history.
- Because the page is a snapshot, an old link shows old information rather than live claim data. Generate a fresh one after a significant update.
- The page is not deliberately published anywhere, but it is also not protected against search engines. Do not paste a status link anywhere public.
- We do not log who opens a status page, and we cannot tell you whether the homeowner viewed it.
Because there is no revocation, the control that matters is who you send it to. If a link needs to stop being useful, the practical remedy is that its contents go stale — and you should tell us at privacy@claimsgap.com if a link has gone somewhere it should not, so we can help.
7. What stays on your phone
ClaimsGap keeps a full working copy of your data on the device so it functions without a signal. That copy includes every claim and its fields, gap findings, notes, tasks, call summaries, check records, sent-letter text, and document records — plus the photograph and PDF files themselves, and a queue of any changes that have not yet reached the cloud.
This local copy is protected by iOS’s own file protection and your device passcode. It is not separately encrypted by us. Use a passcode, and use the device’s remote-wipe feature if a phone with claim files on it is lost — that is the meaningful control here, and it is yours, not ours.
8. Email, calendar, reminders and dictation
Several features hand data to software on your own phone rather than to us:
- Email. Follow-up letters, call recaps and demand letters are sent from your mail account through the iOS mail composer. We never send mail on your behalf. Note that the app pre-fills the homeowner as a CC on these sends — check the recipient list before you hit send, because the homeowner will see what the adjuster sees.
- Calendar. If you add a claim task to your calendar, the event — including the claim reference in its title — is written to your default calendar, which may sync to an account such as Google or iCloud.
- Reminders. Local notifications can include the homeowner’s name, so it may appear on your lock screen.
- Dictation. Call summaries can be dictated. ClaimsGap asks for on-device speech recognition where the device supports it; on devices that do not, Apple’s speech recognition sends the audio to Apple’s servers to transcribe it. If you would rather that never happen, type the summary instead.
9. Automated follow-up (not active)
ClaimsGap contains unfinished groundwork for an automated follow-up feature that would chase adjusters and mortgage servicers by call, text or email. It is switched off and cannot run. No calls are placed, no texts are sent, no recordings or transcripts exist, and no telephony provider holds any of your data today.
We are describing it here rather than staying quiet about it because turning it on would be a real change in who receives claim information. If it ships, this policy will be updated first, and it will be something you switch on rather than something that starts happening to you.
10. Who we share data with
Only the service providers required to make the product work:
| Provider | What they handle |
|---|---|
| Supabase | Database and authentication. Holds your account credentials and every synced claim record described in section 1. |
| Cloudflare | Runs our server code. Handles the Gmail connection and tokens, passes correspondence through without storing it, and renders homeowner status pages. |
| Only if you connect Gmail: the OAuth login, and the narrow message queries described in section 5. | |
| Anthropic, via an API gateway | Only when you scan an estimate: the image of that estimate page, as described in section 4. |
| Apple | Speech recognition where on-device transcription is unavailable, plus the ordinary operating-system services behind notifications, the calendar and the mail composer. |
That is the complete list. There is no analytics vendor, no advertising network, no data broker, and no payment processor — ClaimsGap does not currently take payment at all.
We may also disclose information where we are legally required to. We do not sell, rent or trade personal data, and we do not share it for anyone else’s advertising.
11. How long we keep it
- While your account is open — we keep your claim records, because a claim file is a business record you may need long after the job closes.
- Gmail tokens — deleted the moment you disconnect.
- Correspondence read from Gmail — never stored, so there is nothing to retain.
- Estimate images sent for scanning — not retained by us. Retention at the AI provider is governed by their own terms.
- Photographs — kept on your device until you delete them or remove the app. We never hold a copy.
- On account deletion — your account and every claim record we hold are permanently deleted within 30 days. See the data deletion instructions.
- Backups — residual copies may persist in encrypted backups for a short period after deletion before being overwritten on the normal cycle.
There is no delete button for an individual claim in the app yet, and no self-serve account deletion. Until those ship, deletion is handled by us on request and we treat those requests as a priority. The data deletion page tells you exactly how to make one.
12. Security and isolation
Every record we store carries the account that owns it, and database-level row security rules make it structurally impossible for one contractor’s account to read another’s. That isolation is enforced by the database itself rather than by application code remembering to check.
Requests to our server are authenticated by verifying your session token on the server side, never by trusting an account name the app sends along — which is what stops someone reading or disconnecting your Gmail simply by knowing your email address. Data is encrypted in transit. Google tokens are held server-side and never handed to the app on your phone.
Two limits we would rather state than have you discover: homeowner status links are unauthenticated by design (section 6), and the working copy on your phone relies on your device passcode (section 7).
No system is perfectly secure, and we will not claim otherwise. If a breach affects your data, we will tell you.
13. If you are the homeowner
If your name, address, claim or property photographs are in ClaimsGap, they were put there by the contractor you engaged. That contractor decides what goes in, what comes out, and who gets a status link. We hold it on their behalf.
So the fastest route for a correction or a deletion is to ask your contractor directly — they can act on it immediately, and we would have to check with them anyway before changing their records. If that does not get you anywhere, write to privacy@claimsgap.com and we will help, including by putting the request to them ourselves.
Also worth knowing: the status page your contractor sends you carries no dollar figures, no claim number and no adjuster contact details — but it does show your first name and your address, and anyone with the link can open it. If you would rather not have a link like that circulating, tell your contractor to stop using it for your claim.
14. Your rights
Wherever you live, we will honour these:
- Access — ask for a copy of what we hold about you.
- Correction — most claim fields you can edit directly in the app; ask us for the rest.
- Deletion — see the data deletion instructions.
- Withdraw a connection — disconnect Gmail at any time, from the app or from Google.
- Portability — ask for your claim data in a machine-readable format.
- Object — tell us to stop a particular processing activity.
Depending on where you live you may have additional rights under state privacy laws such as the CCPA, or under the GDPR or UK GDPR. Write to us and we will apply whichever gives you more protection. We respond within 30 days and we do not charge for it.
We do not sell personal information and we do not share it for cross-context behavioural advertising, so there is nothing for you to opt out of on that front.
15. Visiting this website
This marketing site sets no cookies and runs no analytics. It loads fonts from Google Fonts, which means Google receives your IP address and browser details in order to serve them — the only third-party request on the page. The savings calculator runs entirely in your browser; the numbers you type are never sent anywhere.
16. Children
ClaimsGap is a business tool and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child’s data has reached us, contact us and we will delete it.
17. Changes to this policy
If we change this policy we will update the date at the top. For any change that materially affects how we handle your data — including switching on the follow-up feature in section 9 — we will email you before it takes effect.
18. Contact
Privacy questions, requests, or complaints: privacy@claimsgap.com · anything else: hello@claimsgap.com