Privacy Policy — Territory Run
Last updated: 27 August 2026 · Version 2.5 (English translation of the Brazilian Portuguese version 2.5)
This is an unofficial translation, provided for convenience only.
This Privacy Policy was originally written in
Brazilian Portuguese and is governed by
Brazilian law — in particular the Brazilian General Data Protection Law (LGPD, Law No. 13.709/2018) —
with the
ANPD (Brazilian National Data Protection Authority) as the competent authority.
This English version has no independent legal validity. In the event of any divergence, omission, doubt
or conflict of interpretation between this translation and the Brazilian Portuguese version,
the Brazilian Portuguese version prevails for all purposes.
Read the official version in Portuguese.
This policy describes how Territory Run collects, uses, shares and protects your personal information, and how you exercise your privacy rights and choices, in compliance with the Brazilian General Data Protection Law (LGPD — Law No. 13.709/2018).
1. Scope and who the controller is
This policy applies to the Territory Run application, its administrative panel and any related service (collectively, the “Service”). Please also read our Terms of Use, which govern use of the Service.
Territory Run is operated by its independent developer (“we”), acting as the controller of the personal data processed by the Service — that is, the party who decides how and why data is processed. Contact for any privacy matter: support@territoryrun.app.
2. Information we collect
2.1 Information you provide
- Account information: email and password (stored encrypted by Amazon Cognito — we never have access to the password in plain text). If you sign in with Google, we receive your email and name as held in your Google account.
- Profile information: nickname and, if you wish, a profile photo (from gallery or camera).
- Optional profile data: city, state (UF), date of birth, sex and phone number. All optional — you may leave them blank, change or remove them at any time under Profile → Edit profile. The phone number is for internal use only (support and account security): it is never shown to other players nor shared for third-party marketing.
- Content you post: messages on your alliance wall, likes, and reports you submit.
- Private messages (chat): the content of the 1:1 conversations you exchange with your friends in the app, and your friends list, friend requests and blocks. Messages are stored on our servers so they can be delivered and displayed in the conversation history.
- Support communications: the content of messages you send through the Contact us form (accompanied by your nickname, account email and app version, so that we can reply).
2.2 Information generated by use of the Service
- Activity data (runs): when YOU start a run, we collect the device’s precise location (GPS) during the run — with a notification visible at all times. From this we derive: route, distance, duration, pace and the map hexagons covered. We do not collect location outside a run you have started; the only exception is the one-off position used to offer you missions in nearby parks (see 3.2).
- Runs imported from a watch (optional, Android): if you connect Territory Run to Android Health Connect, we import your running exercise sessions and their route (GPS track) recorded by your watch or band and made available in Health Connect by the manufacturer’s app (Garmin Connect, Samsung Health, Zepp, etc.). We use this data to credit in the game the run you did without carrying your phone — the same mechanic as a run recorded in the app. We read only running exercise sessions and the route; no heart rate, sleep, weight or any other Health Connect data. It is entirely optional: you grant the permission once (and, on Android 14+, authorise the route for each run) and can revoke it at any time in the Health Connect settings on your device.
- Game data: XP, level, prestige, alliance, badges, missions, day streak, ranking position and the effect of your runs on the territories on the map.
- Referral programme: if you take part in the refer-a-friend programme, we store your personal referral code, who referred you (when you join via a code) and a trail of when a friend you referred ran enough to reach a milestone (the friend’s nickname and the qualifying run). We use this only to credit and audit the programme and its rewards — never for advertising.
- Notification token: if you allow notifications, we store the device’s technical identifier for sending push messages (e.g. “your territory has been attacked”). This can be disabled in the app’s Settings or in the device settings.
- Technical records (logs): operational data about server requests (time, outcome, performance metrics and errors), used to operate, protect and improve the Service.
- Automatic error reports (application crashes): when the app crashes, closes unexpectedly or encounters an error, it automatically sends a technical report of the failure. That report contains the error message and the technical code trace (stack trace), the device model, the operating system version and the app version, and the technical state of the application at the moment of failure. The report does not identify you: we remove the installation identifier that the tool would populate by default, and we do not send IP address, email, screenshots or the content of your screens. What the report does NOT contain: the screens you visited, your navigation through the app, time spent, how often you open the app, or any behavioural metric — none of that is collected, by our decision and not by limitation of the tool (see section 5). The legal basis is legitimate interest (LGPD art. 7, IX) in keeping the Service working and secure, for the specific and sole purpose of finding and fixing defects; you may object to this processing (section 6) by writing to the contact email in section 12.
2.3 Information from other sources
- Third-party sign-in: if you use “Sign in with Google”, Google sends us your name and email to create or access your account. What Google processes is governed by Google’s privacy policy. We do not receive your Google password and do not access other data in your Google account.
- Other players: other users’ interactions with you (e.g. likes on the wall, friend requests, private messages received, contesting the same territories, content reports).
What we do NOT collect: contacts from your address book, microphone, device files, data from other applications, Health Connect health data beyond the running sessions and routes you choose to import (we do not read heart rate, sleep, weight, etc.), and background location outside runs.
3. How we use your information
3.1 To provide the Service
- Create and maintain your account and authenticate your sign-ins.
- Record your runs and convert them into gameplay: calculate distance, XP, conquered territories and mission progress — the core mechanic of Territory Run.
- Rankings and progression: build global and alliance rankings, calculate level, badges and prestige.
- Interaction between players: alliance wall, territory war, territory attack alerts, friendships and private 1:1 chat — your messages are delivered only to the recipient friend.
3.2 To personalise your experience
- Missions near you: we use the position of your last run (or, with your permission, your current position when you open missions) solely to choose a park or urban landmark within 20 km and offer you the mission of the day. That one-off position is not used for any other purpose.
- Regional actions: if you provide city/state (optional), we may use that data in aggregate form to bring events and challenges to your region.
- Age confirmation: your date of birth (if you provide it) is used solely to confirm the minimum age of 13 required to use the Service (see section 7).
- Aggregate statistics: your sex (if you provide it) may be included in aggregate, anonymous statistics about the player base. It is never shown to other players nor used for advertising.
3.3 To protect you, other players and the Service
- Automated anti-fraud: we analyse run data (speed, movement, GPS patterns) to detect travel that is not running on foot (car, bicycle) and to refuse improper credit. See “automated decisions” in section 6.
- Content moderation: nicknames and wall messages pass through an automatic filter for offensive terms; content reported by players is hidden automatically after multiple reports and reviewed by a human administrator.
- Private messages: chat works only between friends who have mutually accepted each other. We do not routinely read your conversations and they do not pass through an automatic filter; if you report a message, the reported excerpt is sent to moderation and reviewed by a human administrator. You can block any player at any time — blocking ends the friendship and prevents new messages and requests in both directions.
- Enforcement of the Terms: we may review accounts and activity to prevent fraud and abuse, and suspend or ban accounts that violate the Terms of Use.
3.4 To operate, analyse and improve the Service
We use technical records and aggregate statistics (e.g. total runs, kilometres summed per alliance, cities with the most players) to monitor the health of the Service, fix errors and decide on improvements. These analyses involve no advertising and no behavioural profiling.
Defect correction: the automatic error reports (section 2.2) are used exclusively to reproduce, diagnose and fix application failures — knowing that “the app closes when opening the map on a particular device model” is what allows us to fix it. Purpose is the criterion: we collect what describes a defect, not what describes your behaviour. An error report is never used to measure usage, build a profile, evaluate players, make product decisions about specific individuals, or for any form of advertising. If we ever wish to measure usage behaviour, that will require a new decision and an update to this policy beforehand, as required by section 5.
3.5 To communicate with you
Transactional emails (registration confirmation, password recovery), push notifications you have authorised, and notices about relevant changes to the Terms or to this policy.
3.6 Physical rewards
Some game achievements (e.g. becoming a Prestige Runner) entitle you to physical rewards, such as a personalised T-shirt. In that case we will ask, at the time and with your consent, for shipping details (full name, address, size). This data is used exclusively to produce and deliver the reward and is discarded after delivery.
3.7 To comply with legal obligations
We may process data to comply with legal or regulatory obligations and to respond to competent authorities (see section 4.4).
4. How we share your information
4.1 Information visible to other players
Territory Run is a multiplayer game — some of your information is visible by nature:
| Visible to other players | NEVER visible to other players |
| Nickname with tag (Name#TAG), profile photo (if uploaded), bio, city/state (if filled in), alliance, level, prestige, total XP, badges, game statistics (runs, kilometres, achievements), ranking position, messages you post on your alliance wall, and the aggregate effect of your runs on the map (hexagons dominated by your alliance) | Your email, phone number, password, detailed routes of your runs, start/end times and locations, date of birth, sex and notification token |
Private messages are visible only to you and the recipient friend — they do not appear to other players. An excerpt reaches our moderation only if one of the participants reports it.
Important: the map shows only which alliance dominates each hexagon — other players cannot see where you ran nor reconstruct your routes. The victim of a territory attack sees the attacker’s nickname and alliance, never the route.
4.2 Processors (service providers)
We share data with companies that process data on our behalf, only as necessary to operate the Service, under contract and a duty of security:
| Processor | What it does | Where |
| Amazon Web Services (AWS) | Infrastructure: servers, database, photo storage, authentication (Cognito) and sending transactional emails | São Paulo region (sa-east-1), Brazil |
| Google (Firebase Cloud Messaging) and Expo | Delivery of push notifications to your device | United States |
| Google (sign-in) | “Sign in with Google” authentication, if you choose it | As per Google’s policy |
| Functional Software, Inc. (Sentry) | Receives and organises the application’s automatic error reports (section 2.2), so that we can diagnose and fix failures | United States |
4.3 What we do NOT do with your data
- We do not sell your personal data to anyone, under any circumstances.
- We do not share data with advertisers, advertising networks or data brokers.
- We do not use your data for targeted advertising — ours or third parties’.
4.4 Legal requests and prevention of harm
We may preserve and share information with public authorities if required by law (e.g. a court order) or if reasonably necessary to prevent death or serious harm to someone, or to detect and prevent fraud and abuse of the Service.
4.5 Change of business control
If Territory Run is acquired, merged or reorganised, data may be transferred to the successor, who will be bound by this policy (or will publish a new version with prior notice to you).
5. Cookies, advertising and tracking
The Territory Run application does not use cookies, advertising SDKs, third-party trackers or behavioural analytics tools. Should this ever change, this policy will be updated BEFOREHAND, with notice in the app.
The application uses a single third-party component: the crash reporting tool described in section 2.2 (Sentry). It is not a tracker nor an analytics tool, and the difference is concrete — the behaviour-measurement features the tool offers are switched off in our application, deliberately and one by one:
| On (describes the defect) | Off by our decision (would describe you) |
| Application crash and code error, with the technical trace (stack trace); device model, system and app version; technical state at the moment of failure | Session recording (app opened/closed, time spent and retention); performance measurement and screen navigation; tracking of taps and interactions; screenshots and screen tree; identification of the device or installation alongside the error; automatic sending of IP and email |
None of these reports uses a cookie, advertising identifier or device fingerprint, and none of them is shared with advertisers.
The territoryrun.app website uses Cloudflare Web Analytics, an audience measurement tool that does not use cookies, stores nothing in your browser, does not track you across sites and does not build individual profiles. It records only aggregate, anonymous counts (pages visited, approximate country, device type), without identifying individuals. No personal data is collected by this measurement.
6. Your rights and choices
The LGPD guarantees you, at any time and free of charge:
- Confirmation and access: to know whether we process your data and to obtain a copy of it. Much of it is visible in the app itself (Profile, History); for a complete and portable copy, write to the contact email.
- Correction: to correct incomplete or outdated data — directly in the app, under Profile → Edit profile.
- Deletion: to delete your account and your data under Settings → Delete account, within the app. Deletion is irreversible and covers profile, runs, routes, missions, badges and photo. The influence your runs left on the hexagons remains only in aggregate, anonymous form, with no link to you.
- Withdrawal of consent: to remove optional profile data (app), disable notifications (app or device), revoke the location permission (device — without it, runs cannot be recorded) and revoke Health Connect access (in the Health Connect settings on your device — without it, runs from your watch stop being imported).
- Portability: to receive your data in a structured format, upon request by email.
- Objection and information: to object to processing based on legitimate interest — including the automatic sending of error reports (section 2.2) — and to obtain information about data sharing.
- Review of automated decisions: the anti-fraud system may automatically refuse a run whose pattern is incompatible with running on foot, and the moderation filter may refuse a nickname or message. If you believe an automated decision was unfair, write to the contact email — a human will review it.
Requests by email are answered within 15 days. If you are not satisfied, you may petition the ANPD (Brazilian National Data Protection Authority — gov.br/anpd).
Device permissions (Android)
| Permission | Use | Required? |
| Precise location | Record the route during runs (foreground service, with a persistent visible notification) | Only for running — the rest of the app works without it |
| Notifications | Territory attack alerts and automatically finished run alerts | No |
| Camera / Gallery | Profile photo | No |
| Health Connect | Read your running sessions and routes recorded by your watch, to import them into the game. Running and route only — no other health data | No — only if you connect your watch |
We do not request background location (“allow all the time”). Health Connect access can be revoked at any time in the Health Connect settings on your device.
7. Children and adolescents
Territory Run is intended for those aged 13 and over. We do not knowingly collect data from children under 13; if we identify an account in that condition, it will be deleted. For minors between 13 and 18, we recommend use with the awareness of a parent or guardian — and remember: the game takes place on public roads, so always pay attention to traffic.
8. How we protect your information
- Managed authentication (Amazon Cognito) — passwords are never held by us in plain text.
- Encryption in transit (HTTPS/TLS) on all communications and at rest in the database and photo storage.
- Every server request requires a valid access token; each player accesses only their own data.
- Administrative access restricted to authorised accounts, with their own authentication.
- Continuous backups (point-in-time recovery) and monitoring with alerts.
- Request rate limiting and server-side data validation.
No system is 100% secure. Security incidents that may create relevant risk or harm to you will be communicated to you and to the ANPD, as required by the LGPD.
9. How long we keep data
| Data | Retention |
| Account, profile, runs, routes and game data | For as long as your account exists; irreversibly deleted when the account is deleted |
| Friendships, blocks and chat conversations | For as long as your account exists. On account deletion, your friendships, lists and conversations are deleted, and the conversation stops appearing for the other person; messages you have already sent remain stored, but with no link to the deleted account — the sender no longer identifies you |
| Aggregate influence on the map hexagons | Remains after deletion, anonymously and with no link to you |
| Technical records (logs) | Short, rotating periods, solely for operation and security |
| Automatic error reports (app crashes) | 30 days, then deleted. As they do not identify you, they are not affected by account deletion — there is no link to erase |
| Physical reward shipping data | Discarded after delivery |
| Backups | Limited retention cycle; deleted data disappears from backups at the end of the cycle |
10. Where data is held and international transfers
Your data is stored in Brazil (AWS, São Paulo region — sa-east-1). There are two international transfers, both restricted and supported by the providers’ contractual safeguards: (1) delivery of push notifications through the Expo and Google (FCM) infrastructure, in the United States, restricted to the device token and the notification content; and (2) the automatic error reports (section 2.2), processed by Sentry in the United States — restricted to the technical content of the failure and without player identification.
11. Changes to this policy
We may update this policy. Relevant changes will be announced in the app, before they take effect, with the new date and version at the top of this page. If you do not agree with a change, you may delete your account at any time through the app.
Questions, requests or complaints about privacy: support@territoryrun.app (data protection officer/DPO: the developer). We respond within 15 days.
13. Language and prevailing version
This policy was originally written in Brazilian Portuguese, is governed by Brazilian law — in particular the Brazilian General Data Protection Law (LGPD — Law No. 13.709/2018) — and has the ANPD as the competent authority.
We may make translations of this policy available in other languages as a reading convenience. A translation is not a standalone document and has no independent legal validity. In the event of any divergence, omission, doubt or conflict of interpretation between the Brazilian Portuguese version and any translation, the Brazilian Portuguese version prevails for all purposes.
Terms of Use (English) · Versão oficial em português