Security and your data

Straight answers to the questions your insurer will ask.

Where it runs, how it is protected, who touches it, and how you get it back. No marketing language; this is the system as it is built today.

Where it runs

The application runs on Vercel, in Dublin. Your data lives in a managed PostgreSQL database on Supabase in the EU (AWS eu-west-1, Ireland). Photos and documents are stored alongside it in the same region.

Encryption

Every connection to the app, and every upload and download of photos and documents, is encrypted in transit (TLS). The database and file storage are encrypted at rest by the provider.

Backups

The database provider takes a backup every day and keeps it for seven days. Every structural change is rehearsed on a copy first, and we normally take a full backup of our own before it, keep it separately and delete it within ninety days.

Audit at the database

Changes to claims, appointments, estimates and their lines, variations, invoices and their lines, payments, material orders, hire and survey values are recorded by database triggers, with who and when. Estimate prices, quantities and rates, variation values, payments, invoice lines, material orders, hire and survey figures are recorded with the before and after values. So is any change to an insurer’s margin floor or payment terms, or a tradesman’s hourly rate. The application cannot bypass them. Once an estimate is accepted, only a manager can change its prices and quantities, and that change is recorded too; everyone else raises extra work as a variation of its own.

Your company, your data

Every record is tagged with your company, and no other customer can see your data. Staff sign in with an email code, no passwords to leak, and see only the screens their level allows. A manager can suspend a leaver in one click.

Getting your data out

Every management report exports to CSV from the screen. A manager can download a complete export of your company’s data, documents included, at any time, and for 30 days after you leave. Your data is never a reason to stay.

Who processes your data

We run on established providers rather than our own servers. Each one holds only what it needs for its job.

ProviderWhat they do for usWhere
VercelApplication hostingApplication servers in Dublin (EU), beside the database; worldwide delivery network
SupabaseDatabase and file storageEU (AWS eu-west-1)
ClerkSign-in (email code)US
StripeSubscription billingCard details never touch our servers
MailgunEmail: letters, appointment confirmations, specifications, chase emails, the morning digest, the Control Agent’s morning brief and its Friday summary to managers if a manager turns the brief email on, invites and account notices; and, if switched on, replies filed on the claimEU region
ApplePush notifications to iPhone and iPad: a claim reference and a short line, never policyholder detailsApple Push Notification service
GooglePush notifications to Android: the same contentFirebase Cloud Messaging
AnthropicOptional AI wording for the Control Agent (the morning brief, chase drafts you approve, and “What should I do?”), only for a company whose manager switches on Use the AI model: claim references and stage, policyholder, insurer and staff names, what the agent found (including amounts owed and margin percentages) and the first 160 characters of the last ten notes as typed, with email addresses, phone numbers and long numbers blanked; never the estimate’s lines, rates or costs, or bank or card details, though anything a user types at the start of a note goes as written. Its commercial terms say it may not train its models on what we sendUS
SentryError reporting: built in but not switched on, so nothing is sent to it todayEU region, to be chosen if it is switched on

Who is responsible

The Claim Job Control service is run by BizSmart LLC, a Wyoming limited liability company (registered office c/o Republic Registered Agent LLC, 5830 E 2nd St, Ste 7000, Casper, WY 82609, United States). For the claims, policyholders, photographs, bookings and staff records your company keeps in the app, your company is the data controller and we process them on its instructions as its processor. For the sign-in, billing and account data we need to run the service, we are the controller. Questions about any of this come through the contact page.

What we do not do

  • No advertising trackers, no analytics cookies, no selling of data
  • No shared logins: every action is tied to a named person
  • No silent edits: the audit trail is written by the database, not the app
  • No lock-in: CSV export on every report, and a full export a manager can download at any time

Next step

Ask the hard questions on the demo.

Bring your insurer’s due-diligence list. Thirty minutes, one claim, and every answer above shown live.