Starting the game

PRIVACY

What data may be used while you play

1

General information

This privacy policy describes how personal data is processed when you use the game Guess The Code (Zgadnij Kod / Guess The Code) at zgadnijkod.pl and guessthecode.io.

Controller and contact

The data controller is Miłosz Janeczek. Contact for data protection matters: contact@guessthecode.io or the Contact.

2

Data entered in the game

During play, you may enter data required for the lobby and game to function. You do not need an account to create a lobby or join with a code.

Player name

It may be used to identify the player in the lobby, game, attempt history, and summary.

Lobby code

It is used to create a game room and join an existing game.

Profile and friends

A guest profile or account may include a nickname, avatar, title, victory text, friend code, friendships, invitations and multiplayer results history.

Secret code and attempts

They are required for gameplay, calculating hints, recording guess history, and determining victory.

Adventure Mode

Saves locally the progress, times, attempts, typing and correcting characters, hint usage and level results. With a secured account or one linked to the other game site, this data is also synced with the server.

Challenge Mode

Saves locally the challenge history, stage times, answers, hint usage, daily streak and stars earned. With a secured account or one linked to the other game site, this data is also synced with the server.

Account security

You can secure your account with a passkey (your device's fingerprint, face or PIN), a login and password, and a recovery code. Biometric data never leaves your device — the server only receives a public key.

3

Technical data

The application may use technical data required to maintain the connection and synchronize the game between the client and server.

  • an anonymous player identifier saved in the browser, needed to keep the session and recognise the connection in the lobby,
  • the Socket.IO connection identifier required to handle the server connection,
  • a random profile key saved in localStorage that lets the server recognise the guest profile or an active account session; only its one-way hash is stored in the database,
  • aggregated statistics about how the game runs, such as the number of sessions, lobbies, games, attempts and active connections,
  • the app language you set and a two-letter country code provided by trusted network infrastructure, if available; the app does not store IP addresses in the analytics,
  • information about the lobby, players, bots, game mode, and current game phase,
  • game settings such as code length, time limit, player order, and hint type,
  • game state, attempt history, solved-target information, and data needed for the summary.
  • technical connection data that may be processed in the logs of the server or the hosting provider (e.g. date and time of the request, IP address and browser information) to the extent necessary for the security and operation of the service.
4

Purpose of data use

Data is used so the game can work correctly and players can see its current state.

  • creating lobbies and joining games with a code,
  • synchronizing gameplay between online players,
  • handling game modes, bots, and Hot Seat,
  • checking attempts, calculating hints, and ending the game,
  • displaying the attempt history and the summary after the game.
  • saving the profile, multiplayer results history, friendships and lobby invitations,
  • enabling optional sign-in with a passkey or password and account recovery with a recovery code,
  • syncing progress between devices and between zgadnijkod.pl and guessthecode.io if you secure or link your account.

The legal basis for processing the data needed for the game is providing the service at your request (Art. 6(1)(b) GDPR). Limited technical data and aggregated statistics are processed on the basis of the controller's legitimate interest: keeping the service secure, stable and improving it (Art. 6(1)(f) GDPR).

When you use the contact form, we store the subject, message, date and case number, as well as the name and e-mail address you choose to provide. When you e-mail us, we process the sender's address, details in the signature, the subject, the message and any attachments. We do this to reply and handle your request (Art. 6(1)(f) GDPR) and, where the message concerns the provision of the service, also to perform the contract or take steps at your request (Art. 6(1)(b) GDPR). We keep requests and correspondence until the matter is closed and then until any possible claims become time-barred, or for a shorter time if they are no longer needed.

Providing a player name, lobby code and the data needed for a given feature is voluntary, but without them the lobby or game cannot be used properly. The game does not make decisions with legal effects on users and does not use profiling.

Children and young people

Minors may use the game under the supervision of a parent or guardian. The game does not need a real first name, surname, e-mail address or photo — any nickname is enough, so we recommend that children do not enter anything in their nickname or victory text that could identify them. We do not show ads and do not profile users. A parent or guardian may request access to or deletion of a child's data on the child's behalf by writing to contact@guessthecode.io with the subject “Privacy”; the easiest way is to include the friend code from the child's profile.

The game has no chat or private messages. In nicknames, victory texts and lobby names we block contact details: links, e-mail addresses, phone numbers and account names on other services. We do not collect names, e-mail addresses, phone numbers, photos or location from children. A parent or guardian of a child under 13 (including within the meaning of the US COPPA) can at any time review the child’s data, request its deletion or refuse its further use — by writing to the address given above or by deleting the profile with the button in the “Danger zone” section of the profile page.

5

Data storage

  • Your name, avatar and victory text are saved locally and, once a guest profile is created, also on the server so that friends and the public player card work.
  • Guest profiles, friendships, pending invitations and multiplayer results history are stored in a PostgreSQL database. An unused guest profile is automatically deleted after 90 days of inactivity.
  • We keep messages sent through the contact form in a PostgreSQL database until the matter is closed, and afterwards only if they are needed to establish, pursue or defend legal claims. Each request has a random case number visible to the sender.
  • OVHcloud makes daily automatic VPS backups covering the application files and the database. Up to 7 most recent backups from 7 days are available. Deleted data may remain in the backups until they are replaced by newer ones.
  • Once the profile is secured, we store the login name and cryptographic hashes of the password and recovery code. The password and recovery code are never stored in plain text.
  • For a passkey we store its identifier, public key, usage counter, domain, a label with the type of system and browser (e.g. “Android · Chrome”) and the date it was added and last used. Your fingerprint, face image or PIN are never sent to the server. You can remove a passkey in your profile.
  • Adventure Mode progress, Challenge Mode results and match history saved in the browser are copied to the server only for an account that is secured or linked to the other game site, so that they are available on other devices and on both sites. We keep these copies until the account is deleted.
  • Accounts on zgadnijkod.pl and guessthecode.io are linked only at your request and are merged into one account. The link code is valid for a few minutes and kept only in server memory.
  • We keep a secured account until it is deleted. You can delete it at any time with the “Delete account” button in the “Danger zone” section of the profile page. This immediately removes from the database the account, login, password, passkeys, recovery code, sessions, friends, invitations, match history and synced progress; data may remain in backups until they are replaced. A guest profile is deleted with the “Delete guest profile” button.
  • An active account session key is valid for up to 365 days. Signing out on a device removes its local copy and creates a new guest profile.
  • App settings, such as the theme and interface preferences, are saved locally in this browser's localStorage.
  • Adventure Mode progress and detailed attempt history are saved locally in this browser's IndexedDB; they reach the server only with a secured or linked account (described above).
  • Adventure Mode data can be exported or deleted with the buttons on the statistics screen.
  • Challenge Mode results are saved locally in this browser's localStorage; they reach the server only with a secured or linked account (described above).
  • Lobby and game data are, as a rule, kept in server memory only while the lobby exists; we delete them when the lobby ends or expires. Limited data in technical logs may be an exception.
  • The game summary may be stored in the browser's sessionStorage to display the results screen after the game.
  • Data stored in sessionStorage usually disappears when the browser tab or session is closed.
  • The service worker and Cache Storage save app files such as scripts, styles, images and sounds locally to speed things up and allow some features to work offline. Visited files are usually removed from the cache after 30 days or when its limit is exceeded; the core PWA files remain until an update or until the site data is deleted.
  • Aggregated server statistics are kept according to the service configuration; per-minute samples and daily statistical entries (a hash that changes daily, with the coarse categories described below) may be kept for up to 90 days, and the date of the first and last visit assigned to a separate browser hash for up to 400 days after the last visit.
  • A one-way hash of the profile identifier is used for the aggregated breakdown of languages and countries. For each profile we keep only the most recently set language and the first reliable country code, for at most 400 days after the last activity.
  • Production application logs do not contain nicknames, full player identifiers, connection identifiers or lobby codes. They contain limited information about the time and type of an event or error. They are kept only as long as needed to ensure security, diagnose a problem or investigate a specific incident, and are then deleted as part of system log rotation. Data needed to establish, pursue or defend legal claims may be kept until those claims become time-barred.
Important

Enter your password only in the form for securing, signing in to or recovering your account. Do not enter your password, recovery code, payment details or other confidential information in your nickname, lobby code or fields visible to other players.

6

Cookies, analytics, and third-party services

The game does not use advertising or third-party analytics tools and does not show a cookie banner, because it does not store or read anything on your device that is not needed for the features you choose. It uses local browser storage (localStorage, sessionStorage and — for Adventure Mode — IndexedDB) solely to run the game. The profile key in localStorage serves as a technical session and is not used for advertising. The app does not store any data in the browser solely for statistics.

The server keeps internal, aggregated statistics about how the game runs: the number of sessions, lobbies, games, attempts, active connections, account levels and the languages and countries used. To count daily unique players, a one-way hash of the player identifier that changes every day is used; only coarse categories are stored with it: the country (if provided by the proxy server), the device type determined from the User-Agent header sent by the browser (phone, tablet, computer), the entry source — only if you came through a link tagged by us (e.g. from our TikTok profile) — the game domain used to enter, whether a lobby was joined, the number of games started and finished and which tutorials were opened and completed. For tutorials, the step at which they were closed is also counted anonymously. The page you came from and your device's time zone are not read.

Separately, aggregate daily counters of interface use are kept: which page of the game a visit started on, which pages of the game were opened, which buttons and links to other pages of the game were clicked, and how far the pages describing the game were scrolled (25, 50, 75 or 100%). These counters are not linked to a player identifier or to an IP address, and the browser stores no data for this purpose.

To tell new players from returning ones, the date of the first and the last visit is stored under a separate one-way hash. To measure the time from the first visit to the first game, the server keeps the time of a new browser's first connection only in working memory, until the first game or until the server restarts; only an aggregated time range is saved. Visits by automated agents (e.g. search engines and AI bots) are also counted in aggregate based on the User-Agent header — only the bot category name and the number of requests are stored; the header itself is not saved. Aggregated counters of game settings (mode, code length, time limit, duration) are also collected. A separate one-way profile hash is used to break down languages and countries, so that one profile appears in only one current language category. IP addresses are not stored in the analytics. A technical HttpOnly cookie is used only while activating a device in the administrator panel.

The PWA automatically registers a service worker and uses Cache Storage to keep the files needed to start quickly and work offline. You can delete this data in the site settings or browser storage. You can uninstall an installed PWA from your browser or operating system. Clearing the site data removes local settings, the player identifier and the profile key. An unsecured guest profile then becomes inaccessible from that device and will be deleted from the server after a period of inactivity.

The game runs at two addresses — zgadnijkod.pl and guessthecode.io — on the same server and with the same controller; messages sent to kontakt@zgadnijkod.pl and contact@guessthecode.io reach the same controller. Recipients of technical data and correspondence may include OVHcloud, which provides the VPS server, automatic VPS backups and Zimbra Starter e-mail and acts as a processor on behalf of the controller. The VPS is located in Warsaw, Poland (EEA). According to OVHcloud, Zimbra e-mail data is stored in European data centres. Authorised public authorities may also obtain access to data where required by law. We do not sell data or use it for behavioural advertising. If the controller ever launches a service that transfers data outside the EEA, this policy will be updated beforehand with the legal basis and safeguards for that transfer.

7

Your options

Send data requests through the Contact page with the subject “Privacy”. To protect your data, we may ask for information needed to confirm that the request comes from the right person. We reply without undue delay, as a rule within one month.

You can also delete your account or guest profile yourself at any time with the button in the “Danger zone” section of the profile page.

  • access to your data, rectification, erasure, restriction of processing and data portability — where applicable,
  • object to processing based on legitimate interest,
  • withdraw consent where processing is based on consent; this does not affect the lawfulness of earlier processing,
  • lodge a complaint with the data protection supervisory authority in the country of your habitual residence, place of work or place of the alleged infringement — in Poland this is the President of the Personal Data Protection Office (UODO), and in the United Kingdom the Information Commissioner’s Office (ICO).
8

Changes to the Privacy Policy

This policy may be updated if the way the game works, hosting, contact form, analytics, logs, or other data-related features change.

Last updated:

October 15, 2026