1. Who is responsible for your data
The controller of your data is Piotr Stojanowski Consulting (“we”). This policy covers the Kurseo app for iPhone and Android and the kurseo.app website.
For anything about privacy, write to support@kurseo.app. We answer without undue delay and within one month at the latest.
2. In short
- Every install gets an anonymous account, with no name and no email address. Signing in with Apple or Google is optional.
- We sync your favourites in your account so they are on all your devices.
- Your location stays on your phone; the server receives only what the map, search or a journey needs.
- There are no ads, we don’t track you across apps and we don’t sell data.
- Crash and error reports help us fix the app; you can switch them off in Settings → Privacy. Usage data is sent only if you switch it on there yourself. Neither contains your account or your location.
3. Your account
On first launch the app creates an anonymous account in Firebase Authentication (Google). The account has a random identifier and holds no name, email address or phone number. It lets us sync your favourites, attach a Kurseo Plus purchase to you and know whose problem report we are reading.
If you sign in with Apple or Google, they give us an account identifier, your name and your email address. Apple lets you hide your address: we then see Apple’s relay address. No feature needs signing in. It lets you have your favourites and Kurseo Plus on several devices, across iPhone and Android too.
4. Favourites
We store your favourite stops, lines, timetables, places and journeys on your phone and in your account in Cloud Firestore (Google, region europe-central2, Warsaw), the anonymous account included. A saved place can be an address, for example your home, if you save it as one. A saved journey starts and ends at a stop, a place (its name and coordinates) or “My location”; for “My location” we store no position. We don’t store the journey’s time.
In the app (Settings → Account) you can download your data (“Download My Data”) and delete your account (“Delete Account”). Deleting the account erases your favourites on the server; those on your phone stay.
5. Location and requests
If you allow it, the app uses your phone’s location to show you on the map, find stops nearby and work out walking times. In the background only when you start journey guidance yourself, so its countdown on your lock screen stays current. Without location access the map, departures and search keep working.
We send our server:
- the area of the map you are looking at, to show the vehicles there;
- the search text you type and a location rounded to about a kilometre, to list the nearest results first;
- the start and the destination of a journey you plan; when you choose “My Location”, these are your phone’s coordinates.
These data are used only to answer and we don’t keep them in the server’s logs. Place search (addresses, points of interest) is handled by Apple on iPhone and by Google on Android: the text you type goes to them.
6. Notifications
On launch the app registers a Firebase Cloud Messaging (Google) notification token, even before you allow notifications; without your permission the system shows none. We store the token in your account together with the installation identifier, the operating system, the app version, the language, whether notifications are allowed and the time of the update. It is used to send the Kurseo Plus alerts you set up.
We delete the token when you sign out on that device and when you delete your account. The countdown of a tracked vehicle (a Live Activity on iPhone, a notification on Android) is updated on the phone.
7. Kurseo Plus alerts
We store the alerts you set up on your phone and in your account in Cloud Firestore (Google, region europe-central2, Warsaw). An alert holds the stop and its platforms, the lines and directions you picked, the alert type with its settings (walking time, buffer, delay threshold) and the days and hours when it is active. “Notify me before my stop” stores the tracked vehicle, its trip and line and the stop before which we should notify you. For each alert the server stores its state: which notifications it sent that day (the trip and departure time) and whether the alert is paused. Alerts contain no location of yours.
The Kurseo server reads the alerts in your account, checks the live departures and sends notifications to the devices whose tokens are stored in the account.
8. Crash and error reports, usage data
When the app hangs or closes with an error, Firebase Crashlytics (Google) sends a report: the error trace, the device model, the system and app versions and the app’s state (data source, a city identifier such as “gzm”, taken from the map or from the area you are in, and the layers turned on). The report contains neither your account nor any coordinates.
When something important fails without a crash, for example buying or restoring Kurseo Plus, Crashlytics sends an error report the same way: the error code from the store and the step that failed.
Usage data is sent by Google Analytics for Firebase: which features you use, for example opening the Kurseo Plus screen and whether a purchase went through, with the device model, the system and app versions, the country and an app-instance identifier created by Firebase. We don’t send your account, location, searches or the stops and lines you look at. We don’t use the advertising identifier, and the data isn’t used for ads.
Crash and error reports are on by default; you can switch them off in Settings → Privacy (“Crash and error reports”). Usage data is off by default: Google Analytics collects nothing until you switch on “Usage data” in Settings → Privacy yourself, and you can withdraw that consent at any time with the same switch.
9. Report a problem
When you send a report from the app, we receive: the description, the category, the context (the vehicle, stop, line or journey it is about), diagnostics (app and system versions, device model, language, the map area rounded to about 100 m, the connection type), your account and installation identifiers, and a screenshot if you add one. A journey end picked on the map or from a saved place is sent as coordinates rounded to 4 decimal places (about 10 m). When a journey starts or ends at “My Location”, we send instead the stop where you board the first ride or the stop where you get off the last one; your position is never sent.
If you are signed in and turn on replies, we also receive your account’s email address so we can answer. We keep reports for 180 days; deleting your account deletes them sooner.
10. Kurseo Plus
You buy Kurseo Plus in the App Store or Google Play; Apple or Google handles the payment and we never see your card details. Purchases are verified by RevenueCat, Inc. (USA): it receives your Kurseo account identifier and the store’s purchase receipts (product, dates, subscription state). Our server asks RevenueCat whether you have Kurseo Plus.
11. Maps
The map is drawn by Apple Maps (MapKit) on iPhone and by Google Maps on Android. Your phone downloads map tiles directly from Apple or Google, under their privacy policies.
12. Who receives data
We use providers who process data on our behalf:
- Google (Firebase Authentication, Cloud Firestore, Cloud Messaging, Crashlytics, Google Analytics for Firebase, Installations, Firebase Hosting; Google Maps and Places on Android; Google sign-in);
- Apple (Sign in with Apple, notifications, Apple Maps on iPhone);
- RevenueCat, Inc. (verifying Kurseo Plus purchases);
- the Kurseo server: Google Cloud (Cloud Run), region europe-central2 (Warsaw).
Google, Apple and RevenueCat are US companies, so some data may leave the European Economic Area. Google LLC is certified under the EU-US Data Privacy Framework (Commission Implementing Decision (EU) 2023/1795), with the standard contractual clauses of its Firebase Data Processing and Security Terms as a fallback. Apple (Apple Distribution International Ltd, Ireland, the controller for Apple’s own processing; the data is stored by Apple Inc. in the US) and RevenueCat, Inc. (servers in the US, on AWS) receive data under the standard contractual clauses (Commission Implementing Decision (EU) 2021/914). You can ask us for a copy of the clauses at support@kurseo.app. We don’t sell data and don’t pass it on for marketing.
13. Legal bases
- Your account, favourites sync, alerts, problem reports and Kurseo Plus: performing our contract to provide the service (Art. 6(1)(b) GDPR).
- Keeping the purchase history: a legal obligation under tax law (Art. 6(1)(c) GDPR).
- Crash and error reports, security and server logs: our legitimate interest in keeping the app working and secure (Art. 6(1)(f) GDPR). You can switch the reports off at any time in Settings → Privacy.
- Usage data (Google Analytics for Firebase): your consent (Art. 6(1)(a) GDPR and Art. 399 of the Polish Electronic Communications Law, Prawo komunikacji elektronicznej). It is off by default; we collect it only once you switch it on in Settings → Privacy, and you can withdraw your consent at any time with the same switch.
- Location and notifications: your consent given in your phone’s settings, which you can withdraw at any time (Art. 6(1)(a) GDPR).
Withdrawing consent does not affect the lawfulness of the processing before the withdrawal.
14. How long we keep data
- Your account, favourites and notification token: as long as the account exists; deleting the account erases them from the server.
- Alerts and their state: as long as the account exists. Deleting an alert switches it off and erases its state, and the alert stays in the account marked as deleted so the change reaches your other devices; the same goes for “Notify me before my stop” once it ends. Deleting the account erases them all from the server.
- Problem reports: 180 days or until you delete your account.
- Crash and error reports: 90 days (Crashlytics).
- Usage data: 2 months (Google Analytics).
- The Kurseo Plus purchase history RevenueCat keeps for us: until the tax limitation period ends, that is 5 years from the end of the calendar year in which the tax payment deadline fell (Polish Tax Ordinance, Ordynacja podatkowa, Art. 70 § 1 and Art. 86 § 1; Art. 6(1)(c) GDPR). Apple and Google, as the sellers, keep their own purchase history under their own policies.
15. The kurseo.app website
The website runs on Firebase Hosting (Google). It uses no cookies, analytics or ads. Google’s servers keep technical request logs (including the IP address and the browser) to deliver the site and protect it from abuse.
16. Your rights
You have the right to access your data and to have it corrected or deleted, to restrict its processing, to receive it in a portable form and to object. The quickest way is in the app: “Download My Data” and “Delete Account” in Settings → Account. Without the app, write to support@kurseo.app (how to delete your account).
Deleting the app erases the data on your phone but not your account on the server: that is what “Delete Account” is for. You can also complain to the Polish data protection authority (Prezes Urzędu Ochrony Danych Osobowych).
17. Children
Anyone of any age can use Kurseo; we don’t ask for your age. Store purchases and signing in with Apple or Google follow those accounts’ own rules on age and parental controls. Kurseo has no ads and no profiling, and it collects no more data from children than from anyone else. A parent can ask us to delete a child’s account: support@kurseo.app.
18. Changes to this policy
We publish each new version of this policy on this page with the date it takes effect. Earlier versions are available on request.