Privacy Policy
Last updated: April 27, 2026
Trakoras ("we", "us", "our") is a self-hosted live GPS tracking app for
vehicles you own or control. This policy explains exactly what data we
collect, why, where it lives, and how you delete it.
1. Data we collect
- Precise and approximate location — latitude, longitude, speed, heading, accuracy, and timestamp. Sampled in the background by the Trakoras app installed on a device you own. Used to display the device on your private dashboard, build trip history, and trigger geofence and movement alerts you opt into.
- Email address — for one-time-passcode (OTP) sign-in. We never receive a password.
- Stable device identifier — Android
Settings.Secure.ANDROID_ID, used only to link a specific phone to your account so reinstalling the app doesn't break the link.
- Firebase Cloud Messaging (FCM) registration token — required to deliver push notifications to your dashboard phone. Tied to your account.
- Subscription plan tier — "free", "pro", or "fleet" — to enforce vehicle-count limits.
- We do not collect contacts, photos, microphone, camera, SMS, call logs, or any other sensors.
2. How we use it
- Show your vehicles in real time on your private dashboard.
- Compute trip history (start/end, distance, stops, driver score) on the server.
- Detect movement, overspeed, and geofence enter/exit events server-side, then send a push notification via Firebase Cloud Messaging to your registered devices.
- Generate share links you choose to send to others, with optional PIN and expiry.
- Optionally send geofence alerts to a Telegram chat you configure (only if you set this up).
- We do not sell, rent, or share your data with advertisers or data brokers.
3. Where data is stored
Trakoras is self-hosted. The instance you signed up on is operated by
whoever runs the server you connected to. There is no central
Trakoras-owned database aggregating data across operators.
Data is encrypted in transit (HTTPS) between your device and the
server. Server-side storage is on a private SQL database not exposed
to the internet.
4. Third-party processors
The following services receive specific data to provide their function:
- Google Firebase Cloud Messaging (push notifications) — receives your FCM token plus the title/body of any alert sent to you.
- Google Play Billing — handles subscription purchases. We never see your card details. We receive a purchase token from Play to verify your entitlement.
- Email service (Gmail SMTP) — receives your email address and the OTP code, only at sign-in time, to deliver the OTP message.
- OpenStreetMap tile servers — serve the map tiles your app or the public viewer page renders. They see the IP address of the requester and the tile coordinates being viewed.
5. Retention
- Location samples are retained for 30 days by default and automatically deleted after that window. The server operator can adjust this (see
RETENTION_DAYS).
- OTP codes are deleted on use or after 5 minutes, whichever comes first.
- Session tokens expire on logout or after server-configured timeout.
- Account email, vehicle list, plan tier, geofence, and FCM tokens are retained until you delete your account (see Section 7).
6. Sharing & access control
A vehicle's location is only visible to (a) the signed-in account that
owns it, and (b) anyone who possesses a share link you actively
generated. Share links are time-limited (1 hour to 1 month), can carry
an optional PIN, and can be revoked instantly from the app.
7. Your rights — accessing and deleting your data
- View & rename: every vehicle, share link, geofence, and trip is visible and editable from the app.
- Per-vehicle deletion: long-press or tap the ⋮ button on any vehicle in the list → Remove vehicle. This deletes the vehicle, its location history, share codes, geofence, and pair codes.
-
Full account deletion (irreversible): Menu → Danger
zone → Delete account → type DELETE → Delete forever. This permanently
erases your account email, all your vehicles, all location history,
all share links, all geofences, all FCM tokens, all sessions, and
your plan record. There is no recovery — sign-up creates a fresh
free-tier account.
- You may also email ydeonia@gmail.com to request deletion if the in-app flow is unavailable to you for any reason.
8. Security
- All client-server connections use HTTPS.
- Session tokens and share-link PINs are stored as hashes (SHA-256, HMAC) — never plaintext.
- OTPs are single-use, expire in 5 minutes, and are rate-limited per IP.
- The "Stop tracking" PIN configured on the vehicle phone is stored locally on that phone with a per-install salt, never sent to the server.
- Plan changes are written to an audit log on the server.
9. Background location and foreground service
The Trakoras Android app uses a foreground service to sample location
while the screen is off. Android requires a persistent notification
while a foreground location service is running — that's the "Tracking
active" notification you see whenever tracking is on. It cannot be
hidden while tracking; you can stop it from the app at any time
(PIN-protected).
Background location data is used only for the purposes listed in
Section 2. It is not used for advertising, analytics, or shared with
third parties beyond the processors listed in Section 4.
10. Children
Trakoras is not directed at children under 13 and should not be used
to track minors without parental consent. We do not knowingly collect
data from children under 13.
11. Changes
We may update this policy. Material changes will be reflected on this
page with a new "Last updated" date. Continued use after a change
means you accept the updated terms.
12. Contact
Questions, complaints, or deletion requests? Email
ydeonia@gmail.com.