Introduction, scope and data controller
This Privacy Policy explains how personal data is processed when you use Runner, a running, walking and workout tracking app with social features for iPhone and Apple Watch, and the Runner backend service it connects to.
The service is provided by ARS Apps (arsapps.com.tr). ARS Apps acts as the data controller (under the Turkish KVKK, the “data controller”; under the GDPR, the “controller”) for the data described here. Privacy requests go to [email protected].
This policy applies to the Runner app and the pages on arsapps.com.tr/runner. It does not cover third-party services that you use through Apple or Google, which have their own policies.
Personal data we process
The list below reflects what the current version of Runner actually does.
- Account data: email address, username, display name, and a password hash if you register with email. With Sign in with Apple or Google we receive the identifier and the profile details (such as email and name) that provider shares with us; we never receive your Apple or Google password.
- Profile data: an optional profile photo, and optional sex, height and weight that you enter yourself. These are used for profile display and calorie calculations.
- Activity data (Runner’s own records): activity type, start and end time, duration, distance, pace, calories, elevation, floors climbed, split times and the GPS route of activities you record. These are uploaded to our server for your history, statistics, streaks, goals and rankings.
- Location data: precise location while you record an activity, find nearby places or routes, see weather, or take part in a group run (see section 5).
- Content you create: post photos, captions, a location name or map you choose to attach, comments, likes, group names and cover images, and chat messages (direct and group).
- Social data: friends or follows, group memberships and join requests, challenges, notifications and your standing in rankings.
- Safety data: reports you submit (reason, optional details and a short text copy, up to 500 characters, of the reported content, kept as evidence), reports made about you or your content, and your list of blocked accounts.
- Subscription data: a Pro entitlement status and its expiry, purchase and subscription records held by RevenueCat and linked to your Runner account ID (see section 8). We do not receive your payment card details.
- Device and technical data: your Apple Push Notification service (APNs) device token, your notification preferences, IP address and request metadata that reach our server, and local caches on your device.
- Data that stays on your device: heart rate from HealthKit or Apple Watch, motion-sensor readings used for floor counting and auto-pause, and offline caches. Runner does not upload heart-rate data to our server.
We do not ask for your contacts, and Runner does not access your address book. We do not collect payment card numbers, advertising identifiers or browsing history.
Why we process your data
- To create and secure your account, sign you in and verify your email address with a 6-digit code.
- To record, store and sync your activities and show history, statistics, streaks, goals and rankings.
- To provide social features: profiles, friends, groups, group runs, posts, comments, likes and messaging.
- To suggest nearby places and routes, show weather and display maps.
- To send notifications you have enabled, such as messages, friend requests and group events.
- To manage Pro access and restore purchases.
- To keep the service safe: screening content with automated moderation before it is published, handling reports, applying blocks, preventing abuse, applying rate limits, fixing problems and handling support.
- To meet legal obligations and to establish, exercise or defend legal claims.
We do not use your data for advertising, we do not sell personal data and we do not track you across other companies’ apps or websites. Runner contains no advertising SDK and does not use the App Tracking Transparency framework. Runner has no analytics or crash-reporting SDK of its own; the only SDK-level usage data we are aware of is described under Mapbox in section 9.
Legal bases
Under Turkish Law No. 6698 (KVKK, Article 5) and the GDPR (Article 6), we rely on the following bases, depending on the data and purpose:
- Performing our agreement with you (KVKK 5/2-c; GDPR 6(1)(b)): account, activities, social features, notifications you requested and Pro access.
- Legitimate interests (KVKK 5/2-f; GDPR 6(1)(f)): security, abuse prevention, content safety and moderation (including reports and blocks), rate limiting and service improvement, balanced against your rights.
- Legal obligation (KVKK 5/2-ç; GDPR 6(1)(c)): where the law requires us to keep or disclose data.
- Your consent (KVKK 5/1 and 6; GDPR 6(1)(a) and 9(2)(a)): for optional processing where consent is required, such as the optional body measurements you enter, and precise location, camera, motion and notification access you grant in iOS. You can withdraw consent by removing the data or turning off the permission in iOS settings; this does not affect earlier processing.
Device permissions (location, camera, photos, motion, notifications, Apple Health) are controlled by iOS and are requested only for the feature that needs them.
Location, GPS routes and live sharing
Runner uses precise location, with your permission, to record outdoor activities and routes, to find nearby parks and routes, to suggest return routes and to show local weather. While an activity is being recorded, location can continue to be used when Runner is in the background.
Your activity route is stored on our server. Whether other people can see an activity or its route is controlled by separate privacy settings in the app, including a route-sharing setting that can restrict who sees your route. Publishing a post can make its caption, photos, location name and map visible to the audience you choose. Routes can reveal sensitive places such as your home or workplace; review your settings before you share.
In a group run, your live progress (distance, time, calories) and, if you choose to share it, your live location are visible to the other participants. If the organizer enables the public spectator link, only the organizer and participants who separately choose “also show me on the spectator link” (and who share their location) appear on it; anyone who has the link can then see their name, progress and live location until the session ends or they turn it off. The link is revoked when the session ends. The link can be opened without an account, so blocking cannot stop someone who has it from viewing it. A group being closed or private does not guarantee that its existence stays hidden.
To suggest places, our server sends the coordinates or map area of your request to OpenStreetMap’s Overpass service. Weather requests send your coordinates to Apple WeatherKit. Map display uses Mapbox (see section 9).
Apple Health, Apple Watch and fitness data
Apple Health access is optional and is controlled by iOS permissions. If you allow it, Runner can read workouts, active energy, walking/running distance and heart rate, and can write workouts, active energy and distance of activities recorded in Runner to Apple Health. On Apple Watch, Runner uses HealthKit during workouts and sends live metrics, including heart rate, to your paired iPhone.
- Stays on your device: heart-rate readings from HealthKit and Apple Watch are used to show your metrics on screen. The current Runner app does not upload them to our server.
- Sent to our server: the activity records Runner itself records (duration, distance, calories, pace, elevation, floors and route), your optional height, weight and sex, and nothing else from HealthKit.
We do not use or disclose HealthKit or other health and fitness data for advertising, marketing or data-broker purposes, and we do not use it to build unrelated profiles. Revoking Health access stops future access; it does not delete records already saved in Runner or in Apple Health. Apple Health records are managed in the Health app.
Runner is a fitness tracking app and is not a medical device. Calorie and pace values are estimates.
Profile, community, sharing and messaging
Your username, display name, profile photo and ranking information can be seen by other Runner users. You control who sees your activity history and routes in the privacy settings.
Messages are delivered to the people in the conversation and are stored on our server. They are not end-to-end encrypted. Other users may keep screenshots or copies of what you share, and we cannot remove those copies.
Push notifications are delivered through Apple’s APNs. Depending on your notification settings, a notification can include a message preview or details of a social event, so that text passes through Apple’s service and may appear on your lock screen. You can change notification previews in iOS settings or turn notifications off.
Automated content moderation. When you create or change content (captions, location names, comments, chat messages, display name, username, profile and post photos, group and challenge names and descriptions), our server sends that text or image to the OpenAI Moderation API to check it before it is saved or shown to others. We send only the content being checked; we do not send your user ID, email address or other account identifiers alongside it. The content itself can still contain personal data, such as a name in a caption or a face in a photo, so do not include information you do not want processed. If the check flags the content, it is not published and you see a message. If the check cannot be completed (for example the provider is unreachable), the content is also not published and you can try again later. Blocking by this check is automatic; if you think content was blocked by mistake, contact [email protected].
Reports. You can report profiles, posts, comments and messages from within the app. A report stores your account, the reported account, the reason, your optional details and a short text copy of the reported content, so that evidence remains even if the content is later edited or deleted. We review reports and may remove content or restrict accounts that violate the Terms of Use. You can also write to [email protected].
Blocking. If you block an account, we store that block and remove existing follows between you. The blocked account can no longer message you, follow you or see your profile, posts and live-run location in Runner, and you no longer see theirs. A public live-tracking link can be opened without an account, so blocking cannot stop someone who has the link from viewing it; blocking someone who organizes a session turns off their public link for you and removes you from it. You can manage blocked accounts in Settings.
Subscriptions, Apple In-App Purchase and RevenueCat
Runner Pro purchases are made through Apple’s In-App Purchase. Apple handles payment and refunds; we do not receive your card details. Runner uses RevenueCat (RevenueCat, Inc.) to validate purchases and manage entitlements.
Runner links RevenueCat to your Runner account by using your Runner user ID as the RevenueCat App User ID. RevenueCat receives purchase and subscription information, including product and entitlement status, and technical information that its SDK collects. Our server receives entitlement events from RevenueCat and stores your Pro status and expiry on your account.
After you delete your account: your Runner account and Pro status on our server are deleted, but deleting the account in the app does not cancel an Apple subscription, and does not currently trigger a deletion request to RevenueCat. Purchase and subscription records may remain with Apple and RevenueCat under their policies and legal obligations. To ask us to request deletion of RevenueCat records, email [email protected]. Cancel subscriptions in your Apple Account settings.
Service providers and third parties
We use the following services. Each may receive only the data needed for its role. We do not sell your data to them or let them use it for their own advertising.
- Apple (Apple): Sign in with Apple, HealthKit (on-device), APNs push delivery, Apple Maps (the small map pictures of routes and nearby places are generated through Apple’s MapKit, which receives the map area shown), and WeatherKit (receives coordinates to return weather).
- Google: Google Sign-In, if you choose it; it provides identifiers and basic profile data.
- Mapbox: map display. The Mapbox SDK downloads map tiles and, in the version we currently ship, Mapbox Telemetry is on by default. Mapbox’s documentation says it sends de-identified location and usage data to Mapbox when the SDK is used, and that users must be able to opt out; per Mapbox, the opt-out is available from the information (i) button on the map. We are working to disable this telemetry by default and will update this policy when it is done. Mapbox’s SDK privacy manifest declares usage, location, identifier and diagnostic data, not linked to identity and not used for tracking.
- RevenueCat: subscriptions (section 8).
- Resend: sends the verification-code email. It receives your email address and the message content.
- OpenStreetMap / Overpass (OpenStreetMap Foundation) and Wikimedia (Wikimedia Foundation): our server queries Overpass for nearby places using your request area; place photos may be loaded from Wikimedia, and the image host can see your IP address.
- OpenAI (OpenAI): automated content moderation. Receives the text and images described in section 7, without account identifiers. According to OpenAI’s API data documentation at the time of writing, data sent to the API is not used to train its models by default, and the Moderation endpoint is listed with no abuse-monitoring log retention; these terms are set by OpenAI and may change.
- Hosting and infrastructure providers: process the data needed to run our servers and database.
We may also disclose information when the law requires, to respond to valid legal requests, to protect users and the service from fraud or abuse, or in a business transfer, subject to applicable protections.
International transfers
Runner’s servers, and several of the providers above (for example Apple, Google, Mapbox, RevenueCat, Resend and OpenAI), may process data outside Türkiye and the European Economic Area, including in the United States. If you use Runner from another country, your data may be transferred internationally.
Transfers are made to provide the features you use. We do not make additional guarantees beyond what each provider publishes in its own privacy and data-transfer documentation. If you want information about the safeguards for a specific transfer, or to object, contact [email protected].
Retention and security
We keep your account and the data linked to it while your account exists, to provide the service. We have not set fixed automatic deletion periods for activities, posts or messages; they are kept until you delete them or delete your account. Short-lived technical records, such as sign-in challenges and verification codes, expire automatically.
- Database: account deletion removes your account and its linked records (see section 12).
- Backups and logs: server backups and technical logs, where they exist, are used for operations and security only. We do not currently publish a fixed retention period for them, and deleted data may remain in them until they are overwritten or removed.
- Reports and blocks: kept while needed for safety, enforcement and legal purposes, and affected by account deletion as described in section 12. We have not set a fixed retention period.
- Third parties: data held by Apple, RevenueCat, Resend, Mapbox, Google, OpenAI and recipients of your shared content is governed by their own retention practices.
We use access control, authentication and encrypted connections (HTTPS) to protect data. No method of storage or transmission is completely secure.
Deleting your account
You can delete your account in Runner under Settings → Delete account. Deleting the app alone does not delete your account.
When you confirm, our server permanently deletes your account and the records that belong to it, including your profile, activities, routes, posts, comments, messages, group data you own, push tokens and related notifications, and closes your active connections.
- Copies already held by other people (such as screenshots or messages they received), Apple Health records, Apple and RevenueCat purchase records, and any backups or logs described in section 11 are not removed by the app’s deletion.
- Sign in with Apple: deleting your Runner account does not currently revoke the Sign in with Apple authorization on Apple’s side. You can remove Runner yourself in iOS under Settings → your name → Sign-In & Security → Sign in with Apple. We plan to add automatic revocation.
- Active subscriptions are not cancelled by deletion; cancel them in your Apple Account settings.
- Reports and blocks: reports you filed and your block list are deleted with your account. Reports about you or your content are kept for safety and legal purposes with the link to your account removed; the saved text copy of the reported content can remain.
If you cannot use the app, email [email protected] from your account email address and we will help.
Your rights and requests
Depending on where you live, you have rights under KVKK Article 11 and the GDPR, including to learn whether your data is processed, to access it, to correct it, to have it deleted, to restrict or object to processing, to data portability, and to withdraw consent. You can already edit your profile and privacy settings and delete your account in the app.
To exercise a right or ask a privacy question, email [email protected]. We may need to verify your identity, and we will respond within the period required by law (30 days under KVKK; one month under the GDPR).
You may also complain to the Turkish Personal Data Protection Authority (kvkk.gov.tr) or, if you are in the EU/EEA, to your local data-protection authority.
Children
Runner is intended for people aged 13 and over. Runner is not directed to children under 13. Runner does not currently verify age technically; the App Store age rating and this requirement are not an age check.
In some countries, a higher age or a parent’s or guardian’s consent is required to process a minor’s data. If you are under the age required in your country, do not use Runner without that consent. If you believe a child has provided data without required consent, contact [email protected] and we will review and delete it where appropriate.
Changes to this policy
We may update this policy when the app or the law changes. The “Last updated” date shows the current version. We will notify you of material changes in the app or by other appropriate means where required, and we will request consent again where the law requires it for a new use.
Contact and privacy requests
Use this address for privacy questions, access, correction and deletion requests, and content reports.