← Trailborn

Trailborn Privacy Policy

This document has not been reviewed by a lawyer.

Document version: 2026-11-18
Effective date: 24 October 2026

Who processes your data

The data controller is Michał Mijalski, a private individual running the Trailborn project under the name Forest Nap Studio.

Trailborn turns your everyday movement into territory on a map. This document says what reaches us, why, who we pass it to and how long we keep it. It describes the game as it actually works on the document version date above.

Age

Trailborn is intended for people aged 16 and over. On the start screen, above the "Start the game" and "I already have an account" buttons, there is a sentence about age and these documents. By tapping either button you confirm that you are at least 16, accept the terms and have read this policy. We record this with your account, together with the date and the versions of both documents. We do not ask for a date of birth; we store the declaration itself and use it for two things: to avoid creating an account for someone under 16, and to configure advertising correctly. Accounts created before 16 September 2026 gave a birth year, which we keep for that purpose only. We do not infer age from phone settings or from behaviour in the app.

What data we process

Account. The identifier of the Google or Apple account you sign in with, the e-mail address linked to that account (with Sign in with Apple this may be Apple's relay address if you choose so), your nickname, colour, character appearance, age declaration (a birth year only for accounts created before 16 September 2026) and app settings (language, theme, units, notifications, animation speed).

Playing without an account. You can play without a Google or Apple account. We create such an account, without an email address, only when you tap "Start the game" on the start screen; right after you tap, we record your acceptance of the terms, the version of this policy and your age declaration (see "Age"). Your first nickname is drawn at random, and you can pick your own a moment later. Your phone creates a random key and keeps it in the system's protected storage (Keychain on iPhone, Keystore on Android). We store only a one way hash of that key, which lets us recognise your phone the next time you play, plus the other account data described above, without an email address. Until you link Google or Apple, your progress is tied to this phone: if you remove the game from an Android phone or change phones before linking an account, we cannot restore your progress. When you link an account, we delete the hash and you sign in with Google or Apple from then on. To limit abuse, we count new accounts created without signing in from one phone (a random installation identifier) and from one IP address; we do not store the IP address, and the counter is kept in server memory for at most one hour. You delete an account without registration in the app, like any other (see "Deleting your account").

Checking whether you already have an account. Before we create a new account without registration after you tap "Start the game", the app spends a few seconds checking whether you have already played Trailborn on this phone, so that it does not create a second, empty account for you. It checks only what the phone knows from your earlier play: the key of an account without registration stored on the phone; a Google account that has already signed in to Trailborn on this phone (on Android through Google's Credential Manager, which shows only such accounts; on iPhone through the remembered Google sign-in); and the way this phone last signed in to the game (Google or Apple). We store that way in the phone's protected storage after every successful sign-in and delete it when you delete your account; on iPhone it survives reinstalling the game. If Google points to such an account, the server opens it only if it already exists and creates nothing, and the game asks whether it is your account ("That's not me" closes it unchanged). If the phone last signed in with Apple, we suggest signing in with Apple instead of a new account. We do not read the list of accounts on the phone, we do not recognise an account by the phone model, IP address or a device identifier, and we do not fingerprint the device.

Steps and floors — three sources. With your explicit consent we read your step and floor counts from:

Steps and floors are converted into metres, which you spend discovering roads. Only daily totals reach the server, not the raw sensor log. The phone counter's history, including the numbers read from the Recording API, stays on the device for 30 days and is then deleted. Daily totals are kept for as long as your account exists — without them we cannot show statistics or detect the same activity being counted twice. For a new account we count steps from at most the 24 hours before it was created, if Health Connect or the Health app recorded them. The phone counter and the Recording API count steps only from the moment you allow them. Older steps are not turned into metres.

We do not read heart rate, sleep, weight or any medical records. We never write anything back to Health Connect or to the Health app. Health data is never sold, never used for advertising or ad profiling, and never passed to insurers or for credit scoring.

Height and weight (optional). We do not read them from any app. If you enter them in your profile and tick the consent box, we keep them on your account and use them to count the calories you burn walking, from your step count only. The daily total of those calories is stored with your daily steps. Nobody else sees your height, weight or calories, and we do not use them for advertising or profiling. Bjørn’s in-game total of all players’ calories includes them without identifying anyone. You can delete them in your profile at any time, and we then also delete the calories counted from them.

Location. We keep only your last position, overwritten on every change. We do not store a continuous GPS trail. The exception is token visits: when your phone reports a position within 75 m of a token you have not collected yet, we record a visit, that is your account, the token, the time and the distance from it, without coordinates. The next walk with steps uses it to pay out the token. We delete the visit once the token is paid out, after 24 hours at the latest, and together with the account. Collected tokens (which one and when) are kept with the account.

We do store which road segments you have claimed and when — that is the game state without which the map does not work. Claimed roads indicate the areas where you play. In the route privacy settings you can enable incognito mode; it shifts your future routes, while territory claimed earlier stays where it was.

Your first route. If on your first walk the phone gives no GPS position within about 20 seconds, we paint the first route from the approximate position the phone knows from the network (Wi-Fi, cell towers) or from a reading no more than 15 minutes old, accurate to within 500 metres. Later routes always wait for GPS. If you do not allow location, your first route starts in a city in your country, usually the capital. The server picks the country from your phone's time zone and, if it does not recognise the zone, from the region and language set on the phone. We then store that city and the country code as your last position; your first real position after you allow location replaces them.

Messages. The game has two chats. Messages in the team chat are visible to the members of your team. Messages in the global chat are visible to every signed-in player. Both chats expire automatically after 48 hours. You can delete your own message within 48 hours of sending it; a team administrator can delete any message in the team chat. An automatic filter masks profanity in messages before other players see them. When you like another player's message (with a double tap), we store who liked which message; chat participants see the message's number of likes, and we keep the like until that message or your account is deleted.

Message translation. Under another player’s message in the team chat and the global chat you can tap “Translate”. We then translate that one message into the language chosen in the game. The translation is done by our own server with LibreTranslate, running on the same machine as the game (Contabo, European Union); the message text does not go to any external translation provider. The translation program receives only the text of the message, with profanity already masked, without a nickname, account identifier or any other player data. We store the finished translation with the message so that the next person asking for the same language gets it at once, and delete it together with the message: after 48 hours, or earlier if the author, the team admin or a moderator deletes the message or the author deletes their account. We do not record who asked for a translation. To limit abuse, the server keeps the number of your translations in the last hour in memory only, for at most an hour, and records the total number of translated characters per month without any link to an account. We do not ask for separate consent: we translate at your request, as part of the chat.

Flags with a message. If you plant a flag, we store the flag's place on the road, the message (up to 140 characters), the level of the chest you leave and the time. The flag goes up not where you stand but on the nearest walkable road, at most 300 m away; we also store that road and how far the flag was moved. In incognito mode the flag goes up in your stand-in area, shifted from you by a distance (10 to 50 km) and direction fixed for your account, like your routes. The server compares the position you plant from with your last stored position to check that you are there, and does not store it with the flag. The flag is visible to others right after you plant it, without a moderator checking it first; a moderator can remove a flag that someone has reported. All players, with or without a team, plant, see and find flags on every game map (Solo, Team, Team War), and every map shows the same flags. On a walk, a player in a team collects them along the Team War route and a player without a team along the Solo route. You can also collect a flag by tapping it from close by on any map; in incognito mode only by walking. In app versions older than 1.2.1, flags work only in Team War. Only the player who finds the flag sees your nickname, the message and the chest level; everyone else sees just the flag on the map. You only receive a message that someone found it, without the finder's nickname. Do not plant a flag near your home or anywhere you do not want to show to others. A flag nobody finds disappears after 30 days. We delete the record of a flag (message, place, who found it and when) 180 days after the flag closes, that is after it is found, expires, is rejected or is withdrawn, or earlier if you delete your account.

Races. If you organise a race or accept an invitation we store: the race name, the start and finish (or the duration), the invitees and their answers, your progress since the start (metres and steps, computed from the walk records we keep anyway) and the result. The other entrants see your nickname and progress. You receive the result as a message from the game in the in-app inbox.

Duels. If you send or accept a duel challenge we store: both players, the stake and each of its movements (points held, returned or won), when the challenge was sent, answered and expired, each player's time zone at acceptance (the duel's days follow it), when the duel starts, ends and is settled, your steps on each day of the duel (the steps and the gear bonus separately, computed from the walk records we keep anyway), the cheers you send your opponent, and the result and rating change. With your account we store your duel rating, your numbers of wins, losses and draws, and your winning streak. Your opponent sees your nickname, character appearance, rating and gear bonus, your steps live from the start of the duel, and the result after settlement. You both receive the duel messages (challenge, start, daily progress, cheers, result) in the in-app inbox, with the other player's nickname; they disappear after 30 days. The notification about the daily progress and the result only says that a message is waiting, without step counts. The basis is the contract, as for races; the steps come from the daily totals we read with your consent (see "Steps and floors — three sources").

When looking for an opponent, players see a nickname together with the level and the duel rating. Among suggested opponents we show players who walk a similar amount each day: the server compares the median of daily steps over the last 14 days (at most 30 % apart) and picks players who played on at least 4 of the last 7 days. This median is never shown to other players, and a search by nickname does not read steps at all.

At settlement we check whether both players' sync records from the time of the duel raise any suspicion (risk score and steps per hour). A duel with suspicious steps, and a duel in which a phone's time zone changed, is checked by a moderator, who sees both players' steps and result in the admin panel. So that two accounts of one person do not duel each other, we compare the game installation identifiers recorded at both accounts' sign-ins and the step sources of their walks (see "Fair play" and "Starter chest"); if they match, the challenge cannot be sent. When you delete your account we erase your steps on duel days, your cheers and your duel rating. The duel's result stays in your opponent's history without your nickname or identifier: both players' step counts, the stake, the dates and the rating change. Duel records are not deleted automatically; we keep them while either player's account exists, and once both accounts are deleted only the result remains, without any player data.

Country and duels. Duels are not available in Belgium or the Netherlands. To ensure this, when you open duels or the rankings screen (to know whether to show the duel board), send or accept a challenge, the server determines your country from data it already has: the store country of your latest purchase or subscription payment (if any), the country in which the last position reported by your phone lies, the country code from your phone's settings at your latest sign-in and, if the phone never reported a position, the country of your first route (see "Your first route"). A Belgian or Dutch store country turns duels off even while you travel; among the other data, the first one available in that order decides. Among suggested opponents we leave out players whose phone had a Belgian or Dutch region at their latest sign-in. We do not store the result of this check, and your opponent does not learn why you cannot duel. The basis is our legitimate interest in complying with the laws of those countries (Article 6(1)(f) GDPR).

Reports and moderation. If you report content or someone reports yours, we record: who reported, what the report concerns, the chosen reason, your optional comment and a snapshot of the reported message — chat expires after 48 hours, so without the snapshot a moderator would receive an empty case. We also record the moderator's decision and any appeal. A flag's message can be reported by the player who found it; we then also record the message and the nickname of the flag's author.

Blocks. We keep the list of people you have blocked until you unblock them.

Diagnostics. At sign-in we record the app version, device model, system version, interface language and the country code from your device settings. On a crash we record the error and its technical context. From version 1.1.45 the app also records the state of the permissions and settings the game needs — location, step access (Health Connect or Health), the phone’s step counter, notifications and the ad consent — and the kind of app that records your steps (for example “phone” or “Garmin”), without the activity data itself. This lets us explain why someone’s steps are not being counted. We do not record your IP address — with one exception, described below under invitations, where we keep a one-way hash of it for 48 hours.

Fair play. We check whether the activity is humanly possible (step cadence, floor counts, daily limits) and reject data entered manually in a health app. On first launch the app creates a random installation identifier and keeps it in the system's secure storage; its only purpose is to stop the same steps feeding two accounts. It is not a device identifier and none of your data can be derived from it.

Trailborn+ and purchases. The app sells the Trailborn+ subscription and chest bundles. Payment is handled by the store you installed the game from — Google Play or the Apple App Store. We do not receive your card number or any other payment details. The store passes us a purchase confirmation, which we verify with Google or Apple; we store the product identifier, the transaction identifier assigned by the store, the date and, for a subscription, the period it is paid up to. We also store the price, the currency and the store country that the store gives for that purchase or renewal, to count the game's revenue. We ask the store for the subscription status at renewal. We also record whether a free trial is running — the monthly chest bundle is not given during one. Free Trailborn+ days (for invitations, from events, as a gift from another player or from us) are recorded on the account together with their source; if you have a paid subscription, they wait until it ends. For every paid month of the subscription you receive 3 days of Trailborn+ to give away: to a person you choose, to a random player without Trailborn+ who has opened the game in the last 2 days, or to nobody. We record your choice, the recipient and the date. A person you choose yourself receives a message with your nickname; a randomly chosen person is not told who the days are from, and you receive a message with their nickname. You can see your own gift record in the game. A free trial does not earn a gift.

Chest gifts. When you buy a chest bundle as a gift, we store who bought it, what was given to whom and the store's transaction identifier. The gift intent is created before the store window opens and holds the product, the recipient and the buyer. You see the recipient's nickname in the confirmation before paying, and the recipient receives an in-game message with your nickname. Before accepting a gift, the server checks for both sides that the account is not blocked or a test account, and their age and country, as for duels (see "Country and duels"); the excluded countries are Belgium and the Netherlands. We do not store the results of these checks, and the buyer is not told why a gift is not possible. Gift records are kept for 13 months from their creation, and abandoned intents for 60 days, also after one party deletes their account (their link is then removed), because they are needed to settle a refund. The legal basis is performance of the contract (Article 6(1)(b) GDPR) and, for checking whether a gift is possible, our legitimate interest in complying with the law and protecting players (Article 6(1)(f) GDPR).

Invitations. Every account has a personal invitation link and code. When someone accepts your invitation, we record who invited whom, how the game recognised the invitation (a link, a code, the Google Play store or a visit to the invitation page), on how many different days the invited person has played and when both of you received Trailborn+ days. The inviter sees the invited person's nickname and their progress towards the reward. When someone opens an invitation page, we keep for 48 hours a one-way hash of the IP address (computed with a secret key; the address itself is not stored) and the type of device. Its only purpose is to let the game ask a new player on an iPhone — where the App Store does not pass the invitation on — whether they came through an invitation; the new player always confirms it themselves. When the invited person plays on 3 days, people further up the invitation chain are rewarded too: whoever invited the inviter (2 days of Trailborn+), the person one level higher (1 day) and everyone above them (a level 1 chest). Each of them receives an inbox message with the nickname of the invited person and the nickname of the person who invited them. If someone in the chain deletes their account, we record the link to the nearest person above them so that the chain does not break; the deleted account itself is not kept.

Points, challenges and expeditions. We record the points you earn and spend in the game. If you take on Bjørn's weekly challenge, we record the week, the step target, your step count from the previous week, the points set aside and the result. You get the result as a message from Bjørn in the in-app inbox: after a successful week with the week's goal, after an unsuccessful one with the number of steps you were short. With notifications on, a notification may also come; it says at most that the goal was reached and that a message is waiting, without the number of steps. During a community expedition we count your distance from your daily step totals and show it in the expedition ranking.

Daily streak and step goal. We record your streak of days in the game: your current and your longest streak, the last day counted and the day Bjørn covered for you, and for each counted day its number in the streak, the level of that day's chest and when you claimed it. A day counts when you open the game and a synchronisation runs. The step target of the daily quest is your own: we work it out once a day from the median of your daily step totals over the last 7 days and store it together with that median and the number of days it was based on. Only you see your streak and your target. We keep them until you delete your account.

Starter chest. At the end of your first painted route we place a starter chest that only you can see. We store with your account where it stands (the end of that route), its level, when it was placed and opened, and what it contained, so that opening it again gives the same rewards. There is one starter chest per account and one per phone. That is why we store with it the random identifier of your installation of the game, which the app sends when you sign in and which stays on the phone until the game is uninstalled (a different identifier from the one described above under "Fair play"). Separately, without any link to your account, we store that identifier on its own with the date the chest was given, so that a second account created on the same phone does not get a second chest. The record on your account is deleted with the account. The identifier with its date stays even after the account is deleted, because that is exactly when it prevents abuse.

First launch. The app records on our server which first-launch screens (profile, location, first walk, starter chest, first route summary, steps, ad consent, notifications) were shown, which you completed and which you skipped, when, and how long after the screen appeared, together with the app version and the system (Android or iOS). This shows us on which screen new players give up, so that we can improve it. Only we see these records, in the admin panel. We keep them until you delete your account.

The start screen, before an account exists. Before you have an account, the app records on our server that the start screen was shown, that "Start the game" or "I already have an account" was tapped, and the result of the check described above under "Checking whether you already have an account" (account found or not, and how long the check took). Each event carries the time and the random identifier of your installation of the game (the same one as for the starter chest), the app version, the system (Android or iOS), the phone model, the system version, the game's language and the country code from the phone's settings. We mark sign-in and account-creation attempts with the same identifier (method: Google, Apple or without registration; result, duration and error code); a successful attempt is linked to the account that was created or opened. This shows us how many new players give up before they start playing, so that we can improve the first launch. These records contain no IP address, nickname or email address. Only we see them, in the admin panel, and we delete them after 90 days.

Team deputy. A team administrator can name one deputy from among the team's members; we store with the team who it is. Team members see the deputy's nickname, and the team chat announces in a system message, with the nickname, who has become deputy and that the deputy has taken over the team. The deputy can change the team crest, accept and decline requests to join and remove members (except the administrator), so the deputy sees join requests and receives notifications about them. The deputy is first in line to take over the team when the administrator leaves it, deletes their account or has their account suspended. The deputy also takes over when the administrator shows no sign of life for 14 days, that is syncs no walk, does not sign in and does not connect to the server from the app; the roles then swap and the former administrator becomes the deputy. The appointment ends when the deputy steps down, the administrator withdraws it or the deputy stops being a member of the team, including by deleting their account.

Advertising. Advertising in Trailborn is entirely voluntary: you watch an advertisement when you choose to claim a chest or a shortcut (an extra kilometre of road) for it. There are no banners and no full-screen advertisements shown without your decision. Advertisements are served by Google AdMob, which may use the advertising identifier and technical device data to serve the advertisement, cap frequency, produce aggregate reports and prevent abuse. From app version 1.2.7, two advertising partners may also take part in serving advertisements, through Google AdMob (mediation): Liftoff (Liftoff Mobile, Inc., USA; the Liftoff Monetize network, formerly Vungle) and AppLovin (AppLovin Corporation, USA). Their libraries (SDKs) are part of the app. These partners may receive the device's advertising identifier, the IP address and the approximate location derived from it (country, region), technical device data (model, system version, language, connection type) and information on whether an advertisement was shown, watched and tapped. They use them to serve the advertisement, cap frequency, measure and prevent abuse and, with your consent, to personalise advertisements. We do not pass your account identifier, nickname, email address, steps, your phone's location or health data to the advertising partners.

Whether an advertisement is personalised depends on your decision. In the European Economic Area, the United Kingdom and Switzerland we show Google's consent form before the first advertisement; without consent to personalisation we request non-personalised advertisements only. On iPhone the system tracking question applies as well; declining it also means non-personalised advertisements. Accounts whose age declaration is below the age of consent always receive non-personalised advertisements, whatever the form says. Outside those regions advertisements may be personalised according to the advertising settings of your system. You can change your decision in the app's privacy settings. The setting is called “Ad privacy”. Google's consent form also covers Liftoff and AppLovin: your decision reaches them together with the advertisement request, and without consent they may not use your data for personalised advertisements. Changing or withdrawing your consent there applies to Google and to both partners.

To grant your reward after an advertisement, Google sends us a confirmation. We do not pass your account identifier for this: our server issues a single-use, random token valid for 60 minutes, which expires once spent. Google does not learn whose advertisement it was.

Measuring advertising campaigns and use of the game (Firebase Analytics, Android). Trailborn advertises on Google Ads. To see which campaigns bring players who create an account and come back to the game, and to see in aggregate reports how players use the daily streak and the card inviting them to join a team, the Android app uses Google Analytics for Firebase (provider: Google). Google receives: the app instance identifier assigned by Firebase, the device's advertising identifier, the phone model, the system and app versions, the language, the country or region Google derives from the IP address (Google Analytics does not store the address itself) and these events: first launch, creating an account or signing in (with the method: Google, Apple or without an account), the first painted route, opening the starter chest, coming back to the game at least one day and at least one week after the account was created, a streak day counted (the day number), a streak reward claimed (the day number and the chest level) and the team card (shown, joining a team, creating a team or closing the card) and the Trailborn+ offer when setting up a race (the offer being shown and the player's choice: going to the store or "Later"). We do not pass your account identifier, nickname, e-mail address, steps, location or health data. Measurement depends on the advertising consent in Google's form described above; there is no separate question. Before you decide in the advertising consent form, the app sends Google only anonymous signals without identifiers and without Google storing anything on the phone (Consent Mode, advanced), which we use to measure our advertising campaigns in aggregate; full measurement runs only after you consent. In the European Economic Area, the United Kingdom and Switzerland it stays that way without your consent: after a refusal Google receives only such anonymous signals, without the app instance identifier or the advertising identifier. Outside these regions full measurement starts once the form confirms that consent is not required. Data from accounts that declared an age below the age of consent is never used for personalised advertising or advertising audiences. Google keeps event data for 2 months; after that only aggregate reports remain. On the phone we store the date the account was created, which of these events have been sent or are waiting, and the last streak day reported, so that none is sent twice. You can change your decision in the app's privacy settings; after you withdraw consent only the anonymous signals described above remain. Firebase Analytics is not used on iPhone for now.

