Privacy Policy

Scorch · Last updated 25 October 2026

This policy covers the Scorch app, scorch.run and early-access requests. Scorch combines outdoor activity recording, a territory game, private indoor training tools and optional community features. For privacy questions or requests, contact razanians313@gmail.com. Practical help is on our Support page.

Who is responsible

The controller under the EU and UK General Data Protection Regulation, and the Data Fiduciary under India's Digital Personal Data Protection Act 2023, is Mohammad Raza Ansari, Feldtmannstraße 134b, 13088 Berlin, Germany (operator of Scorch). Email: razanians313@gmail.com. The same address answers privacy questions, requests and grievances. Scorch has not appointed a data protection officer because the law does not require one at its current size. See also the Legal notice.

Why we may use your information (legal bases)

What	Legal basis
Your account, saving and syncing workouts, the territory game, standings, clubs, Convoy, buddies, chats, voice messages and calls, and support	Our contract with you, which is the Terms you accept (GDPR Art. 6(1)(b)). In India: your consent at sign-up (DPDP Act s. 6) and, where it applies, use for the purpose you gave the data for (s. 7(a)).
Optional features you switch on: private backup, Apple Health, "Open for a buddy", Alerts, gym-clan scoring	Your consent (GDPR Art. 6(1)(a); DPDP s. 6). You can switch each one off at any time; this does not undo earlier lawful use.
Security, abuse and spam prevention (including request limits), finding and fixing crashes, moderation of reports, fair-play checks of workouts and claims, and keeping proof of what you agreed to	Legitimate interests in keeping Scorch safe, fair and accountable (GDPR Art. 6(1)(f)). You can object; we then stop unless there are compelling reasons, for example an ongoing abuse case.
Keeping records the law requires, and answering lawful requests	Legal obligation (GDPR Art. 6(1)(c); DPDP Rules 2025, rule 8(3)).

The sign-up box records that you accepted the Terms and read this notice. In the EU, EEA and UK, the main processing relies on the contract, not on that box.

Consent records

When you create an account, you see a short list of what Scorch uses and why. You enter the year you were born and tick one empty box to accept the Terms, the Community Guidelines and this Privacy Policy. Accounts made before 7 October 2026 are asked once in the app. Scorch's database stores the following:

what it covered (Terms and Privacy);
whether it was given or withdrawn;
the notice version;
the server's date and time;
the birth year you entered;
the region setting of your phone and the minimum age that applied;
the app language, version and platform.

This record proves what you agreed to and when (GDPR Art. 7(1); DPDP Act s. 6(10)). It cannot be edited, and only you can see your own record in the app.

The record is kept while your account exists. After you delete your account it is kept for one more year, and then erased. You can see it, withdraw and ask for a copy in Settings › Privacy & Security › Your consents.

Account and activity information

