Every insurance document, attached to the right policy.
insia keeps policy schedules, certificates, renewal notices and claim correspondence in private encrypted storage — linked to the policy they belong to, not lost in an email inbox.
Upload, store, and control access to your insurance documents in three steps.
01
Upload from the app
Attach any policy document — schedules, certificates of currency, renewal notices, claim correspondence — directly from your iPhone. Documents are linked to the relevant policy record the moment you upload them.
Every document is stored in a private AWS S3 bucket, encrypted at rest, and served only through authenticated signed URLs. There are no public document links. Nobody can access your documents without being signed in to your account.
Private AWS S3 buckets — no public URLs
Encrypted at rest and in transit (HTTPS/TLS)
Authenticated signed paths, not permanent links
Scoped to your account via Supabase RLS
03
You control who sees what
Documents are only visible to you by default. When you choose to share a policy with your broker, they can access the documents you have attached to that policy — and nothing else. You can revoke that access at any time.
Broker access limited to shared policies only
Other documents remain completely private
Revoke broker access at any time
Consent logged with a timestamp
How it works in the broker portal
When you share a policy with your broker, they access a structured view through the insia broker portal — not your full document library.
What brokers see in the portal
When a client shares a policy record with their broker through insia, the broker can view the policy details and attached documents within the broker portal. Brokers do not have access to documents on policies that have not been shared.
Scoped, not full-account access
Broker portal access is scoped to the specific policies a client chooses to share. The broker portal never provides visibility across a client's full document library — only the records and attachments explicitly shared.
Broker access is structured context, not advice
Documents shared through insia give brokers structured factual context — policy schedules, renewal dates, premiums, excesses. insia does not facilitate advice, underwriting, or product recommendation through document sharing.
Document types supported
insia supports any document relevant to your insurance records — uploaded directly or imported via email forwarding.
Policy schedules and product disclosure statements
Certificates of currency
Renewal notices and renewal confirmation letters
Claim correspondence and settlement letters
Endorsement and amendment notices
Invoice and premium receipts
Broker letters of engagement
Photos and evidence for claim records
Documents are stored in private AWS S3 buckets (Sydney region), encrypted at rest, and served only through authenticated signed URLs scoped by Supabase Row Level Security. No document is accessible without being signed in to your account. Read the full security overview →
Stop hunting for the right PDF.
Join the waitlist and be among the first to organise your insurance documents in insia when we launch.