Controller
The data controller is Klyo Illia Krasnopolskyi, tax ID (NIP) 7822656871, based in Łódź, Poland. For anything about your data write to kontakt@klyo.pl. We answer within one working day.
Players: what stays on your device
To play you create no account and give nothing. The portal remembers a few things in your browser: the colour theme you chose, the lists of recently played and favourite games, your name on the leaderboard and a random device identifier. The theme, the recently played and the favourites never leave the device. The identifier and the name travel to our server only together with a score or with an action that counts towards your rank — the next section describes it. The identifier is a random string made by the browser: it contains nothing about you or your hardware, and we do not link it to a person until you sign in on that device yourself. You can clear all of it in your browser settings. We have no analytics of our own, no pixels and no maps from other servers; fonts are served by us.
We count, in aggregate, how many times a game page was opened and how many times a game started: one signal with the game name, without an IP address and without an identifier. Developers are paid from these numbers.
Leaderboards, ranks and medals
What we store with a score. When a game reports your score we store: the game name, the score, the day and time, the name you chose and the device identifier; if you are signed in, also the account number. From this we build the boards of the day, the week and all time: one row per device on each. The boards are public — anyone can see them without signing in and they may appear in search engines. They show the name, the score, the rank insignia and the time; nobody sees the identifier. You choose the name yourself: do not put your first and last name in it if you do not want them public.
Guest progress moves to the account. When you sign in for the first time on a browser that has played without an account, its progress joins the account: points and day streak, leaderboard scores, ratings, game saves and your own signature (if the account only has a generated one). This happens once — the device's progress disappears and belongs to the account from then on, so a second account on the same computer gets nothing from it. We record an entry in the account log (numbers, no browser number). A private window has no browser number, so nothing moves from it. Game saves follow the account: with an account the save is stored with the account and is the same on phone and computer; without one, with that browser.
Rank. For playing, visiting the portal, comments, posts, reviews and hearts we award points (XP) and a rank from Recruit to General — for activity, never for money. With the identifier (and after signing in, with the account) we keep: the total points in three streams (playing, community, creator), the rank, the number of days with activity, the length of the streak of consecutive days, the day of the last action and the counters of the current day needed for daily caps. The first visit to the portal on a given day records the day of the visit — the streak is counted from it. Medals of the day (gold, silver, bronze) are calculated after midnight from the boards of the day and record nothing beyond what is already in the score. The rank is public: it stands next to the name on the boards, on posts and on comments, and the portal ranking (top hundred in three streams) shows the name, the rank, the points and the streak length — without the identifier. Every player has a name — drawn from two English words and a number until they sign themselves — and a public player page (/player/name/) with the rank, scores by game, medals and the number of posts; pages without content are excluded from search engines.
Notifications. If you have an account, you get a notification inside the service when somebody overtakes you on the daily board — who and at which position. Without an account there are no notifications. A game's developer sees in the studio who leads on the boards of that game (name and score) and can remove a single score that looks like cheating.
Legal basis. The board and the rank are part of the service you ask for by reporting a score or playing (Art. 6(1)(b) GDPR: steps at the request of the person for a guest, the contract for an account). The overtaking notification and the visibility of the rank next to your name rest on our legitimate interest in running a fair competition (point (f)) — you may object, and we carry out the objection by deleting the device data described below.
How long. Scores stay on the boards as long as the game is in the catalogue; the rank as long as the device or the account reports actions. After the account is deleted its rank disappears at once, and the scores stay on the boards under the name, with no link to the account; if they should go too, use the button below or write to us.
Deletion in one click. The “?” next to the rank — in the profile and on the records page — opens the window with the rank ladder; at its end stands the button “Delete this device's data”. It immediately deletes every score, the rank, the points and the streak stored under this browser's identifier (signed in, it deletes the account's rank too); the boards refresh at once. You need no account and no e-mail for it, because only this browser knows its identifier. A score removed by the game's developer disappears from the board of the day and your other scores stay. The way through kontakt@klyo.pl works as well, of course.
Shared game league and Facebook identity
On Facebook, the game uses the Instant Games SDK to read and save game progress for the Facebook player. For the shared competition it sends a recent signed player proof to Klyo. Klyo verifies it and derives a pseudonymous player key; the raw Facebook player ID and proof are not stored in the league tables. On Klyo, the server uses your signed-in Klyo account. The league does not automatically merge Facebook and Klyo accounts. Your Klyo game save follows the Klyo account; your Facebook save follows the Facebook player.
To provide the competition you request (GDPR Article 6(1)(b)), the server stores the game and rules version, pseudonymous player key or Klyo account reference, public alias, edition, random seed, selected columns, game state, calculated score, operation identifier, start and update times and whether a run has finished. The server derives the score from valid moves. Repeated network requests must not create duplicate results. We do not collect your contacts or copy your Facebook profile photo into the competition database.
The shared table is public across Facebook and Klyo: alias, score, rank, edition and acceptance time. Facebook participants receive a neutral alias; Klyo participants use their Klyo alias. The table does not expose your email, raw Facebook ID, account number or move history. People can copy public results or share images outside the service.
Run state and move history are removed by the daily cleanup after 90 days without an update. The table retains the current week and up to 52 previous weeks; the all-time competitive best remains until deletion. In the competition window, Privacy and my data lets you download your league records and delete your league runs and results. Deletion affects the live database and both weekly and all-time tables, but not your ordinary game save. Deleting a Klyo account also deletes its league records. Technical backups follow Klyo’s backup lifecycle and are not used to display deleted scores.
Connections to Klyo use HTTPS/WSS. Hosting and edge-security providers process the connection data needed to deliver and protect the service, including your IP address. Meta separately processes Facebook sessions, cloud saves, social actions and advertising under its own privacy policy. The game may request Meta ads when the platform makes them available; an approval or ad impression is not guaranteed. Klyo competition moves are not sent to AdMob.
A share window, score image or copy-link control opens only after you choose to share. You choose recipients and can cancel. Joining the league does not subscribe you to a new promotional notification campaign. Local reminders in installed apps and existing Klyo account notification preferences remain separate.
Audience statistics: country and totals, never the address
What we count. How many devices came in on a given day, how many games were started and how many scores were saved — separately for each klyo service and each country. Our edge server derives the country from the IP address at the moment of arrival and drops the address immediately: the database receives a two-letter country code and totals, never the address. On the first visit of the day we also record where you came from: just the name of the search engine or site (e.g. Google, Reddit), the fact that you came from a Google ad, or the tag in the link you clicked (the utm_source parameter) — never the full address of the previous page. For a game we count trips to the app store (a click on the Google Play or App Store badge under the game): the developer sees how many people went to download their game, never who. There is no Google Analytics or any third-party tool here; none of these numbers leave our server.
How we count “one person”. Until 19 September 2026 we counted devices by the random browser identifier, and every private window was a “new device”. We now count people: an account is one person across all devices; a guest is a browser number, and so that a private window on the same device does not count the same post twice, the browser runs a short hardware test (screen, system, number of cores and memory, graphics card, language, time zone, how it draws one picture and plays one sound) and a short hash is derived from the result. The result itself never reaches us. We combine the hash with the start of the network address (the first three numbers of IPv4, the shared part of an IPv6 network), and everything we store — browser number, account, hardware hash, tab number — is written to the database only as hashes keyed with a secret server key: the database on its own says neither who someone is nor what hardware they have. The hardware mark is not an identity: it does not link a private window to your account, nickname or progress, and two people with the same hardware on one network are two people. We do not use motion sensors, the camera, the microphone, the battery, the list of fonts or location.
Sessions and views. Against a person we store the browser tab number (so that several tabs are one person) and the list of posts, clips and game clips they have already viewed — so that reloading the page, a second tab or a private window do not add views. We delete a guest's trace ourselves after 90 days without a return, an account's trace after 13 months, and on account deletion immediately. The “Global Privacy Control” signal switches the hardware test off entirely.
Who with an account was here today. When you are logged in, we record on which day and in which part of klyo you were (the games portal, the developer studio, the panel, your account): the time of your first arrival and last exit — without the IP address. Only the klyo administrator sees it, under your nickname, never your e-mail; it tells us how many developers and players with an account really use klyo (Article 6(1)(f) GDPR). We delete the trace ourselves after 90 days, and immediately together with the account.
Where you came from and which page you are on. On your first visit of the day we record the kind of source: a search engine, a site or a link with a campaign tag (for example “google”, “reddit”, “none” for an address typed by hand), once per person per day, also when you open a private window. To that source we add the total minutes played and plays, without linking it to you in reports. While a page is open, the server knows which portal page you are on, only for the “on the page now” counter; nothing of it remains after you close the tab. Basis: our legitimate interest (Article 6(1)(f) GDPR), knowing what brings players. Daily totals are kept like the rest of the statistics.
How long you played. For each game we record how many seconds and plays you had on a given day — under your browser number or your account, with the time of your first and last stretch of play. Our server measures the time: from starting the game until you hide the tab, close the page or leave the game untouched for 90 seconds. The game only tells us “playing” or “not playing”, nothing about what you do in it. Only the klyo administrator sees it together with your nickname (rewards for players, protection against inflated scores and ad fraud); the game's developer sees only totals and the spread of playing time — and only from five players, so that nobody can be recognised in a small group — plus the public leaderboard (Article 6(1)(f) GDPR). We delete it ourselves after 90 days; the “Delete this device's data” button and deleting your account remove it at once, and when you log in, your guest time moves to your account.
Whom we do not count. Automated browsers, robots and traffic from our own server — such visits go into a separate column and do not count towards ranks, the “playing now” counters or ads.
Tailored order. The “for you” order of games is built from your preferences stored in this browser (see the section about what stays on your device). The same memory orders the clip queue: the browser remembers which clips you watch to the end, which you skip right away and which you heart, as weights of clip features (game, genre, mood, clip author), and that decides what you see next. This learning stays in the browser; we only receive the number of views, completions and skips of each clip. Your profile has a switch, “Tailor the order of games and clips to what I play and watch”: off means we remember nothing and the server receives an empty list, ordering games the same way for everyone. The server learns about the switch only so that we know how many people opted out.
The “do not sell my data” signal (Global Privacy Control). If your browser sends this signal, we ask Google ads for non-personalised mode and count your visit in a separate column — no prompt, no clicking.
Proof of ad consent. When you answer Google's consent window (in Europe), we store next to your device identifier only the consent string (the so-called TC string), the date and the country — our proof that the question was asked and how it was answered. The same “Delete this device's data” button that removes scores and rank removes it too.
On what basis and for how long. Daily totals are our legitimate interest (Art. 6(1)(f) GDPR): we need to know whether the portal works and where people come from, and we do it without identifying anyone — which is why we do not ask for consent to the counting itself. Totals are kept indefinitely, because nobody can be identified from them; the identifier in server memory lives one day.
Cookies and ad consent
What and why. Without signing in the portal sets you no cookie at all. Once you sign in there is one: the session cookie that remembers it is you — without it you cannot stay signed in, so we do not ask consent for it and the only way to avoid it is not to have an account. The settings described above (theme, favourites, device identifier) are not cookies: they stay in your browser's memory; the identifier is sent only together with a score and with the actions counted towards the rank, as described in the section on leaderboards.
Ads. Google AdSense ads will stand next to games; the service is waiting for Google's approval, so nothing is shown yet. Google adds its own consent mechanism to the pages and stores your answer in a cookie named FCCDCF. When the ads start, you will see the question on your first visit — you can decline, the ads are then non-personalised and the game works the same. Withdrawing consent is as easy as giving it: the “Privacy settings” link in the footer opens the same question again. You can also change it in Google's ad settings. How Google processes data is described on Google's partner sites page.
Ad consent is separate from the terms. Accepting the terms is a condition of having an account; consent to advertising cookies must be freely given — so we ask for it separately and refusing takes nothing away from you: you play, post and publish games exactly the same. We do not merge the two into one question and we will never make an account depend on consent to ads.
Games by independent developers run on separate addresses (g-yourgame.klyo.pl) and have no access to the portal's cookies. The developer terms forbid them from loading their own ads and collecting player data, and known ad networks are blocked technically inside the game frame; if you still notice a game doing this, report it with the button next to the game and we remove it from the catalogue.
Information required by Google (AdSense)
Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet. You may opt out of personalised advertising by visiting Ads Settings or www.aboutads.info. How Google processes data: How Google uses information from sites that use its services.
Developers: account and payout details
A developer account is an e-mail address and a password (we store only its hash). To pay your share we need settlement details: name or company name, address, tax ID for a company, country of tax residence and a bank account number. These are encrypted in the database and shown in the studio only in masked form. The legal basis is the contract (developer terms) and klyo's tax obligations as the paying party. We keep settlement data for five years from the end of the year of the last payout, as tax rules require. Where platform-reporting rules (DAC7) require it, we report earnings to the tax administration.
We do not sell data, do not profile and do not send offers. E-mails from your account concern only your games: publication, removal, settlement, changes to the terms.
Games with the developer's match server
What happens. Some multiplayer games connect to their developer's match server, so that players on klyo and on the developer's site play in the same matches. A person from klyo approves such a server, and the game page says so plainly and links the developer's privacy policy.
What data. The developer's server sees your IP address and what the game sends during a match (moves, match results). It does not receive your klyo account, e-mail address or anything outside the game. The developer is responsible for data on their server as a separate controller, under their own privacy policy.
How to avoid it. Such games state on their page that they use the developer's server; if you do not want to connect to it, do not start that game. All other games connect only to klyo.
Developers: steps of publishing a game in the studio
What we record. When you are signed in and publish a game in the “New game” wizard, we record against your account which steps you went through: opening the wizard, choosing a package, the result of the package check in your browser (the kind of refusal, for example “no index.html” or “package too large”), the package size in whole megabytes, reaching the description, the start of the upload and closing the wizard before uploading, as well as what your browser did with the files you dropped (for example that it packed a folder), the error messages the studio showed you (our sentence and its code, without file names) and that you sent a report to klyo. We do not record file names, game content or what you type in the form.
Why. To know at which step developers give up and improve that step, and to be able to help you if something stopped you. We see these entries as they happen, so we can react before you close the tab.
On what basis and for how long. The basis is our legitimate interest (Article 6(1)(f) GDPR): improving the tool you use. Entries are deleted automatically after 90 days. You can object by writing to the address in the section about your rights; we then stop recording them for your account and delete the existing ones.
Developers: keeping visits honest next to ads
What we do. Visits to a game that come from its own developer are subtracted before we count statistics and settlements. We recognise them by three things: the signed-in account, the browser the developer signed in from, and the connection they signed in from over the last 30 days.
Where the data comes from. From sign-in records we keep for account security — network address, browser signature, date. We collect nothing new for this purpose and set no additional files in anyone's browser. The comparison happens on our server and does not leave it.
Who it applies to. Only developers, and only on THEIR OWN games. If you play someone else's game from the same connection as its author — because you live together or share an office — your visit counts normally. On their game it will not, and that is a deliberate cost: we would rather lose a few visits than risk the advertising account every developer is paid from.
On what basis and for how long. The basis is our legitimate interest (Article 6(1)(f) GDPR): protecting the advertising account against invalid traffic, the detection of which Google requires of us. We compare against sign-ins from the last 30 days; older ones stop being considered. You may object — write to kontakt@klyo.pl — but we would then be unable to run your developer account with a share of ad revenue, because without this protection we would be putting other developers' payouts at risk.
On what basis and for how long
On what basis. We run your account and the service because you entered into an agreement with us (GDPR art. 6(1)(b)). Personalised ads are shown only with your consent, which you can withdraw with one click in the footer (art. 6(1)(a)). Security, abuse prevention and counters that do not identify anyone rest on our legitimate interest (art. 6(1)(f)). Developers' settlement documents are kept because tax and accounting law requires it (art. 6(1)(c)).
For how long. We keep your account until you delete it; for 30 days after deletion only the record that the account existed remains, so a mistake can be undone, and then it is gone. Developers' settlement documents are kept for 5 years from the end of the tax year, as the law requires. Server logs (address, time, response code) are deleted after 30 days. Content reports and moderation decisions are kept for 6 months, so an appeal is possible and so we can show how a case was handled. Clips and photos disappear when you delete them, or when we remove them after a report.
Who we share data with
The portal and its e-mail run on our own servers in Europe. Ads are delivered by Google Ireland Limited on its own terms; serving them may involve cookies, web beacons, IP addresses and other identifiers read by Google in your browser. Transfers are made by our bank, and settlement documents go to our accountants under a data processing agreement. Nobody else has access to developer data.
Cloudflare. Cloudflare sits in front of our servers: it filters attacks and speeds up loading. It sees the address you come from and the address of the page, but it does not look inside your account. Without that layer a single attack would take the portal down for everyone.
Does data leave Europe. Our servers are in Europe. Two services we use belong to companies in the United States: Cloudflare and Google (ads). Data that reaches them may be processed outside the European Economic Area. Both take part in the EU-US Data Privacy Framework and use standard contractual clauses approved by the European Commission — that is the legal basis for such a transfer. If you do not want personalised ads, withdraw your consent in the footer: no data about your interests then goes to Google.
Your rights
You have the right to access, correct, delete, restrict, port and object. A message to kontakt@klyo.pl is enough. We delete a developer account immediately; data we must keep for the tax office is blocked and deleted after the required period. You may lodge a complaint with the Polish data protection authority (UODO).
Player account, community, clips and age
A player account is an e-mail address (for sign-in and account messages), a password hash, a name you choose yourself and an age bracket (13–15, 16–17, 18+), not a birth date. For 13–15 we store only the fact that a guardian's consent was confirmed. The age bracket decides which games, posts and comments you see and which ads stand next to games. The basis is the contract (terms of service) and the duty to protect minors.
In the community we store what you add: posts, comments, votes, hearts, followed developers, photos and video. Video is processed on our server (compression, trimming to 30 seconds, a preview picture); we strip metadata from files, location included. For rate limits and spam protection we keep a hash of the IP address for 24 hours. Blocking a user. You can block any account (the “Block author” button next to a post): we store the pair “you → blocked” and the date. Effect: you do not see their posts, clips and comments, they cannot comment on your posts and do not trigger your notifications; we do not inform them of the block. You see the list of blocked users in your account, unblocking deletes the entry immediately, and deleting the account deletes the whole list. Content is checked by software: word lists, random strings, pace, links, consistency with the age label; decisions to hide are made by a person or by software with a recorded reason you see in your language and can appeal. About the order of games. The portal adapts the order to what you play and whose clips you watch — but that memory lives ONLY in your browser. It is a dozen words like „puzzle” or „five minutes”, with no history from which anything could be reconstructed. Only those words reach us when we are asked for an order; no profile is created on our servers. The weights fade on their own, and you can see and erase the whole thing with one click in your profile („What the portal remembers about you”).
Posts and clips you delete disappear from view immediately and from technical copies after 30 days. The moderation decision log is kept for 12 months. You delete the account from the profile or by e-mail; the e-mail is kept 30 days in case of a mistake, then it is gone. You have the right to access, rectify, erase and port your data (you receive it by e-mail in a readable file) and to complain to the Polish data protection authority (UODO).
Recording gameplay: the recording stays on your device
When you record your gameplay with our tool, the recording is made and kept in your browser — not with us. We store it chunk by chunk in the device's storage so it survives closing the tab and you can come back to it tomorrow. Those are your „drafts” and only you see them.
Nothing reaches us until you send it. You mark a fragment, we cut it ON YOUR device, and only that cut piece — at most 30 seconds — travels to our server together with the caption you write. The rest of the recording stays with you and you can erase it with one click; we then delete both the entry and every chunk.
We record the game's picture and its sound. We do not record other tabs or windows: the picture is cropped to the game frame itself. Voice and face — only if you turn them on yourself with the “microphone” and “camera” buttons in the recording bar; both are off by default. The voice recording and the camera picture stay only on your device, next to the game recording, and enter the clip only when you leave them on in the editor and press “Post”. Face in frame is available from age 16.
Captions from voice. If you turn on automatic captions, the voice recording goes to our server only so that a program (Whisper, running on our own machine, no third parties) turns it into timed text; the voice file is deleted right after recognition and only the text remains in your editor — you fix it by hand before posting. Profanity in the recognised text is replaced with 🔞 and muted with a tone in the clip's sound — the same applies to captions you type yourself.
A posted clip is a community post and follows the same rules as any other: moderation, reports, and your right to delete it.
What we are building (in progress — not live yet)
We write this ahead of time so nothing surprises you. The items below are in progress; each comes into force with a new version of this policy (date in the header) and a separate question wherever consent is needed.
A session record instead of a video. A clip will be a record of what you saw in the game (changes on screen, your taps and keys with timing, game events — score, record), not a video file. It weighs kilobytes, is created and kept on your device like today's recording, and reaches us only after “Post”. The video for TikTok or YouTube is computed from it on your device. Such a record will also confirm a leaderboard record (session replay) and — if the game's developer asks — show them what you did when the game broke; the latter only with your consent when you report a bug.
Recording by itself. The last 30 seconds of play will be kept in the device's memory continuously so that after a good moment you can press “keep this”. The buffer never leaves the device by itself and vanishes when you close the game.
Player network. Finished public files (video clips, streams) will be able to travel directly between players' browsers so the server is not a bottleneck. Your device gives to others only if you turn it on, only on Wi-Fi, only while you have a game open, with a volume cap; the other player sees only a content hash, never your e-mail or account. Drafts, voice and camera never travel this way.
Mobile app and playing offline. In the klyo games app you will be able to download a game and play offline; scores and clips from such play stay on the device and are sent when the network is back. An ad fetched earlier may be shown offline. Recording in the app will take the picture from the game window inside the app — not from the phone's screen and without the screen-recording permission.
Scope and changes
This policy covers games.klyo.pl (formerly gry.klyo.pl), the developer tools at dev.klyo.pl, the game addresses g-yourgame.klyo.pl and the klyo games mobile apps. It is one service under several addresses: you have one account and we keep one record of your data — we split the addresses so that work tools stand apart from pages for players, not to collect anything twice. The company site klyo.pl has its own policy. We announce material changes inside the service: by the date in the header of this page and, for accounts, by the step “Privacy policy” in the “Your account” card, which stays until you confirm you have read the new version — that confirmation is stored with the account and dated, like the acceptance of the terms. In force since 2026-09-26. Polish version.
What changed on 2026-09-26. We corrected the recording section: since 15 Sept 2026 the clip editor has an optional microphone, camera and captions from voice, while the previous version said “we never turn on the microphone” — that was no longer true, and we now describe exactly what happens to voice and face. We added “What we are building” to announce session records, the player network, the app and offline play before they arrive. Earlier (14 Sept) leaderboards, ranks, medals and the device-data deletion button were added, with the corrected sentence about the device identifier (it travels to the server with the score).