← Home
Privacy Policy
Effective: April 28, 2026 | Last updated: June 29, 2026
This is an English translation. In case of any conflict, the Korean version at
wyr.kr/ko/privacy prevails.
WYR (the "Service") values the privacy of its users and complies with applicable laws including the Personal Information Protection Act of Korea.
This policy describes the categories of personal information we collect, the purposes of use, retention periods, third-party sharing, and user rights.
1. Personal Information We Collect
| Category | Items | Collection Method |
|---|
| Account Registration |
Email, nickname, profile photo (optional), gender (optional), age group (optional) |
Apple/Kakao social login |
| Running Records |
GPS route, distance, time, pace, elevation, heart rate (Apple Watch) |
In-app run tracking |
| Health Data |
Apple HealthKit running records (distance, time, route), external app (NRC, Strava, etc.) GPX/FIT files |
Imported with user consent |
| Social Features |
Instagram account (optional), Signal & Challenge participation history, follow relationships |
User input |
| Media |
Photos and videos attached to Run Cards and Signals |
User upload |
| Push Notifications |
Device push token |
Automatic upon notification permission |
| Automatically Collected |
Device identifier, OS version, app version, access logs, error logs |
Automatic during service use |
2. Purposes of Use
- Storing running records and providing statistics
- Course-based runner matching (discovering runners on the same course)
- Encounter matching (post-run GPS record comparison)
- Providing social features such as Signals, Challenges, and Follow
- Sending push notifications (running activity, social alerts)
- Service improvement and error analysis
3. Location Data Processing Principles
WYR is designed with privacy as the top priority.
- Your exact location is never shared with other users. During a run, the location shown to followers is intentionally fuzzed and displayed only as an approximate area.
- Users can enable Stealth Mode to completely prevent location visibility during runs.
- Encounter matching is performed through post-run analysis only.
- Matching calculations use privacy-masked and downsampled data.
- Exact times are not disclosed; only time-of-day buckets (morning/evening, etc.) are shown.
4. Progressive Information Disclosure
Information visible to other users is determined progressively based on relationships (follow, encounters).
- Profile data (photo, nickname, Instagram) is only shown when the user has explicitly opted in.
- Private accounts only disclose information to approved followers.
- Users can mute other users to block mutual information disclosure.
5. Retention and Deletion
- All personal information is deleted without delay upon account deletion.
- Running records, encounter history, and profile information are all removed.
- Data required by law to be retained is kept only for the legally mandated period.
6. Third-Party Sharing
WYR does not provide personal information to third parties without user consent.
Exceptions are limited to the following cases:
- When required by law
- When the user has given prior consent
7. External Services
| Service | Purpose | Data |
|---|
| Supabase |
Backend (database, authentication) |
User information, running records |
| Apple HealthKit |
Import running records |
Workout data (with user consent) |
| Apple Sign In |
User authentication |
Email (optional) |
| Kakao Login |
User authentication |
Account identifier |
| Firebase Crashlytics |
Error analysis |
Crash logs, device information |
| Firebase Cloud Messaging |
Push notifications |
Device push token |
| Cloudflare |
Web hosting & CDN |
Access logs |
8. User Rights
- You may request to view, modify, or delete your personal information.
- You may refuse location data collection at any time (Settings > Location permissions).
- You may revoke HealthKit access at any time.
- You may control your profile visibility settings directly.
- You may block, report, or mute other users.
- You may request deletion of all data by deleting your account.
9. Security Measures
- All data transmission is encrypted via TLS (HTTPS).
- Database access is protected by Row Level Security (RLS).
- No passwords are stored; only social login (Apple/Kakao) is used.
10. Privacy Officer and Contact
11. Policy Changes
If this policy is updated, changes will be communicated through in-app notices or on this page.