Repair reviews and reports
A review can contain the vehicle year, make and model, mileage, ZIP code, reported symptoms, the shop’s explanation, original estimate text, optional uploaded photos, and labels and file details for that evidence. Estimate extraction can store a shop name, line-item descriptions and quantities, parts and labor amounts, tax, total, and an extraction-quality label. The current structured extractor has no separate fee field. Missing or unreadable values are not filled in as facts.
The app stores the free report, its input-quality notes, generated full report, generation status and timestamps with the saved review. The private-link token is stored as a hash; the token itself is in the private URL and acts as authorization. Keep that link private. Uploaded evidence is sent to Polsia file storage; the app database stores its storage key, URL, filename, type, size, label, and review association. The review API returns these URLs only after the account or private-token check, but anyone who obtains a direct file URL may be able to open that file.
AI processing
Submitted estimate text is sent through the Polsia AI service for structured extraction. Review text, extracted repair descriptions, relevant saved report context, and submitted photo URLs are sent through the same service when reports are generated. These services process the material to return the extraction or report; Wrenchloom does not use the generated report as a confirmed mechanical finding. The app repository does not define the AI provider’s separate retention period.
Accounts and payment records
A Wrenchloom review can be submitted without an account. If you use an account, the auth service stores the account name and email, credential record, and session data. Session rows can include an expiry time, IP address, and user-agent string. A review may also be associated with the signed-in user.
The $19 purchase opens hosted Stripe checkout through Polsia’s payment service. Checkout handles payment details; Wrenchloom’s review record stores the checkout session ID, payment status, verified buyer-paid gross amount, and payment time to unlock the report. The application review schema does not store card numbers.
Optional feedback and older requests
After a completed report, an optional survey can store the five answers, optional text explanations, a per-review browser session key, and report association. The key is kept in session storage to avoid practical duplicate submissions. Survey answers do not require an account and are stored in the application database for owner review.
The former expert-review request flow collected a linked review ID, name, email, and note. New requests are disabled because no reviewer-fulfillment workflow is configured. Any older request records remain in the database unless separately removed.
Site measurement and contact
The app includes a Polsia page-load beacon. It creates a random browser identifier in local storage and sends that identifier and the app slug to Polsia when a page loads. The code does not specify the platform beacon’s retention period.
Older sample-results click records may remain in the database with their source, event, and creation time. The sample-results endpoint is retired and no longer accepts new events.
The contact page opens your email application to the provisioned Wrenchloom inbox. A message you send is handled by your email service and the configured company inbox; the contact page itself does not submit or store message content in the Wrenchloom database.
Storage and retention
Review, report, account, feedback, payment-session, and older expert-request records are stored in the application’s PostgreSQL database. Uploaded evidence is stored by Polsia’s file-storage service. The current application has no automatic deletion, expiry, or retention period for these records and no self-service deletion route. The owner still needs to decide and publish a retention and deletion policy; no deletion deadline or promise is currently made.
For questions about this information, use the configured contact route at Contact Wrenchloom.