Information	Purpose and storage
Account and profile	Email, authentication records, account ID, username and optional bio, city, country, profile photo and social profile handles (Instagram, TikTok, Snapchat or YouTube) are handled by our Supabase app backend. They support sign-in, account security and your profile. A social handle is text you type; Scorch does not sign in to, read from or post to those services. Passwords are handled by the authentication service; the app does not store your password as a profile field.
Outdoor workouts and imported GPX files	Recorded GPS points can include precise latitude, longitude, time, accuracy and altitude. Saved workouts include activity type, distance, duration, pace, recording source and game-validation results. The app keeps recovery and pending-upload data on your device and sends saved workouts to Supabase for your history and eligible game actions.
Territory and game records	Territory shapes, capture times, activity type, strength, coins and cosmetic choices are stored in Supabase to calculate and display gameplay. When someone’s claim takes ground from you, a record of who took it is kept so your own map can colour that player; only you see it. Speed and route checks may flag a workout or prevent a territory reward; they are not medical assessments.
Clubs and Convoy groups	Club descriptions, membership and ownership, plus Convoy codes, start position, participants, activity and group results are stored in Supabase to run the group features.
Buddies and chat	If you use Buddies: whether you are open for a buddy, the activities you choose (gym, running or cycling), an optional gym name and gym pin rounded to three decimal places (about 100 m), an optional short note, your profile city, an approximate area rounded to two decimal places (about 1 km) and a birth year you enter once. The birth year is used only to place you in an age group (13–17, or 18 and over); it is never shown to other people and cannot be changed in the app. Buddy requests, their status and dates, chat rooms, the messages you send (text, sender and time), message deletions and how far you have read are stored in Supabase to deliver chats between buddies and inside clans and clubs.
Voice messages and voice calls	A voice message you record in a buddy, clan or club chat is uploaded as an audio file to a private area of Supabase Storage, together with a message record (sender, chat, time and length). Only people who can read that chat can play it, through short-lived private links, and people who blocked you cannot. It stays while the chat and the message exist and is deleted when you delete the message or your account. When you start or join a voice call, Supabase stores who started the call, who joined and when, so it can ring the chat and let members join; the audio itself goes directly between the phones in the call over an encrypted connection (WebRTC) and is not recorded or stored by Scorch. To connect, the phones in a call see each other’s network address (IP address and port) and exchange connection details through a private Supabase Realtime channel that only current members of that call can use.
Training with a gym buddy	When you choose “Link our phones” in the Gym tab, Scorch sends the accepted buddy you pick a push notification (your username and an invitation to join) and records that you invited them and when, only to limit repeated invitations; that record is deleted with either account. While you train together, the two phones exchange the workout (exercise order, set timers, whose turn it is, rep counts and the weights and repetitions of finished sets) through a private Supabase Realtime channel that only the two of you can open. This exchange is not stored on our servers. Your own finished sets are saved to your indoor journal on your phone as described below; your buddy’s sets stay on their phone.
Group radio (nearby, without internet)	Only while you turn Group radio on: your phone uses Apple’s peer-to-peer Wi-Fi and Bluetooth to connect directly to nearby phones running Scorch that entered the same group code and are in the same age group (13–17 or 18 and over). Your username, account ID, the texts you send and the voice clips you record while holding the talk button go phone to phone to those group members, and group members’ phones pass them on so the rest of the group can receive them. They are not sent to or stored on our servers. Received voice clips are kept in temporary storage on the phone and deleted when the radio is turned off; the conversation is not saved after you leave the app. Nearby phones scanning for Group radio can see a random session name, a short fingerprint of the group code and the age group while the radio is on, never your username. A birth year you enter for Group radio is kept in the app’s private settings on your device.
Earlier coaching records	Coach enrollment, the directory, profile editing, follows and coaching requests have been removed from the current app interface. Earlier coach roles, drafts, published profiles, follows and request records may remain in Supabase; requests can include participants, messages, status and timestamps. Removing these screens does not automatically delete those records or remove copies held by earlier app versions. Contact support about access or deletion, or use account deletion.
Safety and support	Reports, block relationships, report details and relevant content snapshots, including a copy of a reported chat message, support abuse handling. If you email support, your message and any information or attachments you choose to include are handled through email.
Crash reports	When the app crashes or a screen fails, it sends what went wrong to Supabase: the error and where in the app’s code it happened, the screen it was on (without any IDs), the app version and update, the iPhone model and iOS version, Apple’s own crash report for the app (MetricKit) when there is one, and a random number created for this installation. It never includes your account, name, position, messages or anything you typed. Only the Scorch team can read crash reports; they are used only to find and fix problems and are deleted after 90 days.

Local information and optional private backup

Body settings and goals: optional height, weight, birth year and sex support fitness estimates and personal settings. These fields are kept in account-scoped local storage and are not included in the app's workout uploads. Phone step and motion readings are used locally where the device supports them. These readings and estimates are not a diagnosis.

Indoor training: your weekly gym plan (rest days, muscle groups, exercises and their sets, repetitions, rest and weights), the training goal you choose for it (lose weight, gain weight, bulking or cutting), a workout that is still open, your indoor journal, duration, optional distance, exercises, sets, repetitions, load and notes are stored on your device. Exercises you create yourself (their name, muscle group, how they are counted, equipment and default sets, repetitions and rest) are saved to your Scorch account so they also work on a new phone; a deleted one stays archived so workouts you already logged keep its name, and deleting your account deletes them all. Optional private backup is available in the Scorch mobile app and stays off until you turn it on. Before any upload or restore on a device, the signed-in account must explicitly choose to enable private backup. After that choice, new completed indoor and strength sessions can be sent to Supabase, including their record IDs, times and the training fields you entered, and restored to that account on another eligible device. Earlier device-only entries are not automatically uploaded. Unfinished sessions and Moments photos or videos are outside this backup feature. A local save or a pending upload is not confirmation that a cloud backup completed.

