Wabash RiderWabash Rider Privacy Policy
Effective and last updated: October 28, 2026
1. Who we are
This Privacy Policy covers the Wabash Rider mobile app for Android (the "App") and this website, bus.reale.one. The App is published by Joe Wease / RealE.one ("we", "us"). TODO for Jay: confirm the exact legal publisher name (personal name or a registered business) to match the Google Play developer account.
Contact: jaywestmarketing@gmail.com TODO for Jay: confirm this is the right public contact email (the main reale.one site uses admin@reale.one).
The App is an independent rider companion and is not operated by, affiliated with, or endorsed by the City of Terre Haute or Terre Haute Transit Utility.
2. Summary
- No account, sign-up, name, email or phone number is needed or collected by the App.
- The App has no advertising, no analytics SDK and no crash-reporting SDK of our own.
- Your device location is used only on your device. The App does not send it to our server.
- If you search for a place, the text you type is sent to our server and passed to a place-search service to find matching places near Terre Haute (see section 3).
- The map is shown with the Google Maps SDK for Android, which collects some technical data for Google (see section 5).
- We do not sell personal information and do not share it for advertising.
3. Information the App uses
Location (precise and approximate)
If you grant location permission, the App reads your current location while it is open (foreground only) to find the closest bus stop and center the map. The location stays on your device and is not sent to our server. The App does not request background location. If you deny permission, the App uses a default point in downtown Terre Haute instead. You can turn location access off at any time in Android Settings.
Saved stops
Stops you save are stored only on your device. We do not receive your list of saved stops as a list.
Notifications
If you turn on arrival alerts and grant notification permission, the App shows notifications that it creates on your device. It does not register for push notifications and does not send a push token to us.
Requests to our transit data server
To show routes, stops and scheduled departure times, the App requests that data from our server at bus.reale.one over HTTPS. Each request includes the stop number being looked up (for example, a saved stop when alerts are on) and, as with any internet request, your device's IP address and basic request details. We use this only to answer the request and to protect the service. We do not use it to build a profile of you. If the server can't be reached, the App uses a copy of the published schedule stored in the App.
Place search
When you type an address, business or landmark into search (3 or more characters), the App sends that text to our server. Our server sends the text, without your location, IP address or any identifier, to the place-search service Photon, run by komoot GmbH using OpenStreetMap data, and returns matching places in the Terre Haute area with their nearest bus stops. Search results, including the search text, may be cached on our server and our hosting provider's network for up to 24 hours so repeated searches load faster. They are not linked to you. TODO for Jay: if you switch place search to Google (Geocoding API), update this paragraph.
Our server runs on Vercel, which may keep standard request logs, including IP addresses and request URLs (which can include search text), under the Vercel Privacy Policy. TODO for Jay: confirm the log retention period for the J West Marketing Vercel plan.
4. Information we do not collect
The App does not collect your name, email, phone number, contacts, photos, files, messages, payment information, health data or advertising ID, and it does not track you across other apps or websites.
5. Google Maps
When the map is enabled, the map screen uses the Google Maps SDK for Android, provided by Google LLC. According to Google, the SDK automatically collects request metadata (such as device model and OS version), crash data from within the SDK, your IP address and an SDK-specific pseudonymous identifier, and it may collect map interaction events such as panning and zooming. Google uses this information under its own terms: the Google Privacy Policy and Google Maps Terms of Service. Details are in Google's data disclosure for the Maps SDK for Android.
6. This website
bus.reale.one is hosted by Vercel. It sets no cookies, uses no analytics and loads no third-party scripts. Vercel may process standard request logs (including IP addresses) to deliver and secure the site under the Vercel Privacy Policy.
7. Sharing
We do not sell or rent personal information, and we do not share it with advertisers or data brokers. Information is handled by service providers only to run the App (our hosting provider, the Photon place-search service and Google Maps, as described above), or disclosed if required by law.
8. Security
The App talks to our server over encrypted HTTPS. No account data or passwords exist to protect, and saved stops stay on your device.
9. Retention and deletion
Data on your device (saved stops, alert settings) stays until you remove it in the App, clear the App's storage, or uninstall the App. Cached place-search results expire within 24 hours. Server logs are kept only as long as described in section 3. See Data deletion for how to delete your data or ask us to delete anything we hold.
10. Children
The App is a general-audience transit tool and is not directed to children under 13. We do not knowingly collect personal information from children. TODO for Jay: confirm the target age group you will select in the Play Console.
11. Your choices and rights
You can deny or revoke location and notification permissions at any time in Android Settings, and the App keeps working with a default location. Depending on where you live, you may have rights to access or delete personal information. Email jaywestmarketing@gmail.com and we will respond within 30 days.
12. Changes
If the App starts collecting new data, for example if accounts, analytics or crash reporting are added, we will update this policy and the Google Play Data safety section before that version is released, and change the date above.
13. Google Play Data safety summary
This is how the App's current behaviour maps to the Google Play Data safety form. "Collected" means data sent off the device.
| Data type | Collected? | Shared? | Purpose and notes |
|---|---|---|---|
| Approximate and precise location | No (used on device only) | No | Finds the closest stop and centers the map. Not sent to our server. |
| Personal info (name, email, phone, user IDs) | No | No | No accounts. |
| App activity (saved stops) | No (stored on device) | No | Stop numbers sent to fetch arrival data are processed only to answer the request. |
| App activity: in-app search history | Yes, processed ephemerally (search text only) | Sent to Photon (komoot) to find places TODO for Jay: decide whether to declare this as shared | App functionality: finds places and nearby stops. Not linked to the user; cached up to 24 hours. |
| Device or other IDs | Yes, by the Google Maps SDK | No (Google acts as a service provider) | Maps SDK pseudonymous identifier. App functionality and analytics by Google. |
| App info and performance: crash logs, diagnostics | Yes, by the Google Maps SDK | No | SDK crash data and request metadata. App functionality and analytics by Google. |
| App interactions | Possibly, by the Google Maps SDK | No | Map panning and zooming events, depending on how the map is used. |
| Financial, health, messages, photos, files, contacts, calendar, audio | No | No | Not accessed. |
Security practices: data is encrypted in transit (HTTPS). Deletion: users can delete on-device data by clearing storage or uninstalling; there is no account to delete. TODO for Jay: re-check this table against the final release build (for example, if Sentry, Firebase or analytics is added) before submitting the Data safety form.