Privacy policy

Short version: quiz, calculator, repair-log, and packet-builder answers stay in your browser. We never receive them — unless you choose the optional packet review, which sends the text of your generated documents for an automated check and then discards it, or when your generated files are sent to our server for the sole purpose of emailing them to you (also discarded after sending).

What we collect

• Quiz / calculator: your answers are processed locally in your browser and never sent to our servers. Separate usage counts, described below, do not contain your answers.
• Repair log: the repair visits you enter are saved only in this browser's local storage (under the key lemonlawpath_log) so they persist between visits and can pre-fill the packet builder. They are never sent to our servers. Use the tool's “Clear my log” control, or clear your browser data, to delete them.
• Packet builder: your inputs are processed locally to generate your documents. So you can pick up where you left off, your answers are saved in this browser's local storage as you type, and the quiz and calculator save your state, dates, and mileage there so the builder can pre-fill them. That data stays on your device — use "Clear saved answers and start over" in the builder, or clear your browser data, to delete it. On a shared computer, clear it when you're done. The one exception: when you generate your packet, your browser sends the finished Word and PDF files to our server once so they can be emailed to you (described below), then they are discarded — we don't keep copies.
• Packet review (optional, paid buyers only): if you click "Review my packet," the text of your generated documents is sent to our server and to Anthropic, the company that makes the Claude AI model, to produce the review. Before sending, your browser replaces your email, phone number, and street address with placeholders; your name, vehicle details, VIN, dates, and repair history are included. We don't store the document text or the review — it passes through memory for that one request. Anthropic processes it under its commercial API terms. We keep only a count of how many reviews each purchase has used (stored against a scrambled version of your checkout-session ID), so we can apply the 5-review limit. Our server logs record that a review ran and its size in tokens, not what it said. If you don't click the button, nothing is sent.
• Checkout: payment is handled by Stripe, and what you enter at checkout is covered by Stripe's privacy policy. We never see or store your card details. When you return from checkout, our server asks Stripe whether your checkout session is paid and was for this product — that check is the only purchase data we process.
• Abuse protection: to slow down automated requests, our server briefly counts requests to the purchase-check, packet-review, and usage-count endpoints, stored against a scrambled (hashed) version of your IP address — never the address itself. Each count expires within two minutes.
• Your browser: after you pay, your browser stores the Stripe checkout-session ID (in local storage) so the builder stays unlocked on that device. Clearing your browser data removes it.

Usage counts and your choice

We use simple action counts to understand which pages and tools are useful: page views, guide-to-tool clicks, quiz starts and completions, calculator results shown, samples viewed, checkout clicks, verified builder access, packets generated, and print requests. Since October 2026 the counts also include repair-log actions (a visit added, the log exported, the log carried into the builder), buyback-calculator results, sample packet downloads, the builder's separate Word and PDF downloads, failed document exports, and whether the packet email was sent or failed. Each count is only the action name and the page's fixed label — never the contents of your log, your documents, or your answers. Your browser keeps local diagnostic totals in this tab's session storage.

When our usage reporting is enabled, the browser sends only fixed action names and fixed page labels to our own server. We combine them into daily totals in Cloudflare D1. These counts contain no form answers, selected state, names, contact details, vehicle information, VINs, repair descriptions, purchase references, visitor identifiers, full URLs, query strings, or referrers. A state-guide page label identifies the page, not your location or the state you select in a form. We do not link actions into individual visitor histories. Older daily totals are removed as new usage is recorded once they are more than 90 days old. Cloudflare processes the network request as our hosting provider; the usage database does not store IP addresses.

These are action totals, not unique visitors or purchases. Repeat actions, blocked requests, and automated traffic can affect them. Payments are handled separately by Stripe. Usage reporting never controls access to your purchase.

We respect supported Do Not Track and Global Privacy Control signals. You can also turn off local diagnostics and usage reporting in this browser below. Where browser storage is available, your choice is saved in local storage; it contains only an on/off preference. If storage is blocked, the control explains that the choice applies only to the current page. It does not change the tools, checkout, or packet access. Turning off counts cannot remove earlier anonymous totals because they cannot be linked back to you. Clearing browser storage removes your saved preference and local diagnostic counts.

State context between pages

Links from state guides may include a two-letter state code so the next tool can start on that state. Your latest tool state is also kept in this tab's session storage. You can change it in the tool. A saved packet takes priority over an incoming state link, and a notice explains any mismatch. The link never includes your dates, mileage, repair history, or purchase reference.

What we don't do

• No advertising trackers. No sale of personal data. No accounts or passwords.

Email delivery of your packet

When you generate your packet, your browser creates your Word (.docx) and PDF files and sends them to our server for one purpose: emailing them to the address you used at Stripe checkout. The files are attached to a single email and then discarded — we don't keep copies of your documents. You can ask for the email again from the builder ("Email me the files again"), up to 3 emails per purchase, so a leaked purchase reference can't be used to flood an inbox. We use Resend to send the email. Your email address is used only to deliver your purchased files — no marketing, no list, no other use. Files are only ever sent to the email address on your Stripe checkout — never to an address typed into the site. If checkout has no email address for your purchase, we can't email the files; download them from the builder instead.

Contact

Questions: [email protected].

Last updated: October 24, 2026.