Moments and photo tools: selected photos and videos, captions, gym text and attached indoor statistics are stored in the app's private local journal. There is no public Moments feed or automatic upload of this journal. A profile picture is different: choosing one saves it to your cloud profile. Video files you select can retain their original embedded metadata. Glowing muscles: when you add a gym photo or video, Apple’s Vision framework finds your body’s joints and outline on your phone so the muscles you trained can light up; the analysis, the photo or video and the result stay on your device (temporary files in the app’s cache) until you choose to save or share the finished image or video.

Saved plans, recovery files and queued uploads also use local storage. The weekly Chapter and kit checklist have been removed from the current app interface, but earlier local preferences may remain until account cleanup; removing a screen does not erase its existing data. Language, appearance and other device preferences may remain between account changes. Local storage is not the same as an encrypted backup service; device security, operating-system backups and copies you export can affect how long information remains available.

Location and device permissions

Recording: starting an outdoor workout starts GPS recording. Background location supports a session while the screen is locked or another app is open, subject to your permissions and operating system. Stopping the workout stops its recording. Scorch does not start background workout tracking just because you open the app.
Other location actions: opening a map, locating yourself, planning a route or setting a privacy zone can use a foreground position without starting a workout. Search and route services receive the information described below.
Photo stickers: adding a temperature forecast or a place name asks before using location for that feature. Opening the photo composer alone does not request weather or send a location. A temperature request sends coordinates rounded to two decimal places, roughly a one-kilometre grid, to Scorch's Cloudflare service, which uses a shared forecast cache and requests data from MET Norway when needed. Account details, cookies and authentication tokens are not sent with the weather request. Cloudflare and MET Norway may process network IP addresses. The selected temperature is labelled as a forecast, with its forecast hour and source/licence credit included in saved or shared photos. A place-name request uses your device's map service.
Camera and media: camera access is used when you choose to capture media; recording a video may also use its microphone. Group radio uses the microphone only while you hold its talk button. Voice messages use it while you hold the record button, and voice calls use it while you are in a call; you can mute it in the call. Gym voice commands (“Scorch start”, “Scorch stop” or, if you choose it, “Hey stop”, and the weight you say for a set), when you turn them on, listen only while a gym workout is open and on screen; speech is recognised on your iPhone and no audio or text leaves it. Ordinary library selection uses the system picker. Saving an image to Photos may require permission. Scorch does not import your contacts.
Local Network: Group radio asks for Local Network access so your phone can find and connect to group members’ phones nearby. It is used only while you have Group radio turned on.
Buddies: saving your buddy card while “Open for a buddy” is on uses a foreground position once and stores only an area rounded to two decimal places (about 1 km). Other people see a distance rounded to whole kilometres, never your position. Gym suggestions work as described for Photon below.
Notifications: local reminders run on your device. If you turn on Alerts, the app stores a device push token with your private profile and the server sends short alerts (for example when your territory is taken or defended, when you receive a buddy request or when a chat has a new message) through Expo's push service and Apple or Google's notification service. An incoming voice call alert says “Voice call: tap to join” and a voice message alert says “Voice message”. A chat alert shows the sender's username, the clan or club name for group chats and the start of the message (up to 160 characters), which your device may show on the lock screen depending on your notification settings. No location track is included. Turning Alerts off, or deleting the account, removes the token.

Apple Health (optional, iPhone): only if you allow it (on the permissions screen at first start or with Connect Apple Health in Settings), Scorch asks Apple’s permission to read your heart rate, resting heart rate, steps, active energy and exercise minutes (including readings from an Apple Watch), your weight, height and sex (to estimate calories) and to save workouts you finish. These readings are shown and used on your iPhone only (on Home, during a workout and in its summary). Scorch does not read your birth date from Health. Scorch never sends Health data to its servers, never sells or shares it, and never uses it for advertising. Finished runs, rides, walks and gym workouts are written to the Health app only while “Save workouts to Apple Health” is on. You can stop in Settings and change or remove access at any time in the Health app. Scorch does not connect to Health Connect, Garmin or other heart-rate devices; recorded activities can also be imported manually as GPX files.

