Tinkerhowl

Wrench Garage · Privacy and support

Wrench Garage privacy

Wrench Garage keeps vehicle records on your device. Optional vehicle lookups and links send the lookup values to the destination you choose.

About this policy

Effective date: November 9, 2026. This policy covers Wrench Garage 1.1.0, including its local-first Android and browser builds.

Responsible publisher: Gabriel Navarro, operating Tinkerhowl. Application: Wrench Garage (“Wrench”). Android package: com.tinkerhowl.wrench.

These production builds do not require an account or send your garage records to Wrench servers. This version does not expose cloud sync, household sharing, OCR, push notifications, advertising, analytics, crash reporting, or paid vehicle-data integrations. It does not offer license-plate lookup or sell your local records. Android backup and device transfer of private app data are disabled.

Records and files stored on your device

Wrench stores information you enter or select, including vehicle details and VIN, mileage, maintenance history, costs, parts, fuel, tires, reminders, inspections, checklists, shopping items, documents, source notes, and preferences. Record metadata is kept in local app storage. Selected receipt and document names, media types, and file contents are kept in a local file vault using IndexedDB. Wrench does not automatically upload these records or attachments. If you request a lookup or open an external link, the limited values described below are sent to that provider.

Local recovery copies

Local autosave and backup exports can create recovery snapshots containing records and referenced attachment files. Wrench retains at most three snapshots, removing older snapshots as newer ones are added. A recent snapshot can contain a record you have since deleted.

A detached attachment can remain in the local file vault after its record is deleted or a restore replaces records. This preserves recovery options; deleting a record does not immediately erase every local historical copy.

To recover from an interrupted save, Wrench can retain previous and proposed record metadata in a local recovery journal until the save is acknowledged and cleanup succeeds, or recovery finishes. If saved metadata cannot be read, Wrench preserves the original and offers a recovery download. That download contains raw metadata, not separately stored attachment files. These recovery operations do not make a network request.

Vehicle lookups and external links

When you explicitly choose a free NHTSA lookup, Wrench sends the needed lookup values:

  • Decode VIN: the VIN and optional model year.
  • Look up models: the make and model year.
  • Check recalls: the make, model, and model year.

These requests go directly to NHTSA over HTTPS. They do not include maintenance records, photos, or documents. Wrench can save lookup results and source notes locally with the vehicle. NHTSA and network infrastructure can receive ordinary request metadata under their own practices. A lookup does not confirm exact installed equipment, parts fitment, a maintenance schedule, or the absence of open recalls.

Opening the official VIN recall link can include the VIN in the destination URL. An owner's manual search sends the vehicle year, make, model, and any saved trim or sub-trim, together with the search terms “owner's manual” and “official,” to Google Search. Opening a saved manual or document link requests its full saved URL from that external website. The destination, browser, and network infrastructure process the request under their own policies.

Exports, sharing, and printing

Exports are generated locally when you choose an export or sharing action. JSON and ZIP backups can contain selected garage and knowledge records plus attachment files. Service, fuel, and parts CSV exports contain the selected vehicle's rows, including notes and relevant pricing or linked-record details, but no attachment files.

A local read-only service binder contains its generation time, vehicle year, make and model, and service names, dates, mileages, and notes. It excludes VIN, trim, engine, transmission, current vehicle mileage, costs, shop and technician details, warranty, parts, documents, attachments, images, and personal issues. The exported binder does not expire and cannot be revoked. Print / Save PDF can include the vehicle's current mileage, rendered service details, and a locally available receipt preview.

Wrench does not upload these outputs. Android's share sheet, a browser download, or the print destination passes or saves the output where you choose. That recipient or destination can retain its own copy under its own controls.

For Android exports, Wrench stages the file in private app cache. It schedules deletion after five minutes and retries cleanup of older staged exports on a later launch. Cleanup is best effort: if interrupted, the private cache copy may remain until Android evicts it or you clear Wrench's app data. Deleting Wrench's copy does not delete a copy saved by a recipient.

Retention and deletion

Wrench stores records locally. You can edit or delete them in the app, or clear the storage for the platform on which you use Wrench. Deleting an individual record removes it from the active garage. Removing a vehicle removes that vehicle's active records and scoped knowledge notes. Detached files, recent snapshots, and an unfinished recovery journal can still retain the local recovery copies described above.

On Android, clearing Wrench's app storage through Android settings or uninstalling the app removes its remaining app-local data, including attachments, snapshots, and recovery metadata. Android cloud backup of private app data is disabled. Exported, shared, or printed copies must be deleted separately at their destination. Save any backup you want to keep outside Wrench before clearing app storage or uninstalling.

In a browser build, records, attachments, snapshots, and recovery metadata are stored in that browser's local storage and IndexedDB for the origin where you use Wrench. To remove those remaining local copies, clear that origin's site data in your browser. Clearing Android app storage or uninstalling the Android app does not clear a separate browser's site data. Exported, shared, and printed copies must also be deleted separately at their destinations.

Policy hosting and support email

Cloudflare Pages hosts these privacy and support pages. Visiting them allows Cloudflare and network infrastructure to process ordinary request information, such as your IP address, browser information, and the requested page, under their own practices. These pages do not use analytics, advertising, tracking cookies, or a contact form.

If you email us, we receive your email address and the message and attachments you choose to send. Zoho Mail provides the mailbox. We use that information to answer the inquiry, troubleshoot the issue, and address privacy or security requests. Do not send a complete garage backup or sensitive documents unless the particular issue requires them.

We retain routine correspondence for up to 12 months after an inquiry is resolved, then delete it from the mailbox copies we control. Relevant records may be retained longer when necessary to address an ongoing dispute, a security incident, or a legal obligation. Service providers may retain separate copies under their own policies.

Questions and policy changes

Contact us with questions about these practices. We will update this policy and its effective date when our data practices change. Review the policy associated with the version you use.

Privacy questions: privacy@tinkerhowl.com.

App support: support@tinkerhowl.com. Include only the information needed to explain the problem.