Privacy Policy — DRAFT, not published
DRAFT for review, 14 Sep 2026. Written from what the code actually does (moto-tracker-saas at
149e5b8), not from a generic template. Every[ … ]is a fact only the owner can supply. It is not legal advice and must be read by a lawyer before it is published — seeS33-note.md.
Last updated: [ date of publication ]
Status: draft. Everything in double brackets is a decision the operator has not made yet — the legal identity, the contact address, and how long tracker positions are kept. The document is otherwise written against the system as it actually behaves on 16 September 2026.
1. Who we are
Moto Tracker is operated by [ legal entity name, registration number, address ] ("we"). We are the controller of the personal data described here. Contact for anything in this policy: [ privacy contact email ].
2. What Moto Tracker does, in one paragraph
A GPS tracker fitted to your motorcycle sends its position over the mobile network to our server. The app shows you where the bike is, records your rides, and alerts you — by push notification and, if you set it up, by a phone call to a person you choose — when the bike moves while armed or detects a crash. Location data about a vehicle you ride is personal data about you, and continuous location data can reveal where you live, work and spend your time. We treat it accordingly.
3. The data we process
| Data | Where it comes from | Why | Legal basis (GDPR Art. 6) |
|---|---|---|---|
| Email address, password (stored only as a salted hash) | You, at sign-up | Your account and sign-in | Contract (6(1)(b)) |
| Home location and radius, time zone | You, in Settings | Telling "at home" from "away" for theft alerts | Contract |
| Tracker positions — latitude, longitude, speed, time | The tracker | Showing the bike, recording rides, theft alerts | Contract |
| Motion, tilt and crash events from the tracker's sensors | The tracker | Theft and crash detection, ride replay | Contract |
| Tracker diagnostics — battery, signal, firmware version, connection logs | The tracker | Keeping the service working and diagnosing faults | Legitimate interest (6(1)(f)) |
| Tracker identifiers — hardware (MAC) address, device name | The tracker and you | Linking the tracker to your account | Contract |
| Emergency contacts — name and phone number of up to five people | You | Phoning them / the tracker texting them after a theft or crash | Contract; see §6 |
| Rides, saved places and their photos, a 3D model you upload | You | The features you use them for | Contract |
| Buddy Beacon: your display name and live position, shared with the riders you approve | You, when you start or join a beacon | Riding together | Contract |
| Share links: your bike's recent trail, visible to anyone holding the link | You, when you create one | Letting someone follow a ride | Contract |
| Push notification subscription (an endpoint issued by your browser's push service) | Your browser, when you allow notifications | Delivering alerts | Contract |
| A record of the alerts, calls and messages sent to you | Our server | Showing you what happened, and proving an alert was or was not delivered | Legitimate interest |
| IP address and request details in server logs | Your browser, every request | Security and abuse prevention | Legitimate interest |
| Waiting-list email address | You, on the presentation site, if you ask to be told about the launch | Writing to you once when the product goes on sale | Consent (6(1)(a)) |
The waiting list is the one thing above that has nothing to do with a tracker or an account. It is an email address and nothing else — the sign-up form stores no IP address, no browser details and no name — and it is used for exactly one message: telling you the product can be ordered. You can ask us to remove it at any time by writing to [ privacy contact email ].
We do not use advertising, analytics or tracking cookies, and we do not sell or rent personal data. The app sets one cookie — your sign-in session, valid for 30 days — and keeps display preferences (theme, selected tracker) in your browser's local storage. Both are strictly necessary, so no consent banner is shown.
4. How long we keep it
| Data | Kept for |
|---|---|
| Tracker positions (location history) | [ a number of days — see S33-note.md: the current default is "for ever" ] |
| Alert log | 365 days |
| Motion events | 360 days |
| Tilt data | 90 days |
| Tracker connection logs | 30 days |
| Matched routes (the road-snapped version of your rides) | 10 years, or until your account is deleted |
| Share links | until they expire (1, 6 or 12 hours) |
| Buddy Beacons | until they end (2 hours to 7 days) |
| Server request logs (IP addresses) | 14 days (rotated nightly by the web server) |
| Everything else in your account | until you delete your account |
| Waiting-list email address | until we write to you about the launch, or until you ask us to remove it |
| Backups | nightly, the last 14 kept; snapshots taken before a database change, for 30 days |
5. Deleting your account and getting a copy of your data
- Download my data (Settings → Account) gives you a ZIP of everything we hold about you, in JSON and CSV — your right to access and to data portability (Art. 15 and 20).
- Delete account deactivates it at once — no sign-in, no alerts — and permanently deletes your data after 30 days, during which you can restore it with your password. Your tracker is released so it can be linked to another account; its history is not passed on. Deleted data leaves our backups within 30 days as they rotate.
- You also have the right to rectification, restriction and objection (Art. 16, 18, 21). Write to [ privacy contact email ]; we answer within one month.
6. Emergency contacts
When you add someone as an emergency contact, you give us their name and phone number. Please tell them, and add only people who agree to be called. We use the number only to: (a) place an automated phone call through our telephony provider when your bike is stolen or crashes, and (b) have the tracker send them a text message with its position after a crash. We never use it for anything else.
7. Who else processes the data
| Recipient | What they receive | Where |
|---|---|---|
| [ Mobile network operator of the tracker's SIM ] | The tracker's connection to the network; its positions pass through their network | [ country ] |
| Twilio Inc. (phone calls) | Your emergency contact's phone number, when a call is placed | USA — [ Standard Contractual Clauses / Data Privacy Framework ] |
| Google LLC — Geocoding API | Coordinates of your stops and rides, to turn them into street names | USA — see S33-note.md, this is being replaced |
| Your browser's push service (Google, Apple or Mozilla) | An encrypted alert payload and the subscription endpoint | varies |
| OpenFreeMap (map tiles) | Your IP address and the map area you view | [ country ] |
| OpenStreetMap Nominatim | Coordinates, when you look up a buddy's or a pin's street, and your IP address | EU (UK?) [ check ] |
| Sentry (error reporting) | Error reports from the server and the app. Positions, email addresses, phone numbers, tokens and the contents of requests are removed before the report leaves our server or your browser | EU region (Frankfurt) |
| Hosting | All of the above | [ currently: a server operated by us in Romania; planned: Hetzner, Germany ] |
8. Security
Passwords are hashed with bcrypt. The app is served over HTTPS. Each tracker has its own broker credentials, and one tracker cannot read another's messages. Sessions can be revoked from Settings, and a revoked session stops working on every device. The app serves its own fonts and libraries — opening a page does not hand your IP address to a content delivery network. Its content security policy no longer permits inline script, which is the usual way an injected script runs. Photos and 3D models are served only to a signed-in session, or through a share link you created. Error reports are stripped of personal data before they are sent.
What we will not claim: the tracker's own connection to our server is not encrypted — the firmware speaks MQTT in plain text over the mobile network. Someone positioned on that network path could read the positions it publishes. Replacing it requires new firmware on the device. [ Owner: keep this paragraph or fix the firmware before publishing; do not quietly drop it. ]
9. Children
Moto Tracker is not intended for anyone under 16, and we do not knowingly create accounts for them.
10. Complaints
You can complain to the Romanian data protection authority, ANSPDCP (www.dataprotection.ro), or to the authority in the EU country where you live.
11. Changes
We will tell you by email and in the app before a change that affects how your data is used. [ Note: there is no mailer yet — S25. ]