You can change permissions in device settings. Refusing a permission limits the features that need it.

What other people can see

Signed-in Scorch users can see community territory shapes, your username, chosen colour and game information. Map photos depend on your map-photo setting. Standings and recent captures can also display profile and game information. Hiding yourself from standings does not hide your territory or recent captures; switching off your map photo does not remove it from every other feature.

Player page: tapping a player in Standings or on the map opens their player page for signed-in users. For a Public account it shows the username, city, the profile photo only when the map-photo setting allows it, territory and loop totals, and any social profile handles the person added. For a Private account it shows only that the account is private (and the username to people who can already see it, for example in a club or chat). Handles are optional, can be removed in Edit profile at any time and are not verified as proof of account ownership. Opening one leaves Scorch for that service or website. People on either side of a block cannot open each other's page.

A privacy zone in Settings keeps your identity off territory near your home: loops that touch the chosen circle still appear on other users' world maps (every loop is part of the shared game), but without your username, photo, city or colour, and with an owner reference that differs for every such loop, so they cannot be traced to you or linked to each other. The zone's centre is stored with your private profile so the server can apply it. It does not erase the underlying GPS workout, change your own map view or remove coordinates from your GPX exports. The Private switch on your Profile (also on the World tab) does the same for all of your territory everywhere: your loops still count and appear on other users' maps, but the map, the live feed, rival alerts and the standings show “Private player” instead of your username, photo, city or colour, and your player page shows only that your account is private; switch back to Public at any time. Hiding community content is a viewing preference, not a setting that makes your account invisible.

Club directories display club information; membership rosters are available to members with applicable visibility and block restrictions. Convoy participants can see group information and results. The current app no longer offers coach discovery or coaching interactions. Previously published coach information and participant-only requests are retained under the existing backend access rules; this interface change does not revoke earlier publication or perform a database deletion. Contact support to request removal of earlier records. Self-reported qualifications and social handles were not verified credentials or proof of account ownership.

Gym clans: a community-created clan's name, venue, city and approximate map pin can be shown to other signed-in users, together with aggregate member counts and weekly consistency totals. These are community-supplied gym locations, not verified venues or member check-ins. A requested nearby search uses your position to calculate distance; it does not add that position to gym membership records. Membership and competition choices are stored for your account. Joining a clan and opting into consistency scoring are separate choices from enabling private backup. Only eligible new completed sessions backed up after joining and opting in can contribute. The clan summary does not publish your private workout, exercises, loads, notes, media, exact location or individual attendance. Visibility settings and supported blocks also affect the displayed totals.

Buddies and chat: while “Open for a buddy” is on, you choose who can find your card: only your gym (signed-in people in your age group who saved the same gym) or everyone (signed-in people in your age group whose saved area is within about 100 km of yours, who entered the same country in their profile, or who saved the same gym). They can see your username, profile photo (only when your map-photo setting allows it), city, chosen activities, gym name, note and an approximate distance in whole kilometres. Turning the switch off hides your card from new searches. A private chat opens only after both people accept a buddy request. People under 18 cannot find, request or privately message adults through Buddies, and adults cannot find, request or privately message people under 18. Clan and club chats are group chats: current members of that clan or club can read and send messages there, and leaving the group removes access. When a buddy connection ends, your private chat with that person becomes read-only for both of you. Blocking someone ends the buddy connection and hides their chats and messages from you. Messages are not end-to-end encrypted; they are stored on our servers so they can be delivered, checked against the blocked-word filter described below and reviewed when reported.

Buddy invite links: Invite a buddy creates one random invite code for your account, stored in Supabase and deleted with your account. The link you share contains that code and your username. Anyone who opens it can download Scorch. A signed-in person who opens it in Scorch sees your username and profile photo (only when your map-photo setting allows it) and can add you as a buddy straight away, which opens a private chat. This works only within the same age group and never across a block. After a recent decline or ended buddy connection it is also refused. At most 30 people a day can join through one link. You choose where to post the link; posting it publicly lets anyone who sees it add you. You can end a buddy connection or block someone at any time, and Reset link stops the old link working. The invite page on scorch.run sets no cookies and reads the code only to open the app.

