rit.run 개인정보 처리방침 · Privacy Policy

Summary

• We collect data needed to provide features, including run logging and analysis, account operations, security, legal compliance, and customer support.
• This policy now reflects the App Store Privacy Label categories for Contact Info, Health & Fitness, Location, User Content, Identifiers, Usage Data, and Diagnostics.
• Location-based services are governed by the separate Location-Based Service Terms.
• If you share a workout as a post, workout summaries, route maps, start/end areas, photos/videos, and post text may appear in the Social feed according to the visibility you select.
• Guest workouts used without an account stay only in the guestFitness/v1 local area on this device and are not sent to Firestore, Cloud Storage, or workout APIs unless you later sign in and explicitly agree to move eligible guest-recorded workouts.
• A public post and allowlisted public social information may appear to people without an account in read-only mode. Responses exclude account UIDs, raw Storage paths or tokens, and precise locations.
• Service notifications may be sent for operational purposes such as workout recording or sync status, account and security events, service changes, and customer-support responses.
• Health data and precise location / GPS routes are used for app functionality and run analysis, not for ad targeting, sale, or third-party marketing.
• You may exercise access, rectification, deletion, restriction, portability, and withdrawal of consent at any time, and lodge a complaint with a supervisory authority.

1. Data We Collect

• Account/Profile/Contact Info: name, email, profile image, user IDs/tokens from Google or Apple sign-in; login logs (timestamps, partial IP)
• Running/Health Data (with your consent):
  • Precise location / GPS routes, start/end location summaries, distance, speed/pace, elevation, workout time, cadence (if available)
  • Heart rate and derived metrics (if available)
  • Body metrics: height, weight, date of birth, gender (for performance metrics and personalization)
• User Content: customer-support emails/messages, Social feed post text, comments, photos/videos uploaded or submitted through app features, and related metadata
• Guest Mode: country code, applicable minimum age, policy version, declaration-token issue and expiry times, and App Check integrity signals are processed to control Guest Public Feed access. Guest responses exclude account UIDs, raw Storage paths or tokens, precise location, and raw workout identifiers.
• Service Notification Data: notification tokens, notification settings, delivery/receipt status, and notification logs related to workout recording, sync, account security, and service changes
• Device/App Info and Identifiers: device model, OS/app version, language/timezone, internal user ID, device ID, AAID/IDFA, coarse IP, crash/error logs, and performance logs. Optional diagnostic error logs are sent and linked to your account only after in-app consent.
• Usage and Advertising Data: app usage events, ad impressions/clicks, and campaign performance events, subject to your consent and platform settings

2. Purposes & Legal Bases (GDPR)

• Create/manage accounts, authenticate and control access: contract necessity
• Store workouts, provide stats/charts, personalized analysis: contract necessity and, where applicable, consent
• Product personalization, app stability, security, and fraud prevention: legitimate interests or, where applicable, consent
• Customer support: contract necessity / legitimate interests
• In-app ads, developer advertising or marketing, third-party advertising, and measurement: consent and platform privacy settings
• Legal compliance and dispute handling: legal obligation
• Processing of sensitive (health) and precise-location data: explicit consent

3. Handling of Sensitive & Precise Location Data

• Processed strictly to the minimum extent for app functionality and run analysis (purpose limitation).
• Health, fitness, and precise-location data are not used or provided for ad targeting, sale, third-party marketing, or tracking purposes.
• Collection and use conditions, user rights, and contact details for location-information inquiries are also described in the Location-Based Service Terms.
• Raw routes are not automatically posted to the public feed unless you share a workout to the feed.
• Upon withdrawal of consent, we stop new processing, subject to statutory retention and dispute handling.
• When you delete data, raw GPS traces and raw health data are erased; aggregated/de-identified statistics may be retained for service quality.

3.1 Guest Mode and Guest Public Feed

• Workouts imported or recorded in guest mode are kept in local storage on this device, separate from account data. Eligible guest-recorded workouts are copied to an account only after a separate post-sign-in consent; there is no automatic upload without consent.
• The Guest Public Feed applies the same visibility == public rule to historical and new posts. It does not use a separate per-post publication document.
• Account-free viewers receive post text, author display name and handle, a limited workout summary, and image previews delivered by the backend. Comments, reactions, follows, profiles, routes, locations, heart rate, calories, and account identifiers are not provided.
• The backend fails closed when a post becomes non-public, the post or account is deleted, or the author is no longer active and public.
• Guest viewing has no account identity, so signed-in block and mute relationships cannot be applied. A blocked or muted person may therefore sign out and view public posts.

4. External Processors, Integrations, and Cross-Border Processing

