Privacy Policy

This Privacy Policy describes how Motolog ("we", "us", or "our"), developed by Satrujit Behera, collects, uses, and protects information. It covers two separate products:

• The Motolog Android application (package in.satrujit.tripper_bridge)
• This marketing website at https://motolog.satrujit.in (beta access, downloads, and legal pages)

The Android app and the website do not use the same analytics stack. PostHog is used on this website only — not inside the mobile app.

1. Summary

Motolog is designed to keep your ride history on your device by default. We do not sell your personal information. Optional Google Drive backup is entirely under your control and stores data in your own Google account.

If you use group riding (live location sharing or voice intercom), you choose to join a ride room and data is shared in real time with other participants in that room through our group relay service. That relay holds session data in memory only while a room is active — it is not used as long-term ride storage.

2. Information we collect

2a. Mobile application (Android app)

The following applies when you install and use the Motolog app on your phone. The app does not include PostHog or similar third-party marketing analytics.

• Location data — GPS coordinates for navigation, trip recording, and cluster display. Location may be collected in the background while navigation or trip recording is active.
• Bluetooth data — Information about paired motorcycle clusters (device names, MAC addresses, connection state) to maintain pairing and navigation.
• Ride & app data stored locally — Trip routes, speed samples, settings, saved locations, and diagnostics stored in on-device SQLite databases.
• Phone state (optional) — If permitted, call state to show incoming-call alerts on supported clusters. We do not record call audio or message content.
• Google account data (optional) — If you choose Google Drive sync, we access your Google account email, profile information, and your private Drive App Data folder to back up and restore rides and settings you explicitly sync.
• Diagnostic logs — If you export or share logs for support, those logs may contain technical events, device identifiers, and app state. You choose when to share them.
• Group ride & intercom data (optional) — If you create or join a group ride, we process a display name (or rider label), a rider ID, room join credentials, and — when you turn location sharing on — real-time GPS coordinates, heading, speed, and status flags (such as SOS, follow-me, sharing, battery-low, or stationary). This data is sent to our group relay service and distributed to other participants in the same room.
• Voice intercom audio (optional) — If you use push-to-talk or open-mic group voice, the app accesses your microphone and transmits encoded audio in real time to other participants in your room via WebRTC. We do not design this feature to store voice recordings on the relay server.

2a-i. Regional ride analytics (anonymous, aggregate only)

After a ride finishes, the app sends a small, separate set of numbers to our servers so we can see, in aggregate, where and when Motolog is being ridden — how many rides happened in a city this month, what times of day people tend to ride, how far. This is not the same data as your on-device trip history, and it is never enough on its own, or combined with anything else we hold, to reconstruct one specific ride or identify who took it. What is sent, and what is deliberately left out:

• A rounded location, not your route — one coordinate near the middle of the ride, rounded to roughly a kilometre. Your actual GPS track never leaves your device for this purpose.
• An hour and a calendar day, not a timestamp — "around 6pm on 15 October, in your own local time zone" — not the precise minute and second a ride started or ended. A day/hour bucket is shared by thousands of other rides; a to-the-second timestamp is closer to unique to you, which is exactly the kind of detail that lets separate records be re-linked back into one person's pattern of movement. We don't collect it for this purpose in the first place.
• Distance and duration — how far and how long the ride was, as plain numbers.
• A random installation ID, not you — a UUID generated on your device that identifies this app install, not your name, email, phone number, or Google account. If you've never connected Google Drive, there is nothing in this data set that connects it to a real identity at all.

What we store from this is a set of running counters — "N rides, on this day, in this city, lasting this many minutes in total" — not a log of individual rides. The original message your phone sends for each ride is used once, to update those counters, and is not kept afterward as a standalone record. There is no per-ride history sitting on our servers to search, export, or hand over, even if we wanted to — that's a property of how the data is thrown away after aggregating, not just a policy we've chosen to follow. This is also why we can say with confidence that this data cannot be used to fingerprint or single out an individual rider: the pieces that would make that possible — an exact route, an exact timestamp, a real identity — are the ones we never collect for this purpose.

2a-ii. App language and country (anonymous, aggregate only)

Separately from ride analytics, the app periodically reports which language it's currently displaying and a coarse country, so we can understand our audience by language and region — for example, how many installs are using the app in Spanish, or how many are in a given country. What is sent:

• A language code — whichever of the app's supported languages is currently active, whether that follows your phone's system language automatically or you've picked one explicitly in Settings.
• A country, not a location — normally derived from your phone's locale setting alone, with no GPS request involved. If location permission has already been granted for another feature (like ride recording) and a recent position happens to be available on the device, that may be used to resolve country instead — never a fresh GPS fix requested for this purpose, and never anything more precise than the country.
• The same random installation ID used for ride analytics above — not your name, email, phone number, or Google account.