Group radio: anyone who knows your group code and is nearby can join that radio, so share the code only with your group. Texts are checked on your phone against the same blocked-word list described below, before sending and on arrival. You can mute a person on your phone, and anyone you block in Scorch is also silenced in Group radio. Reporting or blocking someone needs an internet connection. Connections between phones are encrypted by Apple’s MultipeerConnectivity framework; each group member’s phone can read the messages it receives and passes on.

Sharing a photo, video or export opens your device's share options. Scorch does not automatically post it to Instagram, Snapchat or another service. Recipients and services you choose can keep or redistribute copies, including previously shared Chapters, under their own rules. The current app has no connected Instagram or other social account access, automatic social posting, public gym-video contest or event feed.

Use in-app report and block controls for supported community content. Reports are not public posts; they can preserve a restricted snapshot of the reported material. Blocking limits supported interactions and visibility, but cannot recall copies already obtained. See our Community Guidelines.

Services that receive information

The current app does not include advertising or cross-app advertising-tracking integrations. Services below process information to provide features, deliver messages, operate infrastructure or diagnose problems. An external request can reveal your IP address and other network or device metadata even when Scorch does not attach your account ID.

Service	Information and purpose
Supabase	Authentication and the app's cloud records listed above. The current main database is configured in West Europe (London, United Kingdom). That database region is not a guarantee that all provider operations or support processing stay in that country.
Expo push service (Expo, Inc.)	Only when Alerts are on: receives your device push token and each alert's title, text and type (for a chat message: the sender's username, the clan or club name and up to 160 characters of the message), and forwards it to Apple Push Notification service or Firebase Cloud Messaging. Tokens identify a device, not your name or location.
Cloudflare and Google STUN servers	Only during a voice call: each phone asks a public STUN server (stun.cloudflare.com or stun.l.google.com) for its own public network address so the phones can connect directly. The server sees your IP address and network port; call audio does not pass through it.
Resend and email services	Recipient addresses, account-confirmation and security messages, and delivery information for transactional email. Your own email provider also receives messages delivered to your mailbox. Support correspondence uses email.
Cloudflare	Website requests and network information for hosting and security; submitted early-access details in D1. Waitlist abuse prevention uses a keyed identifier derived from the IP address rather than storing the raw IP in its rate-limit table. Identifiers rotate in ten-minute windows and expired counters are removed during cleanup; this does not describe Cloudflare's separate infrastructure logs.
Platform map services	Native map display and device geocoding use the platform's map services, including Apple or Google depending on the device. Map areas, location and place queries may be processed to provide those features.
Photon, operated by Komoot	Place-search text and, when used to rank nearby app results, coordinates rounded to two decimal places. Website city suggestions send the city text you type.
BRouter	Selected route start, destination and intermediate coordinates, at up to six decimal places, plus a walking or cycling routing profile, to calculate a planned route. For runs and walks the same coordinates are also sent once with the cycling profile, so the planned line can follow the side of the road for your direction. If you leave a planned route during a session, your current position, the route's remaining stops (or a point further along it) and a point on the route just past where you left it are sent the same way to calculate a new way, at most once every 15 seconds and 30 times per session. If you start a session more than 100 m away from your planned route, your current position and the route's stops (or its start) are sent the same way to find the way there. You can switch this off in the session's map settings (Auto new route).
Scorch/Cloudflare and MET Norway weather	On a requested temperature sticker, Scorch's Cloudflare service receives a rounded location cell and network information. It stores the cell, projected forecast timeseries and cache dates in a shared D1 cache, without an account or device identifier. Provider expiry controls freshness; a 24-hour retention period does not make a forecast fresh for 24 hours. Expired retained entries are removed by a 15-minute cleanup schedule and before new fetch admissions; provider-required longer expiry is respected, and failed cleanup can delay removal. Application code does not log weather requests or copy client headers to MET Norway, but Cloudflare may add visitor IP headers to outbound requests. MET Norway's privacy policy describes provider logs, including IP retention of up to 90 days for public meteorological services. Data is from MET Norway under CC BY 4.0; Scorch selects a forecast hour, rounds temperatures and converts units when selected. The app does not persist a device weather cache. Photos and exports you save remain under your control.
Expo update service (Expo, Inc., USA)	When the app starts, it asks Expo whether a newer version of its JavaScript code exists, so we can fix bugs without a new App Store version. Expo receives the app version, platform, release channel, a random installation ID created by the update library (not linked to your account) and network information such as your IP address. No account, workout, location or chat data is sent.
Services you open or share to	Social profiles, music apps, product resources and your chosen share destinations process your visit or shared content under their own policies. Opening a link is not a Scorch account connection or a purchase through Scorch.

