Privacy

Account: your name, email address and a scrambled (hashed) version of your password. We cannot read your password.

Shop records you enter: customers (names, phone, email, address, notes), vehicles (including VINs), quotes, parts, labor times, settings and team members.

An audit log of changes made in your shop (who did what, and when). It cannot be edited from inside the app.

When a customer answers a quote through their private link: the name they typed, the time, their network (IP) address and their browser's user-agent text, saved with their answer as evidence of approval.

To slow down password guessing we keep a counter of failed sign-ins and password-reset requests, keyed by a one-way hash of the email or address rather than the value itself.

Personal accounts and the request board: a free personal account keeps the vehicles, symptoms and notes the owner enters. When someone posts a request we keep it with the vehicle (including the VIN), the problem, the city and region, and the contact name, phone and email they give. Shops that are signed in can see the vehicle, problem and city. The phone, email and VIN are shown only to the poster and to the one shop whose response the poster accepts, and a responding shop's phone and email are shown to the poster only once that response is accepted. Requests expire after 30 days and can be closed at any time.

PartsTech (optional): if a shop owner connects PartsTech, we store that shop's PartsTech user ID and API key encrypted, and delete them when the owner disconnects. The login is only decrypted at the moment a parts lookup is made.

Follow-up texts: when a shop texts a customer about repairs they declined, we keep a record in that shop (who sent it, when, the exact text and the repairs it covered). When a customer replies STOP, or a shop records that they do not want texts, we keep a one-way hash of their phone number on a do-not-text list shared by every shop, so that nobody on the platform texts them again. We do not store the number itself there.

We use only the cookies needed to keep you signed in and to return you to the page you came from. We do not use advertising or analytics cookies, and the pages contain no third-party tracking scripts.

Payments: if you subscribe, Stripe processes your payment. Card details go to Stripe, not to our servers, and we keep only identifiers such as a customer and subscription reference.

Email and text messages: if the operator has switched on message delivery, the recipient's address or phone number and the message text are passed to the email or SMS provider so it can be delivered, and the provider may tell us when a number has replied STOP. If it is not switched on, nothing is sent and no data goes to those providers.

VIN lookup: when you decode a VIN, the VIN is sent to the US NHTSA vPIC service, which returns the vehicle details.

Parts prices: if a shop has connected PartsTech and looks up a part on a quote, that vehicle's VIN, the search words and the shop's PartsTech login are sent to PartsTech, which returns that shop's supplier prices. Nothing is sent to PartsTech unless the shop has connected it.

We do not sell your data, and shops cannot see each other's records: the database itself enforces the separation.

Passwords are hashed. Sign-in locks after repeated failures. Password-reset and customer-approval links are long random tokens: only a fingerprint of each is stored, and they expire.

No system is perfectly secure, and some protections (such as two-factor sign-in) are not available yet.

Your shop's records stay while your account exists. You can export customers, parts and labor times as CSV at any time. To ask for your account or personal data to be deleted or corrected, contact us using the details on the contact page. Some records, such as the audit log, may be kept for a period so the history stays trustworthy.

Your shop decides what to record about its own customers and is responsible for having the right to record it. We handle that data only to provide the service to your shop.