RAILUMI · KOREA SUBWAY
Privacy
Privacy policy · 2 November 2026
Your journeys stay on your device
BIRDLAB operates Railumi (net.birdlab.railumi). Offline route calculations, saved/recent journeys and language/theme/motion preferences stay in private app storage. Usage and review-prompt settings also stay local. Android backup is disabled. Clear recent journeys, remove saved journeys or clear app storage/uninstall to remove this local data. The online station-timetable request below is separate from your locally saved journey history.
Optional station alarm and location
When you choose to start an optional station alarm, Railumi requests precise-location and, where required, notification permissions through Android. During that active alarm, location fixes are processed on your device to check proximity to the selected station; Railumi does not upload those coordinates to BIRDLAB. An ongoing notification identifies active monitoring and offers a Stop action. Stopping the alarm disconnects location updates. You can also disable location or revoke permission in Android settings. Denying permission does not block manual station search or offline route planning. Location signals and notifications can fail or be inaccurate, especially underground or because of Android settings, battery restrictions or interruption. This convenience alert is not a guaranteed arrival or safety service; keep checking station signs and announcements.
Online timetable service and abuse prevention
Timetables: an online timetable request sends the selected station code, line, direction, day category and ordinary/temporary-service flag to BIRDLAB's Cloudflare Worker over HTTPS. These query fields can be forwarded to the authorized timetable provider. They are not a complete saved journey or raw GPS coordinates. Cloudflare processes the connection IP and headers. When a request needs an upstream refresh attempt, the Worker transiently uses the normalized edge IP plus UTC calendar day to derive a server-secret HMAC-SHA-256 pseudonym. Raw IP is not stored in our D1 tables or application logs. Hourly D1 records retain daily pseudonyms, per-client counts and global counts for security and quota enforcement: at most 96 refresh reservations per shared IP-derived client per UTC day and 8,000 across the current and previous 24 hourly buckets. Fresh shared-cache hits do not create these counters. The pseudonym is not anonymous, is not an advertising/install ID and is not stored with the selected station query as a personal journey profile. Normal hourly cleanup retains counters about 25–26 hours; failed cleanup can retain them longer. Shared timetable cache entries contain query fields, provider rows and freshness metadata; stale fallback is eligible up to 7 days after expiry, with later removal dependent on successful cleanup. D1 Time Travel can retain deleted records for 7 days on Free or 30 days on Paid; the account plan has not been verified, so this draft does not promise the shorter period. Worker application/request observability logging is disabled in the reviewed configuration; Cloudflare operational/security logs and provider logs have separate policies and retention. We do not upload raw GPS, local alarm fixes, saved/recent journeys or advertising identifiers through this endpoint. Station alarms remain local and existing advertising processing is unchanged. Avoid online timetable requests to avoid this optional feature's query transfer; offline planning remains available. App-data deletion cannot directly erase server quota records or provider backups. Contact support@birdlab.net about privacy requests; do not email precise travel history.
Live arrivals
Live requests send provider station and line IDs; the server resolves the official station name. App→Worker uses HTTPS. Worker→official Seoul live source sends the station name over unencrypted HTTP under an explicit source-connection exception; not all collected-data transmission is encrypted. Shared live cache: 20 seconds; manual refresh cooldown: 30 seconds. Predictions account for elapsed provider-timestamp age; future or over-120-second predictions are excluded. Refresh-failure fallback only uses still-valid predictions with freshness indicated. Cleanup selects live entries fetched over 120 seconds ago; hourly execution, bounded batches or failures can prolong storage. Limits apply separately per service: 96 refresh reservations per shared IP-derived client per UTC day; global current+previous24-hour buckets: scheduled 8,000, live 900. These do not guarantee availability or coverage.
Advertising and consent
The Android app includes Google Mobile Ads Next-Gen SDK 1.6.0 and User Messaging Platform (UMP) 4.0.0. Banner ads appear only in eligible saved/recent journey areas, not on the Home map, station search, route instructions or alarm controls. UMP checks regional consent requirements and presents applicable choices before eligible ad requests. Privacy options are available from the app privacy dialog where required. Rejecting personalized ads does not prevent offline journey planning.
Data handled by Google ads
Google may collect and share IP address (which can indicate approximate location), device/account identifiers including advertising ID and app set ID, app/ad interactions, performance diagnostics. The four disclosure categories are approximate location, device or other IDs, app interactions, performance diagnostics. Purposes include advertising, analytics, security and fraud prevention. Google encrypts SDK transfers with TLS. Collection depends on consent, region, SDK configuration and Android ad controls. This is separate from local route history; we do not send your selected journey to an ad request.
Other services and choices
There is no Railumi account, purchase, subscription or LLM. The timetable backend is described separately above. Google Play In-App Review 2.0.2 may request an optional, non-incentivized review after meaningful use. Google controls review availability and handles submitted reviews. Reset or delete your advertising ID in Android settings; use app privacy options to revisit applicable consent choices. Google sets its own SDK retention and international processing practices; see the linked Google policies. We cannot delete Google-held data through app storage controls.
This website and support
This static website uses Cloudflare hosting without our own analytics, advertising scripts, cookies or forms. Cloudflare processes connection details such as IP address and request headers to deliver and secure the site under its policies. Emailing support@birdlab.net shares the message and contact details with BIRDLAB and our email service; include only necessary information. We use support messages to respond and resolve the issue, and delete them when no longer needed except for legal or security obligations. Request access, correction or deletion by email.
Updates and contact
The app is general travel information, not a service specifically directed to children. If a child has sent personal information to support, contact us to request deletion. Privacy questions and local-law rights requests: support@birdlab.net. Material changes are published here with an updated date.