Last updated: August 19, 2026
What this covers
This policy covers the Run With Me Seoul mobile appfor iOS and Android. The runwithmeseoul.com website, guided-run bookings and the contact form are covered by the separatewebsite privacy policy.
Who is responsible
The app is operated by Run With Me Seoul, an owner-led running business in Seoul, South Korea, run by Quintin Willekens. It is the party responsible for the personal information described in this policy.
- Service name: Run With Me Seoul (mobile app)
- Business type: Sole proprietorship operated by Quintin Willekens
- Representative: Quintin James Willekens
- Business registration number: 501-14-72173
- Location-based service provider registration number: 1346 (위치기반서비스사업 신고 제1346호, filed 4 August 2026 under Korea's Location Information Act)
- Registered address: Unit 302, 24-3 Huiujeong-ro 7-gil, Mapo-gu, Seoul 04019, Republic of Korea
- Privacy contact email: [email protected]
Information collected
The app collects only what it needs to record runs, show conditions and routes near you, run leaderboards, and keep the app working. You can use core features, including the weather score and run recording, without creating an account.
| Context | Information | Purpose | Required or optional |
|---|---|---|---|
| Account | Email address, authentication identifiers, display name | Create and secure your account, sync runs across devices | Optional (required once you create an account) |
| Run recordings | Precise GPS location during a run (including in the background while recording), route line, distance, pace, splits, barometric elevation, moving and elapsed time | Record, display and sync your runs; power splits, elevation and share cards | Required to record a run |
| Location while browsing | Your current location while the app is open | Show the running-conditions score and routes near you | Optional (location permission required) |
| Routes, ratings and reports | Routes you draw or save, route ratings, reports and blocks | Save your routes, show ratings, keep leaderboards and content safe | Optional |
| Leaderboard entries | Route, finish time, pace and display name | Show local route leaderboards | Optional (added automatically for signed-in runs; can be hidden) |
| Friends and sharing | Who you follow and who follows you, follow approvals and blocks, aggregate activity stats (total distance, run count, time, average pace) and routes you choose to share. Never your location, run map or GPS trace | Let you follow runners you know, compare aggregate activity on a friends leaderboard, and share routes you design | Optional (only when you turn it on) |
| Notifications | Device push token (APNs on iOS, FCM on Android), a per-install identifier, and your app language and platform | Deliver push notifications about follow requests and approvals. Reminders for races you save are scheduled on your device and do not use this token | Optional (registered only when notifications are enabled and you are signed in) |
| Diagnostics | Crash reports and error traces with device model, OS and app version. Performance samples covering app speed and stability are also collected from about 20% of sessions, including sessions where nothing goes wrong, and are tied to your account identifier while you are signed in | Find and fix crashes and bugs | Required (collected automatically on errors and on a sample of sessions) |
| Usage analytics | In-app events such as opening the app, viewing a route, and starting or finishing a run, together with app version, platform and a per-session identifier. Each event is stored linked to your account. Never your GPS location or run map | Understand which features are used and where the app can be improved, and measure return usage in aggregate | Optional (only with your consent) |
| Purchases | Subscription entitlement status from Apple or Google (never card or bank details) | Unlock paid features you have purchased | Required for paid features (once subscriptions launch) |
Usage analytics is optional. In-app analytics events are collected only with your consent, and you can withdraw that consent at any time in Me → Preferences → Usage analytics. Withdrawing stops collection and deletes the analytics events already collected.
Location, background tracking and sensors
This is a location-based service: it uses your location to record your runs and to show you courses nearby. Under the Act on the Protection and Use of Location Information we collect and use it only with your consent, and you can withdraw that consent at any time under Me → Preferences → Location in the app.
Removing the location permission in your device settings stops collection, but it is not a withdrawal under Article 24(1), so it does not trigger the destruction in Article 24(4). To have what we already hold destroyed, withdraw in the app.
- While using the app: your location is used to show the running-conditions score and routes near you. It is sent to our own weather and map services to answer the request and is not stored there.
- While recording a run: with your permission, the app keeps recording your precise location in the background so tracking continues with the screen off. Recording stops when you finish the run.
- Barometer: with your permission, the barometer is used to measure elevation gain during a run. Readings are stored only as part of that run.
- Notifications: race reminders, including registration-opening and race-day alerts, are scheduled on your device and do not use a push token. When you enable notifications and are signed in, the app also registers a device push token with our backend so it can send you notifications about follow requests and approvals. Those are delivered through Apple's and Google's push services. Signing out or turning notifications off unlinks the token from your account.
- Map tiles: showing a map sends your IP address and the requested map area to our map-tile providers, listed in the vendor table below.
Location Information Act disclosures
Run With Me Seoul is a location-based service provider registered under Korea's Location Information Act (registration number 1346). Article 21-2 of that Act requires the following disclosures about how location data is handled. What the service does, and on what terms, is set out in thelocation-based service terms.
The Korean version of this policy governs where the two differ.
Location access records
Article 16(2) requires us to automatically record and preserve data confirming the collection, use and provision of your location. We keep those records for six months, the minimum set by Article 6(5) of the Standards for Administrative and Technical Protection of Location Information.
Withdrawing consent is the exception. Article 24(4) requires us to destroy these records as well: withdraw one service and the records of how its location was used and shared go with its data, and withdraw everything and the records of collection go too. Six months is how long they last in ordinary use, not a floor we hold them behind when you withdraw.
These records cover who requested collection, when and by what method, and the time and method of any use or provision. Theydo not contain the location itself, which the Act excludes by definition. You may ask to view or be told the contents of your own records, and to have any errors in them corrected.
How location data is destroyed
We destroy personal location data without delay once its purpose is fulfilled, when you withdraw consent in whole or in part, or when the business suspends or closes. Where you request account deletion, we destroy it within 30 days. Destruction is a technical deletion that cannot be recovered or reconstructed; marking a record as deleted does not count.
The access records above follow the trigger. Where the purpose has simply been fulfilled, Article 23(1) leaves them out of what must be destroyed and they are kept for the period stated, then destroyed the same way. Where you withdraw, they go with the location data itself, without delay, as described above. Where weclose the service rather than suspend it, Article 11(2) requires the records of how your location was used and shared to be destroyed at the same time.
Provision to third parties
We do not provide your personal location data to third parties. Because we provide none, no notification duty arises under Article 19(3). Should that ever change, we would state it in the terms first, obtain your consent, and notify you of the recipient, time and purpose on every occasion.
Guardians of children aged 8 and under
Article 26 lets a guardian consent on behalf of a child aged 8 or under, an adult under guardianship, or a registered person with a severe intellectual disability, where this protects their life or body. This app is for users aged 14 and over, so we do not serve those groups and hold no location data consented to by a guardian.
Location information manager
The person responsible for protecting location data and handling complaints about it:
- Name: Quintin Willekens
- Position: Owner
- Email: [email protected]
- Phone: 010-2720-9604 (from outside Korea: +82 10-2720-9604)
Friends and sharing
Friends features are optional. They let you follow runners you know, compare activity on a friends leaderboard, and share routes you design. They are built so that following someone never exposes where you run.
Friends see your activity stats and the routes you share. They never see your location, your run map, or where you started.
- What friends can see: A friend sees your aggregate activity over a window you choose: total distance, run count, total time and average pace, plus any routes you choose to share. That is the whole of it.
- What friends never see: Friends never see your location, your run map or GPS trace, or where a run started or ended. That data stays private to you and is never shown through any friends feature.
- You approve who follows you: Following is approval-based. If your profile is private, another runner can only follow you after you approve the request, and you can remove or block a follower at any time.
- Sharing is opt-in: Friends features are optional. You choose whether to follow anyone, whether to share a route, and who can follow you. Nothing is shared with other runners unless you turn it on.
- Only routes you design are shareable: You can share a route you built or imported. A recorded run is a GPS trace of where you actually ran, so it can never be shared as a route.
How information is used
- To record, display, store and sync your runs.
- To show the running-conditions score and routes near you.
- To operate route leaderboards you choose to join.
- To save routes you draw and ratings you leave.
- To act on reports and blocks and keep shared content safe.
- To find and fix crashes and bugs.
- To understand which features are used and improve the app.
- To unlock paid features you purchase, once subscriptions launch.
The app does not sell personal information and does not use it for third-party advertising.
Retention and deletion
- Account details: kept until you delete your account; purged within 30 days of a deletion request.
- Run recordings, routes and ratings: kept until you delete them or your account.
- Leaderboard entries: removed when the run or account is deleted; anonymous aggregate route statistics (such as completion counts) may be retained.
- Push tokens: unlinked from your account when you sign out or turn notifications off; a token that stops working (for example after the app is uninstalled) is removed when a delivery attempt reports it invalid.
- Crash diagnostics: kept at our crash-reporting vendor for about 90 days.
- Usage-analytics events: kept 400 days, then deleted.
- Backup copies: expire on a rolling basis within 90 days of deletion.
- Support emails: kept up to 1 year after last contact.
You can delete individual runs and routes inside the app at any time. To delete your whole account, useMe → Delete account in the app, or theaccount deletion page on this site.
Vendors, outsourcing and overseas processing
The app uses a small set of vendors for its backend, maps, route building and crash reporting. Some vendors process information outside Korea.
Under the Personal Information Protection Act, Article 28-8(1)3(a), we publish the following about transfers of personal information overseas.
When and how information is transferred: at the moment you use the relevant feature, over an encrypted connection (HTTPS/TLS).
| Vendor | Role and purpose | Information transferred | Country | Kept for | Contact | Status |
|---|---|---|---|---|---|---|
| Supabase | App backend: accounts, run sync, routes, leaderboards, push-token registry | Account details, run recordings (including the GPS track), routes, ratings, leaderboard entries, usage-analytics events, device push tokens and install identifiers | Republic of Korea (Seoul); vendor incorporated in the United States | Until you delete your account; purged within 30 days of a deletion request | [email protected] | Active |
| Sentry | Crash, error and performance reporting | Crash traces, device model, OS and app version, and your account identifier | United States | About 90 days | [email protected] | Active |
| MapTiler | Map tiles and styles in the app | IP address and map-tile requests (approximate viewing area) | Switzerland / global infrastructure | IP address normally destroyed at their CDN within about 20 minutes, and up to 2 months where a security check requires it; tile-request logs for a limited period under their own policy | [email protected] | Active |
| Cloudflare | Hosting for our website and our own running-conditions service | IP address, request metadata, and the approximate coordinate sent to score conditions where you are | United States / global infrastructure | Network and security logs, kept for a limited period under the vendor's own policy | [email protected] | Active |
| Vultr | Hosting for our own route-building server | The start, end and turn-around points sent to draw a route, and your IP address | Republic of Korea (Seoul); vendor incorporated in the United States | Not stored: the points are used to calculate the route and are never written down | [email protected] | Active |
| Apple / Google | App distribution, subscription billing, and push-notification delivery (Apple Push Notification service / Firebase Cloud Messaging) | Download, update and purchase records under their own policies; device push tokens and notification content pass through their delivery services | United States / global infrastructure | Under their own policies | Apple and Google privacy contacts, in their own privacy policies | Active |
| RevenueCat | Subscription management | Purchase entitlement status and anonymous app-user identifier | United States | Not applicable until subscriptions launch | [email protected] | Planned; listed here before subscriptions launch |
Refusing an overseas transfer. You can withdraw consent for each purpose separately inMe → Preferences → Location use, and the location information for a withdrawn purpose is destroyed. The transfers above are needed to provide those features, so a withdrawn purpose stops working. To refuse all of them, end your use of the app inMe → Delete account.
Opening a place in Kakao Map or Naver Map hands you to those apps, which operate under their own privacy policies. Data is encrypted in transit between the app and all listed services.
Your rights
Subject to Korean law, you may ask to access, correct, delete or stop processing of your personal information. Most of this you can do directly: delete runs and routes in the app, change your display name, or delete the whole account fromMe → Delete account or theaccount deletion page.
I may need to verify your identity before acting on a request made outside the app.
Age requirements
You must be at least 14 years old to create an account. The app is not directed at children and does not knowingly collect personal information from children under 14.
Changes to this policy
When this policy changes in a way that matters, the app will show a notice and this page will carry a new effective date. Continued use after the effective date means the updated policy applies.
Personal information protection officer
Article 30(1)(6) of the Personal Information Protection Act requires this policy to name the officer responsible for personal information handling and for complaints and remedies. That is:
- Name: Quintin James Willekens
- Position: Owner
- Email: [email protected]
- Phone: 010-2720-9604 (from outside Korea: +82 10-2720-9604)
Privacy contact
For privacy requests or questions about the app, email[email protected]or see the app support page.