Security & data handling

Your claim data is yours.

Insurance work touches policyholder PII — names, addresses, claim numbers, property photos. Below is exactly what LossNarrative does with it, in plain English. If something here isn't clear, email us.

No vendor trains on your data

Photo captions, narrative reports, and section regenerations are generated by Anthropic's Claude API. Per Anthropic's API terms, customer inputs and outputs are not used to train their models. Voice memos are transcribed by AssemblyAI, which has the same no-training policy for API customers.

Practically: a photo you upload today is not going to surface in a response someone else gets next month.

Where your data lives
  • Claim metadata + reports — Postgres on Supabase (US region). Each row is row-level-security gated to the owning user; another customer cannot see your rows even through a misconfigured query.
  • Photos + voice memos — Supabase Storage, private bucket. Access is gated by user-folder rules; signed URLs (10 minutes for caption/narrative processing, 1 hour for in-app viewing) are the only way to fetch the bytes.
  • Narrative generation — Anthropic API. The photo URL + prompt are sent; the generated narrative comes back. Anthropic does not retain the prompt or response after the request, per their API privacy policy.
  • Transcription — AssemblyAI. The audio URL is sent; the transcript comes back. Same retention model.
  • Billing — Stripe. Card numbers never touch our servers; we only store the Stripe customer + subscription IDs to associate your plan with your account.
Encryption
  • TLS 1.2+ for every request, in-app and to all sub-processors.
  • Postgres and object storage are encrypted at rest by Supabase.
  • Database credentials, API keys, and webhook secrets are environment-scoped and never committed to source.
Deletion

Delete a claim and its photos, voice memos, transcripts, and generated reports are removed from the database immediately (foreign key cascade). The matching storage objects are removed in the same request.

Want to nuke your whole account? Email us and we'll do it within one business day, including a confirmation of completion.

Liability and the adjuster sign-off

LossNarrative generates a draft narrative. The adjuster reviews, edits, and signs it. Final responsibility for accuracy and any communication with the carrier remains with the licensed adjuster. The report engine is built to write[ADJUSTER TO CONFIRM]rather than invent facts; you fill those in before signing.

We do not represent that a generated draft is automatically suitable for submission; treat it like draft work from a junior associate.

Sub-processors
  • Supabase — database, authentication, file storage
  • Anthropic — Claude API (narrative + captions + section regeneration)
  • AssemblyAI — voice-memo transcription
  • Stripe — subscription billing
  • Resend — transactional email (account confirmations only)

Questions about a specific compliance regime (HIPAA-adjacent injury claims, state-specific carrier requirements, your firm's vendor checklist)? Email us — we'll answer directly.

Related: Privacy policy · Terms of service