International transfers: the main database is in the United Kingdom, which the European Commission recognises as providing adequate protection. Expo, Resend, Cloudflare, Google and Apple are companies based in the USA. Where a provider processes personal data outside the EU/EEA, the transfer relies on the European Commission's adequacy decision for certified organisations (EU–US Data Privacy Framework) or on the Commission's standard contractual clauses in that provider's data processing terms. You can ask us for a copy of the relevant safeguards.

These providers may process information internationally. A provider's infrastructure, support and retention arrangements can differ from the main database region. Contact us with questions about a particular service or transfer.

Automated checks and AI

On-device features: the muscle glow on gym photos, the weigh-in (the weight read from a photo of your scale) and the AI Coach in a gym workout use Apple's Vision framework on your iPhone. A weigh-in photo stays on your phone and is never sent; only the weight you save is kept, in Plan & progress. The AI Coach watches your form through the front camera only while its screen is open. The picture is turned into 19 body points on the phone, kept in memory for that exercise, and never recorded, stored or sent. The AI Coach also works without camera access, by time and voice. Its spoken lines are fixed sentences written in advance; no chatbot or language model is used.

Apart from these on-device features, Scorch does not use artificial-intelligence or machine-learning services to process your personal information, does not send it to AI providers and does not use it to train AI models. There is no AI chatbot in Scorch. Workout and territory checks are fixed rules, such as speed, distance and loop-closure limits. They can flag a workout or withhold a game reward. Text you publish or send, including buddy notes and chat messages, is compared with a fixed list of blocked words and phrases; a match stops that text from being saved or sent. These checks do not make decisions with legal or similarly significant effects. If you think a check was wrong, contact support and a person will review it.

Website and early access

The website stores a language preference in your browser. Submitting early access saves your email, optional city and activity, signup source and timestamp in Cloudflare D1 so we can manage the list and contact you about availability. This does not create an app account. City suggestions can contact Photon before you submit the form.

To remove a waitlist entry or stop early-access messages, contact razanians313@gmail.com from the address you used. App-account deletion does not automatically remove a separate waitlist entry.

Retention and deletion

Cloud account and activity records remain while the account exists unless removed through an available control or a supported request. Local journals and files remain on that device until removed. Scorch does not currently apply a general automatic expiry period to account histories, indoor journals, Moments or early-access entries.

Consent records are kept while the account exists and for one year after it is deleted, then erased. A moderation notice telling you that a message of yours was removed stays in your Activity list until you swipe it away or delete your account. Request-limit counters are kept for 15 minutes. Crash reports are deleted after 90 days.

Deleting a privately backed-up indoor session removes its stored workout content and records a deletion marker linked to your account and that record ID. This marker prevents a delayed upload from recreating the session and lets other devices reconcile the deletion when they next sync. These markers do not currently expire automatically; deleting the account removes them. A device-only entry has no cloud backup to delete. Offline deletions remain pending until the service confirms them.

For gym clans, deleting a contributing session, leaving its clan or withdrawing competition consent revokes the affected contributions. A private consumed-day marker remains to prevent scoring the same day again, even after changing clans or opting back in. It contains account, clan and session identifiers, the contribution day and receipt time, and revocation status; it does not retain the workout content. These markers have no automatic expiry and are removed with the account. Action receipts preserve membership changes and their results for safe retries.

Voice messages and calls: voice messages remain while their chat and message exist; deleting your voice message deletes its audio file. Call records (who started and joined a call, and when) remain while the chat exists. Calls are not recorded.

Chats: messages remain while their chat exists. You can delete a message you sent; it is removed for everyone in that chat, but people may already have read or copied it, and a report can keep a snapshot of it. Messages do not yet expire automatically. Buddy cards, requests and connections remain until you change them or delete your account.

