Draft — not in force. The marked blanks are decisions the operator has not published yet.

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 — see S33-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

DataWhere it comes fromWhyLegal basis (GDPR Art. 6)
Email address, password (stored only as a salted hash)You, at sign-upYour account and sign-inContract (6(1)(b))
Home location and radius, time zoneYou, in SettingsTelling "at home" from "away" for theft alertsContract
Tracker positions — latitude, longitude, speed, timeThe trackerShowing the bike, recording rides, theft alertsContract
Motion, tilt and crash events from the tracker's sensorsThe trackerTheft and crash detection, ride replayContract
Tracker diagnostics — battery, signal, firmware version, connection logsThe trackerKeeping the service working and diagnosing faultsLegitimate interest (6(1)(f))
Tracker identifiers — hardware (MAC) address, device nameThe tracker and youLinking the tracker to your accountContract
Emergency contacts — name and phone number of up to five peopleYouPhoning them / the tracker texting them after a theft or crashContract; see §6
Rides, saved places and their photos, a 3D model you uploadYouThe features you use them forContract
Buddy Beacon: your display name and live position, shared with the riders you approveYou, when you start or join a beaconRiding togetherContract
Share links: your bike's recent trail, visible to anyone holding the linkYou, when you create oneLetting someone follow a rideContract
Push notification subscription (an endpoint issued by your browser's push service)Your browser, when you allow notificationsDelivering alertsContract
A record of the alerts, calls and messages sent to youOur serverShowing you what happened, and proving an alert was or was not deliveredLegitimate interest
IP address and request details in server logsYour browser, every requestSecurity and abuse preventionLegitimate interest
Waiting-list email addressYou, on the presentation site, if you ask to be told about the launchWriting to you once when the product goes on saleConsent (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

DataKept for
Tracker positions (location history)[ a number of days — see S33-note.md: the current default is "for ever" ]
Alert log365 days
Motion events360 days
Tilt data90 days
Tracker connection logs30 days
Matched routes (the road-snapped version of your rides)10 years, or until your account is deleted
Share linksuntil they expire (1, 6 or 12 hours)
Buddy Beaconsuntil they end (2 hours to 7 days)
Server request logs (IP addresses)14 days (rotated nightly by the web server)
Everything else in your accountuntil you delete your account
Waiting-list email addressuntil we write to you about the launch, or until you ask us to remove it
Backupsnightly, the last 14 kept; snapshots taken before a database change, for 30 days

5. Deleting your account and getting a copy of your data

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

RecipientWhat they receiveWhere
[ 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 placedUSA — [ Standard Contractual Clauses / Data Privacy Framework ]
Google LLC — Geocoding APICoordinates of your stops and rides, to turn them into street namesUSA — see S33-note.md, this is being replaced
Your browser's push service (Google, Apple or Mozilla)An encrypted alert payload and the subscription endpointvaries
OpenFreeMap (map tiles)Your IP address and the map area you view[ country ]
OpenStreetMap NominatimCoordinates, when you look up a buddy's or a pin's street, and your IP addressEU (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 browserEU region (Frankfurt)
HostingAll 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. ]