Privacy & data
How the current HypeTrain app handles your information.
Updated
A shared plan, not a location tracker
HypeTrain does not ask for continuous GPS, contacts or a social graph. Directions open an external maps app. Boarding expresses interest, not confirmed attendance. Attendance feedback is voluntary and is not proof of your location.
Your private identity
The connected app creates an anonymous Firebase identity when you board, save preferences, report attendance or record a revealed route view. No name, email or public profile is required. Browsing an unrevealed train does not create an account.
An identity can have one active boarding per daily train. It is tied to this browser or app installation; separate devices and cleared storage can create separate identities. Cross-device person verification is not implemented.
To limit automated boarding, we temporarily keep action counters and a secret-keyed network identifier that changes daily. IPv6 addresses are grouped by network. These abuse-control records expire after 48 hours and are removed by background cleanup; we do not store raw IP addresses in these records. Shared networks may temporarily reach the same boarding limit. Provider connection logs have their own retention policies.
Interest and attendance are separate
We store daily boarding status, optional mood tags, whether a shared link led to boarding, a deduplicated route-view flag, and voluntary attendance feedback. Operators see aggregate totals and overlapping mood counts. People can choose several moods, so those totals do not represent separate groups.
Authorized backend services and project administrators can access private records to run and troubleshoot HypeTrain. Other participants see the shared count and published itinerary, not your identity or mood tags.
Optional calendar reminders
The daily train can open a Google Calendar event with the reveal time and a link to that date’s train. You must save the event and choose an alert in your calendar. No calendar data is read by HypeTrain. This version does not deliver daily route push or email notifications.
Deletion and retention
Use Delete my data here or in native Settings to remove the currently signed-in anonymous identity and its private daily participation records. Cloud cleanup can continue in the background. Current boarding interest is removed when deletion is requested; anonymous historical aggregate totals remain. Clearing browser storage alone does not delete cloud data and can lose access to an identity.
Daily participation records currently remain until deletion is requested; automatic expiry for this new data model is not yet enabled. Legacy ride records follow their existing cleanup schedule. Provider logs and backups follow their own retention policies.
Services and external links
Firebase supplies authentication, backend storage and app verification. Google Maps and Google Calendar handle directions and optional reminders when you open them. Those services can receive connection information under their own privacy policies. HypeTrain does not provide them a live GPS track.
Firebase privacy and securityGoogle privacyDevelopment previews
The native daily preview stores data on this device. The web preview uses a private HttpOnly cookie and stores data on its development server. These previews do not contribute to live counts. Delete my data removes your linked local daily records. Local development storage does not automatically expire.
Delete my data
End your ride, turn off alerts and request deletion of this browser’s anonymous account, preferences, linked reports and private activity records. Cleanup continues even if you close the app. A private deletion marker expires after two days; aggregate totals and provider logs follow the policies above.
This applies to the identity currently signed in here. It cannot recover an identity lost by clearing browser data.