Privacy Policy

PlayRoute (the “Service”) is an app for iPhone and Apple Watch, and for Android phones and Wear OS watches, that records your runs and lets you keep the routes you ran as courses so you can run them again. The Service is operated by its developer, Ilkyum Kim. This policy explains how the Service collects, uses, stores, and deletes your information. Where iPhone and Apple Watch differ from Android and Wear OS, the device is named.

The Service can be used without signing up. When you first open the app, it creates a random identifier on your device and uses that value to tell users apart (the “device account”); device accounts in the iPhone app and the Android app are separate accounts that are not linked to each other. If you wish, you can sign up under Profile in the app with an email address and a password (the “email account”). When you log in with an email account, you can pick up the same runs and courses after changing devices or reinstalling the app, and even between iPhone and Android. The Service does not ask for your phone number or real name.

The Korean version of this policy is the original. If a translation differs from it, the Korean version prevails.

The Service sends the following information to its server and stores it there.

The following information is used only on your device and is not sent to the server.

• ·Health information: if you allow it, the app reads heart rate, resting heart rate, weight, stride length, active energy, date of birth, and sex from the Apple Health app on iPhone, and the items listed below from Health Connect on Android, and uses them for the run screen, statistics, heart rate zones, and calorie estimates. Information read from the Health app or Health Connect is not sent to the server. However, if you are logged in with an email account, only the “Heart rate zone values” in the table above are stored in your account, so that your other devices using the same account use the same heart rate zones too. Health information is never used for advertising or provided to third parties.
• ·Steps and cadence: if you allow it (Motion & Fitness on iPhone, Physical activity on Android and Wear OS), read from your device's motion sensors and used for run statistics.
• ·Run result images: when you tap “Save as image”, the image is saved only to the Photos app on your device (the gallery on Android). The Service does not read your photo library or gallery.
• ·Accelerometer and barometer: used during runs to decide when to auto-pause and to calculate elevation gain.

On Android, if you allow it, the Service reads health information from Health Connect and saves runs recorded with your phone or a Wear OS watch to Health Connect. Information read from Health Connect, and values calculated from it (such as calories), are used only on your own devices (your phone and the Wear OS watch connected to it) and are not sent to the server. However, if you are logged in with an email account, the maximum heart rate and resting heart rate obtained from the heart rate records in Health Connect are sent over an encrypted connection (HTTPS) and stored in your account, so that you use the same heart rate zones as on your other devices using the same account (“Heart rate zone values” in the table above). Information read from or written to Health Connect is never used for advertising, sold, or provided to third parties. The use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements.

• ·What is read: heart rate and resting heart rate (to calculate heart rate zones; your maximum heart rate is found from the past 6 months of heart rate records, and if there is no resting heart rate record, your resting heart rate is estimated from your lowest heart rate on each of the past 7 days), weight (to estimate calories), and active calories (after a run, to refine the calorie estimate using values other apps or devices recorded for the same period). To look back over the past 6 months, the app also asks for permission to read records from more than 30 days before you granted access.
• ·The resting heart rate, maximum heart rate, and weight obtained from Health Connect are kept in the app's storage on your phone for later runs, and are erased when you delete your account.
• ·What is written: runs are saved to Health Connect as running exercise sessions with their start and end time, pauses, distance, active calories, heart rate, and steps — a run recorded with your phone when you finish it, and a run recorded with just a Wear OS watch when it reaches the app on your phone. The route (latitude, longitude, altitude, and the time of each point) is saved only if you allow exercise routes. Only the data types you allow are saved.
• ·Deleting a run or your account in the app does not delete the records the Service saved to Health Connect. You can delete them yourself in Health Connect.
• ·You can turn off each permission, or review and delete the data the Service saved, at any time in Health Connect in your phone's settings. You can still record runs with these permissions turned off.

Runs recorded on Apple Watch are passed to the app on your iPhone and then handled as “Runs” in the table above. Heart rate measured on Apple Watch is kept only on your devices (including the Apple Health app, if you allow it) and is not sent to the server. However, if you are logged in with an email account, the highest heart rate measured during your runs is stored in your account as your maximum heart rate, one of the “Heart rate zone values” in the table above. If you allow it, Apple Watch saves your runs to the Apple Health app as workouts, and the iPhone app saves runs recorded with just your iPhone (without Apple Watch) to the Apple Health app as running workouts when you finish them, with their start and end time, pauses, distance, active energy, and, if you allow it, the route.