This is sent at most once a day, plus immediately if you change your language in Settings, and simply overwrites our previous record for that install — it is a current snapshot, not a history of every language or country you've ever used. If notifications are enabled, your device may also be grouped into broad categories (such as language, region, or subscription tier) using the same standard app-notification mechanism most apps use, so we can send announcements relevant to you — this reaches devices by category, not by individually addressing you.

2b. Marketing website only (motolog.satrujit.in)

The following applies when you visit https://motolog.satrujit.in in a browser. It does not apply to normal use of the installed Android app.

• Firebase App Distribution (beta access) — When you click "Get Early Access", you are redirected to Firebase App Distribution (operated by Google). We do not collect your name or email on this website. Firebase/Google handles sign-in, tester registration, and build delivery. Your use of Firebase App Distribution is governed by Google's Privacy Policy.
• PostHog website analytics — We use PostHog (EU-hosted project) on this website to understand how visitors use our pages. PostHog may collect page views, button clicks, technical device and browser metadata, and approximate location derived from IP. PostHog is not embedded in the Android application.

3. How we use information

• Provide navigation to your motorcycle cluster over Bluetooth
• Record and display your ride history and analytics
• Maintain background reconnection to paired devices
• Back up or restore your data when you enable Google Drive sync
• Respond to support requests you initiate
• Improve reliability, security, and performance
• Relay live location, SOS alerts, and voice audio between riders who have joined the same group ride room
• Measure website traffic on motolog.satrujit.in via PostHog (page views and button clicks only — not app usage)

4. Third-party services

The Android app and website rely on different providers. PostHog and Vercel apply to the website only.

• Google Sign-In & Google Drive (app) — Optional backup; governed by Google's Privacy Policy
• Mapbox (app) — Map tiles and routing when navigation is used; governed by Mapbox's Privacy Policy
• Group ride relay infrastructure (app) — A Motolog-operated relay used when you join group rides. It receives real-time location updates (UDP/HTTP), distributes updates to other room participants (SSE), and routes live voice audio (WebRTC, including TURN when needed for NAT traversal). Session state is held in server memory while rooms are active.
• Firebase App Distribution (website) — When you click "Get Early Access" on this site, you are redirected to Firebase App Distribution (Google). Your sign-in and tester data are governed by Google's Privacy Policy
• Vercel (website) — Hosts this marketing website
• PostHog (website only) — Product analytics for motolog.satrujit.in. Not used in the Android app. Data is processed under PostHog's EU infrastructure. Governed by PostHog's Privacy Policy. You can use browser tracking protections or opt out of non-essential cookies where your browser and jurisdiction allow.

Trip logs and ride analytics remain on your phone unless you enable Google Drive backup. Group ride data is shared only with participants in a room you join and is processed by the relay for real-time coordination — not as permanent cloud ride storage.

5. Data retention

• On-device data is kept until you delete it, uninstall the app, or clear app storage.
• Google Drive backups remain in your Google account until you delete them.
• PostHog website analytics data is retained according to PostHog's project settings and policies (website visitors only).
• Group ride relay data (live locations, room membership, and voice routing state) is kept in memory only while a room is active and is discarded when the room ends or times out. Server logs, if enabled for operations or security, may retain limited technical metadata for a short period.

6. Data sharing

We do not sell, rent, or trade your personal information. We share data only when you direct us to (for example, exporting a trip or enabling Google backup), when you join a group ride (in which case location and voice data you enable are shared with other participants in that room), when required by law, or with service providers that help us operate the website and group relay infrastructure.

7. Your choices & rights

• Grant or revoke Android permissions in system settings
• Disable Google Drive sync and sign out at any time
• Delete local trips and saved locations inside the app
• Leave a group ride, disable location sharing, or mute your microphone at any time
• Choose whether to share your live location with your group
• Uninstall the app to remove local data from your device
• Contact Satrujit Behera at beherasatrujit12@gmail.com for any privacy questions or data requests

8. Security

We use reasonable technical measures to protect information processed by the app and website. No method of storage or transmission is 100% secure. You are responsible for securing your device and Google account credentials.

9. Children

Motolog is not directed to children under 13, and we do not knowingly collect personal information from children.

10. International users

If you use Motolog from outside India, your information may be processed in countries where our service providers operate, including the United States (Google, Mapbox, Vercel) and the European Union (PostHog website analytics).

11. Changes

We may update this policy from time to time. We will post the revised version on this page and update the "Last updated" date.

12. Contact

For privacy questions or requests, contact Satrujit Behera at beherasatrujit12@gmail.com.