Draft — not yet in effect. It will be published once the operator details and the effective date are confirmed.
Privacy Policy
- Effective
- to be confirmed
- Version
- 2026-11-21
This is an English translation of the Korean original. If they differ, the Korean version prevails.
초코데브(chocodev, the “Operator”) runs the Roxlogy website (roxlogy.com) and the Roxlogy phone and watch apps (the “Service”) and processes your personal information under the Personal Information Protection Act of Korea (PIPA). This policy explains what we collect and why, how long we keep it, who we entrust it to, and the rights you have.
1. Why we process personal information
- Sign-up, sign-in, account management and abuse prevention
- Storing, analysing and comparing your workouts (HYROX-style simulations, runs, PFT, official race results), leaderboards and percentiles
- Crew, center and race tools: join requests and approvals, schedules, attendance, dues, bookkeeping, polls, race timing and the photo zone, center event applications and entry-fee refunds (when you enter a refund account while cancelling), recognising faces when sending participants their photos after an event and giving participants their finish photo (when the staff add one), post-event participant surveys and the event photo album (finding photos you appear in), and staff contacting members (if you add a phone number)
- Live race position (if you connect watch live sharing): showing your current segment, pace, distance and, if you choose, heart rate on crew and center position boards and race boards
- Following crew and center members on an official race day (if you are in a crew or a center and have a HYROX race on your schedule): showing your current segment and expected finish on that crew’s or center’s position board, and saving a finish confirmed by official race timing to your race results
- Following athletes that crew or center staff add to a position board: showing, on that board, the official race timing of an athlete the staff added by race and bib number (who may not be a member of the Service)
- Payments for paid plans and event passes of centers and crews, automatic billing, refunds and receipts
- Community features: feed, follows, posts and comments
- Web push and app push notifications
- AI comments (short write-ups that interpret your records)
- Error analysis, security and statistics to improve the Service
- (Only with your optional consent) building and improving analysis models from pseudonymized workout records — see section 8
If a purpose changes, we will tell you in advance and ask for consent again where required.
2. What we collect
| Category | Items | When |
|---|---|---|
| Account (required) | Email, password (stored with one-way hashing), display name | At sign-up |
| Google sign-in | Email, name and profile picture URL of your Google account | When you sign up or in with Google |
| Profile (optional) | Gender, birth year, height, weight, division, time zone and language, Instagram handle, phone number, official-results athlete link | When you enter them |
| Workouts | Session start and end times, splits, exercises, recording device, RPE, notes, PFT and official race results, goals and training programs, race schedule entries (race, date, division, bib, start time, notes, partners, ticket name) | When you record or import them |
| Health data (sensitive, optional) | Heart rate during exercise (per-segment average and max) — stored only with your separate consent | When you have consented and record with a heart-rate watch or strap |
| Machine raw data | Time-series speed, power and stroke data from machines such as the Concept2 PM5 | When you connect a machine |
| Crews, centers, races | Membership, tier and role history, attendance, dues charges and payment status, bookkeeping entries, posts, comments, polls, race entries and timing, simulation slot bookings, center event applications (division, team, partner name, expected time, depositor name, notes, payment status), event questions and the answers given, the refund account (bank, account number, account holder) you enter when cancelling a center event application and whether it was refunded, the finish photo added by center event staff (to recognise faces, one per application), your answers to a center event participant survey, and event album photos with the participants the staff tag in each photo | When you use those features |
| Payments (paid plans) | Order number, product and amount, payment and cancellation time, payment method, card issuer, masked card number, receipt URL, automatic billing status and next charge date, who paid | When center or crew staff pay for a plan or event passes |
| Photo-zone background | One photo you upload (resized in your browser, with location and other metadata stripped before upload) | When you upload one after finishing a race |
| Race participants without an account | Name or nickname and gender of a participant who has no account (including a doubles partner without an account), and their timing | When race staff enter them for on-site timing |
| NFC checkpoints (wristbands and watches) | Band ID and who it is assigned to (a member or a race entry); if you use a watch linked for live sharing instead of a band, that watch’s tag number; when and where the band or watch was tapped (node, station) and the judgment; on-site device information (node MAC address, firmware version, signal strength, battery; on-site server name and version) | When center staff hand out a band and when you tap a band or your linked watch on a node during a race |
| Watch live sharing (optional) | Name (model) of the connected watch, when it was connected and last sent; during a race simulation your current segment, segment time, total time, distance of the current run, pace and whether you paused; heart rate if you turn on heart rate sharing on the watch (health information — not stored without heart rate consent) | When you connect live sharing in the watch app and record a race simulation |
| Official race timing | As published on the race organiser’s official results site: your team’s name, start wave and start time, split times (16 run and station segments) and roxzone time, race status, expected finish, total time and, if disqualified, the reason | When you are in a crew or a center and have added a bib number to a HYROX race on your schedule — looked up from three days before the race and read from your start until you finish |
| Athletes that staff add to a position board | The race, day and bib number the staff entered and, as published on the race organiser’s official results site, that athlete’s (team’s) name, start wave and start time, split times (16 run and station segments) and roxzone time, race status, expected finish and total time | When a crew leader or co-leader, or a center coach or above, adds an athlete on a position board — collected from the record published on the official results site, not from the athlete |
| Notifications | Web push endpoint and keys, app push device token, browser user agent, notification settings | When you turn notifications on |
| AI connection (MCP) | Connection token you create and whether writes are allowed | When you create a token in settings |
| Collected automatically | IP address, access time, browser and device information, cookies, anonymous cookie-less page performance metrics | While you use the Service |
Account (required)
- Items
- Email, password (stored with one-way hashing), display name
- When
- At sign-up
Google sign-in
- Items
- Email, name and profile picture URL of your Google account
- When
- When you sign up or in with Google
Profile (optional)
- Items
- Gender, birth year, height, weight, division, time zone and language, Instagram handle, phone number, official-results athlete link
- When
- When you enter them
Workouts
- Items
- Session start and end times, splits, exercises, recording device, RPE, notes, PFT and official race results, goals and training programs, race schedule entries (race, date, division, bib, start time, notes, partners, ticket name)
- When
- When you record or import them
Health data (sensitive, optional)
- Items
- Heart rate during exercise (per-segment average and max) — stored only with your separate consent
- When
- When you have consented and record with a heart-rate watch or strap
Machine raw data
- Items
- Time-series speed, power and stroke data from machines such as the Concept2 PM5
- When
- When you connect a machine
Crews, centers, races
- Items
- Membership, tier and role history, attendance, dues charges and payment status, bookkeeping entries, posts, comments, polls, race entries and timing, simulation slot bookings, center event applications (division, team, partner name, expected time, depositor name, notes, payment status), event questions and the answers given, the refund account (bank, account number, account holder) you enter when cancelling a center event application and whether it was refunded, the finish photo added by center event staff (to recognise faces, one per application), your answers to a center event participant survey, and event album photos with the participants the staff tag in each photo
- When
- When you use those features
Payments (paid plans)
- Items
- Order number, product and amount, payment and cancellation time, payment method, card issuer, masked card number, receipt URL, automatic billing status and next charge date, who paid
- When
- When center or crew staff pay for a plan or event passes
Photo-zone background
- Items
- One photo you upload (resized in your browser, with location and other metadata stripped before upload)
- When
- When you upload one after finishing a race
Race participants without an account
- Items
- Name or nickname and gender of a participant who has no account (including a doubles partner without an account), and their timing
- When
- When race staff enter them for on-site timing
NFC checkpoints (wristbands and watches)
- Items
- Band ID and who it is assigned to (a member or a race entry); if you use a watch linked for live sharing instead of a band, that watch’s tag number; when and where the band or watch was tapped (node, station) and the judgment; on-site device information (node MAC address, firmware version, signal strength, battery; on-site server name and version)
- When
- When center staff hand out a band and when you tap a band or your linked watch on a node during a race
Watch live sharing (optional)
- Items
- Name (model) of the connected watch, when it was connected and last sent; during a race simulation your current segment, segment time, total time, distance of the current run, pace and whether you paused; heart rate if you turn on heart rate sharing on the watch (health information — not stored without heart rate consent)
- When
- When you connect live sharing in the watch app and record a race simulation
Official race timing
- Items
- As published on the race organiser’s official results site: your team’s name, start wave and start time, split times (16 run and station segments) and roxzone time, race status, expected finish, total time and, if disqualified, the reason
- When
- When you are in a crew or a center and have added a bib number to a HYROX race on your schedule — looked up from three days before the race and read from your start until you finish
Athletes that staff add to a position board
- Items
- The race, day and bib number the staff entered and, as published on the race organiser’s official results site, that athlete’s (team’s) name, start wave and start time, split times (16 run and station segments) and roxzone time, race status, expected finish and total time
- When
- When a crew leader or co-leader, or a center coach or above, adds an athlete on a position board — collected from the record published on the official results site, not from the athlete
Notifications
- Items
- Web push endpoint and keys, app push device token, browser user agent, notification settings
- When
- When you turn notifications on
AI connection (MCP)
- Items
- Connection token you create and whether writes are allowed
- When
- When you create a token in settings
Collected automatically
- Items
- IP address, access time, browser and device information, cookies, anonymous cookie-less page performance metrics
- When
- While you use the Service
- Heart rate is sensitive information under PIPA Article 23, so we ask for it separately from other consents. Without it you can use the Service as usual; only heart rate is not stored. You can turn it off anytime in settings, and stored heart rate is then deleted without delay.
- Photos you put on a record card (share card) are composed only inside your browser and are never sent to our servers.
- NFC checkpoints record race splits automatically from the time you tap your wristband. Band IDs and raw taps are visible only to that center’s coaches and above; race screens show only the timing. The roster the on-site server downloads before a race (band IDs and names) is used only for on-site display and while the internet is down, and is deleted from the on-site server when the race ends. If you tap a watch linked for live sharing on a node instead of a band, the watch gives the node the tag number it received from our server, and taps are recorded the same way. The node talks to the watch only to read that number and exchanges nothing else.
- A race sim you record separately (on a watch, for example) at the same time as a timed race is merged into that race’s record: its per-segment heart rate is moved onto the race segments and the separate record is hidden from your lists.
- The ticket name on a race schedule entry is optional. If you race on a transferred ticket whose name was not changed, you can enter the name printed on that ticket (the name of the person who passed it on); we use it only to confirm identity, together with the bib, when we fetch official results. Only the person who created the entry can see it, and it is not copied into race results.
- Official race timing is the record the race organiser publishes for anyone to see on its official results site (results.hyrox.com). If you are in a crew or a center and add a bib number to a HYROX race on your schedule, from three days before the race we look that bib up in the official start list and link it to your entry, and from your start until you finish we read your team’s splits about once a minute. We link it only if the official name contains the surname of a person on the entry (or, for a transferred ticket, the ticket name); if it does not match, we do not store that team’s name or times. We do not look up an entry that has no bib.
- Crew leaders and co-leaders, and center coaches and above, can add athletes to their crew’s or center’s position board by race and bib number (up to 30 per race day). An added athlete may not be a member of the Service, and because there is no name to match, we read the official record for that bib in the same way without an identity check. This information is collected from the record published on the official results site, not from the athlete; if you do not want your record added to a board, tell us at the contact in section 11 and we will remove it.
- Card numbers, expiry dates and other payment details are entered directly into Toss Payments’ payment window; the Operator never receives them. For automatic billing we keep only the card token (billing key) Toss Payments issues.
- Information about race participants without an account is entered by the staff of the crew or center running the race, for on-site timing and rankings, and the staff must tell the person before entering it. The name appears with gender and division only on that race’s screens (TV board, photo zone, race page); no session, leaderboard or feed record and no AI comment is made from it.
- Watch live sharing turns on only when you connect it yourself in the watch app, and you can disconnect it anytime on the watch or in Settings > Integrations. Distance is measured from your wrist movement; the “position” shown on boards is your race segment (run or station), not a map location.
- The Service does not collect GPS location data.
- You must be at least 14 years old to sign up. If we learn an account belongs to a child under 14, we delete the account and its data.
3. Retention and destruction
| Information | Retention |
|---|---|
| Account, profile, workouts, crew and center activity | Until you delete your account — deleted immediately when you do (see “What remains after deletion” below) |
| Heart rate (health data) | Until you turn off heart-rate consent or delete your account — turning it off deletes stored heart rate, and AI comments that used it are rewritten without it |
| Workouts you delete | Removed from screens and statistics immediately. A deletion marker is kept so that an offline device cannot bring the record back when it syncs again, and it is destroyed with your account. |
| Ticket name on a race schedule entry | Deleted as soon as your result for that race is confirmed from the official results, and otherwise automatically once 15 days have passed since the race date. Deleted together with the entry if you delete it or delete your account |
| Official race timing linked to a race schedule entry (official name, start wave, splits, status) | Kept with that schedule entry — deleted together with the entry when it is deleted (including when the person who created it deletes their account). Your finish result stays separately in your race results |
| Bib number and official race timing of athletes that staff add to a position board (official name, start wave, splits, status) | Deleted as soon as the staff remove the athlete from the board, and otherwise 14 days after the race |
| Photo-zone background | Deleted within about 5 minutes after it has been shown once and the photo zone moves on, or 24 hours after upload if it was never shown |
| Names of race participants without an account | Deleted automatically 30 days after the entry’s last timing event (finish, did-not-finish, start or entry). Gender and timing stay in the race results without the name. On request we delete it sooner (to be confirmed) |
| Raw NFC taps (band ID, tap time, judgment) | Deleted automatically 180 days after the tap — splits recorded from them stay in the race results |
| Band assignments (band ID ↔ person) | Used until the band is returned (for guests, until that race entry ends); ended assignments are deleted after 180 days. When you delete your account the link to you is removed immediately |
| Watch tag number (when a watch is used instead of a band) | Kept with the watch link — no longer used once you unlink the watch, and erased when you delete your account. Raw taps made with it follow the raw NFC taps above |
| Race roster on the on-site server | Deleted from the on-site server when the race ends |
| Watch live status (segment, times, distance, pace, heart rate) | Cleared automatically 30 minutes after the last update, and immediately when you disconnect the watch or delete your account. Your race record is kept separately, as the session you send after the simulation |
| Watch connection (device name, connection and last-sent times) | Until you delete your account — a disconnected watch can no longer send, and the device name is removed when you delete your account |
| Center event refund account (bank, account number, account holder) | Deleted automatically 14 days after the staff mark the refund as sent, or 60 days after the event even without that mark — only the request and refund times stay in the application record. Deleted immediately if the staff restore the cancelled application |
| Center event photo album (photos and participant tags) | The album closes and the photo files are deleted 90 days after the event ends. Photos the staff remove from the album are deleted at the next sync (within 5 minutes) |
| Center event survey answers | 180 days after the event ends, the link to who answered is removed and only the answers remain as statistics. Deleted with your account |
| Center event finish photo (added by the staff to recognise faces) | Deleted automatically 30 days after the event. If the staff replace or remove the photo, the previous file is deleted within an hour |
| Notification subscriptions | Until you turn notifications off or the subscription expires, at the latest until account deletion |
| Payment records (orders, payments, cancellations, refunds) | 5 years for payment and supply records and 3 years for complaint and dispute records, as required by the Korean Act on Consumer Protection in Electronic Commerce — kept separately for that period even after account deletion, then destroyed |
| Automatic billing card token (billing key) | Deleted immediately when you cancel automatic billing, change the card or delete your account |
| Consent records | Until you delete your account |
| Access logs | Deleted automatically after the hosting and database providers’ log retention period (30 days or less) |
| Pseudonymized data (training datasets) | Up to 2 years from creation — see section 8 |
Account, profile, workouts, crew and center activity
- Retention
- Until you delete your account — deleted immediately when you do (see “What remains after deletion” below)
Heart rate (health data)
- Retention
- Until you turn off heart-rate consent or delete your account — turning it off deletes stored heart rate, and AI comments that used it are rewritten without it
Workouts you delete
- Retention
- Removed from screens and statistics immediately. A deletion marker is kept so that an offline device cannot bring the record back when it syncs again, and it is destroyed with your account.
Ticket name on a race schedule entry
- Retention
- Deleted as soon as your result for that race is confirmed from the official results, and otherwise automatically once 15 days have passed since the race date. Deleted together with the entry if you delete it or delete your account
Official race timing linked to a race schedule entry (official name, start wave, splits, status)
- Retention
- Kept with that schedule entry — deleted together with the entry when it is deleted (including when the person who created it deletes their account). Your finish result stays separately in your race results
Bib number and official race timing of athletes that staff add to a position board (official name, start wave, splits, status)
- Retention
- Deleted as soon as the staff remove the athlete from the board, and otherwise 14 days after the race
Photo-zone background
- Retention
- Deleted within about 5 minutes after it has been shown once and the photo zone moves on, or 24 hours after upload if it was never shown
Names of race participants without an account
- Retention
- Deleted automatically 30 days after the entry’s last timing event (finish, did-not-finish, start or entry). Gender and timing stay in the race results without the name. On request we delete it sooner (to be confirmed)
Raw NFC taps (band ID, tap time, judgment)
- Retention
- Deleted automatically 180 days after the tap — splits recorded from them stay in the race results
Band assignments (band ID ↔ person)
- Retention
- Used until the band is returned (for guests, until that race entry ends); ended assignments are deleted after 180 days. When you delete your account the link to you is removed immediately
Watch tag number (when a watch is used instead of a band)
- Retention
- Kept with the watch link — no longer used once you unlink the watch, and erased when you delete your account. Raw taps made with it follow the raw NFC taps above
Race roster on the on-site server
- Retention
- Deleted from the on-site server when the race ends
Watch live status (segment, times, distance, pace, heart rate)
- Retention
- Cleared automatically 30 minutes after the last update, and immediately when you disconnect the watch or delete your account. Your race record is kept separately, as the session you send after the simulation
Watch connection (device name, connection and last-sent times)
- Retention
- Until you delete your account — a disconnected watch can no longer send, and the device name is removed when you delete your account
Center event refund account (bank, account number, account holder)
- Retention
- Deleted automatically 14 days after the staff mark the refund as sent, or 60 days after the event even without that mark — only the request and refund times stay in the application record. Deleted immediately if the staff restore the cancelled application
Center event photo album (photos and participant tags)
- Retention
- The album closes and the photo files are deleted 90 days after the event ends. Photos the staff remove from the album are deleted at the next sync (within 5 minutes)
Center event survey answers
- Retention
- 180 days after the event ends, the link to who answered is removed and only the answers remain as statistics. Deleted with your account
Center event finish photo (added by the staff to recognise faces)
- Retention
- Deleted automatically 30 days after the event. If the staff replace or remove the photo, the previous file is deleted within an hour
Notification subscriptions
- Retention
- Until you turn notifications off or the subscription expires, at the latest until account deletion
Payment records (orders, payments, cancellations, refunds)
- Retention
- 5 years for payment and supply records and 3 years for complaint and dispute records, as required by the Korean Act on Consumer Protection in Electronic Commerce — kept separately for that period even after account deletion, then destroyed
Automatic billing card token (billing key)
- Retention
- Deleted immediately when you cancel automatic billing, change the card or delete your account
Consent records
- Retention
- Until you delete your account
Access logs
- Retention
- Deleted automatically after the hosting and database providers’ log retention period (30 days or less)
Pseudonymized data (training datasets)
- Retention
- Up to 2 years from creation — see section 8
What remains after deletion: crew dues and bookkeeping records, past meetup attendance and poll votes, finished team race results, programs used by others and crew or center races you ran are also other members’ records, so they stay under the name “Deleted member” with every profile detail removed. They cannot identify you.
Information that other laws require us to keep is stored separately for the period those laws require.
Electronic files are destroyed in a way that cannot be recovered. Copies in database backups disappear automatically when the backup retention period ends.
4. Disclosure to third parties
We do not provide your personal information to third parties, except where a law specifically requires it or an investigative authority requests it through legal procedure.
If you create an AI connection (MCP) token in settings and connect an AI tool you use, that tool can read your own records (and write only if you turned on “allow changes”). This transfer happens at your direction, and you can regenerate or revoke the token at any time.
What other users can see according to the visibility you choose is described in section 6.
5. Processors and transfers abroad
We entrust the following providers with work that is essential to running the Service. Except for Toss Payments, their servers are outside Korea, so personal information is transferred abroad to perform our contract with you (PIPA Article 28-8(1)(3)).
Supabase, Inc. (supabase.com/privacy)
- Country / location
- Japan (Tokyo) data center · US company
- Entrusted work
- Database, sign-in, file storage, server functions, authentication emails
- Items
- All information in section 2
- When / how
- Whenever you use the Service, over encrypted connections
- Retention
- Until account deletion or the end of the contract
Vercel Inc. (vercel.com/legal/privacy-policy)
- Country / location
- Japan (Tokyo) servers and a global edge network · US company
- Entrusted work
- Website hosting and delivery, page performance metrics
- Items
- Access logs, information in requests, anonymous performance metrics
- When / how
- Whenever you visit, over encrypted connections
- Retention
- Log retention period (30 days or less)
Google LLC (policies.google.com/privacy)
- Country / location
- United States and others
- Entrusted work
- Google sign-in, app push delivery (Firebase Cloud Messaging)
- Items
- Google sign-in credentials, app push device tokens and notification content
- When / how
- When you sign in or we send a notification
- Retention
- Until each purpose is fulfilled
Browser push services (Google, Mozilla, Apple, etc.)
- Country / location
- Each provider’s country
- Entrusted work
- Delivering web push notifications
- Items
- Subscription endpoint, encrypted notification content
- When / how
- When we send a notification
- Retention
- Until delivered
Toss Payments Co., Ltd. (tosspayments.com)
- Country / location
- Republic of Korea (not a transfer abroad)
- Entrusted work
- Processing payments for paid plans and event passes, card registration and charges for automatic billing, cancellations and refunds, receipts
- Items
- Order number, product name and amount, payer’s email and name, payment details you enter in the payment window
- When / how
- When we take a payment, run an automatic charge or cancel one, over encrypted connections
- Retention
- Until the retention period required by law (5 years)
If you do not want your information transferred abroad, you can choose not to sign up or delete your account. Supabase and Vercel are essential, so the Service cannot be used without them. You can sign up with email instead of Google, and turn notifications off in settings.
AI comments are generated by an AI model on a server the Operator manages directly. Your records are not sent to outside AI companies.
We fetch public race results from a results lookup service (hyroxresultapi.com). If you link an official-results athlete, we periodically fetch that athlete’s results, and only the linked athlete identifier is used for the lookup. If you add a bib number to a race on your schedule, for 14 days after the race we download that race’s public results list, find the result by bib within the Service, and add it to the race records of the person who created the entry and the partners who accepted it. No information about you is sent to the results lookup service for this. If the name on the result does not match the people on the entry (or, for a transferred ticket, the ticket name entered on it), we do not add it and ask the person who created the entry to check. The ticket name is likewise used only for matching within the Service and is not sent to the results lookup service.
During a race we read official race timing from the race organiser’s official results site (results.hyrox.com). The only things we send to that site are the race and the bib number (and, once linked, the number that site assigns to the team); we do not send your name or account information. We do not download the race’s full start list; we look up only the bibs on crew and center members’ schedule entries and the bibs staff add to a position board, one at a time. Whether the official name matches the people on the entry (or, for a transferred ticket, the ticket name entered on it) is checked within the Service (for an athlete added by staff there is no name to match, so the staff member who added them checks the official name on screen). When a finish is confirmed, we add the result to the race records of the person who created the entry and the partners who accepted it and notify them, and the next day we confirm the ranking and other details from the official results through the results lookup service above. If the official results show a disqualification, we keep the record, show it as disqualified together with the reason, and leave it out of comparisons such as percentiles and trends.
6. What other users can see
- Your display name and the public parts of your profile
- Sessions you make public — their splits (and per-segment heart rate, if you consented to heart-rate collection) are visible to other users in the feed and on your profile
- If you join leaderboards, your records along with the division, gender and age group used for rankings
- In crews and centers you join, their staff can see your attendance, dues status and membership history, and members can see your activity and leaderboard records
- In crews you join, your race schedule entries (race, date, start time, division, notes) and your result for that race appear on the crew schedule. For public crews, people who are not members can see them too. The entry details, including bib and partners, are visible only to members of the same crew. The ticket name does not appear on the crew schedule or in the entry details; only the person who created the entry can see it.
- If you are in a crew or a center and have a HYROX race on your schedule, on race day your team’s name, division, bib and start time and your current segment and expected finish appear on that crew’s position board and that center’s member position board. Only that crew’s active members and admins can open the crew board, and only that center’s active members and admins can open the center board (if one of them puts it on a TV or similar, people watching that screen see it too). Once official race timing is linked through your bib, the board shows your official splits and a link to your official result page; until then it shows a position estimated from the start time on your entry and the race-sim record of you or a teammate in the same crew or center, or else your goal, or else the division average, labelled with the basis used (“From sim sessions”, “From goal”, “Division average”). The contents of your sim record or goal are not shown on the board, but they can be inferred from the expected finish time.
- For an athlete that a crew leader or co-leader, or a center coach or above, adds to a position board, the official name, division, bib, official splits and a link to the official result page are shown to the people who can see that board (the same people as above). They are not shown on other crews’ or centers’ boards or on other pages.
- In races you enter, your name and timing appear on venue screens (TV board, photo zone) and race pages. The same applies to participants without an account entered by race staff (their names are deleted after 30 days)
- If you are given an NFC band or use your linked watch instead of one, that center’s coaches and above can see the band (watch tag) number and your taps (time, station, judgment); if you tap your watch on the center’s registration node, your name appears in that list too
- If you connect watch live sharing, your current segment, segment time, total time, distance of the current run and pace during a race simulation (and heart rate if you turn on heart rate sharing) appear on the position board of crews and centers where you have a race that day (visible to that crew’s active members, that center’s active members, and admins) and on the boards of timing races you enter (track board and live board — public pages anyone can open without signing in). Turn off heart rate sharing on the watch if you don’t want heart rate shown
- If you add a phone number to your profile, the leaders and co-leaders of your crews and coaches and above at your centers can see it on member-management screens and roster files. When you apply to a center event, coaches and above at that center see it on the applicant roster (even if you are not a member). Other crew members and your public profile don't show it
- If you enter a refund account when cancelling a center event application, only that center’s coaches and above see it, on the applicant management screen. It is not included in roster files or sent through the AI connection (MCP)
- A finish photo added by center event staff is kept in private storage. Only that center’s coaches and above (on the applicant management screen) and the applicant and linked doubles partner of that application (on their registration, to view and save) can see it. It is not shown on public pages and not included in roster files or the AI connection (MCP)
- If you answer a center event survey, that center’s coaches and above can see your answers with your name and download them as a file.
- The center event photo album is kept on a server managed directly by the operator and shown at an unguessable address only to that center’s coaches and above and the event’s participants (only those who answered the survey, if the staff require it). Other participants can also view and download the album’s photos, and anyone with the address can open the photos without signing in, so please don’t post the address elsewhere. Which photos you are tagged in is visible only to you and the staff.
Heart rate is sensitive health information. Public sessions show heart rate, so keep a session private if you do not want it seen. You can change session visibility and leaderboard participation at any time.
7. Your rights
You may ask at any time to access, correct, delete or stop processing your personal information, and withdraw consent.
- You can edit or delete your profile and records, and change session visibility, leaderboard participation, notifications, heart-rate and training consent yourself in settings and on each screen.
- You can delete your account yourself in Settings > Data & privacy > Delete account (crew leaders and center owners must hand over first).
- If you cannot sign in, send deletion and other requests to to be confirmed. After verifying your identity we act without delay (within 10 days) and tell you the result.
- You may also make requests through a legal representative or an authorized agent (with a power of attorney).
- Information other laws require us to keep cannot be deleted on request, and requests to stop processing may be refused where a law specifically provides otherwise. We will tell you the reason if we refuse.
8. Pseudonymized data (optional training consent)
Only the records of users who agree to “use pseudonymized workout records to improve analysis models” are processed as below. This consent is optional; every feature works the same without it.
| Item | Details |
|---|---|
| Purpose | Building and improving workout analysis models (e.g. time prediction, pacing analysis) |
| Data | Splits, exercises, machine raw data, RPE, division and recording method, PFT results, gender, age group (10-year bands). Heart rate only with both heart-rate collection and “include heart rate in training data” consents; height and weight only as 5 cm / 5 kg bands |
| Pseudonymization | Names, emails, notes, crews, centers, race titles, locations and official-results links are removed; account and session IDs are replaced with codes derived from a separately kept secret; dates become “days since the person’s first record”, and birth year becomes an age group. |
| Additional information | The secret used to derive codes is kept separately in the database and cannot be read by anyone. Every export is logged with who exported how many records and when. |
| Retention | Up to 2 years from when a dataset is created, destroyed without delay once the purpose is fulfilled |
| Third parties / processors | None |
| No re-identification | We never attempt to identify individuals from pseudonymized data. |
Purpose
- Details
- Building and improving workout analysis models (e.g. time prediction, pacing analysis)
Data
- Details
- Splits, exercises, machine raw data, RPE, division and recording method, PFT results, gender, age group (10-year bands). Heart rate only with both heart-rate collection and “include heart rate in training data” consents; height and weight only as 5 cm / 5 kg bands
Pseudonymization
- Details
- Names, emails, notes, crews, centers, race titles, locations and official-results links are removed; account and session IDs are replaced with codes derived from a separately kept secret; dates become “days since the person’s first record”, and birth year becomes an age group.
Additional information
- Details
- The secret used to derive codes is kept separately in the database and cannot be read by anyone. Every export is logged with who exported how many records and when.
Retention
- Details
- Up to 2 years from when a dataset is created, destroyed without delay once the purpose is fulfilled
Third parties / processors
- Details
- None
No re-identification
- Details
- We never attempt to identify individuals from pseudonymized data.
You can withdraw this consent at any time in Settings > Data & privacy. After you withdraw, your records are left out of datasets created later. Records cannot be singled out and removed from datasets already created or from models already trained on them (PIPA Article 28-7).
9. Security measures
- Administrative: administrator access to personal information is kept to a minimum.
- Technical: encryption in transit (HTTPS), one-way password hashing, row-level access control in the database so only you and authorized people can read your data, and server secrets kept on servers only — never in apps or browsers.
- Physical: we rely on the access control and security of our cloud providers’ data centers.
11. Privacy officer
| Item | Details |
|---|---|
| Operator | 초코데브(chocodev) |
| Privacy officer | to be confirmed |
| Contact | to be confirmed |
Operator
- Details
- 초코데브(chocodev)
Privacy officer
- Details
- to be confirmed
Contact
- Details
- to be confirmed
Send privacy questions, complaints and requests for remedy to the contact above. We will respond without delay.
12. Remedies
- Personal Information Dispute Mediation Committee: +82 1833-6972 (www.kopico.go.kr)
- Personal Information Infringement Report Center: 118 (privacy.kisa.or.kr)
- Supreme Prosecutors’ Office Cyber Investigation: 1301 (www.spo.go.kr)
- Korean National Police Agency Cyber Bureau: 182 (ecrm.police.go.kr)
13. Changes to this policy
This policy takes effect on to be confirmed. We announce changes in the Service 7 days before they take effect, and ask for consent again for significant changes such as new items or purposes.
Document version: 2026-11-21
Business information
초코데브(chocodev)
CEO김초호Business registration no.544-09-03252Mail-order sales reg. no.PendingAddressPendingCustomer servicePendingEmailflexmania@gmail.comPrivacy officerPendingHosting providerVercel Inc.Terms of ServicePrivacy PolicyRefund policy
© 2026 초코데브(chocodev)