RailMeter Privacy Policy
First effective: 15 August 2026 · Change notice: 3 November 2026 (v1.0.33 and v1.0.34 usage analytics)
This notice describes VersaTiles use and cache management in v1.0.17. These changes apply to that version when distributed on or after 2 November 2026. Older installations use the existing map/query services. The effective distribution date was changed on 2 November 2026.
This notice also describes trip endpoint administrative-area lookup in v1.0.24 and overseas administrative-boundary files in v1.0.25. These changes apply to the relevant version when distributed on or after 2 November 2026.
From v1.0.25, trip titles use bundled and country boundary files instead of Overpass coordinate lookups.
Planned from v1.0.33: Google Analytics usage collection is on by default in the production app. You can turn it off in Settings at any time, and a previous choice to turn it off is preserved after updating. This change applies only when that version is distributed and installed. Installed versions v1.0.30–v1.0.32 follow their own usage-analytics choice; versions v0.18 through v1.0.27 do not include a usage-analytics SDK.
Planned from test v1.0.34: The same usage analytics are on by default in the test app, and you can turn them off in Settings. Each installation manages its own choice. The test app uses a separate app in the same Firebase project as the production app, so test usage may be included in the same Analytics property. This change applies only when that test version is distributed and installed.
RailMeter (“the Developer”) processes personal information lawfully and manages it securely in compliance with the Personal Information Protection Act (PIPA) of the Republic of Korea and related statutes, in order to protect the freedom and rights of data subjects. Accordingly, pursuant to Article 30 of PIPA, the Developer establishes and discloses this Privacy Policy to inform data subjects of the procedures and standards for the processing and protection of personal information and to enable prompt and smooth handling of related grievances.
RailMeter does not transmit your location data or trip records to any server operated by the Developer. “Online maps & road information” is on by default, so a surrounding map area required for maps and supplemental track or road data may be sent to external map services. Trip endpoint coordinates without a bundled boundary may be sent to Overpass in v1.0.24; from v1.0.25, country codes are used to download boundary files. The Developer neither relays nor can access those requests, and you can turn the setting off at any time.
This is an English translation provided for the convenience of readers. In the event of any discrepancy, the Korean original prevails.
1. Purposes of Processing Personal Information
The Developer processes personal information for the following purposes. The personal information processed is not used for any purpose other than those stated below, and where the purpose of use is changed, the Developer will take necessary measures such as obtaining separate consent pursuant to Article 18 of PIPA.
- Providing the speed and railway line display service
To calculate and display travel speed, the railway line the current position belongs to, the previous and next stations, the direction of travel, and the kilometrage — on screen and in notifications — using the device’s satellite positioning (GPS) data and motion sensor readings. - Storing trip records and calculating line completion
To process on the device the route, timestamps, and speed statistics of automatically started trip records when the user selects “Finish recording,” to store them on the device when Automatic saving is enabled, to calculate the completion rate for each line, and to export them as a GPX file or a shareable image at the user’s request. When Automatic saving is off, finished records are not kept in the list. - App usage analytics
From production v1.0.30 and test v1.0.34, Google Analytics for Firebase is used to understand and improve app usage. You can stop collection in Settings at any time.
2. Items of Personal Information Processed
a. Personal information processed without the consent of the data subject
| Legal basis | Purpose | Items | Where processed |
|---|---|---|---|
| PIPA Article 15(1)4 (performance of a contract) |
Providing the speed and line display service; storing trip records and calculating line completion | Location data (latitude, longitude, positional accuracy, altitude, speed, heading), the time of each position fix, accelerometer and magnetometer readings, and the title and memo the user enters for a record | Location measurement and trip records are processed and stored on the device, not on a Developer-operated server. If the user enables Android system backup, they may be included in a Google Account backup or device transfer. See Section 6 for external requests made by “Online maps & road information,” which is on by default. |
b. Information generated and collected automatically
“Online maps & road information” is on by default. Your device sends requests directly to external map services. The operator may receive your IP address and the coordinate range of a map tile or query grid. In v1.0.24, trip endpoint coordinates without bundled boundaries may be sent to Overpass for titles. From v1.0.25, GitHub requests use the country code, not exact coordinates. From v1.0.17, road and railway names are primarily read by analysing VersaTiles OSM vector tiles on the device, with supplementary Overpass queries. RailMeter does not use the public Nominatim service for automatic road-name reverse geocoding and does not send the current latitude and longitude for a road-name lookup. See Section 6 for details and how to turn this off.
From production v1.0.30 and test v1.0.34, when “Send usage analytics” is enabled, it may send Google app lifecycle and session events, app-instance and Firebase installation identifiers, and app and device information. Google may derive an approximate region from the IP address. Exact GPS coordinates and trip records are not sent as analytics events. This setting is separate from online maps; turning it off stops further usage analytics collection. See Sections 6 and 8.
The analytics setting is also stored with app settings and may be included in Android system backup. A separate choice record and its time are kept in this installation's non-backed-up storage when available; that record is deleted with the app. If it cannot be saved, the off choice can be preserved in the ordinary settings. These choices are not sent as analytics events.
c. Information that is not processed
The Developer does not offer user accounts and collects no name, date of birth, telephone number, email address, resident registration number or other unique identifying information, sensitive information, payment information, or data belonging to other apps on the device such as contacts, photos, or call logs. The app does not include an advertising SDK and disables Android Advertising ID collection. The Developer does not separately collect or distinguish the personal information of children under the age of 14.
3. Processing and Retention Periods
The Developer processes and retains personal information within the retention and use period prescribed by statute, or within the retention and use period agreed to by the data subject at the time of collection. The respective periods are as follows.
| Category | Retention period |
|---|---|
| Location data being measured (for on-screen display) | Held in memory only while the app is running; erased immediately when measurement stops |
| Trip records started automatically or manually and then stored | Until the user deletes them. Stored in app-private storage; if Android system backup is enabled, they may be included in the user's Google Account backup or device transfer |
| Station-to-station run times learned from trips | Until the user runs “Delete all data” in Settings |
| Google Analytics usage data (from production v1.0.30 and test v1.0.34) | The property currently retains event-level data for 2 months and user-level data for 14 months; new user activity may reset the user-data retention period. Standard aggregated reports may be retained separately. Firebase installation IDs may be retained until a deletion request is made to Google and are distinct from Analytics identifiers. |
| Downloaded map/road/track data cache | Automatically evicted within size limits, or removed by “Clear cache” or “Delete all data” in Settings. In v1.0.17, analysis tiles are limited to 128MiB / 2,048 tiles; backgrounds to approximately 96MiB; Overpass railway and road caches to 48MiB and 16MiB respectively, and v1.0.25 overseas boundary files to 64MiB. The operating system may reclaim ordinary cache earlier. |
4. Procedure and Method of Destruction
- The Developer destroys personal information without delay when it becomes unnecessary, such as upon expiry of the retention period or attainment of the purpose of processing.
- The Developer does not process any personal information that must be preserved under other statutes.
- The procedure and method of destruction are as follows.
- Procedure — A trip-record file is destroyed when the user deletes it individually or in bulk from the records list, or runs “Delete all data” in Settings. Completion sections derived from individually or bulk-deleted records remain until “Delete all data” is run. If the app is uninstalled, the operating system deletes the app’s private storage along with it. However, if the user enables Android system backup, a new installation or device may restore a copy retained by the operating system. Retention and deletion of that copy follow the user's Google Account and device backup settings; the Developer cannot access it.
- Method — Personal information recorded and stored in electronic file form is destroyed by deleting the file itself so that the record cannot be reproduced. The Developer does not retain personal information in paper form.
Turning usage analytics off stops subsequent collection; it does not immediately delete data already sent to Google Analytics. Contact the Privacy Officer in Section 10 to request deletion or suspension of processing.
5. Disclosure to Third Parties
The Developer does not collect location information or trip records on a developer-operated server and does not provide them to other businesses. When online information is enabled, external operators may receive the IP address and map/query grid; v1.0.24 may also send trip endpoint coordinates to Overpass, while v1.0.25 and later request boundary files by country code. Section 6 identifies those services and their purposes. From production v1.0.30 and test v1.0.34, Google processes the usage analytics described in Section 6 when enabled.
6. External Map, Search and Analytics Services and Overseas Transfer
The requests below are made while “Online maps & road information”, which is on by default, is enabled. Each operator may receive your IP address and the coordinate range being queried. In v1.0.24, trip endpoint coordinates may be sent to Overpass; from v1.0.25, country codes are sent to GitHub for boundary files. From v1.0.17, road and railway names are primarily read from OSM vector tiles on the device, with Overpass as a supplement. RailMeter does not use the public Nominatim service for automatic road-name lookup. Processing is governed by each operator’s own privacy policy. The Developer neither relays these requests nor retains their contents.
| Service | Purpose | Operator / Location information |
|---|---|---|
| OpenFreeMap vector maps | Dark/light map backgrounds and place labels | Hyperknot Software Kft. / Hungary (may use Cloudflare / United States as a CDN) |
| VersaTiles OSM vector tiles (from v1.0.17) | On-device analysis of z14 tiles near the current location and heading for road/railway names and geometry | VersaTiles project / country not specified in its public operating guide |
| OpenStreetMap map tiles (v0.18 and earlier) | Standard backgrounds in older installations | OpenStreetMap Foundation / United Kingdom |
| CARTO map tiles (v0.18 and earlier) | Dark/light backgrounds in older installations | CARTO / United States, Spain |
| Overpass API | Supplementary track, station and road attributes; v1.0.24 also used it for trip endpoint administrative areas | overpass-api.de / Germany; overpass.private.coffee (formerly overpass.kumi.systems) / operator Private.coffee, Austria |
| GitHub / geoBoundaries (from v1.0.25) | Download public administrative-boundary files by country code | GitHub, Inc. / United States. Data: William & Mary geoLab and original providers |
From production v1.0.30 and test v1.0.34, Google Analytics for Firebase, provided by Google LLC (United States), analyzes app usage. While enabled, app-instance and Firebase installation identifiers, usage events, and device and app information are sent to Google, which may derive an approximate region from the IP address. Data may be processed in the United States and other Google processing locations. Transmission is encrypted. The advertising ID, precise GPS coordinates and trip records are not sent as analytics. See the Firebase privacy information.
From v0.19, background map requests go to OpenFreeMap instead of CARTO and the OpenStreetMap Foundation tile servers. Geometry and labels share vector tiles and are drawn using RailMeter's own styles. Recently viewed tiles are cached on the device and refreshed after 14 days when online; existing cached tiles may remain available without a connection. The cache is kept at approximately 96MiB and, from v1.0.17, can also be removed by “Clear cache.” According to OpenFreeMap's privacy policy, IP addresses are not normally logged, but may be logged for up to 30 days during security investigations.
VersaTiles analysis tiles are stored in the app's ordinary private cache. While moving, the app prioritises the current tile and the next two tiles along the heading. While stationary or with online services off, it reads remaining cache without making new requests. Requests contain tile numbers, not exact GPS fixes, speed, heading, trip records or installation identifiers; however, IP addresses and successive requested areas can reveal approximate movement. The app follows HTTP cache instructions and ETags for revalidation and does not delete usable stale tiles merely because refresh fails. Revisited areas receive retention priority within the same size cap. “Clear cache” removes these tiles, supplementary query caches and background maps, while retaining trips and ridden-line records. VersaTiles states in its operating guide that anonymised request logs are used to investigate issues and detect misuse.
In v1.0.24, trip endpoints without bundled boundaries may be sent to Overpass for administrative-area lookup. From v1.0.25, Korean and global broad boundaries are evaluated on-device; when online, a geoBoundaries country file may be downloaded from GitHub for finer areas. Those file requests do not contain exact coordinates, speed, heading, or trip records. The operator can see the IP address and requested country. The cache is limited to 64MiB and is removed by “Clear cache” or “Delete all data.”
Korean railway, station, kilometrage and SGIS-based administrative boundaries and Natural Earth global broad boundaries are bundled with the app. With “Online maps & road information” off, no location-derived map or search request is sent anywhere: the bundled railway, speed measurement, recording, and completion features continue without a background map. Remaining analysis tiles can also be used offline. Turning the setting off again stops new and in-progress requests.
7. Measures to Ensure Security
The Developer takes the following measures to ensure the security of personal information.
- Administrative measures — Only the minimum items necessary for the purpose of processing are collected, and the architecture is maintained such that location data is never collected to any server operated by the Developer.
- Technical measures — Trip records are stored only in the app’s private storage area, which the operating system shields from other apps. Communication for online maps and road information is encrypted with HTTPS (TLS).
- Physical measures — The Developer does not operate any separate server room or document storage facility holding personal information.
8. Installation, Operation, and Refusal of Devices that Automatically Collect Personal Information
- RailMeter does not use a web browser and therefore does not use cookies.
- The Developer does not serve personalised advertising, and does not collect or use behavioural information for advertising purposes or permit third parties to collect it. Production v1.0.30 and test v1.0.34 include an analytics SDK and do not collect the Android Advertising ID (AAID).
- How to refuse — Turn off Settings > Online maps & road information to stop location-derived map and search requests. This setting is on by default.
- Turn off usage analytics — From production v1.0.30 and test v1.0.34, turn off Settings > Send usage analytics to stop subsequent Google Analytics collection. From v1.0.33 it is on by default and operates separately from online maps.
9. Rights and Obligations of Data Subjects and Legal Representatives, and How to Exercise Them
- Data subjects may at any time request access to, correction of, deletion of, or suspension of the processing of their personal information (“exercise of rights”).
- The location data and trip records processed by RailMeter reside solely on the user’s device,
so the user can view, correct, and delete them directly within the app. The method and
procedure for exercising rights is no more difficult than the method and procedure of collection.
- Access — The Records tab shows every saved trip and its details (route, speed, timestamps).
- Correction — A record’s title and memo can be edited on its detail screen, and completed sections can be checked or unchecked directly on the line completion screen.
- Portability — Records can be exported as a GPX file or a backup file (JSON).
- Deletion — Records can be deleted from the share card shown after finishing, or individually or in bulk from the records list (completion sections derived from them remain), and “Delete all data” in Settings destroys all saved records, completion data, learned values, and the map cache at once.
- Suspension of processing — Selecting “Finish recording” on the speedometer or ongoing notification halts recording and location processing together, and turning off “Online maps & road information” stops external map and search requests. Processing can also be suspended by revoking the location permission on the device.
- Rights may be exercised by email or other means pursuant to Article 41(1) of the Enforcement Decree of PIPA, and the Developer will act on such requests without delay, responding within 10 days of receipt.
- Rights may also be exercised through a legal representative or a duly authorised agent. In that case a power of attorney in the form of Annex 11 of the Public Notice on Methods of Processing Personal Information must be submitted.
- A data subject’s right to request access and suspension of processing may be restricted under Article 35(4) and Article 37(2) of PIPA.
- The Developer verifies whether the person exercising the rights is the data subject in person or a duly authorised agent.
10. Privacy Officer
The Developer designates the following Privacy Officer, who takes overall responsibility for matters relating to the processing of personal information and handles complaints and remedies from data subjects in connection with such processing.
| Privacy Officer | Name: Juhyun Oh (Developer of RailMeter) Email: customer.ohapps@gmail.com |
|---|
Data subjects may direct any enquiry, complaint, or request for remedy relating to personal information protection arising from their use of RailMeter to the Privacy Officer. The Developer will respond to and handle such enquiries without delay.
11. Remedies for Infringement of Rights
To obtain redress for infringement of personal information, data subjects may apply for dispute resolution or counselling to the Personal Information Dispute Mediation Committee, the Korea Internet & Security Agency’s Privacy Infringement Report Centre, and similar bodies. For any other reporting of or counselling on personal information infringement, please contact the organisations below.
- Personal Information Dispute Mediation Committee: +82-1833-6972 (www.kopico.go.kr)
- Privacy Infringement Report Centre: 118 (within Korea) (privacy.kisa.or.kr)
- Korean National Police Agency: 182 (within Korea) (ecrm.police.go.kr)
In addition, a person whose rights or interests have been infringed by a disposition or omission of the head of a public institution in respect of a request under Article 35 (access), Article 36 (correction or deletion), or Article 37 (suspension of processing) of PIPA may file an administrative appeal as provided by the Administrative Appeals Act.
- Central Administrative Appeals Commission: 110 (within Korea) (www.simpan.go.kr)
12. Changes to this Privacy Policy
- This Privacy Policy takes effect on 15 August 2026.
- 3 November 2026: notice of usage analytics and settings planned for test v1.0.34, effective when that version is distributed and installed. Previous published policy.
- 3 November 2026: notice of default usage analytics and the Settings opt-out planned for production v1.0.33, effective when that version is distributed and installed. Previous published policy.
- 2 November 2026: notice of optional Google Analytics usage collection and first-launch consent planned for production v1.0.30, effective when that version is distributed and installed. Previous published policy.
- 2 November 2026: usage analytics was first announced for v1.0.28, then changed to optional consent in v1.0.30 before distribution. Previous published policy.
- 2 November 2026: notice of v1.0.24 and v1.0.25 administrative-area lookup and overseas boundary files (effective 2 November 2026). Previous published policy.
- 2 November 2026: changed the effective distribution date for the v1.0.17 VersaTiles changes to 2 November, and updated the privacy contact email.
- 1 November 2026: first notice of VersaTiles tile analysis and cache management in v1.0.17. Previous published policy.
- Should content be added, deleted, or amended in future, the Developer will give notice within the app or on this page, and will make previous versions available in this section.