Trancemoto Privacy Policy
Contents
- 1. Who we are
- 2. Who can use Trancemoto
- 3. The data we collect
- 4. Why we use your data, and our legal bases
- 5. Who we share data with
- 6. Other cases where data is shared
- 7. International transfers
- 8. Statistics about motorcycle models
- 9. How long we keep data
- 10. Your rights
- 11. Deleting your account
- 12. Security
- 13. Your choices in the app
- 14. Apple-specific terms (iOS)
- 15. Changes to this policy
- 16. Contact
Effective date: TO DO: effective date
Last updated: TO DO: date of last change
Version: TO DO: version, e.g. 1.0
This policy explains what personal data the Trancemoto app collects, why, who we share it with, how long we keep it, and the choices and rights you have. It applies to the Trancemoto app for Android and iOS (package com.trancemoto.garage) and to the pages at trancemoto.com that link to it.
Plain-language summary:
- We collect what the app needs to work: your account, your bikes, your rides, your fuel and service records, your trips, and what you ask the AI.
- Ride tracking records your precise location, including in the background while a ride is recording.
- We use service providers to run the app, including AI providers. Each one is listed below with what it receives.
- We do not sell your personal data. We do not share it for targeted or cross-context behavioural advertising. The app contains no advertising.
- Your trip journal is never sent to an AI provider.
- You can delete your account in the app or from the web. Deletion is final after 7 days.
1. Who we are
Trancemoto is operated by TO DO: legal entity name — e.g. "Saswat Pati, sole proprietor" or a company name, TO DO: registered postal address ("Trancemoto", "we", "us").
We are the controller (GDPR) and the Data Fiduciary (India's Digital Personal Data Protection Act, 2023) for the personal data described here.
| Purpose | Contact |
|---|---|
| Privacy questions and requests | TO DO: privacy@trancemoto.com — confirm; the wiki says privacy@trancemoto.app |
| Account and support | support@trancemoto.com |
| Grievance Officer (India) | TO DO: name, email, postal address |
| EU representative (GDPR Art. 27) | TO DO: name and address, or remove if not appointed |
| UK representative (UK GDPR Art. 27) | TO DO: name and address, or remove if not appointed |
2. Who can use Trancemoto
You must be 18 or older to create an account. The app asks you to confirm this when you set up your profile, and our server refuses a profile without that confirmation. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, write to us and we will delete it.
3. The data we collect
We collect data in three ways: you give it to us, the app records it while you use it, and our service providers return it to us.
3.1 Account and sign-in
You sign in with Google or Apple. We do not offer password sign-in.
- From Google: your name, email address and profile picture (the "profile" and "email" scopes), and a Google account identifier.
- From Apple: your email address (or an Apple private-relay address if you choose to hide yours) and your name, if you share it, and an Apple account identifier.
- We create a random account ID for you. Most of your records are linked to this ID.
- We record which version of our Terms you accepted, and when.
- Our sign-in provider keeps security logs of sign-in events, which include IP addresses.
3.2 Your profile
Required: your name and your confirmation that you are 18 or older.
Optional — you choose whether to add them:
- phone number, gender, country, currency, distance units, riding styles, profile photo;
- a public alias (a nickname other riders use to invite you to group rides);
- blood group, emergency contact name and emergency contact number.
Blood group is health information. Your emergency contact is another person's data. Add them only if you want them in the app, and only with your contact's agreement. TO DO: confirm the in-app wording that collects explicit consent for blood group — GDPR Art. 9(2)(a)
3.3 Your bikes
Make and model, nickname, purchase year, odometer readings, fuel type and tank size, licence plate, insurance and pollution-certificate (PUC) expiry dates, last service date and odometer, and photos of your bike.
3.4 Rides and location
When you record a ride, the app collects your precise location (GPS) about once per second, with time, speed and altitude. It keeps recording while the app is in the background or the screen is off, and it shows a notification while it does so. Location is collected only while a ride is recording TO DO: confirm no other background location use.
From that we store: the route, distance, duration, speeds, elevation, stops, start and end place names, a map image of the route, and ride statistics. You can add a description, comments and photos. Ride photos you attach may carry the place they were taken.
The app also reads your phone's motion sensors and compass to show live instruments such as lean angle and heading. These readings are processed on your phone and are not sent to us. TO DO: remove the developer sensor-logging feature before release — see OPEN-QUESTIONS OQ-14 — or disclose it here
Some features use your current location once, when you ask: for example, finding the fuel station you are standing at, or tagging a journal entry or a trip event with where you are.
3.5 Fuel and service records
- Fuel logs: date, odometer, quantity, price, total cost, currency and exchange rate, fuel grade, station name, address and location, notes, and an optional photo of the receipt.
- Receipt scanning: text is read from the receipt photo on your phone (Google ML Kit, on-device). Only that text is sent to our AI provider to fill in the form.
- Service logs: date, workshop, odometer, work done, parts, costs, currency, notes, and optional invoice photos or PDFs.
Receipts and invoices can show other details, such as a station's or workshop's address, a tax ID, your licence plate or your name. We store the image as you give it to us.
3.6 Trips and journal
Multi-day trips: name, dates, bike, budget and currency, plans and routes, trip events (fuel stops, expenses, places, photos), progress and summaries, and weather forecasts for your planned stops.
Trip journal: text, photos, voice recordings, mood tags, tags, and the place an entry was made (if you allow it). The journal is never sent to any AI provider. If you tag a journal entry with a location, its coordinates are sent to a geocoding provider to turn them into a place name (section 5).
3.7 AI features
- AI chat: your messages and the assistant's answers. Photos, PDFs and voice notes you attach. Voice notes are transcribed; we keep the transcript. To answer you, the assistant can read your bikes, fuel logs, service history, maintenance schedule, ride summaries, trip list and past diagnoses.
- AI diagnosis: the symptoms you describe, the questions and answers, the likely causes and urgency, and what you did next.
- Service invoice scanning: the invoice image or PDF.
- AI trip planner: your trip request (start, destination, dates or season, must-visit places, bike, fuel range, preferences) and the plan produced.
- Feedback: ratings and reasons you give on AI answers.
- Usage records: for each AI request we log the feature, the model, token counts and the cost. This is how we meter AI credits and enforce fair use.
3.8 Group rides
If you join a group ride: your membership, role and status, your alias, the messages and media you post in the group chat, and — only if you choose to share it for that ride — your live location (position, heading, speed and accuracy). Section 6 explains who sees what.
3.9 Subscriptions and AI credits
Your plan (Free or Pro), billing period, expiry date, AI credit balances, and your purchase history (products, dates, renewals, cancellations, refunds). We never see your card or bank details — the app store (Google Play or the App Store) takes the payment.
3.10 Notifications and devices
A push-notification token for each of your devices, the platform, app version, language and time zone. Your notification settings, quiet hours, and the notifications we sent you. If you turn "News & offers" on or off, we record when, as proof of your choice.
3.11 Diagnostics and technical data
- Crash reports (Firebase Crashlytics): what failed, device model, operating system, app version, and an installation identifier.
- Performance data (Firebase Performance Monitoring): app start time and screen rendering timings, with device and app details. TO DO: keep or remove this SDK — see OQ-20
- Ride error logs sent by the app when ride recording hits a problem.
- Connectivity checks: the app contacts a Google and a Cloudflare test address to tell whether you are online. These receive your IP address like any web request.
- Server logs: our hosting and edge-function logs record requests, errors and IP addresses.
- In-app search queries, kept for 90 days to improve search, without your account ID.
3.12 When you contact us
Your email address and what you write to us.
3.13 Data we do not collect
We do not use advertising IDs, we do not run advertising or marketing analytics SDKs, and we do not read your contacts, calendar, SMS or call logs.
4. Why we use your data, and our legal bases
| What we do | Data used | GDPR / UK GDPR basis | India (DPDP Act) |
|---|---|---|---|
| Run your account and the features you use: garage, rides, fuel and service logs, trips, journal, reminders | Sections 3.1–3.6, 3.10 | Contract (Art. 6(1)(b)) | Consent (§6) |
| Record rides with precise and background location | Section 3.4 | Contract; you also grant the location permission | Consent |
| AI chat, diagnosis, scanning and trip planning, when you use them | Sections 3.5, 3.7 | Contract | Consent |
| Meter AI credits, enforce fair use, stop abuse of free credits | Section 3.7 usage records, 3.9 | Contract; legitimate interests in preventing fraud and abuse (Art. 6(1)(f)) | Consent; legitimate uses where §7 applies |
| Subscriptions and purchases | Section 3.9 | Contract; legal obligation for tax records (Art. 6(1)(c)) | Consent; legal obligation |
| Group rides, live location sharing | Section 3.8 | Contract for membership and chat; consent for live location (Art. 6(1)(a)) | Consent |
| Blood group (optional) | Section 3.2 | Explicit consent (Art. 9(2)(a)) | Consent |
| Service notifications (reminders, alerts, account messages) | Section 3.10 | Contract | Consent |
| "News & offers" notifications | Section 3.10 | Consent; off by default | Consent |
| Crash reports and performance data, to fix problems | Section 3.11 | Legitimate interests in a working, secure app | Consent TO DO: counsel to confirm the Indian basis |
| Security, preventing misuse, enforcing our Terms | All, as needed | Legitimate interests; legal obligation | Legitimate uses (§7) where applicable |
| Model-level statistics (see section 8) | Section 3.3, 3.4, 3.5 | Legitimate interests, with a right to object | Consent only (the "Usage analytics" setting) |
| Comply with law, answer lawful requests, defend legal claims | As needed | Legal obligation; legitimate interests | Legal obligation |
Where we rely on consent, you can withdraw it at any time in the app's settings or by writing to us. Withdrawal does not affect what we did before it.
Where we rely on legitimate interests, you can object (section 10).
We do not make decisions about you that have legal or similarly significant effects based solely on automated processing.
5. Who we share data with
We do not sell personal data. We share it only with the service providers below, who process it for us, and in the cases listed in section 6.
| Provider | What it does for us | What it receives |
|---|---|---|
| Supabase | Hosts our database, sign-in, file storage and server functions | All the data in section 3. Region: India (Mumbai, AWS ap-south-1) |
| Google — Firebase | Push notifications (Cloud Messaging), crash reports (Crashlytics), performance monitoring | Device push token and notification content; crash and performance data (section 3.11) |
| Google — Sign-In | Sign in with Google | Your sign-in request |
| Google — Maps Platform | Shows maps in the app; place search in the trip planner and trip forms (Places Autocomplete) | Map views requested by your device; the text you type in those place searches |
| Google — Gemini API | Reads fuel-receipt text into a form; writes short maintenance tips; helps build trip plans | Receipt text (not the photo); your bike's service item; your trip request |
| Google Play / Apple App Store | Payments, subscriptions, refunds | Handled under their own privacy policies. They tell us about your purchases through RevenueCat |
| RevenueCat | Manages subscriptions and AI credit balances | Your random account ID, purchase history and credit balances. We do not send it your name or email |
| OpenAI | AI chat, voice-note transcription, AI diagnosis, service-invoice scanning, AI trip planning, and search embeddings | Your chat messages and attachments (photos, PDFs, voice notes); the bike and record data the assistant reads to answer you; diagnosis conversations; invoice images; trip requests. For diagnosis, also your random account ID, for abuse monitoring |
| Perplexity | Web search inside AI chat; research for AI trip planning | Chat: a search query about a bike or topic. Queries that look like a licence plate, email, phone number, VIN or long number are blocked before sending. Planner: your trip request (start, destination, dates or season, must-visit places, bike name, fuel range) |
| Geoapify (OpenStreetMap data) | Place names for rides, ride map images, nearby fuel stations, place search, route checks | Coordinates of your ride's start and end and its route; your location at a fuel stop; places you search for; trip plan points |
| OpenCage | Place names | Coordinates of a journal entry you tagged; fuel station addresses |
| Open-Meteo | Weather forecasts for active trips | Names or coordinates of your planned overnight stops |
| OpenStreetMap Foundation — Nominatim | Place names when you add a trip event, called directly from your phone | Your current coordinates when you tag a trip event with your location; a planned stop's name. TO DO: keep or replace — see OQ-18 |
| GoDaddy (email relay) | Sends account emails (for example, deletion confirmations) | Your email address and the email content |
| flagcdn.com | Shows country flags during profile set-up | Your IP address, like any image request |
Our providers process data only to provide their service to us, under their terms and data-processing agreements. TO DO: confirm a DPA is in place with each provider listed — OQ-16
What AI providers keep. We send AI providers only what a request needs. Their retention is set by their own terms:
- OpenAI does not use API data to train its models by default. It may keep API inputs and outputs for up to 30 days to detect abuse. AI chat requests are sent with storage turned off. AI trip-planner requests are stored by OpenAI so that long-running plans can be collected TO DO: confirm retention of stored Responses — OQ-17.
- Google Gemini API: TO DO: confirm we use the paid tier. On the paid tier Google does not use prompts to improve its products and keeps them for a limited period for abuse detection. On the unpaid tier Google may use them to improve its products and humans may review them — that must not be used for personal data. OQ-15
- Perplexity, chat web search: Perplexity's terms for its Search service let it keep the queries it receives and use them to improve its products, and its zero-retention commitment does not cover Search. So the assistant sends only a short query about a bike or topic, and the app blocks any query that looks like a licence plate, email address, phone number, VIN or long number before it leaves your phone. No account ID, records or notes are attached to a query.
- Perplexity, AI trip planning: TO DO: retention for the Agent API is not confirmed — OQ-16
AI output. AI answers are generated by machine learning models. They can be wrong. See our Terms of Service.
6. Other cases where data is shared
- Other riders in a group ride see your alias, your role and status in the ride, whether you are sharing location, and the messages and media you post. If you choose to share your live location for that ride, members see your position, heading and speed while the ride is active. Live positions are deleted when the ride ends, when you leave, or when you stop sharing, and in any case within about 24 hours.
- Riders searching for someone to invite to a group ride can find you by your alias. TO DO: the "Discoverable by alias" setting is not yet enforced by the server — fix before publication or remove this setting's promise — OQ-13
- Public file links. Some files are stored at web addresses that are long and hard to guess but are not protected by sign-in: anyone who has the exact link can open the file. Today this covers fuel receipt photos, service invoices, trip and journal photos and journal voice recordings, ride map images, and profile and bike photos. We do not publish these links. TO DO: we are moving these files to private storage — update this paragraph when done — OQ-10 AI chat attachments are already private.
- Legal reasons: when the law requires it, to answer a valid legal request, to protect the rights, safety or property of riders, the public or us, or to enforce our Terms.
- Business transfers: if Trancemoto is sold, merged or reorganised, data may pass to the new owner, who must honour this policy or tell you before anything changes.
- With your instruction: for example, when you share a trip card or a ride outside the app.
7. International transfers
We and our providers process data in several countries, including India (where our database is hosted, in Mumbai), the United States (Google, OpenAI, RevenueCat, Perplexity and others) and the European Union. Where data leaves the EU, the UK or India, we rely on: an adequacy decision where one exists; the European Commission's Standard Contractual Clauses (and the UK Addendum) in our providers' data-processing terms; and for India, the transfer rules under §16 of the DPDP Act. TO DO: counsel to confirm the transfer mechanism for each provider — OQ-07
You can ask us for a copy of the safeguards we use.
8. Statistics about motorcycle models
We may produce aggregated statistics about motorcycle models — for example typical fuel economy, service intervals and parts life — from data across many riders. Each statistic combines at least 5 different riders and 5 different bikes, and contains no route, location, date, plate or free text. These statistics do not identify you and are kept after you delete your account. We commit not to try to re-identify anyone from them.
Your data is included only while the Usage analytics setting (Settings → Privacy → Diagnostics) is on. Turn it off at any time; your data then stops being included the next time the statistics are rebuilt. TO DO: this setting is currently ON by default; it must be OFF by default before we rely on it as consent — OQ-11
9. How long we keep data
We keep your data while your account exists, unless a shorter period is listed. When you delete your account, we erase it as section 11 describes.
| Data | How long |
|---|---|
| Account, profile, bikes, rides, fuel and service records, trips, journal, AI conversations, files | Until you delete them or your account |
| A bike you archive | Kept with its records until you restore it or choose "Erase all data for this bike". Erasing a bike deletes its fuel, service, maintenance and AI diagnosis records; your rides are kept |
| Group-ride live location | Deleted when the ride ends, when you leave or stop sharing; anything older than 24 hours is deleted hourly |
| In-app notifications and their delivery records | 90 days after they were created, unless still active; expired ones 30 days after expiry |
| AI trip-plan jobs (the working record, not your saved plan) | 30 days after the job finishes |
| Credit and fair-use security events | 30 days |
| In-app search queries (no account ID) | 90 days |
| AI usage records (feature, model, tokens, cost) | TO DO: 12 months intended; no automatic deletion is configured yet — OQ-30, and erased with your account |
| Record of a completed account deletion (random account ID, a one-way hash of the email, dates, counts — no content) | 3 years |
| Your email address after account deletion | Erased when the final "account deleted" email is sent |
| Backups | TO DO: backup period — depends on the hosting plan; today's plan may keep no backups — OQ-08 |
| Purchase records held by Google, Apple | Under their own policies and tax law |
| Data held by AI and map providers | Under their terms (section 5) |
10. Your rights
You have the rights below wherever the law gives them to you. We extend the core rights — access, correction, deletion, portability and withdrawal of consent — to all riders.
How to exercise them: write to TO DO: privacy email from the email address on your account. We may ask you to confirm your identity. We do not charge a fee, except where the law allows for requests that are clearly unfounded or excessive.
Response times: we reply within one month (GDPR, extendable by two months for complex requests, and we will tell you), within 45 days (US state laws, extendable once by 45 days), and within TO DO: committed period — at most 90 days for grievances under India's DPDP Rules.
Rights for everyone
- Access: ask what we hold about you and get a copy.
- Portability: get your data in a structured, machine-readable format (JSON). TO DO: the in-app "Export my data" button currently asks you to email us — OQ-27
- Correction: most of your data can be edited in the app. For the rest, write to us.
- Deletion: delete individual records in the app, erase a bike's data, or delete your whole account (section 11).
- Withdraw consent: turn settings off in the app, or revoke the location, microphone, camera, photo or notification permission in your phone's settings. Some features stop working without them.
EU, EEA and UK
You also have the right to restrict processing, to object to processing based on legitimate interests (including the model statistics in section 8), and to complain to your data-protection authority. In the UK, that is the Information Commissioner's Office. We would like the chance to help first.
India
Under the DPDP Act you may access a summary of your data and the processing, correct, complete, update or erase it, nominate another person to exercise your rights if you die or become unable to, and seek redress of grievances. Write to our Grievance Officer (section 1) first. If you are not satisfied with our answer, you may complain to the Data Protection Board of India. You may also give and manage consent through a registered Consent Manager once such managers operate; we will accept requests that reach us that way. TO DO: counsel to confirm the Consent Manager wording
United States (including California, Colorado, Connecticut, Virginia, Texas and other states with privacy laws)
- Know what personal information we collect, use and disclose (sections 3–6 list the categories, sources, purposes and recipients).
- Delete and correct your personal information.
- Opt out of sale, sharing and targeted advertising: we do not sell personal information, we do not share it for cross-context behavioural advertising, and we do not use it for targeted advertising. There is nothing to opt out of.
- Sensitive personal information: we collect precise geolocation (for ride recording, location tags and group rides you join) and, if you add it, blood group. We use it only to provide the features you ask for, not to infer characteristics about you.
- Appeal: if we refuse a request, you may appeal by replying to our decision. We will answer within the time your state's law sets. If we still refuse, you may contact your state Attorney General.
- Authorised agents may make requests for you with your written permission; we may verify your identity directly.
- No discrimination: we will not treat you differently for exercising these rights.
11. Deleting your account
You can delete your Trancemoto account at any time from Settings → Privacy → Danger zone → Delete account. When you confirm, your account is locked immediately: you are signed out everywhere and no one can sign in to it. We email you to confirm the request.
You have 7 days to change your mind. Reply to that email from the same address and we will restore your account as it was. You can also ask us for a copy of your data during those 7 days.
After 7 days we permanently delete everything in the account: your profile, bikes, rides and GPS tracks, fuel and service history, trips, journal entries, photos, AI conversations, notifications, devices, settings, and your subscription and AI-credit record at RevenueCat. Unused AI credits are lost. We then send one final email to confirm, and delete your email address with it. This cannot be undone.
Deleting your account does not cancel a Trancemoto Pro subscription. Cancel it first in Google Play (or the App Store) → Subscriptions, or the store may keep charging you.
If you hosted a group ride, that ride is deleted with your account, including other members' messages in it.
Some things survive for a limited time: TO DO: backups — OQ-08; the records of providers that processed your data while you used the app, under their own terms (section 5); and a record that a deletion took place — a random ID, a one-way hash of your email, dates and row counts, never your data — for three years, so that we can show we honoured your request. Statistics already produced under section 8 contain no personal data and are not affected.
In rare cases the law requires us to keep data despite a deletion request, for example while a legal claim is open. If that applies to you we will tell you when you ask.
If you cannot use the app, request deletion at trancemoto.com/delete-account or write to support@trancemoto.com from the address on your account.
12. Security
We protect your data with measures suited to its sensitivity:
- all traffic between the app, our servers and our providers is encrypted in transit (HTTPS/TLS);
- database access rules restrict each rider to their own records;
- our servers check who you are on every request;
- payment details never reach us;
- access to production systems is limited to the maintainer.
No system is perfectly secure. If a breach affects your personal data, we will notify you and the authorities as the law requires — under GDPR, the supervisory authority within 72 hours where required, and under India's DPDP Rules, the Data Protection Board and affected users without delay.
Section 6 describes files that are stored at unprotected links today. TO DO: storage encryption at rest — confirm with the hosting provider before stating it
13. Your choices in the app
- Settings → Privacy: Discoverable by alias; Share riding stats; Share location by default (pre-enables live location when you join group rides — off by default); Usage analytics; Crash reports. TO DO: the Crash reports switch does not yet turn off crash reporting — OQ-12
- Settings → Alerts: turn each kind of notification on or off; quiet hours; "News & offers" (off by default).
- Phone settings: location, background location, microphone, camera, photos and notifications.
- Group rides: you choose for each ride whether to share live location, and you can stop at any time.
14. Apple-specific terms (iOS)
- If you sign in with Apple and choose Hide My Email, we only receive an Apple relay address. Emails we send go through Apple's relay.
- When you delete your account, we TO DO: will revoke the Sign in with Apple token, as Apple requires — not built yet, OQ-28.
- The App Store's privacy labels for Trancemoto summarise this policy. If they differ, this policy explains the detail.
15. Changes to this policy
We will update this policy when the app or the law changes. We will change the "Last updated" date above. For material changes we will tell you in the app or by email before they take effect, and ask for your consent again where the law requires it.
16. Contact
TO DO: legal entity name TO DO: postal address Privacy: TO DO: privacy email Support: support@trancemoto.com Grievance Officer (India): TO DO