Our Promise
Drivers shouldn't have to take the shop's word for it.
Why this page exists
We work for the person paying the repair bill.
Anyone can put up a tagline. A promise only matters if the business is built so that breaking it would be hard, not just discouraged. This page is the public version of how Wrench.Pro is built, and what we will and won't do as we grow.
Seven promises. One section explaining why you can believe them. One section showing, line by line, what we share with shops and what we never will. If any of this changes, we'll change the page. And we'll say what changed and when.
The pledge
Seven promises to every driver who uses Wrench.Pro.
- 01
We work for you, not the shop.
Every recommendation comes from the manufacturer's published maintenance schedule, not what a service advisor would prefer to sell you.
- 02
The core product is free and stays free.
Forever. Premium just removes ads. The maintenance information is identical for everyone, paid or not.
- 03
We don't collect personal information about drivers.
Looking up a vehicle needs no account, no name and no email. We are building optional driver accounts so you can save your cars and come back to them, and that will stay optional: the free lookup never asks who you are. If you do make an account, what you save is yours and stays inside Wrench.Pro.
- 04
We may share anonymous, aggregated trends with shops. Never individuals.
A shop in your area might learn that "30 Honda drivers in the Phoenix metro searched for oil changes this week." They will never learn who you are, which model you drive, or which neighborhood you live in. And we couldn't tell them even if we wanted to. We don't have it to give. We spell out exactly what's in the aggregate, and what isn't, further down this page.
- 05
Shops pay to be seen. They never pay to change what we tell you about your car.
Paid placements buy visibility in the directory and nothing else. No shop, advertiser, or partner can influence the maintenance schedule you see, the order of recommendations, or whether a service is flagged as overdue.
- 06
We tell you when something isn't due, not just when it is.
The most valuable advice is often "you can wait." Knowing when to skip a service is just as important as knowing when to do one.
- 07
We read what comes in, and we respond.
We may use AI to reply faster as we grow, but every message reaches someone who can do something about it. If we ever get this wrong (a bad recommendation, a sketchy shop, a promise we didn't keep), we want to know.
Why you can believe this
Architecture, not policy.
The strongest privacy promise isn't "we won't do this." It's "we can't." Wrench.Pro is built so the bad outcomes drivers worry about are out of reach in the code, not just against the rules.
The lookup asks for a vehicle, never for a person: no name, no email, no phone number. Optional driver accounts are coming so you can save vehicles and find them again, and the architecture holds either way. What a shop can see is the anonymous aggregate, and that is true whether or not you have an account, because account data never enters what we share.
When a shop or partner asks about driver interest in their area, the only thing we can show them is the aggregate. Not because we're refusing to share more. There is no "more" to share.
During your visit
How your ZIP and mileage work on this site.
When you add your ZIP and mileage on a vehicle page, your browser holds those values in session storage, the same kind of short-term memory your bank uses to keep you signed in for one visit. We use them to show shops near you and to flag recall coverage for your area. They also work out when your next service is due, and pre-fill the fields if you check another car in the same visit.
Closing the tab clears it. There's no cookie that remembers your area between visits, no cross-device sync, no driver profile we're quietly building. You can also click “change” on any vehicle page to clear or update it mid-visit.
We also log each lookup to our private analytics: Year, Make, Model, mileage, ZIP, and the locality or metro that ZIP maps to. Those logs live in Wrench.Pro tools and a private spreadsheet. The next section spells out exactly what leaves Wrench.Pro to be seen by shops, and only what.
Transparency
What aggregated data actually looks like.
When we tell shops or partners about driver interest in their area, this is what we share, and what we never do.
Vehicle data
| Make | May appear in aggregate counts (e.g. "Honda drivers"). |
| Year | May appear in aggregate counts when the bucket is large enough to stay anonymous. |
| Model | Never shared. Too identifying for uncommon vehicles. |
| Mileage | Never shared with shops. Used to build your maintenance timeline. If you save a vehicle to an optional driver account in the future, your mileage lives only inside that account. |
| Service searched for | May appear in aggregate counts (e.g. "searched for oil changes"). |
| VIN | We don't ask for it. Year/Make/Model is enough to look up a schedule. |
Location data
| Metro area | May appear in aggregate counts (e.g. "in the Phoenix metro"). |
| Zip code | Never shared. Too granular to stay anonymous in smaller communities. |
| Street address | We don't collect it. |
Personal information
| Name, email, phone | Not collected. Unless you write to us through the contact form, in which case we use it only to reply. |
| Driver account / login | Optional, and not required. Today, there's nothing to log into. You can use the lookup with no signup. We plan to offer optional driver accounts so you can save vehicles, log completed services, and set reminders. The free lookup will always stay no-signup. |
| Linkage to a person | Kept inside your account, if you have one. Anything we share with shops is anonymous aggregates only. Driver-level data, including anything tied to a future account, stays inside Wrench.Pro. It never leaves in a form a shop could connect to a person. |
One more rule: minimum bucket size.
We won't share an aggregate small enough to identify someone, even indirectly. If only a handful of drivers in a metro looked up a given service for a given make, that bucket gets suppressed. As we build out the sharing pipeline, we'll bake this rule into the code itself, so it doesn't depend on anyone remembering to apply it.
What we publish
What we show, and don't show, about vehicle issues.
On each vehicle page we publish a 'Known Issues' section drawn from federal records and owner reports. This is what goes on the page, and what stays off it.
Vehicle issues data
| NHTSA complaint counts | Always shown. Public-domain data filed by drivers. We display counts, dates, word-for-word quotes, and a direct link to the source on nhtsa.gov. |
| NHTSA technical bulletins | Shown when published. Manufacturer-issued repair guidance, summarized in NHTSA's own words, with a link to the bulletin. |
| Owner reports we publish | After human review. Year, make, model, mileage, metro, and the driver's own words. Each one is labeled "User-submitted, not verified by Wrench.Pro." |
| Owner names or contact info | Never published. If you give us an email so we can follow up, it stays internal. Same rule as the contact form. |
| Wrench.Pro's interpretation | Off the page. We don't write a verdict on whether a car is "good" or "bad." We show the data and the sources. The conclusion is yours. |
If this ever changes
We'll update this page. And say what changed.
Businesses evolve. Say we broaden what counts as aggregate, add a new data point, or change how a promise works. We'll edit this page to reflect it and note the date of the change. We won't quietly walk a commitment back. If we can't keep a promise as written, we'll rewrite it in public.
Found a mistake? Spot a gap? Tell us.
If something on this page doesn't match your experience of Wrench.Pro, we want to hear about it.