WRENCHENGINE

Privacy policy

How WrenchEngine and its technician app handle personal information.

Effective 25 September 2026 · Last updated 5 October 2026

Who we are

WrenchEngine, Inc. makes WrenchEngine, software for heavy-duty truck service shops. We sell it to businesses (a “Customer” below), not to the public.

Most information in WrenchEngine belongs to the Customer: their staff, their own customers, their drivers and trucks. The Customer decides what goes in and how long it stays. We hold it for them.

If you are a driver, a shop’s customer, or a shop employee and want your information seen, corrected or deleted, contact that shop. They control the record, and we help them act on it.

What we hold

  • Customers and contacts: names, phone numbers, emails, addresses, company details, billing terms, and whether they accept text messages.
  • Drivers and callers: name, phone number, the reported problem, and the breakdown location.
  • Trucks: VIN, unit number, plate, make, model, mileage and service history.
  • Staff and technicians: name, work contact details, address, job title, certifications, signature, pay rate, and clock-in and clock-out times.
  • Calls and messages: call recordings, transcripts, text messages and chat messages.
  • Photos and documents: job photos, signatures, invoices and attachments. A job photo can show where it was taken.
  • Locations: truck positions from GPS tracking (where the shop connects it), job site addresses, and photo locations.
  • Sign-in and security records: accounts, roles, and a log of who did what and when.
  • Payments: amounts and payment status. Card payments are taken on Stripe’s own payment page. Card numbers go to Stripe and never reach us. We keep only Stripe’s reference for a payment or a saved card.

Notes and other free-text fields can hold anything people type or say.

What we do with it

We use it to run the service for the Customer: sign-in and permissions, notifications the Customer has set up, connections the Customer has turned on, support, security and legal duties.

We do not sell personal information. There is no advertising, and no third-party analytics or tracking software, in the product, the dashboard, or the technician app.

AI features

AI helps turn calls, emails and texts into draft jobs, transcribe and summarise calls, suggest parts, and check invoices before a person sends them. To do that we send the relevant text, call audio, transcripts and photos to AI providers (listed below). OpenAI and Deepgram process that audio or text to provide transcription and AI features, under their own terms. Vapi, which runs the AI Dispatcher’s voice, keeps its own copy of those calls under its own terms, as described under Calls. AI output is always a draft: nothing is invoiced or sent to a customer without a person approving it.

Calls

Calls handled by WrenchEngine’s phone features are recorded and transcribed, including calls answered after hours by our automated voice agent, the AI Dispatcher, where the caller is talking to software.

Telling callers that a call is recorded is the Customer’s responsibility, for example in its phone greeting.

Call recordings, including calls the AI Dispatcher answers, are deleted automatically about 90 days after the call. When we can't tell when a call took place, the 90 days count from when the recording reached us. Deletion runs in the background, so a recording can remain for a short time past that point. Some older recordings carried over from an earlier storage location, which we can't match to a call, are not deleted automatically; a shop can ask us to delete them. A recording can also be deleted sooner if our storage limit for recordings is reached, so a shop should keep its own copy of any recording it needs. A shop can ask us to delete any recording sooner. This covers the copies WrenchEngine stores. The companies that carry the calls, the telephone provider (Twilio) and the voice agent provider (Vapi), keep their own copy of a recording under their own terms, and deleting ours does not delete theirs.

The technician app

The app is used by a shop’s own technicians. It asks the phone for:

  • Camera: to take job photos. A technician can also send a job photo into a chat; it goes as the original file, which can include where it was taken.
  • Location, only while the app is open: to tag a photo with where it was taken, and to show the technician on the jobs map. Each reading holds the phone’s position, height, direction and speed at that moment. It never tracks location in the background. A technician can say no and keep working.
  • Photos: it asks for access to the photo library so a technician can pick a picture to attach to a chat, and it uses only the pictures they pick.
  • Microphone: to record a short voice note (up to two minutes) on a job photo. Voice notes stay on the phone and are never uploaded. The app also contains a voice assistant that is switched off and has no button or menu anywhere in the app. On Android its screens can still be opened by a direct link; if one is opened, it asks our assistant service for the technician’s jobs, sending their identifier, and its speech screens can use the phone’s own speech recognition, which may send speech to Google.
  • Notifications: the app asks once, the first time a technician opens Messages, whether it may show notifications. If they allow it, the app sends our server a push token for the phone, with the phone type and app version. We use it to send notifications about the technician’s jobs, such as a job assigned to them with its order number, and about new chat messages. A chat notification shows the sender’s name and the message text, and the phone may show it on the lock screen, depending on the phone’s settings. A technician can turn notifications off in the phone’s settings. Signing out asks the phone to stop notifications and asks our server to remove the phone’s token; if the phone does not stop them, the app tries again each time it opens; if our server cannot be reached, the removal is sent at the next sign-in on that phone.

The app keeps some job information on the phone so it works without signal. Signing out deletes the job data the app keeps on the phone. If part of it cannot be removed at sign-out, the app tries again the next time it opens, or when someone else signs in on that phone. In rare cases one file the phone refuses to delete can stay in the app’s private storage, where nothing in the app can open it, until the app is uninstalled. Android’s own backup of the app’s data is turned off, so no copy goes to the technician’s Google account. The current app does not read the phone’s text messages, and it does not track location or record sound in the background. While the app is closed, the phone’s own system shows its notifications.

Who we share it with

Only what each provider needs to do its job:

ProviderFor
OpenAIAI features: text, call audio, transcripts, photos
DeepgramTranscribing call recordings
VapiThe after-hours phone agent
TwilioText messages and calls
ResendEmail: invitations, payment links, receipts, approval requests
FusionAuthSign-in and identity: staff account credentials and profile
StripeCard payments and saved cards
Google Maps, Apple Maps, OpenStreetMapMaps, addresses and travel times
GPS InsightTruck positions, where the shop connects it
QuickBooks Online (Intuit)Accounting, where the shop connects it
TavilyWeb search for the technician assistant
US NHTSADecoding VINs
ExpoDelivering updates and notifications to the technician app
Apple and GoogleDelivering notifications to the phone
Cloud hosting and file storage providersRunning the service and storing files

How long we keep it

Until the Customer deletes it. Deleting a record usually hides it rather than erasing it. For a permanent erase, the Customer asks us.

Call recordings are deleted about 90 days after the call, as described under Calls.

Security

Sign-in goes through an identity provider, with roles controlling what each person can see. The dashboard’s connections to our servers are encrypted. In our main database, the database itself stops one shop from reading another shop’s records. Sign-in keys on the phone are kept in its secure storage. We hold no security certification and don’t claim one. No system is perfectly secure.

Where it is held

Information may be stored and processed in the United States and in other countries where the providers above operate.

Changes

The current version is always at wrenchengine.com/privacy/app, with its effective and last-updated dates at the top.

Contact

WrenchEngine, Inc., 12105 Rayo De Luna Ln, Austin, TX 78732, United States

Privacy questions, privacy requests and security reports: barry@servicebay.ai

Example Cockpit screen