Privacy Policy

This policy covers the MIR//AUTOS instance at mir.autos, operated by [Operator name]. It describes what we store about you as an account holder, what other people can see, and which third parties are involved.

1. Your account

We store, for as long as your account exists:

• your email address, username, and the optional display name, bio, location and profile photo you add;
• a bcrypt hash of your password — never the password itself;
• if you sign in with Google, GitHub, Microsoft or Facebook: the provider's stable account id and the name and email it shares, so we can recognise you;
• your interface preferences, such as the theme you chose;
• API tokens you create for the mobile apps, stored as hashes, with the time each was last used;
• signed-in devices. For every browser session and every app sign-in we keep a device record: a name derived from the browser or the phone model, the operating system and app or browser version, the IP address it last connected from, an approximate location (city and region) derived from that address, and — for the Android app, if you allow location — the phone's last reported position. You can see these records and log any device out under Settings › Devices; the administrator can see and log out devices too. A record is closed when the device is logged out; and
• the time of failed sign-in attempts against your address, kept for one day, to slow down password guessing.

1a. The Android app and trip tracking

The MIR//AUTOS Android app keeps a copy of your garage on the phone so it works offline and uploads changes when it is back online. If you switch on automatic trip detection, the app watches your movement (activity recognition and a low-power location fix every minute or so) and, while you are driving, records your route with GPS every few seconds. Each finished trip — its times, distance, start and end addresses and route points — is stored on the phone and then on our server against the vehicle you assigned. Only the phone you mark as the primary trip tracker records trips automatically. You can turn detection off at any time in the app, delete any trip, and revoke the app's access under Settings › Devices.

Diagnostics. The app keeps a rolling record of what it is doing — trips starting and ending, syncs, screens opened, errors — on the phone. If the app crashes, or its main thread wedges long enough to count as a freeze, that record and the stack trace are sent to this server the next time the app opens, so the fault can be traced. The record holds no addresses, coordinates or garage contents. Reports are readable only by the administrator, under Admin › Diagnostics, and are deleted automatically after 30 days. You can send one yourself, or read what the record holds, under More › About in the app.

Photos of receipts and invoices you scan in the app are processed on the phone (cropping and cleaning up the page) and uploaded to your service history; when the administrator has enabled AI reading for your account, the pages are also sent to the configured AI provider to fill in the form (section 6).

2. Your garage

For each vehicle you add we store what you enter: nickname, VIN, year, make, model, engine and other specifications, licence plate, colour, photos, notes, purchase date, odometer readings with their time and source (manual, trip, service, app), service records with cost and notes, and trips with their times, distances, labels, purpose, and, when the mobile apps supply it, GPS coordinates and route points.

VIN lookups. When you ask the service to decode a VIN, the VIN is sent to the United States National Highway Traffic Safety Administration's public vPIC service, which returns the vehicle's specifications. The VIN identifies a vehicle, not a person, and no account details accompany it. Results are cached on our server for an hour.

3. What other people can see

• Private by default. Your vehicles, records, trips and profile are visible only to you and the administrator.
• Public profile. If you turn it on, anyone can see your username, display name, bio, location, photo, join year, and the vehicles you mark public — their name, year, make, model, trim, engine, colour, odometer, photo and notes. The VIN, plate, service history and trips are never shown.
• Manual contributions. Every edit you make to a manual is recorded in its version history with your display name and account email, and that history is visible to anyone who can read the manual — including, when the administrator allows it, visitors who are not signed in. Comments show your display name and profile link.
• Private messages are visible to the two participants and, on the server, to the administrator.

4. Uploads

Photos, videos and PDFs you upload are stored on the server and served from an unguessable address. Anyone with that address can open the file, so a photo you attach to a public manual step or a public vehicle is public. Files may contain metadata such as location; strip it before uploading if that matters to you.

5. Retention and deletion

• Deleting a vehicle deletes its odometer readings, service records and trips.
• Deleting a comment blanks its text but keeps its place so replies stay attached.
• Manual content lives in a git repository: removing a procedure creates a new version without it, but earlier versions remain retrievable by anyone who can read the manual. Ask the operator if you need history purged.
• To close your account, contact [contact email]; the operator can disable or delete it.

6. Sharing and third parties

Your data is not sold and is not shared with advertisers or data brokers. Third parties are involved only as follows:

• NHTSA vPIC — receives VINs you decode (section 2).
• Google, GitHub, Microsoft or Facebook — only if you sign in with one of them; we receive your id, name and email from the provider.
• YouTube — when a manual step embeds a YouTube video, your browser loads it from YouTube's privacy-enhanced domain, and YouTube's own policy applies.
• Maps — trip maps load tiles from OpenStreetMap or, when the administrator has configured it, from Mapbox. The map provider receives your IP address and the map areas you view (which reveal where your trips took place) under its own privacy policy.
• IP geolocation — to show you where each of your devices connected from, the IP address of a sign-in is looked up with a geolocation service (ipwho.is), which returns a city and region. Only the address is sent; no account details accompany it.
• AI providers — if the administrator has enabled AI for your account and you use it, the receipt pages, part pages or step text you submit are sent to the configured provider (for example OpenAI, Google or Anthropic) to be read or illustrated, under that provider's policy.
• Google Fonts — the interface loads its typefaces from Google's servers, which see your browser's request.
• An analytics provider chosen by the administrator — if the administrator installs an analytics snippet, it runs in your browser subject to that provider's policy. Where the administrator has marked it as requiring consent, it loads only after you accept cookies; see the Cookie Policy.
• Cloudflare or a similar proxy in front of the site may see your IP address and requests as part of serving them.

7. Security

Passwords are bcrypt-hashed, the session cookie is signed, encrypted and HttpOnly, API tokens are stored hashed, and the service is served over TLS. No system is perfectly secure, and we make no guarantee of absolute security.

8. Your rights

Depending on where you live you may have rights to access, correct, export, delete or restrict processing of your personal data, and to complain to a supervisory authority. Most of your data can be viewed and changed directly in the app, and exported through the API; for anything else contact [contact email].

9. Children

The service is not directed at children, and accounts should not be created for anyone below the age at which they can agree to the Terms where they live.

10. Changes

Material changes are reflected in the “last updated” date above.

11. Contact

[contact email]