Measuring campaigns on Facebook and Instagram (Meta SDK) and the install source from Google Play. Trailborn also advertises on Facebook and Instagram. To see which of those advertisements bring players who make an account, take their first walk and come back, the app contains the Meta SDK (provider: Meta Platforms Ireland Limited, Dublin). We start the Meta SDK only after your consent in Google's advertising consent form described above (on an iPhone additionally according to your answer to the system tracking question); without consent, or before an answer, the SDK is not started and sends nothing, and after you withdraw consent in the app's privacy settings it stops sending. After consent, Meta receives: the device's advertising identifier, phone model, OS and app version, language, the country Meta derives from the IP address, the SDK's automatic events (app launch) and the events: account created, first walk, and return to the game the day after the account was made. We do not pass on your account identifier, nickname, e-mail address, steps, location or health data. Independently of the SDK, on Android the app reads once from Google Play the so-called install referrer - the information which link the game was installed from (Meta's encrypted campaign record, Google Ads' click identifier "gclid", our link forestnap.com/graj, or the mark of an install from the store) - and sends it to our server, where we store the install source and the campaign identifier next to the account, without any advertising or device identifier. On that basis our server passes two events to Google Ads: account created and return to the game the next day, together with the ad click identifier (gclid), the app and OS version, language, phone model and the phone's IP address at the moment the install source was sent, without any advertising or device identifier; from this Google Ads counts, in aggregate reports, which advertisements bring players. An iPhone has no install referrer. Independently of this, before you create an account the app sends three events to our server: the app being opened, the start screen being shown and the first button being pressed, each once per installation, together with a random installation identifier of the game (the same one as in "The start screen, before an account exists"), the phone model, the system and app version, the language and the date the game was installed; when you create an account we store the same identifier next to the account. This lets us compare the number of installs from the store with the number of accounts and see at which step new players give up. We use no advertising identifier or device identifier for this, we store no IP address, and only we see these records, in the administration panel; the basis is our legitimate interest in measuring campaigns in aggregate. We delete them after 12 months.

