숨런 · SoomRun

개인정보 처리방침

Privacy Policy — 2026-09-26

Summary

SoomRun works without an account, and if you never sign in, nothing leaves your phone. Your runs, location, and health data stay on your device by default.

Only if you choose to sign in are your runs and the routes you ran stored in your account as a backup. There are no advertising SDKs and no third-party analytics SDKs. Everything the app sends by itself is listed in 3-1, with nothing left out.

Apple handles all payment for SOOM+. SoomRun never sees your payment details.

Accounts (optional)

An account is optional. Every feature works the same without one. Its only purpose is getting your runs back after you change or lose a phone.

You can sign in with Apple or with Google.

DataWhere it comes fromWhy
Account identifierApple / GoogleLinks the backup to you
Email addressApple / GoogleIdentifies the account
NameApple / GoogleShown on screen

Data the app uses

DataPurposeStoredSent off device
Location (while in use)Measuring your route and distanceYour deviceBacked up only if you sign in
Step count (motion)Estimating distance when GPS drops in tunnelsYour deviceNever
Heart rate, energy, cadence, elevation (Apple Health)Metrics during a run, and in run detailsYour deviceOnly if you sign in, backed up to your account
Run historyComparing against your past runs (the "ghost")Your deviceBacked up only if you sign in
Sleep, heart rate variability (HRV), resting heart rate (Apple Health, optional)Today's readinessUsed on the device for the calculation only, never storedNever (not backed up even when signed in)
Body weight (Apple Health)Estimating active energyYour deviceNever

Location

Apple Health

Purchases and subscriptions

Apple handles all payment for SOOM+.

For the free trial (three weeks from your first finish), a single start date is stored on your device and in your own iCloud key-value store, so that changing devices does not restart the trial. It is never sent to SoomRun. That store is operated by Apple inside your own iCloud account.

3-1. Crash reports (diagnostics)

When the app stalls or dies, Apple hands over a daily report (MetricKit) and SoomRun sends it to its own server. It goes up as Apple wrote it, so besides the stack trace and the build number it also carries that day's launch, memory and network metrics. It is tied to no device and no person, and carries no runs, no location and no health data.

The same channel carries a quality summary of one run: how many location fixes arrived and how many were thrown away, how long the first fix took and the median accuracy, how long the signal was lost, the share of distance filled in from step count, the location permission state and whether Low Power Mode was on, whether the run came from the phone, the watch or an import, whether it ended by reaching the goal or by the stop button, whether it was a decided race, and whether writing to Health and looking up the neighbourhood and the weather succeeded. Distance and duration are folded into ranges such as 3-5k and 20-40m. No coordinate, no timestamp, no record id, no neighbourhood name, no user identifier — all deliberately left out so that no single run can be picked out of it. The only question it exists to answer is why distance goes wrong in a tunnel.

The same channel carries subscription-screen counts: how often the purchase screen opened, whether the yearly or monthly plan was tapped, and whether it ended in a purchase, a cancellation or a dismissal. It carries no user identifier, no device identifier, and no identifier that could tie two events to the same person. No prices, receipts or transaction numbers. Your number of runs is folded into a range such as 5-19. It counts screens, not people.

Turn it off at Me → Help → Send diagnostics and nothing leaves at all. It is on by default. There is no third-party analytics SDK and no ad SDK.

What we never collect

SoomRun does not track you, and none of your data is ever used for advertising.

Processors (third parties)

SoomRun uses Firebase, operated by Google LLC, to handle sign-in and store backups.

ServiceRoleWhere it lives
Firebase AuthenticationSign-in, account identifiersGoogle's global infrastructure (no region choice)
Cloud FirestoreRun summaries (distance, time, pace, win–loss)Seoul, South Korea (asia-northeast3)
Cloud StorageRoute coordinatesSeoul, South Korea (asia-northeast3)

Cross-border transfer

Your runs and routes never leave South Korea. Only account details are held abroad, disclosed here as required by Article 28-8 of the Personal Information Protection Act (PIPA).

RecipientGoogle LLC
CountryGoogle's global infrastructure — Firebase Authentication offers no choice of storage region
What is transferredAccount identifier, email address, name
When and howAt sign-in, over encrypted HTTPS
RetentionUntil you delete your account
PurposeHandling sign-in and identifying the account
Run records — distance, time, pace, win–loss — and GPS routes are held in the Seoul region and are not part of any cross-border transfer.

How to refuse

Sharing a run

After a run you can generate a "receipt" image to share.

Retention and deletion

Apple Watch

Runs recorded standalone on the watch are stored there and handed to your iPhone when they reconnect — between your own devices only. The watch app uses no network of its own. Backup happens on the iPhone, and only while you are signed in.

Children

SoomRun is not directed at children under 13 and does not knowingly collect their data.

Changes

If this policy changes, we update the date at the top of this page.

Privacy officer

SoomRun is operated by XTI Co.,Ltd. (주식회사 엑스티아이). The person responsible for personal information handling, and for your questions and complaints, is:

Requests to access, correct, delete or stop processing your data go to the address above and are handled without delay. You can also delete everything yourself in the app, under Me → Delete all runs, and by deleting your account.

Contact

manager@x-ti.org