RailMeter Privacy Policy

Archive note: the contact email, notice period and, where applicable, effective date in this copy were updated to the current policy, so it differs from the original.

First effective: 15 August 2026 · Change notice: 1 November 2026 (v1.0.17 map analysis and cache)

한국어 (Korean original)

This is advance notice of 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.

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. 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.

  1. 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.
  2. 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.

2. Items of Personal Information Processed

a. Personal information processed without the consent of the data subject

Legal basisPurposeItemsWhere 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. 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.

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 includes no usage-analytics or advertising SDK and does not create or collect an app-instance identifier or advertising ID. 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.

CategoryRetention 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
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. The operating system may reclaim ordinary cache earlier.

4. Procedure and Method of Destruction

  1. 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.
  2. The Developer does not process any personal information that must be preserved under other statutes.
  3. 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.

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. However, when the user enables “Online map and road information,” the device sends requests directly to external map services for map tiles and nearby rail or road data. Those operators may receive the IP address and the geographic area of the requested map tile or query grid. Section 6 identifies those services and their purposes.

6. External Map/Search 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. 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 or transmit exact latitude/longitude for reverse geocoding. Processing is governed by each operator’s own privacy policy. The Developer neither relays these requests nor retains their contents.

ServicePurposeOperator / Location information
OpenFreeMap vector mapsDark/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 APISupplementary original track, station and road attributes (primary queries in older installations) overpass-api.de / Germany; overpass.private.coffee (formerly overpass.kumi.systems) / operator Private.coffee, Austria

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.

Railway line, station, and kilometrage data for the Republic of Korea is 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.

  1. 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.
  2. 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).
  3. 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

  1. RailMeter does not use a web browser and therefore does not use cookies.
  2. 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. The app includes no usage-analytics or advertising SDK, and does not collect the Android Advertising ID (AAID).
  3. How to refuse — Turn off Settings > Online maps & road information to stop location-derived map and search requests. This setting is on by default.

9. Rights and Obligations of Data Subjects and Legal Representatives, and How to Exercise Them

  1. 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”).
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

  1. Personal Information Dispute Mediation Committee: +82-1833-6972 (www.kopico.go.kr)
  2. Privacy Infringement Report Centre: 118 (within Korea) (privacy.kisa.or.kr)
  3. 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.

12. Changes to this Privacy Policy

  1. This Privacy Policy takes effect on 15 August 2026.
  2. 1 November 2026: advance notice of VersaTiles tile analysis and cache management in v1.0.17, effective 2 November 2026. Previous published policy.
  3. 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.