Security and data
How we keep your claim data
Written for your claims manager and your IT reviewer, in the same words: where data lives, who can see it, and what we never do.
Seven promises
- We never connect to your claim system.There is no integration, no login, no key. Your people type or upload what they want Subrobuddy to hold, or forward a referral email to your company’s Subrobuddy inbox. Nothing else ever comes in, and nothing goes back out. There is no door to worry about.
- Your data sits in its own locked room.Every record is stamped with your company, and the database itself refuses to hand a record to anyone from another company. The lock is on the shelf, not just the front door, so even a bug in our code can’t show your claims to someone else.
- Your admins decide who is in the room.Only your admins invite people, remove them, and hand out roles. We cannot give anyone at your company access.
- Every change is on record.Stage changes, payments, settlements, approvals, tasks and accounting marks go in the claim’s audit trail with who did it and when.
- Your data is yours.Your admin can download everything at any time: every claim, its notes, its history and its documents. When you close your account, you have 30 days to take that download, and then everything is permanently deleted.
- We never store card numbers, bank account numbers or Social Security numbers.Payment details stay with our payment processor. No letter needs an insured’s bank details, so we never ask for them.
- Hosted in the United States, encrypted on disk and in transit.And our name never appears on your letters. They are yours, sent on your company’s behalf.
What IT asks about first
Encrypted everywhere
Data is encrypted in transit (TLS) and at rest (AES-256) by our database provider.
Your people only
Everyone in your company can read its claims. Only the assigned specialist can change one (Intake can add to a new claim until it’s assigned). Nobody outside your company sees anything. The database enforces it.
Documents read on your computer
Reading a document, including scanned pages, happens in the browser. Documents are never sent to an AI service.
Every change on record
Stage changes, payments, settlements, approvals, tasks and accounting marks go in each claim’s audit trail.
The details
| Connection to your systems | None. Subrobuddy never logs in to, reads from or writes to a carrier’s claim system. Information gets in one way: a person types it or uploads a document. |
|---|---|
| Where the website runs | Vercel, which holds a SOC 2 Type 2 attestation and ISO 27001 certification. |
| Where claim data is stored | Supabase, a managed database on Amazon Web Services. Supabase reports SOC 2 Type 2 compliance and ISO 27001 certification, encrypts data at rest with AES-256 and in transit with TLS, and runs regular penetration tests. |
| Signing in | Work email and a one-time code sent by email, or a password the person chooses. Passwords are kept only as a salted hash by our sign-in provider, so nobody at Subrobuddy can read one. |
| Who can see a claim | Row-level security in the database: everyone in your company can read your company’s claims, and nobody outside it can. Only the specialist a claim is assigned to can change it (Intake can add to a new claim until it’s assigned), only a supervisor can reassign it, and only admins hand out roles. The accounting page is limited to admins, supervisors and the Accounting department. |
| Documents | Kept on the specialist’s computer, with a copy in private cloud storage so the claim opens on any computer. Only people who can see that claim can open its documents, through links that expire after 10 minutes. |
| Reading documents | Text and scanned pages are read in the browser with open-source tools. Document contents are not sent to any AI or outside reading service. |
| Task notices and the morning summary are sent through Resend and include claim numbers and task titles, not documents. Each person can turn the morning email off. | |
| Dashboards | Show claim numbers and dates only, so a screen can be shared in a meeting. |
| Audit trail | Each claim keeps a dated record of who changed the stage, payments, settlements, approvals, tasks and accounting marks. Approvals can’t be given by the person who asked. |
| Your data is yours | Your admin can download everything at any time, from the Team page: a spreadsheet of every claim, plus each claim’s notes, audit trail and documents. An admin closes the account from the same place. Your people can keep working for 30 days, the admin can cancel during that time, and after 30 days every claim, note, document and setting is permanently deleted from the database and from document storage. Sign-in emails are removed on request. |
| What we never store | Card numbers, bank account numbers or Social Security numbers. Payment details stay with our payment processor. |
What we don’t have yetSubrobuddy is a young company and doesn’t have its own SOC 2 report yet. Our hosting and database providers do, and we’re glad to share what we can for your review. If your security team needs everything inside your own network, ask us about a private installation.
Security questionnaire?
Send it over. We’ll answer it and walk your team through how Subrobuddy works.
Email our team →