Privacy Policy
Effective date:
Original policy effective date:
This is the English version of JIHASEOM's privacy policy. 한국어
JIHASEOM (the “app”) can be used without an account, and journey guidance works without location permission. We handle only the minimum information needed to provide the service. This policy explains which information the app handles and which information it does not collect.
1. Information we collect
- Installation identifier. A random string (UUID) is generated on your device when you first open the app. It distinguishes journey, service-quality and feedback records from the same installation. It does not contain your name, contact details or account information. Removing and reinstalling the app, or restoring an operating-system backup, may create a new identifier or restore the previous one.
- Push tokens. These are tokens issued by the operating system to update arrival information for an ongoing journey. On iPhone, Apple Live Activity tokens update the Lock Screen and Dynamic Island. On Android, Google Firebase Cloud Messaging registration tokens update status-bar and Lock Screen notifications.
- Widget update information (iPhone, iOS 26 or later). To refresh arrival widgets on the
Lock Screen and Home Screen when train information changes, we store the following on our server:
- An Apple widget push token
- The lines, stations and directions selected for your widgets (up to two locations)
- The update window, when commute reminders are enabled: one hour before and after the selected time on the selected days
- The app version and major operating-system version
- The arrival information last fetched by the widget and the time it was fetched, to determine whether an update is needed
- Journey information. The departure and destination stations, lines, trains and journey times you select are used to track your train and provide get-off alerts.
- Flight lookups. When you enter a flight number on the train-selection screen, we send the flight number and selected airport to our server to find the departure terminal, domestic/international classification, check-in counter and departure time. Depending on the airport, we query flight information from Incheon International Airport Corporation or Korea Airports Corporation. Unavailable fields are not displayed. The flight number and airport are not linked to your installation identifier or journey information. The server keeps the public flight result by airport and flight number for reuse and refreshes it on a later request once it is more than five minutes old. The flight information you select is displayed on your device's Live Activity or ongoing Android notification and is not sent as part of your journey to our server.
- Service-quality records. Arrival predictions and guidance-delivery results are used to measure and improve guidance accuracy and delivery quality. The installation identifier distinguishes records from the same installation.
- App-use and customization records. We record feature use; previews, selections and application of customization items; and purchase attempts and their success or failure, together with the installation identifier. These records are used for usage analysis and service improvement. We do not collect payment-method details such as card numbers.
- Device language and region settings. On first launch, we record the app's display language, the first language in the device's language settings (language code), and the configured region (country code), together with the installation identifier. These are settings you choose, not your device's actual location. We use them to distinguish domestic users and overseas visitors in usage analysis and decide which languages to support next.
- Commute-reminder usage. We record whether commute reminders and notification permission are enabled on a daily basis. We also record notification-delivery times observed by the app and the times notifications are opened, to the second, together with the installation identifier. We use these records to assess reminder use and whether reminders help users start a journey. Station and place names, routes and notification text in your reminder settings are not sent in these records. Repeated delivery times can nevertheless suggest your usual reminder time.
- Customer-support content. If you send feedback or suggest an information correction, we collect the text and category you submit, your installation identifier, and app and operating-system versions. Journey corrections also include the line, departure and destination stations, transfer sections, current section and train, estimated times, guidance state, last-update time and journey identifier shown when you opened the form. We use this information only to handle your request and reproduce the issue. We do not collect the report unless you send it.
- Optional support image. We collect an image and the consent time and version only when you choose one image, agree to its use and submit your report. The app uses the system photo picker and does not access your entire photo library. Images are resized and re-encoded without sending the original EXIF or photo-location metadata. Content visible in the image is still sent, so please obscure unnecessary personal information before attaching it. You may decline consent and submit a report without an image.
- Support request-limit records. To limit excessive submissions, we process installation identifiers, hashed IP addresses, request identifiers, submission times and whether an image was attached. These limit records do not store the original IP address.
- Request-limit records. To prevent excessive journey-start, route-lookup, widget-registration, widget-arrival and flight-lookup requests from one source, we process an IP-derived value pseudonymized with a secret key and request counts. The original IP address is not stored. These records are deleted by scheduled cleanup within two hours of the last request.
- Journey-sharing records. We process share-link issuance and opening, app handoff, and the share identifiers, installation identifiers, channel information and usage results needed for iPhone Live Activity subscriptions or Android friend notifications. The sharing website processes IP addresses to limit excessive requests; its limit records use hashed values.
- Android friend-notification information. If you choose to follow a friend's journey in notifications, we process a push token, share and notification-subscription identifiers, information that distinguishes your installation, and connection and disconnection results. Line, station, journey-state and estimated-arrival information is sent through Firebase Cloud Messaging for the notification. Server-side push tokens are encrypted in storage.
- Public sample records. These include a virtual journey's start time and progress state, and hashed IP addresses for request limits. The sample does not show a real user or a train in service.
2. Information we do not collect
- Device location is not collected by our server. Only when you press the nearby-station button on the departure-station screen does the app request your location once while in use. It fills one nearby station as an editable departure suggestion; it does not start a journey automatically. Coordinates, accuracy, location history and automatically calculated candidates are not sent to our server or analytics services and are not saved to logs or disk. Coordinates are discarded after candidate calculation; candidates are cleared when you finish selecting, cancel or leave the screen. A station applied to the departure field follows the normal recent-station and journey flows, and you can tap the departure field to change it. Declining location permission or allowing only approximate location does not prevent manual search or journey guidance. There is no background location lookup or continuous location tracking. Train guidance uses public real-time train information and timetables.
- Identity information. We do not require registration or ask you to enter your name, email address or phone number. If you include such information in feedback or an email, we may process it to handle your request.
- Settings kept on your device. Recent and frequent journeys, home and work stations and the times and days set for commute reminders, Home Screen widget reference stations and display caches are stored on your device. When you use these settings to start a journey or request widget arrival information, selected stations and other information needed for the request are sent to our server. If you add Lock Screen or Home Screen arrival widgets on iOS 26 or later, the stations and update windows described under “Widget update information” are stored on our server. Commute reminders are scheduled and delivered locally on your device. Their delivery and opening times are nevertheless recorded on our server as described under “Commute-reminder usage”. An operating-system backup may restore some settings after app removal. Friend-notification connection and disconnection credentials are kept in separate storage excluded from backups.
- Advertising and tracking data. We do not use advertising identifiers (IDFA on iOS or the Android advertising ID), include advertising or analytics SDKs, or use any information for advertising.
3. How we use information
We use the information we collect only to provide real-time get-off guidance (tracking your train, updating arrival information, and providing get-off and transfer alerts), offer customer support, analyze usage and guidance accuracy, and improve the service. We do not use it for advertising tracking or sell it to third parties.
If you choose to share a journey, anyone with the link can see the departure and final destination stations, line, estimated arrival time and current journey state in the app or on the web. If the link is forwarded, the recipient can also view it while it remains valid, so share only with people you trust. GPS location and contact lists are not shared. If you choose KakaoTalk sharing, the link, message and public image URL are passed to Kakao's sharing function, and you choose the recipient yourself.
4. Retention and deletion
Journey information, service-quality, app-use and customization records, and customer-support content you submit are stored on our server for service operations, usage analysis, accuracy improvement and support. If you request deletion using the contact details below, we delete the records associated with your identifier. Sending a request through in-app feedback includes information that identifies your installation. If an email alone does not identify the records, we will explain what additional verification is needed.
Commute-reminder usage records are deleted by scheduled cleanup after 90 days.
Widget update information is deleted when you remove all relevant widgets from your device and then open the app. It is also deleted automatically after seven days without a widget check-in, or if Apple reports that the token is invalid. Widget-update delivery records retain a token hash instead of the token for 30 days, after which only daily totals remain.
Support images are stored privately to review reports and reproduce issues, and are deleted by hourly cleanup once 30 days have passed since submission. Support request-limit records are cleaned up after two days. Failures and retries may delay deletion. Request identifiers and content hashes are kept with support content to prevent duplicate reports on retry; expired images are not restored by retries. Copies in backups are removed according to the hosting provider's backup retention and disposal cycle.
After a shared journey ends or its link expires, access stops according to the applicable display-validity period. Public sample sessions and their request-limit hashes become eligible for cleanup 24 hours after the session ends, and are deleted after the linked Live Activity channel has been closed and deleted. Retries may delay cleanup.
On Android, turning off a friend notification or swiping it away stops that notification. Choosing to stop following also disconnects the friend in the app. If there is no connection, the device stops displaying the information first and retries the server disconnection request. Turning off notifications or removing the app does not immediately delete all server records.
When the server processes the end of a friend-notification subscription, it removes that subscription's push token, share and installation connection details, and detailed display information. Scheduled cleanup does the same for expired subscriptions. Minimal end records, used to prevent duplicate requests and late retries from reactivating notifications, become eligible for cleanup 24 hours after termination or the original subscription expiry. Request-processing records are cleaned up 24 hours after creation or when the related end record is deleted, whichever comes first.
Friend-notification delivery aggregates that contain no tokens, station names or journey content are cleaned up using a retention limit of seven days. Cleanup runs periodically regardless of whether notification delivery is stopped. Network or server failures and retries may delay actual deletion. These limits do not apply to all records of the original journey and sharing services, general service logs or backups.
5. Service providers and data locations
- Supabase. Server and database hosting. Data is stored in the Seoul, Republic of Korea region.
- Apple (APNs). Delivery of iPhone Live Activity and widget updates.
- Google (Firebase Cloud Messaging). Delivery of Android journey-notification updates.
- Cloudflare. Web pages, public images and share-link routing. It processes connection information, such as IP addresses, when forwarding network requests.
- Kakao. Delivery of messages and links when you choose KakaoTalk sharing. Kakao's processing of information is governed by its own privacy policy.
6. Children's information
The app does not require registration or identity details and does not intentionally collect personal information from children under 14. Information you voluntarily include in a support request is handled as described under customer-support content above.
7. Changes to this policy
When this policy changes, we publish the changes on this page and update its effective date.
8. Contact
Operator: LINAREEN (리나린). Representatives: CHANYOUNG PARK (박찬영) and PANJUN KIM (김판준).
Privacy officer (questions and deletion requests): CHANYOUNG PARK (박찬영)
Email: pcy2177@gmail.com
Phone: 0507-1303-5742 (Korea)
Address: Unit 101, Yuwon Building, 8, Seongnae-ro 6ga-gil, Gangdong-gu, Seoul 05400, Republic of Korea.