Effective Date: July 21, 2026
The SMTOWN RUN CLUB 26 Organizing Committee processes only the information needed to provide the service. This Policy applies to the SMTOWN RUN CLUB 26 website, Android mobile app, Wear OS app, and connected race services.
In this Policy, “we” or the “Operator” means the SMTOWN RUN CLUB 26 Organizing Committee. The app and its systems are operated by FXIP Co., Ltd.
| Category | Information | Purpose | Retention |
|---|---|---|---|
| Participant verification | Name, email or Korean mobile number, entry number, entrance zone, domestic/foreign participant category, departure group, ticket and race status | Verify the registered participant, determine app login eligibility, manage bibs and starts, operate the race, and answer inquiries | Until race operations and related inquiries are complete. A period separately disclosed at registration or required by law applies where relevant |
| Login and account | Email or mobile number, six-digit verification code, account identifier, login session, Terms version and acceptance time | Verify identity, maintain sessions, prevent duplicate or abusive use, and record acceptance | A verification code is valid for 5 minutes, and its encrypted delivery job is kept for up to 24 hours. A session record is replaced on a new login and deleted on logout or account closure. Acceptance records remain until account closure |
| Authentication protection | Android app-scoped device identifier, IP address, request count | Prevent mass verification requests and attacks | The server converts the device identifier to a SHA-256 hash for a one-minute rate-limit window. Technical information in access logs is kept for up to 7 days |
| Profile and race use | Email, phone number, name, entrance zone, entry number, departure group, race date, place and distance, finish status, token balance | Display profile and race participation details | Until account closure. The participant roster may be retained separately as explained below |
| Running and missions | Precise location and route, start and finish times, distance, pace, duration, completion date, mission and completion status, display polyline, map bounds and point count, rewards and token records | Provide running history, verify missions, prevent duplicate rewards, and check abnormal records | On our servers until account closure. Failed uploads remain on the device for up to 5 days. Backup copies are deleted when the applicable backup lifecycle ends |
| Shuttle demand survey | Selected boarding stop and submission time | Measure shuttle demand and display submission status | Until account closure or completion of the survey purpose |
| Notifications | FCM token, notification setting, delivery, receipt and read status | Send notices and service notifications and prevent duplicates | FCM token until invalidation, logout, or account closure; per-user delivery and read records until account closure |
| Spotify connection | Connection status, one-time authorization code, encrypted refresh credential, access token and expiry, current track and playback status, playlist ID, title, artists and image URL | Provide user-requested Spotify connection and playback control, check track suitability for younger users, and launch NFC playlists | Server refresh credentials are deleted after a successful disconnect request, account closure, or loss of authorization. If a disconnect request fails, the credential may remain until expiry, but never longer than 6 months after issue. NFC metadata stays on the device for up to 5 days. Current-track data is held in memory only while playing |
| Error and security records | Request ID, snapshots of account and participant identifiers, IP address, user agent, app version and build, platform, route, error code and diagnostics | Troubleshoot failures, investigate security incidents, and stabilize the service | API access logs for up to 7 days; application error records for up to 30 days |
The ticket seller may separately process date of birth, gender, shipping address, and payment information during booking and payment. The current app server does not store these items as app-account fields. The ticket seller's privacy policy and the notice shown during registration apply to that processing.
The following information is processed on the device to provide a feature and is not stored on our servers.
The current public production server does not accept photo-print image uploads from ordinary users. We will update this Policy and the in-app notice before enabling that processing.
The app does not read past health data from Health Connect or write records to Health Connect. Some local app data may be included in operating-system backups depending on the user's Android backup settings.
When a user completes a run, information such as the processed route and map bounds, prepared so the route can be redrawn on a map, is automatically transferred to and stored on servers located in the Republic of Korea. The recipient is FXIP Co., Ltd., and the information is retained until the account is closed. Information that must be kept under applicable law may be retained separately for the period required by that law. When the retention period ends or the processing purpose is achieved, the information is deleted using methods that make recovery or reconstruction impracticable. We do not use location information or routes for advertising, marketing, user profiling, or sale, and we do not provide them to a third party for that party's own purposes. We may use service providers that process the information on our instructions to the extent needed to provide the service, including server operations, and such providers are disclosed in this Privacy Policy. A user may change or withdraw location permission at any time in device settings. Without location permission, route measurement and map display features are unavailable.
The information transferred and stored is as follows.
Our systems store the completed route and results. We do not store the accuracy of individual location fixes used by the device during measurement, activity-state classification results, or raw step-detection signals.
Completed run results are used for the following purposes.
The Organizing Committee does not use completed run results or routes for advertising, marketing, user-preference analysis, or data sales.
| Service | Information and purpose | Retention basis |
|---|---|---|
| Firebase Analytics | Screen, button, mission, running and Spotify feature events; device model; OS and app version; country and language; login state; app-instance identifiers. Used to understand and improve service use | The Google Analytics property setting for user- and event-level data (2 or 14 months). Aggregated reports may remain longer |
| Firebase Crashlytics | Crash, error and stack information; relevant app state; device information; installation identifiers; app version; network and locale country; Android SDK version. Used to diagnose errors | Google keeps crash information and associated identifiers for 90 days before beginning deletion |
| Firebase Cloud Messaging | FCM token, Firebase installation ID, and notification delivery and interaction data. Used to deliver push notifications | After an installation-ID deletion request, Google removes it from live and backup systems within 180 days. Our FCM token is kept until logout, account closure, or invalidation |
| Google Maps and Google Play services | IP address, device and app data, SDK identifier, map viewport, zoom and pan interactions, and error data. Used for map display and device location | Governed by Google's Privacy Policy and service settings |
Depending on the device and its settings, Firebase Analytics may process the Android Advertising ID or advertising-related identifiers. We do not serve personalized advertising and do not send running routes, heart rate, email addresses, or phone numbers as Analytics event parameters.
We use the following providers for the services described below.
| Provider | Service | Processing location |
|---|---|---|
| NHN Cloud Corp. | Korean server infrastructure, databases and backups, verification email and SMS delivery | Republic of Korea (KR1) |
| Google LLC and affiliates | Firebase Analytics, Crashlytics, Cloud Messaging, and Google Maps | United States and other countries where Google and its subprocessors operate infrastructure |
| Spotify AB and affiliates | User-requested Spotify authorization, content lookup, and playback control | Sweden, United States, and other countries where Spotify operates the service |
Information is sent to Google and Spotify over encrypted networks when a user uses the relevant feature or when the app sends analytics, error, or notification data. The categories, purposes, and retention periods are limited to this section and Sections 2 and 5, together with each provider's policy. A user may avoid Spotify processing by not connecting Spotify and may change app permissions. Refusing processing required by core SDKs may limit use of the app.
Race registration information may be shared, only as needed and within the notice shown at registration, with the organizer and providers responsible for planning, on-site operations, tickets, and shuttle services. Ticket reservations and payments are currently also governed by the notices and policies of KREAM or the applicable seller.
We do not sell personal information. Except with separate consent or where required by law, we do not disclose personal information for another business to use for its own purposes.
You may request access, correction, deletion, restriction, or withdrawal of consent. Use My Profile → Account → Delete Account in the app or email us. We may verify your identity before completing a request.
Closing an account deletes the active login session, FCM token, running routes and completions, mission attempts and completions, token transactions, shuttle demand submission, personal notification records, and Spotify credential from active systems. The token balance is reset to zero.
The following may not be deleted at the same time:
Information remaining in backup is used only for recovery. Send questions or objections to smtownrunclub@smtownrunclub.com.
Permissions can be changed at any time in device settings. Spotify can also be disconnected at any time in the app.
The race and app are intended for participants who are at least 15 on race day. A minor must have permission from a parent or legal guardian and must also meet any higher age or consent requirement in their country of residence. The app does not newly collect date of birth; eligibility is checked through race registration information and race procedures.
We use encrypted network transport, protected storage for authentication and Spotify credentials, server-side encryption of route data, limited access rights, administrative access controls, and protected backups. Electronic files are deleted using methods designed to make recovery impracticable, and paper records, if any, are shredded or incinerated.
No security measure eliminates every risk. If an incident is confirmed, we will take the measures and provide the notices required by applicable law.
Depending on local law, we process information to perform our service contract, pursue legitimate interests in security and service improvement, obtain consent, and comply with legal obligations. Users may have rights to access, correct, delete, restrict, object, port data, withdraw consent, and complain to a supervisory authority.
We do not sell personal information, share it for targeted advertising, or make solely automated decisions that have legal or similarly significant effects. Mandatory rights under the law of the user's place of residence are not limited by this Policy.
We update this Policy when our service or data practices change. We will announce a material change on the website or in the app at least seven days before it takes effect. Before launching token-entry drawings, prize delivery, or ordinary-user photo-print uploads, we will separately provide the necessary rules, privacy notice, and consent.