Privacy Policy

• A random device identifier, generated and stored locally in your browser (not a cookie). It is not linked to your name or email. Because an online/device identifier can potentially be considered personal data under applicable privacy law, DevaHop treats it conservatively and uses it only for the functions described here. Creating an account is optional and is not required to use DevaHop. Your device identifier is hashed in your browser before it is sent to our servers; the raw identifier never leaves your device.
• Your Scout handle — a randomly generated pair of words plus a number (e.g. “Carpathian Falcon 195”), also stored in your browser. It is designed as a nickname and is not linked to your name, email, phone number, or other directly identifying information.
• The reports you submit — which stop, what you reported (e.g. “Bus is Leaving Now”), and when. These are stored to show the live community status to other riders.
• Your device’s own trip progress (e.g. “currently heading to the Citadel”) — used only to show or hide the right buttons for you.
• A one-way hashed version of your IP address, kept only to prevent spam/abuse (e.g. a script flooding fake reports). Your real IP address is never stored — only a one-way cryptographic hash. Because hashed online identifiers can still potentially be personal data, DevaHop treats this information conservatively. The hash changes every day and these records are automatically deleted after up to 48 hours.

• No name, email, or phone number for riders using the app
• No precise location or GPS tracking
• No cookies for riders using the app — the only cookie DevaHop ever sets is a login session for the single admin account, used solely to view the operational debug log described below
• No advertising, analytics, or third-party trackers of any kind — DevaHop has no optional analytics at all

DevaHop does not use optional analytics of any kind. Ordinary browsing is not tracked: opening the app, searching for a station, opening a station or a line, checking a schedule, or arriving via the sticker QR code records nothing at all. Records are created only when you use a feature that genuinely needs them to work — Journey Mode, community reporting, XP, or voluntarily signing in. The single admin dashboard shows statistics calculated from those necessary records and nothing else.

• People who only consult schedules are not counted as users — nothing is recorded about them, so they cannot appear in any figure anywhere
• Journey GPS coordinates are never sent to, or stored by, DevaHop — GPS stays entirely on your device and is used only to advance Journey Mode locally
• There is no analytics identifier, analytics cookie, analytics browser-storage key or fingerprinting of any kind. Where the dashboard counts distinct devices, it counts the functional device identifier already present in reporting records — never presented as a guaranteed individual person

During active testing and maintenance periods, DevaHop temporarily records a log of report activity to help diagnose display/timing bugs — for example, confirming that both direction pages show consistent information after a report. This log:

• Does not include IP address, in any form — it is not needed for this purpose, so it is not collected here
• Stores your device identifier only as a one-way hash (a different hash than the one used for abuse prevention), not the raw value
• Includes timestamps and app state (which buttons were available, what the status pages showed) — this is the actual diagnostic data the log exists to capture
• Is visible only to the single admin account (Google sign-in, restricted to one specific email address) — there is no public or rider-facing access to this data
• Is not run continuously — it is used in short, periodic testing/maintenance windows, not as an ongoing feature