Privacy

Account and personal data

• There is no account and no sign-in. The app does not ask for your name, email address, phone number or any other personal data.
• Favourite stops are stored only on your phone. They are not sent to the server.

Location

• Your location is used only if you allow it, and only while the app is open: to find stops near you and to centre the map.
• For the nearby-stops lookup, the coordinate is sent to the Reaalnebuss server. The Map tab centres on you and sends the bounds of the visible map area to the server to load stops. The server uses these only to answer that request, does not store them, and does not tie them to an account or profile.
• You can change the location permission at any time in the phone’s settings. Without it, you can search for stops by name.

App install identifier

So that the server serves only the genuine app, the iPhone app creates an Apple App Attest key on first launch. The key identifies the app install to the server, not a person. The server keeps the key’s identifier and public key and issues access tokens based on it. The key is not tied to your name, your Apple ID or any other identity.

Live Activities

When you follow a bus or a stop on iPhone, or ask for a reminder before getting off, the iPhone shows it on the Lock Screen and in the Dynamic Island. So that it updates while the app is closed, the app sends the server that Live Activity’s Apple push token and what it follows (a trip and a stop, or a stop and the chosen lines). The server sends the updates through Apple’s push service (APNs). This data is deleted when the Live Activity ends: after the bus has left, when its time is up, or when you stop it.

Server logs

Like any web server, the Reaalnebuss server (nginx) keeps a request log: IP address, time, the requested path (without query parameters), the response code and the app type (User-Agent). The logs are used only to run the service and keep it secure, and are deleted automatically after 14 days. The same applies to this website; it has no cookies and no third-party scripts.

What there is not

• No ads, no tracking, no profiling and no third-party analytics.
• No data is sold or shared with third parties.

Android app

The Android app does the same and follows the same principles. The differences:

• You can allow approximate instead of precise location.
• Instead of App Attest, the app creates an Android key in the phone’s security hardware (Key Attestation). The server keeps the key’s identifier, its public key and a note of the phone’s boot state (whether the system is verified and the bootloader locked). The key identifies the install, not a person. To check keys, the server downloads Google’s list of revoked certificates once a day; none of your data is sent to Google for this.
• Maps are shown by Google Maps and location comes from Google location services, which receive the map and location requests under Google’s privacy terms.
• When you follow a bus or a stop, the app shows it as an ongoing notification. So that it updates while the app is closed, the app sends the server its Firebase Cloud Messaging (FCM) token and what it follows (a trip and a stop, or a stop and the chosen lines). The server sends the updates (lines and times) through Google’s FCM service. This data is deleted when the follow ends.

Maps and data sources

On iPhone, maps are shown by Apple Maps (MapKit), which loads the map images from Apple under Apple’s privacy terms. Vehicle and departure data come from the public data of the transport operators and the state. None of your data is sent to these sources.

Contact

The app is made by Pastakas OÜ.