BetterSL — Privacy Policy
Last updated
About this policy
BetterSL is an independent journey-planning app for public transport in Stockholm, not an official SL app. Stefan Pihlanen is responsible for the processing of personal data described here and can be contacted through the BetterSL support form or at support@pihlanen.com.
This policy covers both local storage on your iPhone and the app's server features. The data processed depends on your app version and the features you use. You do not need to register manually, sign in or provide an email address to use the app. However, a technical session and identifiers are created automatically, so the processing is not entirely anonymous.
Data on your phone
Favourites, saved commutes, settings and optional search and journey history are stored locally. Local history covers the most recent 60 days. You can delete saved items and history in the app and turn off learning. Any personal background image is handled locally and is not uploaded to our own server.
GPS and motion data for automatic boarding and alighting assistance are processed on your phone. This can also happen while the screen is locked during active journey assistance. If you use server features, information about the selected journey may also be sent to and stored on the server, as described in the server monitoring section below.
The technical session is stored in the iOS Keychain with ThisDeviceOnly protection. It does not sync between devices and may remain after the app is uninstalled.
Journey searches, maps, location and motion
Journey searches and current traffic information require internet access. The stops, places, address coordinates, dates and times needed for a search are sent to SL's traffic-data services through Trafiklab.
BetterSL uses Apple MapKit for maps, address searches and requested walking directions. A walking-route request may send start and destination coordinates to Apple. This is a separate network request, even though GPS and motion processing for journey assistance takes place locally. Requests to providers may include an IP address and other technical information that may appear in their logs.
Location access is optional and is used for features such as nearby stops and journey assistance. Motion permission is separate and also optional. You can still search manually and manually confirm boarding and alighting. You can change these permissions in iOS Settings.
Technical identity and daily usage statistics
Supabase Auth automatically creates a technical anonymous session with a user ID. A separate installation ID is also created, stored and linked on the server. Anonymous in the session type does not mean that the entire system or its data is fully anonymous: the identifiers make the processing pseudonymous, and data can be linked to the same technical user or installation.
When a new client is used in the foreground, a day of activity is automatically recorded on the server. The private daily table contains only the installation ID and the date in the Europe/Stockholm time zone, with at most one entry per installation per day. It contains no locations, journey plans or exact usage times. Days when the app is used offline are not backfilled later.
The purpose is to count active installations and improve the service, not to count identified people. The administrator receives aggregate figures for these statistics. Recording does not depend on notification permission or a selected journey, and the app currently has no separate setting to opt out of these statistics.
Daily entries are retained for 35 calendar days. Older daily entries are removed by a daily automated task. This limit applies specifically to daily usage statistics, not to all server data.
Server monitoring, notifications and Live Activities
If you choose server monitoring, push notifications or Live Activities, the app may send and store:
- Technical user, installation and activity IDs, and APNs and ActivityKit tokens for updates.
- Selected stops and lines, departure and arrival times, and the journey plan.
- Commuting days and times, buffer and walking minutes, and journey progress and status.
These data are used to monitor the selected journey and send relevant updates. Supabase is used for technical authentication, the database and server functions. Apple APNs is used for push notifications and Live Activity updates. These features are optional; local reminders are also available. iOS may restrict background work and delivery, so updates and notifications cannot be guaranteed.
Checking journey status and your access to app features is separate from advertising tracking. BetterSL does not use these data for advertising profiling or tracking across other companies' services.
Retention, deletion and your choices
Daily statistics entries have a retention period of 35 calendar days as described above. You can delete locally saved items and history in the app and turn off learning.
Stopping monitoring or deleting a commute does not mean that all historical server records are deleted. Other stored server data may remain after monitoring ends and currently have no common automatic deletion deadline. Uninstalling the app does not automatically delete server data, and the technical session in the iOS Keychain may remain.
To delete your server account, open Settings in the app. Under Server data, choose Delete my server data and confirm. This deletes your technical account and its associated server data, including saved journey watches and daily usage records. Server features stay off until you turn them on again. You keep your local journeys, favourites and purchases. If the app cannot confirm deletion, try again when you have an internet connection.
You can also contact support to request access to, correction or deletion of data, or to object to processing. Requests are assessed under applicable data-protection rules.
Recipients and security
Relevant data are processed by Supabase for operation and technical authentication, by Apple for maps, push updates and purchases, and by SL/Trafiklab for journey information. These providers may process IP addresses and other technical information for their respective services.
Administrative access is permission-restricted, and network traffic is encrypted using HTTPS. No technical solution can guarantee absolute security.
We do not sell user data or use them for advertising profiling or tracking across other companies' apps and services. Data that can be linked to a technical user or installation should not be regarded as fully anonymous.
Purchases
Digital passes are paid for through Apple using StoreKit and in-app purchases. BetterSL verifies purchase status to determine access to app features. The developer does not receive or store payment card details. The current purchase implementation does not send purchase history or card information to our own server. SL tickets are not included and are not sold in the app.
Support and privacy questions
You can reach Stefan Pihlanen through the BetterSL support form or at support@pihlanen.com. If you contact support, we process your message and the email address you provide to handle your question and reply. Use the same contact details for questions about personal data or to make a request about your data.
Children
BetterSL is not specifically directed at children under 13. Because technical identifiers and daily statistics are created automatically, this processing may also occur when a minor uses the app. A parent or guardian can contact support with questions or a deletion request.
Changes and date
If this policy changes, the updated text will be published on this page with a new update date. This version was last updated on November 8, 2026.