Runs recorded on a Wear OS watch are passed to the app on your Android phone through Google Play services' connection between devices and then handled as “Runs” in the table above; they are kept on the watch until the phone app confirms it has received them. The watch measures heart rate, steps, and calories with Health Services, and also records the watch's location when you run with just the watch. While you run with your phone, the watch sends the heart rate it measures to the phone app for the run screen and your records. Heart rate measured on the watch is kept only on your devices (also in Health Connect, if you allow it) and is not sent to the server. However, if you are logged in with an email account, the highest heart rate measured during your runs is stored in your account as your maximum heart rate, one of the “Heart rate zone values” in the table above.

On iPhone, your runs, courses, and app settings are also kept in your device's storage and keychain. What is kept in the keychain remains after the app is deleted and reinstalled, and is used to restore your records on the same device. If you log in with an email account, the login information (your email address and an authentication token) is also kept in the keychain, and this device's records from before you logged in that you did not merge into the email account are kept aside in the keychain until you log out.

On Android, your runs, courses, and app settings are kept in the app's storage on your phone and are excluded from Google backup and device-to-device transfers. This phone's records from before you logged in that you did not merge into the email account are also kept aside in the app's storage until you log out. Only the account identifier and credentials (when you are logged in with an email account, including your email address and account number; also including markers showing that an account deletion or a login switch is in progress) are also kept in Google Play services' Block Store. If your device's Google backup is on, these values are included in your Google Account backup (end-to-end encrypted on devices with a screen lock) and remain after the app is deleted and reinstalled; they are used to recover the same account and download your runs and courses stored on the server again.

• ·Storing and showing your runs
• ·Signing up for and logging in to an email account, sending verification code emails to confirm it is you, resetting passwords, and picking up the same account's records on several devices
• ·Calculating rankings (top %) that compare the distance run in a period by users in the same country
• ·Saving and sharing courses, and guiding you when you follow a course
• ·Likes: collecting the courses you heart on a course screen so you can choose them when you start a run
• ·Friends: sending and receiving friend requests by nickname, and showing the runs (times, distance and running time) that a friend has chosen to share
• ·Friend request notifications: notifying the devices logged in to an email account when it receives a friend request
• ·Matching heart rate zones: making the devices you use with the same email account (for example, an iPhone and an Android phone) divide heart rate zones on the same basis
• ·Keeping the Service stable, analyzing errors, and preventing misuse such as falsified records
• ·Responding to your inquiries

The Service does not use the information it collects for advertising and does not track you across other companies' apps or websites. The Service has not added any advertising or analytics SDKs to the app. However, the Google Maps SDK and Google Places, which the app uses for maps and place search, collect the information described in Section 6 (such as device and app identifiers, map interactions, and crash and diagnostic information), and Google uses it to operate and improve its services, including for analytics.

The Service collects your device's location only while a run is being recorded. Recording continues until the run ends, even while the screen is off or you are using another app. Your location is not recorded when you are not on a run.

On Android phones and Wear OS watches, the app runs a foreground service only while a run is being recorded and shows that a run is in progress in a notification (an ongoing activity on the watch). The service stops when the run ends, and the app does not ask for “Allow all the time” location access, which would let it use your location while it is not on screen.

The location collected is used to calculate distance and pace, draw your route on the map, guide you along a course, and calculate rankings. Except when you save and publish a course (Section 5), your location information is not provided to other users or third parties.

When you are not running, the app uses your device's location only while you are using the app, to show where you are on the map and to show nearby courses and place search results. This location is not stored in your runs or your account. To show nearby courses, the app sends the range of the map area visible on the screen to the server, which uses it only to find courses and does not store it. When you search for a place, your search text and current location are sent to Google (Section 6).

To show the addresses of a course's start and finish points, the course screen sends the coordinates of those points to Apple's address lookup service on iPhone and Google's on Android (Section 6). These coordinates are points on the course, not your current location. If you tap an address to open it in a map app, the coordinates of that point and the course name are passed to the map app you choose. The list of map apps shows only apps installed on your device, and this list is not sent to our server.

You can turn off location access in your device's settings at any time. Runs cannot be recorded when location access or Precise Location is turned off.

When you save a run as a course, or create and save a course on the map, the course's name, description, distance, route, and the date and time it was saved become visible to other users along with your nickname. The app tells you this before saving. Because the route shows exactly where it starts and ends, we recommend not saving as a course any run that starts somewhere you would rather not reveal, such as in front of your home.

You can delete a published course in the app at any time, after which it is no longer shown to other users. If you delete your account, all the courses you have published are deleted as well.

