UNAPPROVED PUBLIC DRAFT. NOT PUBLISHED. Production and payments are disabled.

Privacy Notice

Privacy Notice version: 2026-10-22-1.

Seller: James Knight, doing business as milehiiv Reconstruction. Business/legal-notice address: 11500 Jollyville Rd #513, Austin, TX 78759. Service website: https://milehiiv.com. Contact: support@milehiiv.com.

Service providers and processing location

Host: Google Cloud Platform, one VM in us-central1. Storage region: us-central1.

Google Cloud Platform provides hosting and storage. Namecheap provides DNS and email forwarding. These providers are used for the stated service purposes.

Payment provider: Stripe for payments when activated. No live payment provider is connected; this build uses the offline fake boundary only. Naming Stripe does not activate payments or send it driver files.

Records, purposes and access

Service data includes the contact you supply, uploaded platform records, reconstructed results, source/file hashes, consent and acceptance records, delivery records, and case support messages. Platform files may contain trip dates, locations and mileage. We process these for the requested reconstruction, private free summary, optional paid-file delivery and support.

Private browser/session cookies and case access records support access and recovery. Do not provide passwords, Social Security numbers or unrelated tax records. Uploaded data is not sold or used for advertising or unrelated analytics. Service or vote contact does not enroll you in marketing.

Access model: accountless access using contact plus recovery code. Recovery: operator re-link through Help using the case contact plus recovery code. Save the recovery code shown once; only its hash is stored. The operator checks the contact and code before binding the current browser to the case. A wrong code fails closed without revealing another case. This procedure does not establish independently verified ownership of an email address or phone number.

Keep your recovery code and private access information confidential. Help and the support address remain available for privacy, recovery, delivery and charge-error requests after browser access ends, subject to appropriate verification. A request does not automatically restore expired browser access or reveal another case.

Browser access and privacy retention are separate. Delivery-based access deadlines apply to new Uber and Lyft queue requests and paid orders, as disclosed with the case or order. Other-platform cases keep the separate clock and assisted-reconnection path described below. Browser expiry is not erasure.

Other-platform browser access ends 30 days after sending your records. Access expiry alone does not delete the records. Through Help, the operator can reconnect your browser after checking the case contact plus recovery code, provided the records have not been deleted or trashed. This assisted reconnection is separate from ordinary queue access. No answer or timeline is promised.

Retention and deletion schedule

Driver files are deleted 90 days after delivery, except dispute evidence under a legal hold.

Delivery is actual packet availability for a paid case, checked-preview availability for a free case, or recorded-answer availability for an other-platform case. Time waiting for delivery does not consume retention.

The same driver-file deadline covers app Trash and private case versions; moving a file to Trash does not restart the clock.

Backups roll off within 30 days of a deletion, except evidence preserved under a legal hold.

Paid-order minimal bookkeeping is deleted seven years after the end of the calendar year containing that order's last financial transaction, such as payment or refund. Nonpaying-case minimal bookkeeping is deleted 12 months after recorded case closure. Necessary tracking remains while a case is genuinely active. Passive visits, operator notes and outgoing messages do not restart these periods.

Minimal bookkeeping is limited to necessary case/order identifiers, dates, amounts, tax and currency, payment/refund references, version hashes, consent facts and delivery status. The longer bookkeeping periods do not extend the 90-day driver-file deadline or authorize retaining customer contacts, recovery information or full case packets as bookkeeping.

Legal holds preserve the exact dispute evidence needed while the hold applies. Held evidence is excepted from ordinary driver-file deletion and backup roll-off; closing a financial dispute does not automatically release a legal hold.

A documented legal obligation or scoped legal hold can override an ordinary deletion deadline, limited to only the necessary records and the period they are required. Releasing a hold does not restart retention; delete unheld records whose ordinary deadline has passed. Backup copies follow the disclosed 30-day roll-off after deletion.

Enforcement is a manual operator run at launch; dry-run is the default and no scheduler is active. The operator reviews the exact deletion plan before an explicit execution. This is the decided procedure, not proof that deletion or backup expiry has occurred. No existing files or backups are deleted by this policy build.

This build implements bookkeeping and optional-contact expiry, renewal and withdrawal handling only in marked offline synthetic stores. It does not enable production enforcement or prove host deletion, backup expiry, timely manual execution or real contact-ownership verification. No live files or records are deleted by this policy build.

Privacy or deletion requests can be made through Help or the support address. A request is not a completion receipt. The operator verifies the case, checks legal holds, reviews exact files and records completed actions. Backups follow the 30-day roll-off after a deletion; no instant erasure of every copy or forensic media erasure is claimed.

Wave signups and app votes are separate records, not delivered case files. Their contacts are used for the requested wave or app response, with no price, date or result promised. The delivered-case 90-day rule does not silently assign these records a delivery date.

Wave-signup and app-vote contacts are deleted by the earliest applicable deadline: 180 days after signup or a fresh explicit driver renewal; 30 days after the requested notification is completed; or seven days after withdrawal. Contact use stops immediately on withdrawal. Only a fresh affirmative driver request renews the 180-day clock; browsing, operator notes and outgoing messages do not.

After contact deletion, only non-identifying app totals may be retained, after removing contact, browser/session identifiers, nonces and identifying write-ins. Submitting a case does not silently renew a wave/vote contact record; the case has its own disclosed access and retention rules.

Other-platform free looks

Other-platform submissions remain separate from the paid Uber and Lyft queue. They carry no paid price hold, checkout, turnaround or result promise.

Processing consent and optional default-off test-copy consent remain separate. No reusable copy is created automatically. Under these Terms, development and testing use synthetic records only; optional permission alone does not activate a secondary-use program.

Any future retained test-copy program requires separate approval and the separate optional consent. A request to withdraw that consent or delete a copy must be recorded and completed; the request alone is not proof of deletion.

Launch support and current operating proof

Launch support model: James only at launch; one business day reply target. This is a target, not a guaranteed response time or proof of actual inbox coverage.

Namecheap forwarding alias: support@milehiiv.com forwards to ops@reclaimware.com. Configuration was verified by panel readback. One outside-sender test reached this destination Inbox through Namecheap on October 22, 2026, in about nine seconds. The earlier test sent from the destination mailbox remains unconfirmed. Ongoing delivery reliability and practical inbox monitoring remain unproven. This application build sends no email.

Production remains disabled. This notice records the decided launch model; it does not activate the service, certify host security or prove retention enforcement or backup expiry. Actual handling and required safeguards must be verified before public operation.