Your garage.
Your records.
This notice describes the current prototype. The operator must add their legal identity and privacy contact before a wider public launch.
What this version stores
For registered accounts: display name, email address, a salted password hash, session records, vehicle profile details, owner notes, and timestamped simulated telemetry, diagnostic examples, and demo trips. Account and garage records are stored on the operator’s server. No actual vehicle readings or GPS location are collected. If Google traffic is configured and you request a route check, the entered addresses are sent to Google Maps Platform. Route responses are used temporarily and are not saved in the car timeline.
Demo mode
The public demo uses sample data in the current page’s memory. Changes disappear when the page reloads. No account is created. Hosting access logs may still record requests to the site.
Cookies and browser storage
A first-party session cookie keeps registered users signed in for up to seven days. The browser stores the selected vehicle ID as a convenience. This version includes no advertising or analytics scripts. Enabling the optional Google map loads Google Maps resources and sends requests to Google; its terms and privacy policy apply. Your theme choice is stored on this device.
Access and security
Authenticated server requests check vehicle ownership. Passwords use salted scrypt hashes. HTTPS must be configured by the operator. Anyone who can access the server, its database, or backups may have access to stored records; this is not end-to-end encrypted storage.
Your choices
Use Account → Export data to download your profile, cars, and history. Removing a car deletes that car and its timeline from the active database. Full account deletion currently requires the server operator; there is no in-app account deletion or password recovery flow yet. Do not use this beta for sensitive records.
Retention and logs
Garage history remains until removed by you or the operator. Database backups may retain deleted information until those backups expire. Application request logs include request paths and network metadata. Login throttling keeps short-lived pseudonymous email keys and connection-address counters. The operator must establish and communicate backup and log retention before public launch.
What is not connected
No live OBD connection, GPS collection, radar detector, ECU programming, or code-clearing feature is enabled. Google traffic is optional and requires server configuration. Radar alerts in this build are labelled tests. The native iPhone prototype does not sync to this server yet.