When you are logged in with an email account, you can use the friends feature. Another user can send you a friend request by entering your exact nickname, and the user who receives a request sees the sender's nickname. Once a request is accepted and you become friends, you see each other's nicknames and, for the runs each of you has chosen to show to friends, the start and end times, distance and running time. Other information, such as routes and locations, heart rate, calories and the courses you followed, is not visible to friends either.

The default setting for showing your runs to friends is turned on at first, and you can turn it off or on again on the Friends screen in the app. For each friend, you can also choose to follow the default setting, or to show or not show your runs regardless of it. When you remove a friend, you can no longer see each other's runs. When you block another user, your friend connection and any requests between you are removed, and the blocked user can no longer find you by your nickname or send you friend requests. You can unblock users on the Friends screen.

The routes of your runs are not visible to other users unless you save and publish them as a course, and the times, distance and running time of your runs are visible only to the friends you have chosen to show them to, as described above. The ranking screen shows only your own top % and rank, and does not show other users' nicknames or records. The email address of an email account is not visible to other users, including friends.

To operate the Service, we entrust the processing of information as shown below, and information is transferred outside your country in the process.

Information is sent over encrypted connections (HTTPS) at the time you use the app and is kept for the periods in Section 7. These transfers are necessary to provide the Service, so if you do not want them, you cannot use the Service. Google's privacy policy also applies to your use of Google Maps and place search, and Apple's privacy policy to your use of Apple Maps.

Friend request notifications are sent only to devices logged in with an email account, and notification tokens are not sent to the server before you log in. Notifications are sent through Google's Firebase Cloud Messaging and reach iPhone through the Apple Push Notification service; Google's and Apple's privacy policies also apply to this delivery. If you do not want notifications, you can turn off PlayRoute notifications in your device settings, and you can keep using the friends feature with notifications turned off.

• ·Device account, email account, runs, courses: kept until you delete your account or ask us to delete them. The Google or Apple account identifier and the token issued by Apple are also kept until you delete your account; when an account that signed in with Apple is deleted, we ask Apple to disconnect the app.
• ·Email verification records: a verification code can be used for only 10 minutes after it is sent, and its sending record is deleted one day after the code is used or expires. When you delete your account, the sending records for its email address are deleted as well.
• ·Friends: friend connections and sharing settings are kept until you remove or block the friend, friend requests until the recipient accepts or declines them, and blocks until you unblock the user. When you delete your account, all of this is deleted, and you are also removed from other users' friend lists and received requests.
• ·Notification tokens: kept while you are logged in with an email account. When you log out, the app deletes that device's notification token; the value left on the server can no longer be used and is deleted the next time a notification is sent. Tokens that can no longer be used, for example because the app was deleted, are removed in the same way, and only the tokens of the 10 most recently used devices are kept for each account. They are deleted when you delete your account.
• ·Heart rate zone values: kept until you delete your email account. When a device sends new values, they are updated according to set rules (for the maximum heart rate, the higher value; for the resting heart rate, a value measured by a watch takes priority over an estimated one, and between values of the same kind, the one measured later). When you log out, the values received from your account are erased from that device, and when you delete your account, they are deleted from the server as well.
• ·Course likes: kept until you remove the like or delete your account. Your likes are not shown to other users, and a liked course that is deleted disappears from your list. If you merge this device's records from before you logged in into your email account when logging in, your likes move with them.
• ·If you delete your account under Profile in the app, your account and all the runs and courses you uploaded (including courses published to other users) are permanently deleted from the server. If you delete it on iPhone, the runs and courses stored in the app on this iPhone, the copies kept in the keychain, records not yet uploaded, recovery copies kept in case the app closes unexpectedly, Apple Watch run results waiting on the iPhone, your personal settings (nickname, weight, values read from the Health app, and heart rate zone values received from your account), and the email account login information are erased as well. Apple Watch is told to discard the results of runs that ended before the deletion. Deleted information cannot be restored.
• ·If you delete it on an Android phone, then along with the information on the server, the runs and courses stored in the app on this phone, records not yet uploaded, recovery copies kept in case the app closes unexpectedly, Wear OS run results waiting on the phone, your personal settings (nickname, weight, values read from Health Connect, and heart rate zone values received from your account), and the account identifier and credentials kept in the app's storage and Block Store are erased. The Wear OS watch is told to discard the results of runs that ended before the deletion. Deleted information cannot be restored.
• ·Device settings such as distance units, sounds and voice guidance, auto-pause, and checkpoint and sprint alerts remain after you delete your account. Workouts and heart rate that Apple Watch saved to the Apple Health app, and workouts that the iPhone app saved there, are not deleted either; you can delete them yourself in the Health app. On Android, the workouts the Service saved to Health Connect are not deleted either; you can delete them yourself in Health Connect. If you keep using the app after deleting your account, a new device account is created.
• ·If you merge this device's records from before you logged in when logging in to an email account (each email account can do this only once), those records are moved to the email account, and the device account is merged into the email account and no longer exists. If you do not merge them, the records stay in the device account and show again when you log out. If you delete your account while logged in to an email account, that email account and its records are deleted, while the records kept aside from before you logged in and their device account remain.
• ·When you delete an individual run or course in the app, it is immediately removed from ranking calculations and public lists. To erase the copies remaining on the server as well, delete your account or make a request as described in Section 8.
• ·Server access logs: kept only as long as needed for security and troubleshooting, then deleted.

