What we can show, and what we cannot yet.
The guarantees are held by the database, not by a setting. The certifications are listed with their state, including the ones we do not have.
Request the security summaryor write to support@shopbook.io. A person replies.
History is never edited.
A change is a new entry; nothing is rewritten. A correction sits beside the entry it corrects, so what was quoted, approved and charged stays readable.
Amounts are whole cents, each line rounded and the sum exact. An issued invoice never changes; a void is its own record.
One shop's data stays its own.
Every table that holds a shop's data carries the shop's id, and the database refuses a read or write of another shop's rows.
Shopbook's operations console signs staff in with passkeys and cannot read a shop's customers, vehicles, repair orders, invoices, payments or messages: the database refuses it. Every staff action is written to an audit log no one can edit.
Sign-in is guarded, and changes are on record.
Passkeys, or email and password with a second step. After five failed sign-ins, each further try waits longer, from 30 seconds up to 15 minutes, per account and per network.
Settings changes and writes to audited records leave an audit event with who, when and what changed; the owner's export includes them.
Every AI action goes through one metered path and is capped before it runs. AI drafts; a person approves anything with a price or a promise.
Card numbers never reach us.
Cards are handled by Stripe; a card number is entered on Stripe's page and never reaches Shopbook. Invoices and payments are integer cents, reconciled to the cent.
Your data leaves with you.
An owner exports the shop's records (repair orders, customers, invoices and their history) any time, in a form another system reads.
The database and its backups are held by Neon, in the United States. No restore rehearsal is recorded yet.
Certifications, listed as they are.
Including the ones we do not have.
Who else handles a shop’s data.
One list, shared with the Privacy Policy, so the two never disagree. It is updated there before a new provider receives shop data. Privacy Policy
| Provider | What it receives | Where | When |
|---|---|---|---|
| Vercel, Inc. | Every request to the app while serving it; a shop’s own domain name when it adds one; AI feature requests, routed through the Vercel AI Gateway to the AI providers with no retention | United States | Always |
| Neon, Inc. | The shop’s data, stored in the database and its backups | United States | Always |
| Vercel Blob | Files and photos a shop uploads, and the exports it downloads | United States | Always |
| Functional Software, Inc. (Sentry) | Error reports with customer data removed: the error type and stack trace, the page’s route pattern (never its address), the release, the runtime and browser family, an opaque shop id, the shop’s short name (its slug) and the signed-in member’s role; never request bodies, headers, cookies, addresses, names, emails, phone numbers, plates, VINs, links with tokens or prompts | United States | Always |
| Stripe, Inc. | The amount and the invoice or deposit it is for, for each card payment; the shop’s own billing details for its subscription | United States | Always |
| Anthropic, PBC | The request and the shop records it cites, and any attached images, when someone uses an AI feature | United States | Always |
| Microsoft Corporation | The audio of an inspection voice note, to transcribe it, with zero data retention; for someone who signs in with Microsoft, the sign-in request (Microsoft returns their name and email address) | United States | Always |
| Resend, Inc. | The recipient’s address, the subject and the body of each email Shopbook sends | United States | Always |
| Twilio Inc. | The recipient’s phone number and the message, for a shop with text messaging configured | United States | When connected |
| Google LLC | The sign-in identity, appointment details written as calendar events, and contact names, emails and phone numbers read on a contacts import; at setup, the shop name and town an owner types to find the shop’s Google profile | United States | When connected |
| Intuit Inc. | Paid invoices (lines, tax, customer name and email) and their payments, for QuickBooks | United States | When connected |
| PartsTech, Inc. | The vehicle’s VIN, or its year, make and model, when a shop opens a parts search | United States | When connected |
| Have I Been Pwned (Superfly Pty Ltd) | When a password is set or changed: the first five characters of its hash, and nothing else; the match happens on Shopbook’s servers | Australia | Always |
| U.S. National Highway Traffic Safety Administration (vPIC) | A vehicle’s VIN, or its year, make and model, to decode it and look up open recalls | United States | Always |