Settings → Delete account requests removal of the current backend's sign-in record and associated profile, workouts, territories, coach records, privately backed-up indoor records and deletion markers. It also removes that account's gym membership, action receipts and contribution markers, its buddy card, buddy requests and connections, its gym buddy invitation records, its private chats and the messages it sent in clan and club chats, including its voice message files (removed first; if that fails, the deletion stops so you can try again) and its call records. The app then attempts to clear that account's local journals, media, private preferences, route plans, gym plan, any open workout, queued uploads and recovery data. A failed local cleanup is reported. See Delete your account for the request route if you cannot use the app.

Deletion has limits:

Reports made by other people can retain restricted snapshots of material you previously made visible, for abuse handling. There is no general automatic expiry schedule for these reports. Deleting your own account removes reports you submitted.
A shared club or gym clan can continue with another owner, and shared Convoy results may remain after an individual account is removed.
Separate early-access records, earlier-project accounts and data on other devices are not automatically removed by deleting the current account. The current backend did not automatically migrate older-project account history. Identify these separately when contacting support; never send your password.
Device-wide preferences, some local safety caches and older records that cannot be attributed to the current account may remain. Signing out alone does not delete local journals.
Files saved to Photos, downloaded exports and copies held by recipients are outside the app's deletion controls. Provider logs and recovery copies can also remain subject to their retention arrangements. Deletion is not a promise of immediate removal from every backup or recipient's device.

Your choices and rights

In the app, Settings › Privacy & Security › Your consents shows what you agreed to and when. It lets you ask for a copy of your data and withdraw your consent. Withdrawing your Terms or Privacy consent means Scorch can no longer run your account, so the app takes you to Delete account.

Depending on applicable data-protection law, you may request access, correction, deletion, restriction or portability, object to processing, and withdraw consent where consent is the basis for processing. Withdrawal does not undo earlier lawful processing. Send requests to razanians313@gmail.com; we may need information to verify that a request concerns your account. Do not email passwords, confirmation codes or unnecessary identity documents.

You can edit profile information, manage supported visibility settings, remove local Moments and change device permissions. Available exports include an individual outdoor session as GPX, an indoor journal as JSON and media you choose to share. GPX exports contain the private route, including coordinates inside a privacy zone. These tools are not a complete export of every account record; contact us for other access requests.

You may raise a concern with your local data-protection authority. Our Support and account-deletion pages provide contact options.

India (Digital Personal Data Protection Act 2023)

If you use Scorch in India:

We ask for your consent with an itemised notice before your account is created. The app shows it in English, Hindi or Urdu.
You can withdraw your consent as easily as you gave it.
You can ask for a summary of your personal data and of who received it. You can ask for correction, completion, updating and erasure. You can nominate a person to exercise your rights if you die or cannot act.
For grievances, write to razanians313@gmail.com. We answer within 90 days at the latest. If you are not satisfied, you can complain to the Data Protection Board of India.
People under 18 cannot create a Scorch account in India.
If there is a personal-data breach, we inform the Board and the affected people as the DPDP Rules 2025 require.

Children

Scorch asks the year you were born once, when you create an account. The minimum age is 18 in India, 16 in the EU and EEA, and 13 elsewhere. The app uses your phone's region setting to choose the rule. The birth year is self-declared and is not identity verification.

Accounts of people under 18 start as Private on the map. Their loops stay anonymous to others until they switch to Public themselves. Buddies and chat ask for a birth year once: people under 13 cannot use them, and people under 18 are matched only with other people under 18 for buddy search, buddy requests and private chats. This birth year is self-declared, not verified identity; report anyone you believe is misrepresenting their age. Do not use Scorch if you do not meet the applicable requirements. If you believe an underage child has provided information, contact us so we can investigate and handle the account and data request.

Security and policy changes

Scorch uses encrypted network connections, account-scoped database access controls and secure native session storage. Request limits protect the service from abuse: a per-account counter per minute is kept for 15 minutes. If a personal-data breach is likely to put you at risk, we will tell you and the competent authority without undue delay, within 72 hours where the law requires. Local fitness journals and selected media are not all stored in the authentication keychain. Protect your device and account, and share only information you intend others to receive. No security control removes every risk.

The date above identifies this version. Updates will be published on this page. Read it alongside our Terms and Community Guidelines.