Privacy Notice
What Hide Tag knows, why it needs it, and when it goes.
This notice applies to the Hide Tag Android and iOS apps and website. Seba Games, Finland, is the developer and data controller. Questions and privacy requests can be sent to hello.sebagames@gmail.com.
Delete your Hide Tag account or data
The short version
- You can play without an email address. We use a random account ID and your nickname.
- The game needs your precise location while you are in a lobby, including setup and the post-game map in current apps. Leaving the lobby stops new location reports.
- In current apps, saving statistics, replay routes and developer analytics is optional. Accept only necessary lets you play without these saved personal histories.
- Temporary game records are cleaned up after the whole lobby becomes inactive. Saved replays, account records and backups have different retention periods, explained below.
- You can download your data, erase your replay routes, withdraw optional collection or delete your account. Uninstalling the app does not delete server records.
- We do not sell personal data or use advertising trackers in the game.
Precise locations are stored for gameplay and, where available, round replay. They can remain on the server after a round ends and appear in your data download. Necessary gameplay uses your latest position. In version 4.8.59 and later, saving statistics and replay routes is optional; Accept only necessary does not enable those features. Older installed versions, including 4.8.36, also record round replay as part of gameplay. The version-specific retention and export sections below explain the difference.
Data the game processes
- Precise location. The game server stores your latest reported latitude, longitude, accuracy, speed and report time to run the game. These are precise coordinates, not the broad area used for optional analytics. With replay enabled, the app also stores timestamped positions and role changes during the round so its participants can review their routes afterwards. These records are stored in the database, not only displayed on your phone. Optional saved replays in version 4.8.59 and later have a separate retention period from temporary lobby records, as explained below.
- Your chosen name. The nickname you enter is stored with that game and is visible to its invited players. Use a nickname, not your full name.
- A random account and session. Supabase Authentication creates a random identifier and session so the server can recognise the same installation. Current apps do not request an email address, phone number or social login. These identifiers and location records are personal data even though we do not ask for your real name.
- Game and profile activity. Lobby membership, team and role, catches, missions, powerups, penalties, game settings and results are processed to run the match. Older versions retain coins, game counts and achievements on the random account identifier. In version 4.8.59 and later, saving statistics and replay history requires the separate optional choice described below.
- Technical request data. Internet services necessarily receive data such as an IP address, device or browser information, requested resource and timestamp when answering a request. Seba Games does not use advertising tracking. Optional game analytics is described below.
- Service activity totals. We record the total number of recently connected players in active rounds once per minute, including players using necessary-only settings. These counts contain only a timestamp and total, with no player or game identifiers or locations, and are kept for up to 12 months.
The camera is used only on your device to scan a game invitation QR code. Hide Tag does not store or send the camera image. Local notifications, sound and vibration are used for game alerts. Hide Tag does not collect contacts, photos, advertising identifiers or payment information, and does not sell personal data.
Data on your device and information you send us
Your device keeps the session needed to recognise your account, privacy choices, app preferences and saved game presets. Optional usage events can wait on the device for retry for up to 24 hours; expired events are discarded when the app next processes the queue. Withdrawing optional collection clears that queue. Data files you download remain wherever you save them until you delete them.
If you email us, we receive your email address and what you send, such as a support reference or screenshot. If you choose to answer our feedback form, we receive your answers and any details you include. Please avoid sending other players' locations or identifying details unless needed for your request. These voluntary communications are separate from the game's optional analytics switch.
Website traffic statistics
The public homepage, rules, privacy and terms pages use Vercel Web Analytics to measure visits and page views. These aggregate statistics include the page, referring website, approximate region, browser, operating system and device type. Vercel uses a temporary request-derived identifier, discarded after 24 hours, without analytics cookies or cross-site tracking. Query strings and URL fragments are removed from reported page URLs. This tracking is not added to the game, invitation, replay or administration pages and is separate from the optional in-game analytics described below. See Vercel Web Analytics privacy information. This website statistics section was added on 21 October 2026.
Optional statistics, saved replays and analytics
You can play with these features off. In version 4.8.59 and later, Accept all saves your statistics and replays and lets Seba Games review individual game histories to improve the game and help with support. This includes hosting, return visits, power-ups, missions, screen and feature use, joining methods and technical quality such as connection failures, request timing and location quality. These records are linked to your random player identity. There is no email/password registration or cross-device sign-in in this release; losing the device session may prevent recovery of your saved history.
Optional saved replays contain precise routes, names and game events. The round's participants and authorised developer support can view them after the round. They are not public. A necessary-only player's route is not copied into these optional saved replays. Older 4.8.36 round routes remain part of its temporary gameplay records.
Separately, opted-in aggregate round analytics records a random analytics ID, participation date, observed duration, planned duration, end reason, group size, area radius, app version, platform, starting role, host status, catches, supplies, missions and early departure. Abandoned rounds have no invented finish time. Group size includes everyone; linked participant records are saved only for players who opted in before participating. Older 4.8.36 consent continues to authorise only this older analytics contract, not the new statistics, saved replay library or detailed usage events.
Approximate game area is a separate optional choice. Only when every participant agrees may we retain the centre of a 0.1-degree grid cell containing the host's game centre. A cell is about 11 km north to south; width varies with latitude. A non-consenting late arrival removes the saved area. Precise routes, nicknames and invitation codes are not copied into this aggregate analytics dataset. Precise gameplay locations and optional saved replay routes are separate datasets, with their own rules above.
These are pseudonymous personal data, not fully anonymous data. Seba Games uses them internally to understand and improve the game. Supabase processes them on our behalf. They are not sold, used for advertising, published as player histories or provided to independent researchers. This choice does not enrol you in research.
Both choices start off. Accept only necessary leaves optional collection off; Accept all enables shared statistics/replays and approximate-area analytics. You can select these separately in Settings → Privacy and data. In version 4.8.59 and later, turning shared statistics off deletes linked optional analytics, statistics and saved routes and stops future optional records. In 4.8.36, its analytics switch controls only aggregate analytics. Turning approximate area off removes that area from your recorded rounds. Enabling either again does not import earlier play. We retain the notice version, time and choices to honour and demonstrate your decision.
Saved profile statistics include games, distance, estimated steps, time on each team and gameplay totals. Steps are estimated from distance, not measured by a pedometer. The same optional choice makes these statistics available to you and to Seba Games; there is no private-statistics-only option. Detailed usage events do not contain typed nicknames, invitation codes, message contents or precise coordinates. Your profile name and precise replay routes belong to the separate profile and replay records described above.
Why it is processed
Location, nickname, anonymous account and game activity are processed because they are necessary to provide the game you choose to join (GDPR Article 6(1)(b)). Limited technical data may also be processed to keep the service secure, diagnose failures and prevent abuse, based on Seba Games’ legitimate interests in operating a reliable service (Article 6(1)(f)). We also use this basis to respond to support requests and review voluntary feedback. Optional saved statistics, replay routes and analytics rely on your consent (Article 6(1)(a)). Necessary gameplay does not depend on agreeing to analytics. We keep your privacy preferences and limited choice history to honour your decisions and meet accountability obligations (Article 6(1)(c)). Withdrawal does not affect earlier lawful processing.
Your phone's permission choices control whether the app can access location and the camera. You can revoke a permission in Android or iOS settings. Revoking location stops new location reports, but a location-based match cannot work without it.
Location in the background
Hide Tag collects and sends precise location while a match is running even when the app is not visible or the phone is locked. This is needed because players walk or run with their phones in their pockets and everybody’s map must continue updating. Background collection starts only for a lobby you joined. In version 4.8.59 and later, sharing includes lobby setup and continues on the post-game map so players can find each other; it stops when you leave the lobby. Earlier versions stop at the end of the round. Stopping new reports does not immediately delete positions already stored. Precise routes can be saved in optional replays when you enable that choice, but are not copied into aggregate analytics or used for advertising. The optional approximate-area record comes from the game area chosen by the host, not your route.
Who receives data
- Players in your invited game. They see your nickname and game activity. Location is revealed only as the rules require: for example to teammates, through a reveal, freeze, footprint, arrival or mission. A lobby code is required to enter the game; Hide Tag has no public player directory or stranger matching. In versions with round replay, the round’s participants can review everyone’s recorded route and role changes after it ends. Replay history is not accessible during play or to people outside that round, except authorised developer support. Newer saved replays include routes only from participants who enabled the optional statistics/replay choice.
- Discord. Community buttons open an external invitation. Joining or using Discord is your choice and is subject to Discord's own privacy policy and terms. Hide Tag does not embed Discord chat or send your game route with the invitation.
- Supabase, Inc. provides anonymous authentication, the database and the game API as a service provider. See Supabase’s privacy information.
- Vercel Inc. hosts the website and developer tools and may process request and security logs. See Vercel’s privacy notice.
- Google. Gmail handles support email, Google Forms and Sheets handle voluntary feedback, and a private Google Drive folder holds encrypted recovery backups. These services receive the information submitted to them; backup contents are encrypted before upload. See Google's privacy policy.
- OpenFreeMap (Hyperknot Software Kft.) and its delivery providers. Your device requests map styles and tiles directly, which discloses its IP address, browser or app information and the map area requested. OpenFreeMap says its ordinary access logs omit IP addresses, but error logs can contain them for seven days and security-incident logs for up to 30 days. See OpenFreeMap’s Privacy Notice.
Data may also be disclosed when required by law, to protect somebody from harm, or to establish or defend legal claims. It is not shared with advertisers or data brokers.
International transfers
The current game databases are hosted in Supabase's EU North region in Stockholm, Sweden. Our providers also operate infrastructure in other countries. Data may therefore be processed outside Finland or the European Economic Area. Where required, providers use recognised safeguards such as adequacy decisions, the EU–US Data Privacy Framework or standard contractual clauses. Their current notices linked above describe their locations, subprocessors and transfer safeguards.
How long data is kept
- Temporary game data: a lobby and its player names, precise locations, game events and replay history become eligible for deletion once no player in that lobby has been active for 24 hours. The clock runs from the last activity by any player, not from the end of the round or when you personally leave. If someone remains active in the lobby, its records can be kept longer. Cleanup runs daily and when somebody hosts a game, so deletion can occur up to a day after the lobby becomes eligible. Starting a rematch deletes the previous temporary lobby replay. It does not delete an optional saved replay already copied to the newer replay library or other lobby records.
- Guest account and current privacy settings: kept until account deletion. There is currently no automatic inactivity expiry for the guest authentication record. Losing access to the device does not itself delete it.
- Saved profile statistics and results: kept until you turn optional collection off or delete your account. Older profile totals remain until deletion. The 90-day and 12-month analytics limits below do not apply to these profile totals.
- Optional saved replay routes: available until you erase them, withdraw optional collection, delete your account or reach two years of player-account inactivity. Two years is measured from account activity, not from the date of each replay: older replays can remain while you keep using the account. Expired routes are hidden from the replay reader and removed by scheduled cleanup in batches. Other players' routes and shared match records can remain until their own deletion conditions are met.
- Deleted-account security record: a random retired account ID and the time it was retired remain to prevent old credentials from restoring access. This record has no nickname, email or route. It currently has no automatic expiry.
- Support, feedback and legal records: retained according to the request, feedback purpose, unresolved disputes and applicable legal obligations, rather than the game's automatic deletion schedule. Contact us to request access or deletion. Provider operational logs have separate retention under their service terms; the game cleanup does not erase those logs.
Analytics retention
In version 4.8.59 and later, detailed optional usage events and developer review records become eligible for deletion after 90 days; game and session summaries after 12 months. These limits are separate from saved replay routes and profile totals described above. Round analytics and privacy-choice history become eligible for deletion after 12 months. Daily cleanup removes expired records within the next day, even when nobody plays. Cleanup also runs when a game starts, privacy choices are saved or the private analytics report is opened. Current preferences remain until account deletion. Deleting your account also removes your choice history. Other players' summaries and non-identifying group totals may remain. Counts cover the retained records, not a lifetime history.
Backups and recovery
We keep encrypted recovery copies on protected devices and in a private Google Drive folder, separately from Supabase's own backups. Our managed backup cleanup uses a 35-day threshold, keeps the two newest verified copies and pauses removal when a fresh verified copy is unavailable. This is not a guaranteed 35-day deletion deadline: recovery copies can remain longer when those conditions are not met. They are for recovery, not analytics.
Deleting data from the live service does not immediately remove it from an older backup. Before restored data is made available again, withdrawals and deletion requests must be reapplied. Provider backups and records follow their applicable retention terms. Contact us if your request concerns a backup or other record outside the app.
Delete your Hide Tag account or data
To request account or data deletion without using the app, email hello.sebagames@gmail.com and say whether you want all your player data or only optional statistics, replays and analytics deleted. If you still have access, include the support reference from Settings → Privacy and data. We may need to verify ownership; the reference alone does not authorise deletion. If you have lost access, contact us before sending identity documents. We may be unable to identify your random account once its session is lost.
Leaving a game stops participation; ending or abandoning a game does not immediately erase it because the short retention period lets the match finish and results be shown. Uninstalling Hide Tag or clearing its storage stops new collection and removes the anonymous credentials from that device, but does not itself delete the server-side pseudonymous profile.
In updated apps, Settings → Privacy and data → Delete my account and data verifies your current session and deletes your authentication account, profile, coins, achievements, privacy preferences and history, linked analytics, memberships, nicknames, positions and temporary and saved replay samples and personal replay events from the active database. The limited deleted-account security record and backup exceptions above still apply. Other players' records remain and hosting is transferred where necessary. You do not need to email a UUID. Deletion cannot be undone; continuing afterwards creates a new account.
In current apps, use Settings → Privacy and data → Turn off and delete saved statistics to keep your guest login but delete your optional profile, saved statistics, replay routes and linked analytics, and stop future optional collection. Necessary gameplay records and privacy-choice history remain under the retention rules above. In older 4.8.36 apps, the button is called Turn off and delete analytics and controls that version's narrower aggregate analytics only.
To erase your route from one saved round, use Profile → Your replays → Manage replay → Erase my route for everyone. This removes your nickname, route and personal replay events from the service's temporary and saved copies of that round. Remove from my library only removes your library entry; it does not erase your route from other participants' copies. Their own routes and shared game records remain. Backup exceptions still apply.
Why your data download can contain coordinates
Download my data includes your records still held in the active database, not just optional analytics. Depending on the app version and what remains stored:
-
player_accountincludes your optional saved profile and your own archived replay samples and events, when present. It is separate from the temporary lobby records. locationscontains your latest reported precise location for a lobby.-
replaycontains your saved round samples. Theirlatandlngvalues are precise replay coordinates, with timestamps and game state. -
Gameplay records such as
footsteps,forbidden_zonesandflare_samplesmay also contain coordinates used by the game’s rules. -
analyticscontains the separate optional summaries. Any saved area there is the broad grid-cell centre described above, not your precise route.
Precise coordinates in necessary gameplay records do not mean you opted into analytics. Saved personal replay routes in current apps require the optional collection choice; older versions recorded temporary round routes as described above. Downloading a copy does not delete the server records; the cleanup rules and account-deletion option above still apply. A downloaded copy remains on your device until you delete it.
A support reference appears on the same screen. You can send it to us for help, but a reference alone is not proof of account ownership. An internet connection is needed; the app reports failures rather than claiming unconfirmed changes succeeded.
Deletion cannot recall information other players have already seen or copied. Provider security logs and backups can persist for their applicable retention periods, restricted to operational purposes. Contact us about records outside the app export or if you cannot use the in-app controls.
You may request access, correction, deletion, restriction, portability or objection, and may withdraw consent where consent is the legal basis, by emailing hello.sebagames@gmail.com. Because Hide Tag deliberately does not collect your real identity, Seba Games may need information that can reliably connect you to the pseudonymous record. Do not send more personal information than requested. If the app has been removed and no reliable connection remains, Seba Games may be unable to identify the record without collecting additional data solely for that purpose.
We respond to privacy-rights requests without undue delay and normally within one month. If a permitted extension is necessary, we explain the reason and timing within that month. If we must retain information despite a deletion request, we explain what is kept and why.
You may complain to the Office of the Data Protection Ombudsman of Finland or the data-protection authority where you live or work. These rights may vary by location and may be subject to lawful exceptions.
Children
Hide Tag is for players aged 13 and over. It is not intended for children under 13, including through the guardian-permission option. Players aged 13–17 must have a parent or legal guardian's permission where the law requires it. That adult should understand the location sharing and know where the game is being played.
The app asks whether you can consent yourself or need a parent or guardian to complete the permission step. We store that declaration, the choices, notice version and time, not a birth date or proof of guardianship. This is a declaration on the same device; the app does not independently verify age or the adult's identity. The guardian option does not remove the minimum age of 13.
Eligible teenage players still generate the necessary account, nickname, location and game records described above. Optional statistics, routes and analytics require the separate choice, made by a parent or guardian where required. Accept only necessary remains available.
If you believe a player is under 13, or that required parental permission is missing, contact hello.sebagames@gmail.com. We will investigate and delete the affected account and personal data where the player is not eligible or the processing is not authorised, subject to the limited security, legal and backup exceptions above. A parent or guardian can also use the signed-in app's privacy controls to withdraw optional collection, download data or delete the account. Please contact us before sending identity documents.
Security
Data is encrypted in transit. Database tables are not directly readable by app users; server-side access rules decide what each invited player may receive. Hide Tag minimises location retention and limits sharing to your joined lobby. No internet service can promise absolute security, so report a suspected privacy or security problem to the contact address above.
Changes to this notice
This notice will be updated when Hide Tag’s data use, providers or legal obligations change. Material changes will be described in the app or its store listing where appropriate. The effective date appears below.