Notifications. If you enable them, we store the device's push notification token, its language, the kinds of notification you chose and the phone's time zone. When you disable them, the token is deleted from the server and from the device. Notifications about achievements, settled steps and the daily reminder are created locally on the device. The next day's walk reminder comes at the time of day you choose when asked about notifications (morning, midday or evening); we keep that choice only on the phone and do not send it to the server. Messages from the game (race results, rewards, announcements, Bjørn's morning summary of the previous day) go to the in-app inbox.

If you turn notifications on, the server may send at most two automatic notifications a day, by your own calendar, and sends none at night, from 21:30 to 8:30 your time. You can switch each kind off in Options. Kinds marked "encouragement" are sent only with a separate consent (see "Encouragement to come back and gifts" below). The kinds:

Notifications never contain your step count or distance from Health Connect or the Health app. When an inbox message mentions them (the challenge, a race, an expedition), the notification only says that a message is waiting; the numbers stay in the game. Outside this limit, with notifications on you may receive a notification about a new team chat message (with the sender's nickname and the message text), a request to join a team you administer or are deputy of, a new team member, and announcements from the game (encouragement); none of them is sent during your night. Push notifications are relayed by Expo and delivered to the phone by Google (Firebase Cloud Messaging) or Apple (Apple Push Notification service).

Encouragement to come back and gifts. Some notifications do not report something that happened in your game but encourage you to come back or go for a walk, or tell you about a gift: the "Bjørn is waiting" reminder after three days away, the reminder of an unopened chest, the evening reminder of the daily quest chest, last week's ghost, the postcard from Bjørn, a gift from the game (for example chests after a game update) and announcements from the game. We send these notifications only if you agree to them separately: in a one-time question in the game, or with the "Encouragement and gifts from Bjørn" switch in Options. We do not ask for this consent in your first session: the notifications card only has the "Yes, remind me" button, which turns on notifications without the encouragement, and "Not now". We ask the one-time question on your second day of play at the earliest, at least 24 hours after the account was created, only if your notifications are on and you have never chosen an answer. In it you can agree ("Yes, tell me about gifts"), refuse ("No gifts, thanks") or put it off ("Not now"); we do not ask again on that phone. This consent is not pre-selected, it starts switched off for everyone, accounts created earlier included, it is not a condition for playing, and you get nothing for giving it. You get at most one automatic encouragement a day, within the limit of two automatic notifications a day described above, and never at night, from 21:30 to 8:30 your time. We do not send an announcement from the game as a push to anyone who has already had an encouragement in the last 20 hours; announcements are not sent at night either. To choose who receives it, we use the date of your last activity in the game, the date your account was created, whether you have unopened chests or an unclaimed daily quest chest, and your routes from this week and last week (ghost, postcard). With your account we store whether the consent is given, when you last changed it, where in the app you did so (the one-time question or Options) and the version of the consent text you saw then. We keep this until the account is deleted, and only we see it, in the admin panel. The legal basis is your consent (Article 6(1)(a) GDPR and Article 398 of the Polish Electronic Communications Law, Prawo komunikacji elektronicznej). You can withdraw it at any time with the same switch in Options, and you can also object at any time to the use of your data for this purpose (Article 21(2) GDPR). Messages in the in-app inbox, including those with gifts, reach every player, also without this consent; the consent covers only push notifications.

Uninstalling the game. When we send a notification and Google or Apple answers through Expo that the game is no longer on the phone (the DeviceNotRegistered response), we delete that phone's notification token and record in our uninstall table: the date, the system (Android or iOS), a one-way hash of the token (SHA-256; the token itself is deleted, and nothing can be sent with the hash) and whether it was your last phone with notifications. When you open the game again (a new notification token, the app connecting to the server, or a sign-in), we add the date and how we noticed. This tells us that a player uninstalled the game. Only we see this record, in the admin panel, and we keep it until the account is deleted. It works only with notifications on: nobody tells us when the game is removed from a phone without a token.

Time zone. The app sends the server the time zone set on your phone (for example "Europe/London") with every request, also when notifications are off. It sets the bounds of your day, that is the moment when the daily limit of chests for watching an advert, the daily quests, the daily streak, Bjørn's Trail and the daily Trailborn+ chest renew, and when the week of Bjørn's weekly challenge begins and ends. If you do not allow location, it also decides the country your first route starts in (see "Your first route"). It also sets the night silence, the daily notification limit and which day Bjørn's morning summary describes. If the phone does not send it, we estimate it from your last position. We store the latest time zone on your account (until you delete the account), and also with the phone's notification settings (until you turn notifications off or delete the account) and with each summarised day (30 days). A time zone roughly indicates the region you are in. With every request the app also sends the units you chose in the settings (metric or imperial). We store them on the server as well, with your account (until you delete the account), so that messages from the game (the inbox, push notifications, daily summaries, race results, the expedition) give distances in kilometres or miles.

What is publicly visible

Another player who taps your nickname sees: your nickname, colour, character appearance, total distance and territory, player level, worn items and accessories, and the teams you belong to. If your Trailborn+ gift choices lean to good or to evil, the profile has a gold frame or a red background. We do not show how many choices you made or who received the days, but the frame or background does reveal that the account once had a paid subscription. In the global chat every player sees your nickname and message. In a race the entrants see each other's nicknames and progress. Rankings, including the expedition ranking, show your nickname and result. A flag with a message is visible to all players right after it is planted, on every map, at its place on the road; only the player who finds the flag sees your nickname and the message. In a duel your opponent sees your nickname, rating, gear bonus and, once a day, your steps for the finished days of the duel. The duel ranking and your profile show your duel rating and your numbers of wins, losses and draws, and players looking for an opponent also see your level (see "Duels").

Your invitation page (forestnap.com/z/…) is open to anyone with the link: it shows your nickname, avatar, team, total distance, number of road segments uncovered and the town you last played in — without your exact position.

They do not see: your e-mail address, health data, last position, daily activity (only your opponent in a duel sees your steps on the days of that duel), birth year, purchases, or whether the account is suspended.

Map tiles show claimed roads in the owner's colour but contain no player identifiers.

Legal bases

Providing data is voluntary, but without an account and a source of steps the game cannot work — there is nothing to count metres from.

Who we share data with

We do not sell data.

WhoPurposeWhat reaches them
Google (sign-in)signing in with a Google accountGoogle account identifier
Apple (sign-in)signing in with an Apple accountApple ID identifier, e-mail or relay address
Google Play, Apple App Storepurchases and the subscriptiontransaction confirmation for verification; payment happens in the store
Google AdMobrewarded advertisementsadvertising identifier, technical device data, your personalisation decision, single-use verification token
Liftoff Mobile, Inc., USA (Liftoff Monetize, formerly Vungle)rewarded advertisements served through Google AdMob mediationadvertising identifier, IP address and the approximate location derived from it, technical device data, information on whether an advertisement was shown and tapped, your personalisation decision; the partner's privacy policy: https://liftoff.ai/privacy-policy/
AppLovin Corporation, USArewarded advertisements served through Google AdMob mediationadvertising identifier, IP address and the approximate location derived from it, technical device data, information on whether an advertisement was shown and tapped, your personalisation decision; the partner's privacy policy: https://legal.applovin.com/privacy/
Google (Google Analytics for Firebase, Google Ads)measuring advertising campaigns, returns to the game and use of the daily streak and the team card (Android)app instance identifier, advertising identifier, phone model, system and app versions, country or region, events: first launch, account creation or sign-in, first route, opening the starter chest, return after a day and after a week, streak day, streak reward (day number, chest level), team card (shown, joined, team created, closed), Trailborn+ offer when setting up a race (shown, went to the store, "Later"); before you answer Google's consent form and without consent only anonymous signals without identifiers (Consent Mode, advanced); full measurement in the EEA, the UK and Switzerland only with your consent
Meta Platforms Ireland Limited (Meta SDK)measuring campaigns on Facebook and Instagram; only after consent in Google's formadvertising identifier, phone model, OS and app version, language, country; events: app launch, account created, first walk, return the day after the account was made
Google Ads (from our server)aggregate measurement of Google Ads campaigns by install sourcead click identifier (gclid), account-created and next-day-return events, app and OS version, language, phone model, the phone's IP address; no advertising or device identifier
Expo, and through it Google (Firebase Cloud Messaging) and Apple (Apple Push Notification service)push notification deliverynotification token, notification content: for team chat the sender's nickname and the message text; for gifts, the invitation chain and flags other players' nicknames; for an attack on territory the team's name and the district or town; never your step count or distance
Contabo GmbH (server in France, European Union)game servers, game database and the world road databaseeverything described above
OpenFreeMap / OpenMapTilesbase maptile requests from your device: your IP address and the map area you are viewing
OpenStreetMap Foundation (Nominatim)place searchthe text typed into the place search, and the address of the Trailborn server
Overpass API (overpass-api.de, overpass.kumi.systems)landmarks from OpenStreetMap around where people playthe map area our server asks about, without any player data

Chat message translation (the “Translate” button) is done by our server at Contabo with LibreTranslate. There is no additional recipient here: the message text does not go to an external translation provider.

Place search is called by our server, not by your phone, so your IP address does not reach Nominatim.

The base map is downloaded by your device directly from OpenFreeMap's servers, so they receive your IP address and which part of the map you are looking at. We do not pass them your nickname, account or steps.

Google, Apple and Expo may process data outside the European Economic Area; this takes place under the European Commission's standard contractual clauses or an adequacy decision. Liftoff and AppLovin are based in the United States and process data there. Both companies state in their privacy policies that they take part in the EU–U.S. Data Privacy Framework, so the transfer relies on the European Commission's adequacy decision of 10 July 2023 and, where that framework does not apply, on the European Commission's standard contractual clauses.

How long we keep data

The periods below match what the code actually deletes.

DataPeriod
Account, profile, territory, inventory, level, purchasesuntil account deletion
Time zone and units stored with the account (only the latest)until account deletion
Height, weight and the calories counted from themuntil you delete them in your profile, or until account deletion
Team chat and global chat messages48 hours
Chat message translations (translated text, language, nothing about who asked)as long as the message, at most 48 hours
Visits to an invitation page (IP address hash, device type)48 hours
Invitations and the Trailborn+ days they earneduntil account deletion
Trailborn+ gifts and your gift choices, the invitation chain, weekly challengesuntil account deletion
Flags with a message (message, place, who found it and when)180 days after the flag closes
Token visits (account, token, time, distance, no coordinates)until the token is paid out, at most 24 hours
Collected tokens (which one and when)until the account is deleted
Races you took part inuntil account deletion
Duels (players, stake and its movements, dates, time zones, result, rating change)until account deletion; after that the result stays in the opponent's history without your nickname or identifier; not deleted automatically
Your steps on duel days and your cheersuntil account deletion
Duel rating, wins, losses, draws and winning streakuntil account deletion
Duel messages in the inbox30 days
Daily streak, streak rewards and the personal step targetuntil account deletion
Starter chest (place, level, opening, rewards, installation identifier)until account deletion
Identifier of an installation that received a starter chest, with the date (not linked to any account)not deleted automatically; it stays after account deletion
First-launch screens (shown, completed, skipped, time)until account deletion
Start screen and sign-in attempts before an account exists (installation identifier, version, system, model, language, country, time)90 days
How the phone last signed in, Google or Apple (on the phone)until account deletion
Steps recorded by Google Play services, Recording API (on the phone)10 days; once read by the game, kept in the phone counter's history for 30 days
Team deputy appointmentuntil the deputy steps down, it is withdrawn or the deputy's team membership ends (including by account deletion)
Crash reports7 days
Walk processing jobs (full request and response)14 days
Activity sync batches180 days
Activity security events180 days
Advertising events and confirmations of ad rewards90 days
Google Analytics for Firebase event data (at Google)2 months; not linked to your account, so deleting the account does not cover it
Install source next to the account (Google Play install referrer, campaign identifier, ad click identifier, the phone's IP address at the time of sending)until account deletion
Install funnel before an account (random installation identifier, three events with their time, phone model, system and app version, language, install date)12 months; the installation identifier stored next to the account until account deletion
Meta SDK event data (at Meta)under Meta's rules; not linked to your account, so deleting the account does not cover it
Account creation date and measurement events sent (on the phone)until account deletion
Log of push notifications sent (type and time)90 days
Mark in the push notification log whether a notification was encouragement90 days
Consent to encouragement and gifts from Bjørn (given or not, date of the last change, place in the app, version of the consent text)until account deletion
Uninstalls of the game (date, system, hash of the notification token, date the game was opened again)until account deletion
Daily summaries (the day and the phone's time zone)30 days
Sign-in telemetry (country, language, version, model, system)90 days
Chest gift records (who, what, to whom, transaction identifier)13 months from creation; abandoned intents 60 days
Closed moderation cases and appeals180 days after review
Single-use advertisement verification tokens60 minutes, deleted after a day
Expired sessions7 days after expiry
Database backups14 days

A moderation case is not deleted while an appeal against it is pending.

Backups. Every night we make a backup of the database and keep it for 14 days on the game server, in the same infrastructure as the database. Data deleted from the database — including after account deletion — may remain in a backup for at most 14 days, after which the backup is deleted. Backups are used for nothing but restoring the database after a failure.

Deleting your account

You can delete your account in the app: Settings → Account and data → Delete account, with two confirmations. An account without registration is deleted the same way. You can also submit a request without installing the game, through https://forestnap.com/delete-account/.

After a confirmed deletion we erase your profile, sessions, step and floor data, personal territory, inventory, chests (the starter chest too), tokens and token visits, the daily streak, the record of first-launch screens, purchase records, notification token, uninstall records and the data stored on the device, except the random identifier of your installation of the game. On the server only that identifier remains, with the date the starter chest was given and no link to the account. Team events, races, duel results and the shared world history may remain in anonymised form so that other players' maps and rankings do not fall apart — without your nickname and without your identifier. Deleting the account does not cancel a subscription in the store — you cancel it in Google Play or the App Store.

A plain sign-out clears from the device the sensor step history, Health Connect cursors, the installation identifier and the notification token. Claimed territory stays on the device, tied to your account, so that you find your map again after signing back in.

Your rights

You have the right to: access your data, rectify it, erase it, restrict processing, data portability, object to processing based on legitimate interest, and withdraw consent at any time.

We make no decisions about you based solely on automated processing that would produce legal effects. Fair-play checks may flag activity as unreliable and the word filter may mask part of a message, but decisions to suspend an account are made by a human and can be appealed.

Requests: forestnapstudio@gmail.com. We respond without undue delay and at the latest within one month.

You also have the right to lodge a complaint with a supervisory authority — in Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warsaw.

Changes

We will announce material changes in the app. The version of this document you accepted is stored with your account together with the date.

Version 2026-11-18 compared with version 2026-11-16: from app version 1.2.7, two new recipients may take part in serving rewarded advertisements through Google AdMob mediation: Liftoff (Liftoff Mobile, Inc.) and AppLovin (AppLovin Corporation). Describes which data they may receive (advertising identifier, IP address and the approximate location derived from it, technical device data, information on whether an advertisement was shown and tapped), that Google's consent form and, on iPhone, the system tracking question cover them, the transfer of data to the United States, and where you change your decision (“Ad privacy”). Adds them to the table of recipients. The change does not require new acceptance; earlier acceptances remain valid.

Version 2026-11-16 compared with version 2026-11-11: describes token visits (when your phone reports a position within 75 m of a token, we record the account, the token, the time and the distance, without coordinates, for at most 24 hours, to pay out the token on your next walk) and adds them and collected tokens to the retention table. The change does not require new acceptance; earlier acceptances remain valid.

Version 2026-11-11 compared with version 2026-11-10: describes chest gifts (we store who gave what to whom, and the recipient sees the buyer's nickname) and adds gift records to the retention table. The country check (see "Country and duels") now also runs when the rankings screen is opened, to decide whether to show the duel board. The change does not require new acceptance; earlier acceptances remain valid.

Version 2026-11-10 compared with version 2026-11-07: in a duel your opponent sees your steps live from the start instead of once a day. The data and the purpose of processing it do not change.

Version 2026-11-07 compared with version 2026-11-06: from app version 1.2.1 it describes duels: which duel data we store and why, what the opponent and other players see (the duel rating, wins, losses and draws; nobody else sees the median of daily steps the server uses to suggest opponents), the country check that keeps duels unavailable in Belgium and the Netherlands, and the check that two accounts do not belong to one person, both based on legitimate interest. It adds duels to the retention table. The change does not require new acceptance; earlier acceptances remain valid.

Version 2026-11-06 compared with version 2026-11-03: from app version 1.2.1, players without a team also plant, see and find flags, on every game map. A flag goes up on the nearest walkable road, not exactly where you stand; in incognito mode in your stand-in area, and your real position is not stored with the flag. The change does not require new acceptance; earlier acceptances remain valid.

Version 2026-11-03 compared with version 2026-11-01: adds translation of chat messages at the player’s request (the “Translate” button). Our server translates with LibreTranslate, without an external provider; the program receives only the message text without player data, and the translation is deleted together with the message. The legal basis is the contract (the chat is part of the service). Adds translations to the table of retention periods. The change does not require new acceptance; earlier acceptances remain valid.

Version 2026-11-01 compared with version 2026-10-25: adds measurement of campaigns on Facebook and Instagram through the Meta SDK (new recipient: Meta Platforms Ireland Limited), started only after consent in Google's advertising consent form, with the events account created, first walk and return the day after the account was made. Describes reading the install source from Google Play (install referrer) and storing the campaign identifier next to the account, without an advertising identifier, and passing the account-created and next-day-return events from our server to Google Ads with the ad click identifier (gclid), on the basis of a legitimate interest in measuring campaigns in aggregate. Adds this data to the tables of recipients and retention periods. It also describes the three events of the install funnel before an account (app opened, start screen, first button) under a random installation identifier, without an advertising identifier and without an IP address, kept for 12 months. The change does not require re-acceptance; earlier acceptances remain valid.

Version 2026-10-25 compared with version 2026-10-24: describes the new start of the game in versions 1.1.58 and 1.1.59. An account without registration is created when you tap "Start the game", and right after the tap we record the acceptance of the terms, the policy version and the 16+ declaration; until it is linked to Google or Apple, the progress of such an account is tied to the phone, and you delete it in the app. Describes the short check, before such an account is created, whether a Trailborn account is already on the phone (the key of an account without registration, a Google account that has already signed in to Trailborn, the last sign-in method stored on the phone), without device fingerprinting. Describes the record of the start screen and of sign-in attempts before an account exists (random installation identifier, version, system, model, language, country; 90 days) on the basis of legitimate interest. Describes step recording by Google Play services (the Recording API) on Android while the step counter is on (on the phone, up to 10 days, under the same permission), and that a new account is credited with steps from at most the 24 hours before it was created. Adds the point "Encouragement to come back and gifts": the "Bjørn is waiting" and chest reminders, last week's ghost, the postcard, gifts and announcements from the game come as push notifications only with a separate consent, not pre-selected, given in a one-time question (on the second day of play at the earliest, never in the first session) or in Options (we store its value, date, place and text version), while inbox messages reach everyone. Adds these data to the retention table. Describes the advanced Consent Mode in Firebase Analytics on Android: before you decide in the advertising consent form, and also without consent, the app sends Google only anonymous signals without identifiers and without Google storing anything on the phone, to measure our advertising campaigns in aggregate; full measurement runs only after you consent. Describes likes on messages in the team chat and the global chat: we store who liked which message, chat participants see the number of likes, and likes disappear together with the message or the account. Describes flags with a message as visible to other players right after they are planted, without a moderator checking them first; a moderator can remove a reported flag. Adds to the Firebase Analytics events on Android the event of the Trailborn+ offer being shown when setting up a race and the player's choice (going to the store or "Later"), without steps or personal data. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-24 compared with version 2026-10-23: adds that for a purchase and every subscription renewal we store the price, the currency and the store country given by the store, to count the game's revenue. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-23 compared with version 2026-10-22: removes from Firebase Analytics on Android the event of the first synchronisation in which the game counted steps. The app no longer sends it from version 1.1.57, and we do not use events from earlier versions to measure advertising campaigns. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-22 compared with version 2026-10-21: describes the record of uninstalls. When Google or Apple reports that a notification did not reach a phone because the game is no longer installed (DeviceNotRegistered), we record the date, the system and a one-way hash of the notification token (until the account is deleted), on the basis of legitimate interest. It also describes the inbox message with the result of Bjørn's weekly challenge and the notification about it. Adds the uninstall record to the retention table. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-21 compared with version 2026-10-20: adds a Firebase Analytics event on Android: the first synchronisation in which the game counted steps from the phone's step counter, Health Connect or the Health app (the event alone, without the number of steps). It is sent once per account created on that phone, under the same consent rules as the other events. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-20 compared with version 2026-10-19: describes the data new in version 1.1.55 of the game: the daily streak and its rewards, the personal step target worked out from the median of 7 days of steps, the starter chest at the end of the first route (one per account and one per phone, hence an installation identifier that stays, without a link to the account, even after the account is deleted), the record of first-launch screens and the team deputy (visible to team members, announced in the team chat, taking over the team also after 14 days of the administrator's absence). Also describes the approximate network position (within 500 m) for a first walk without a GPS signal, the first route starting in a city in the player's country when location is not allowed, the reminder time kept only on the phone, and the new Firebase Analytics events on Android (opening the starter chest, streak day, streak reward, team card) with the new purpose of that measurement: how players use the daily streak and the team card. Adds this data to the table of retention periods. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-19 compared with version 2026-10-18: describes measuring advertising campaigns with Google Analytics for Firebase in the Android app (new recipient: Google; app instance identifier, events, phone model, country or region). Nothing is sent before you answer Google's consent form, and in the European Economic Area, the United Kingdom and Switzerland measurement runs only with your consent. Also describes the legal bases and how long Google keeps this data (2 months). The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-18 compared with version 2026-10-16: describes storing the phone's time zone and the units you chose with your account (until account deletion); the app sends them with every request. The time zone now also sets the player's day for the daily limit of chests for watching an advert, the daily quests, the weekly challenge, Bjørn's Trail and the daily Trailborn+ chest (previously Polish time or UTC), and the units are used to give distances in messages from the game in kilometres or miles. Adds this data to the table of retention periods. The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-16 compared with version 2026-10-10: describes playing without an account (a random key on the phone, only its one way hash on our side, a counter of new accounts kept in server memory for at most one hour). The change does not require a new acceptance; earlier acceptances remain valid.

Version 2026-10-10 compared with version 2026-10-06: describes flags with a message in Team War mode (the exact place of a flag is visible to other players once a moderator approves it; its author's nickname and the message only to the player who finds it), the invitation chain and the messages to people further up it, free Trailborn+ days and the Trailborn+ gift after a purchase, the gold frame or red background on the public profile that follows Trailborn+ gift choices (which indirectly reveals that the account once had a paid subscription), points, the weekly challenge and expeditions, the new push notifications (at most two automatic ones a day, night silence from 21:30 to 8:30 the player's time, each kind can be switched off, no step count or distance in their text) together with the services that deliver them (Google, Apple), the phone's time zone, the morning summary of the day, reporting a flag's message, and our server's queries to the Overpass API. It adds retention periods for flags (180 days after closing), ad reward confirmations and the push notification log (90 days), and daily summaries with the time zone (30 days), and removes the previous game server, now shut down, from the list of recipients. The change does not require a new acceptance — earlier acceptances remain valid.

Version 2026-10-06 compared with version 2026-10-05: optional height and weight in the profile, kept with explicit consent to count the calories burned walking, and the daily total of those calories. The change does not require a new acceptance — earlier acceptances remain valid.

Version 2026-10-05 compared with version 2026-09-30: diagnostics include the state of the permissions and settings the game needs (location, step access, the phone’s step counter, notifications, the ad consent). The change does not require a new acceptance — earlier acceptances remain valid.

Version 2026-09-30 compared with version 2026-09-29: describes friend invitations (including the IP address hash kept for 48 hours for the invitation page), automatic notifications — at most one a day — and the record of a Trailborn+ free trial. The change does not require a new acceptance — earlier acceptances remain valid.

Version 2026-09-29 compared with version 2026-09-26: messages in the team chat and the global chat are kept for 48 hours instead of 24, and the author can delete their message throughout that time. This applies to messages sent from 29 September 2026; earlier messages expire after 24 hours. The change does not require a new acceptance — an acceptance of version 2026-09-26 remains valid.

Version 2026-09-26 compared with version 2026-08-29: describes Sign in with Apple, purchases of Trailborn+ and chest bundles through Google Play and the App Store, the global chat, races, the advertising personalisation consent form, the move of the game servers to Contabo, backups kept for 14 days and the 60-minute advertisement token.