• Firebase / Google Cloud: account identifiers, profiles, workouts, health, location, content, and operational logs are processed for authentication, databases, Storage, API hosting, and Analytics through HTTPS/API. Verified placements are Firestore nam5, Storage US-CENTRAL1, and backend asia-northeast1.
• Apple / Google platform services: account, permission, and health data are processed through the selected sign-in, HealthKit/Health Connect, and platform APIs.
• Google Maps, OpenStreetMap, Open-Meteo: location or map/weather queries may be processed over HTTPS/API for map, route-display, and weather features.
• Garmin / COROS: when connected by the user, tokens and workout, health, and route data are processed through provider APIs for synchronization and connection management.
• Google AdMob / Firebase Analytics: advertising identifiers, ad/use events, and device/app information may be processed for advertising and measurement. On iOS, personalized ads are requested only after ATT authorization; otherwise the App requests non-personalized ads.
• OpenAI: workout evaluation may process required workout context and free text; RunCover/background generation may process a selected image and prompt context. Workout evaluation uses store=false; the current background image workflow may use store=true. Requests use HTTPS/API under standard paid API terms.
• Google Gemini / Veo: RunCover or generated-media features may process prompts, images, and selected workout context over HTTPS/API under standard paid API terms.
• ChatGPT connector: when you initiate the external connection, the selected request and required service context are processed to provide that connection.
• Email provider: addresses and message bodies are processed for support, rights requests, and operational email. The deployed SMTP provider was not verified.

Detailed processing countries, subprocessors, and retention periods may vary by feature, account setting, and provider terms. This is a factual inventory based on verified source and infrastructure, not evidence that contract, console, subprocessor, or legal review is complete. We do not provide health, fitness, or precise-location data for advertising.

5. Retention

• Account, workout, health, location, and content data: retained in the primary store while the feature is provided or until you request deletion of the record or account. A separately identified basis and period must apply where statutory or dispute preservation is required.
• Firestore recovery data: PITR and daily backups are enabled; daily backup retention is 30 days. Deleted data may remain recoverable during this bounded window.
• Cloud Storage: deleted objects have a seven-day soft-delete window.
• Cloud Logging: the verified `_Default` bucket retains data for 30 days and the locked `_Required` bucket for 400 days. `_Required` is for Google Cloud-required audit logs, not ordinary app-content storage.
• Optional app diagnostics: target retention is 30 days and the new writer is prepared to add expiresAt. That writer is not deployed and legacy records may lack expiresAt, so 30-day deletion of all records is not yet proven.
• External providers and support messages: retained according to the relevant request, account settings, and provider terms. Provider deletion SLAs, preservation holds, and contractual retention still require operational reconciliation.

6. Your Rights & How to Exercise

• Rights: access, rectification, deletion, restriction, portability, withdrawal of consent, object to certain processing
• How: in-app Settings > Profile > Delete Account, or privacy@dendrove.com (rights & general privacy), and dpo@dendrove.com for regulatory/legal matters.
• Complaints: you may lodge a complaint with your local supervisory authority (e.g., Korea PIPC or your EEA/UK authority).

7. Ads, Tracking & Personalization

• App Store tracking disclosures are limited to Contact Info, Identifiers, selected User Content, Diagnostics, and Advertising Data, subject to consent and OS settings.
• Health, fitness, precise-location data, and original photos/videos are not used for ad targeting.
• On iOS, the App requests personalized ads only after ATT authorization. If ATT is denied, restricted, unavailable, or the notice fails, the App requests non-personalized ads and does not block core use. You can also manage advertising choices through Android advertising ID and app/OS settings.
• (California) We do not sell personal information for money. If ad/measurement partner processing is considered “sharing” or targeted advertising under applicable law, you may opt out or request limitation of sensitive data use by contacting us with subject: [CCPA Request].

8. Security

• TLS in transit, encryption at rest (where applicable), access controls/least privilege, anomaly monitoring
• We will notify you of breaches as required by law.

9. International Transfers

Use of the global providers in Section 4 may process data outside your country. Verified Google Cloud placements are Firestore nam5, Storage US-CENTRAL1, and backend asia-northeast1, using HTTPS/API transfers. Where applicable law requires it, we apply the required transfer basis, notice, consent, or contractual safeguards. Exact provider subprocessors and contract status remain subject to review.

10. Children

Signup minimum ages are KR 14, US 13, GB 13, DE 16, ES 14, FR 15, IT 14, and 18 for unreviewed countries. Users below the threshold cannot sign up, and no guardian-consent flow is offered. The country matrix remains subject to legal review.

11. Automated Decision-Making

We do not engage in automated decisions producing legal or similarly significant effects.

12. Regional Notices (Brief)

• EEA/UK (GDPR/UK GDPR): see Section 2 for legal bases. You may lodge complaints with your supervisory authority. Where legally required, we will appoint and disclose our EU/UK representative here.
• California (CCPA/CPRA): residents may request to know/delete/correct/opt out/limit sensitive data use.
• Republic of Korea (PIPA): Data subject rights available; cross-border transfer safeguards will be disclosed where applicable.

13. Contact & Deletion

Use in-app Settings > Profile > Delete Account or privacy@dendrove.com. For general help contact support@dendrove.com; for regulatory/legal communications contact dpo@dendrove.com. Data will be erased except where retention is required by law.

14. Changes

We will announce changes via in-app notice or by updating the “Effective Date”.

Annex: HealthKit / Health Connect Notice

• Apple HealthKit: health data is used only for features and personalized analysis; not for ads, marketing, sale/sharing, or tracking. You can change permissions in iOS Settings.
• Android Health Connect: accessed health data is used only to provide services; not for ad targeting or tracking. You can manage permissions in Android Settings.