Skip to content

Data handling

Data handling

Last updated November 1, 2026 · How ShopBoss isolates and protects shop data

This page is the short operational version of the Privacy Notice. It is for shop owners and for anyone asking how we treat tenant data.

Tenant isolation

Each shop is a separate tenant. Jobs, recordings, transcripts, photos, crew accounts, and customer records belong to that shop. Other shops cannot open them in the app. On Postgres, row-level security is forced so a database role cannot read another tenant’s rows even if application code is wrong. The hotline tenant is the shop whose dashboard token is attached to this deployment.

Encryption in transit

The website and APIs are served over HTTPS (TLS). Sign-in cookies are marked Secure in production. We do not put private links in public marketing pages. Data at rest is stored by our processors (today Supabase and Vercel) under their encryption practices.

Access controls

Retention

Call audio and transcripts are kept about 90 days. Job and customer records stay while the shop is active. Server logs about 14 days. Backups about 30 days, then overwritten. A shop can export or delete its account; backups then age out. STOP on a phone is kept so we do not text that number again.

Breach notice

If we learn of a security breach that affects your shop’s data, we will notify the shop owner at the account email without unreasonable delay, and in any case as Indiana and applicable U.S. law require. We will say what we know, what was involved, and what we are doing. Processors (Vapi, Vercel, Supabase, and later Stripe, Telnyx, or Resend) have their own incident processes; we pass through what they tell us when it affects you.

Questions: support@getshopboss.com · Support.