How Pitlane keeps your shop's data safe.
The honest list of every meaningful technical control that protects your shop's data, your customers' data, and the AI prompts your team sends through PitCrew. Updated when anything changes. Never as marketing copy, only as documentation.
Technical controls
The six controls that matter most.
Every SaaS tool ships the same marketing-page list (“encrypted! cloud-native! SOC 2 ready!”). Here is what actually exists in the code.
Row-level data isolation per shop
Tenant-owned tables are scoped to the signed-in shop at two layers. Route handlers pass the shop filter on their own queries, and a Prisma extension injects the current shop's ID into tenant-scoped models underneath them whenever a request context is active. Defense in depth: the same filter is applied from the handler and again at the data layer.
Encryption at rest and in transit
Supabase Postgres encrypts data at rest. All web traffic is HTTPS-only and forced to TLS 1.2+; HSTS is set on every response. Twilio per-shop credentials are encrypted with AES-256-GCM before they hit the database.
Auth handled by Supabase
Pitlane never stores passwords. Authentication is delegated to Supabase Auth, which stores credentials with bcrypt. Sign in with email and password or with Google. Sessions use short-lived JWTs plus a rotating refresh token in HttpOnly cookies. Two-factor sign-in is available on every account: a one-time code emailed at login, enforced server-side once you turn it on.
AI that doesn't train on your data
PitCrew AI calls the Anthropic API. Per Anthropic's commercial API terms, the prompts and completions Pitlane sends aren't used to train Anthropic's models. Your shop's customer data, RO notes, and review-reply drafts never become anyone's training set.
Carrier-registered SMS (A2P 10DLC)
Two-way SMS runs over Twilio under Pitlane's own carrier-registered A2P 10DLC brand and campaign. Your shop registers nothing and brings no Twilio account. We provision a dedicated local number on a managed per-shop subaccount. STOP / HELP keywords are auto-handled and unsubscribes are honored per TCPA.
Strict CSP with nonce-only scripts
Every HTML response carries a per-request CSP nonce; only scripts stamped with that nonce execute. The script-src directive forbids 'unsafe-inline' and 'unsafe-eval'. XSS bypasses that work on most SaaS apps don't reach the browser here.
The Pitlane Privacy Promise.
The same promises we lead our privacy policy with, in plain terms. They hold for every shop on Pitlane.
Your customer list is yours
Every contact, vehicle, and service record is yours to keep. We just hold it for you.
Export everything, anytime
One click in Settings pulls the whole workspace into CSV files you can open in any other tool.
Leave whenever, take it all
Cancel in one click. Your data stays exportable on the way out, and nothing traps you here.
We never sell it
No ad-data partners, no data brokers, no enrichment. Not now, not ever.
Delete on request
Type your shop name to confirm and the whole workspace comes out of production right away.
If something goes wrong, we tell you fast
If a breach touches your data, affected shops hear from us within 72 hours of confirming it.
The fine print lives in our Privacy Policy.
Found a vulnerability?
Email support@usepitlane.com with the details. Critical issues get acknowledged within 24 hours and a fix timeline within 72 hours. We don't run a bounty program yet. When shops on Pitlane reach the size where one is justified, we'll launch one. Until then, responsible disclosure gets a written thank-you.
Please don't test against production data without permission. Shops trust us with their customer lists; a blind pen test against the live database isn't the right path. Email first, and we'll set up a sandbox.
Questions shop owners actually ask.
Is Pitlane SOC 2 compliant?
Pitlane runs on SOC 2 Type II–compliant infrastructure (Vercel for compute and edge, Supabase for the database, AWS for the underlying VPC). Pitlane's own SOC 2 audit is not yet complete. The technical control inventory is on this page.
Where does my data live?
Inside the United States. The Pitlane application runs on Vercel's US-based regions; the database runs on a Supabase project in us-east-1. Backups stay in-region. There is no offshore data processor in the path.
How is PitCrew AI not training on my shop's data?
PitCrew calls the Anthropic API. Per Anthropic's commercial API terms, the prompts and completions Pitlane sends are not used to train Anthropic's models. We pass user prompts and shop-context strings; we don't send credentials, payment details, or PII beyond what's necessary for the writing task.
What happens if Pitlane gets breached?
The disclosure plan: identify the scope, notify affected shops within 72 hours of confirming the breach, then follow up with a written post-mortem once the scope is confirmed. We follow the standard notification timeline most state-level breach laws require, applied across all shops regardless of state.
What about HIPAA?
Pitlane is for auto repair shops, which are not HIPAA-covered entities. We don't sign BAAs and we don't market into healthcare. Customer health information shouldn't flow through Pitlane, and there's no shop workflow where it should.
Run your next job on one work order.
Start free for 30 days. No credit card, no setup fee, no per-transaction platform fee.