Information whose retention period has ended or whose purpose has been fulfilled is destroyed without delay in a way that cannot be recovered. Information that the law requires us to keep is stored separately for the required period.

You may request access to, correction of, deletion of, or a halt to the processing of your information.

• ·In the app: change your nickname, country, and units; delete runs and courses; sign up for, log in to, and log out of an email account, and change or reset its password; delete your account under Profile (your account, all the runs and courses you uploaded to the server, and the records and personal settings stored in the app on this device are permanently deleted together; see Section 7 for what is erased and what remains)
• ·Friends (email accounts): on the Friends screen in the app, accepting or declining friend requests, removing and blocking friends, unblocking users, and changing whether your runs are shown to friends (the default setting or the setting for each friend)
• ·Friend request notifications: if you turn off PlayRoute notifications in your device settings, you will not receive them (on Android, you can also turn off just the Friend requests notification channel). Notifications are not sent to devices that have logged out.
• ·In your device's settings: withdraw permission for Location, Motion & Fitness, Health, and Photos on iPhone; for Location, Physical activity, Notifications, and Health Connect on Android phones; and for Location, Physical activity, Heart rate (Body sensors), and Notifications on Wear OS watches
• ·Any other request (including a request to delete everything stored on the server if you cannot delete your account in the app): email admin@playmong.com with your nickname (for an email account, please send it from the email address you signed up with). After verifying that the request comes from you, we will handle it without delay and no later than 30 days after receiving it, and tell you the result. How to delete your account, including how to request deletion without the app, is also explained on the Delete your PlayRoute account page.
• ·Deleting some data while keeping your account: you can delete individual runs and courses in the app, and they are immediately removed from ranking calculations and public lists (Section 7). To permanently erase specific runs or courses (including copies left on the server after you deleted them in the app), your nickname, or your heart rate zone values from the server while keeping your account, email the address above. We verify that the request comes from you in the same way as for account deletion requests and handle it no later than 30 days after receiving it. Section 7 of the Delete your PlayRoute account page explains how.

On iPhone, deleting your account in the app also erases the records kept in your device's keychain. If you delete the app first, the Service cannot remotely erase what remains in the keychain; it is erased when you reinstall the app and delete your account, or when you reset the device.

On Android, deleting the app erases the records in the app's storage, but the account identifier and credentials kept in Block Store may remain. If they do, reinstalling the app recovers the same account, so you can then delete your account in the app; to erase the information on the server without the app, email us at the address above. Records the Service saved to Health Connect remain after the app is deleted, and you can delete them yourself in Health Connect.

The Service is not directed at children under 13 (under 14 in South Korea, as required by its Personal Information Protection Act, or under a higher age if the law where you live sets one) and does not knowingly collect their information. If we learn that a child's information has been collected, we delete it without delay.

• ·All communication between the app and the server is encrypted (HTTPS).
• ·The account identifier and credentials (including the email account login information) are stored in your device's keychain on iPhone, and in the app's storage and Google Play services' Block Store on Android.
• ·Passwords are stored only as a value transformed irreversibly (bcrypt), so even the Service cannot know your password. Email verification codes are also stored only as transformed values.
• ·After 10 wrong passwords in a row, logging in and changing the password are blocked for 15 minutes. When you change or reset your password, other devices logged in to that account are logged out.
• ·Access to the server and database is restricted to authorized operators.

The Service has a privacy officer who oversees the handling of personal information and responds to user inquiries.

• ·Privacy officer: Ilkyum Kim
• ·Email: admin@playmong.com

When we change this policy, we will announce it on this page at least 7 days before it takes effect. For changes that matter to you, such as what we collect or why, we will announce it at least 30 days in advance.

For questions, complaints, or remedies related to the handling of personal information, please contact admin@playmong.com.