Security
What protects your shop's data, in plain English, and what we do not have yet.
What is in place today
A towing company holds vehicle locations, customer phone numbers and photographs of other people's property. Below is how that is handled. Every item describes something that is built, not planned.
- One shop cannot see another shop
- Every job, customer, photo and site row is owned by an account, and the database enforces that ownership with row-level security rather than trusting the application to remember. A query that is not entitled to a row does not get the row, whichever screen or API key asks for it.
- The link is the only key, and it expires
- A customer tracking link and a driver job link carry no login on purpose, because a stranded motorist will not create an account and a driver will not install an app. Each link is a single-purpose token bound to one job. Customer links are never indexed, expire after 30 days and can be revoked by the shop; driver links stay open for a week.
- We never see a card number
- Subscriptions run through Stripe Checkout, so card details go from the payer to Stripe and never reach our servers or our database. Your customers pay you through your own pay-online link, which means their card details do not touch us either. We hold no card data to lose.
- Encrypted in transit, everywhere
- Every page, including the website we host on your own domain, is served over HTTPS with a certificate we provision and renew for you. The SSL certificate is part of the subscription, not an extra.
- Two-factor authentication on your account
- Every user can turn on an authenticator app from account settings. Dispatchers and drivers do not need one to work a job, so switching it on for owners and admins costs the shop nothing operationally.
- A job history nobody can rewrite
- The timeline on a job is append-only. Status changes, quotes, arrival times, notes and photos are added, never edited away, so what the record says happened is what the system saw happen. That is what makes it useful in a dispute.
- Texts only with recorded consent
- A customer is texted only where consent was captured on your form or recorded by your dispatcher, the consent is stamped on the record, and a reply of STOP stops the messages immediately. The consent belongs to your company, not to us.
- Your data leaves with you
- One button in team settings downloads the whole account as a zip: jobs, customers, timeline events, services, website pages and reviews as CSV, plus a manifest and time-limited links to your job photos. Your jobs also export to CSV from the reports screen, and the REST API reads jobs, services and units with a key you issue and revoke yourself. Your domain and your website content are yours.
What we do not have yet
You are going to ask, and you should. Here it is before you have to.
- No SOC 2, ISO 27001 or PCI attestation. We are a small team and we have not been audited. If a contract you are bidding on requires one, tell us before you sign it rather than after.
- No published Data Processing Agreement yet. If your insurer or a commercial account needs one, ask and we will work through their paperwork with you.
- No published uptime commitment. We do not run a status page or an SLA, so we are not going to quote you a number of nines that nothing backs.
- No third-party penetration test to show you. The audit is a real item on the list, and it is not done.
Found something, or need paperwork?
Report a vulnerability, or ask for what a commercial account needs, at support@www.towsitepros.com. Please give us the detail and a way to reach you, and do not test against a live towing company's site: those are somebody's working business, and a real job may be running on it.