← Back to game

Privacy Policy — Pyatnashki

Effective date: 27 September 2026 Applies to: the Pyatnashki game available at https://pyatnashki.com and the Pyatnashki Android app (net.dcp0.pyatnashki), distributed through F-Droid and Google Play — together, the "Game".

This policy is written to satisfy both EU/EEA/UK requirements (GDPR / UK GDPR / ePrivacy) and US requirements (CCPA/CPRA and other state laws, CalOPPA, COPPA). Because the Game collects no personal data, the same short policy serves users in every region.

1. The short version

Pyatnashki is a puzzle game that runs entirely on your device, in a browser or as an Android app. We do not ask for your name, email, or any personal details; we have no user accounts; and we show no advertising. Your game progress — the puzzle you have part-solved — is saved only on your own device, and we never see a game you have not finished.

The app and the website are the same game and the same rules. Everything below applies to both, and where they differ the difference is stated in place. There are exactly four differences and they are all here: the app keeps its saved game in the app's own storage rather than in a browser (section 3), the app photographs its own screens (section 5), the app uses a Google service to report crashes and the website does not (section 5), and the app measures no visits and shows no cookie notice, because it is not a website (section 6).

We do measure visits to the site — which pages, from where, and for how long — and section 6 says exactly what that means. By default this is done without storing anything on your device and without any identifier that connects one visit to another. A cookie notice offers you the option of allowing one, so that we can tell a returning visitor from a new one; declining changes nothing else, and ignoring it is the same as declining.

There is one thing the Game can send, and it is on unless you turn it off: a switch in Settings labelled "Send gameplay records", described in section 5. A first visit, a cleared browser, a private window and a fresh install all send until you say otherwise. While it is off, nothing about your play leaves your device — in the app that includes the pictures described in section 5, and the crash reporting done by Google's service described there.

One thing is sent even with that switch off, and we would rather say so here than bury it: when the Game breaks, it sends a report of the failure. It carries no identifier and nothing you typed, and section 5 lists every field. The reason it is not behind the switch is that a game that dies on launch never reaches the Settings screen, so the only crashes we would ever hear about would be the ones from people whose game already works.

The personal data processed in connection with the Game is the technical information (such as your IP address) that our hosting provider automatically records in its server logs when your browser requests the Game's files — the same as for any website — and, in the Android app and only while records are on, what Google's crash service receives when the app crashes (section 5). Details below.

2. Who is responsible (Controller / Business)

dcp0 Email: contact@pyatnashki.com

For any privacy question or to exercise your rights (Section 8), contact us at the email above.

3. What the Game stores on your device

To let you keep playing where you left off and to work offline, the Game stores the following on your device — in the browser, using localStorage and the browser Cache API; in the Android app, in the app's own private storage. All of it stays on your device, with one exception named in the table: the last two rows are the record of a solved puzzle waiting to be sent, and they exist only while gameplay records are switched on. Everything else is not transmitted to us or any third party:

WhatWherePurpose
Everything the game saves (state, theme, rules-seen, lang)localStorageSave and restore your game and your settings
telemetry — only while gameplay records are switched on, and only while a puzzle is unsolvedlocalStorageA puzzle in progress and any finished record not yet sent: a random game id, a counter, and the records waiting to go. It is what lets you leave a puzzle for a week and have it counted as one game rather than two. Nothing about you
run — only while gameplay records are switched on, and only while a puzzle is unsolvedlocalStorageThat puzzle's moves so far, with how long each took. The board you were dealt is not copied here — state already holds the game, and the record reads the opening from it when the puzzle is solved
dcp0.telemetry — written once you answer the records switch either waylocalStorageYour answer to "Send gameplay records", so the Game stops asking. The word yes or no and nothing else
dcp0.sessionlocalStorageA random game session identifier: this game in this browser, not you and not your computer. It exists whether or not records are switched on, because the Game uses it to ask which features are switched on for it — and it is not attached to the performance reports below, which carry no identifier at all. You can reset it in Settings, which makes a new one
The Game's own files (HTML/JS/CSS, icons, manifest)Cache Storage (service worker)Offline play and fast loading

In the Android app it is the same list with two differences. The entries are written to the app's own private storage (an on-device key-value store called MMKV, readable by no other app) instead of localStorage, under the same names; and there is no service-worker cache, because the app already carries its own files — nothing is fetched to make it work offline. One picture-keeping entry is added, described in section 5. Nothing in the list leaves your device except where this policy says so.

The app's crash reporting adds two more things to that private storage, both written by Google's Crashlytics library and described in section 5: a Crashlytics installation identifier for this app on this device, and any crash report it has collected but not yet sent. The library is present in every copy of the app and collects nothing until you turn records on; clearing the app's storage or uninstalling it removes both, and a new identifier is generated if you turn records on again afterwards.

This is functional / strictly-necessary storage for a feature you requested (playing and saving the game). See the separate Cookies & Storage Notice for detail. You can erase all of it at any time: clear this site's data in your browser settings, or — for the app — clear its storage or uninstall it, which removes every entry above along with the app.

4. What our hosting provider processes

The Game's files are served by Cloudflare, Inc. (United States), from its global network — the data centre that answers you is the one nearest you, which is what makes the Game load quickly wherever it is opened. When your browser loads the Game, Cloudflare's servers automatically receive and may log standard technical data, including your IP address, browser/user-agent string, requested files, and timestamp.

(GDPR Art. 6(1)(f)).

at <https://www.cloudflare.com/privacypolicy/>.

We do not combine these logs with anything else, and we do not use them to identify you.

The Android app does not fetch the Game. Its files arrive with the install, from F-Droid or Google Play, so nothing above happens when you open it. The app contacts a server of ours only to send what section 5 describes, and to ask which features are switched on for it. The store you installed from is its own controller: Google (Google Play) and F-Droid decide for themselves what they record about a download or an update, under their own policies and not ours.

5. Gameplay records (on by default)

The Game has a switch in Settings labelled "Send gameplay records". It is on unless you turn it off, so a first visit, a cleared browser and a private window all send until you say otherwise. While it is off, nothing about your play leaves your device.

This changed on 23 September 2026. Until then Pyatnashki sent only a summary of how smoothly it ran, and this section said the Game recorded nothing about how you played. It now records a solved puzzle in the same way our other games record a finished game, and both halves are described below.

What is sent when it is on

When you solve a puzzle — and also when you leave one unfinished, which is described below the list — the Game sends one record to a server we run:

took. Times are the gap between one move and the next, not clock times.

puzzle. This is a board, and it is sent deliberately: without it the list of moves describes nothing, because a slide only makes sense against the squares it started from. It is the arrangement the Game shuffled for you — it says nothing about you, and the puzzle you are part-way through is never sent.

coincidence.

in this browser — not you and not your computer — and it exists whether or not records are switched on, because the Game also uses it to ask which features are switched on for it. It is not derived from anything about you or your hardware: it is a random number. You can reset it in Settings, which makes a new one.

A puzzle you leave unfinished is also reported, marked as paused: when you switch away from the Game with moves on the board, the same record is sent with the slides you have made so far and nothing else added. It is sent again if you leave again having played further. This is how we can tell a puzzle somebody is still working on from one whose record went missing — without it, the two look identical to us.

Leaving is the only trigger. A puzzle sitting open in front of you is not being reported as you play, and a game you open and put down without moving a tile sends nothing at all.

Performance reports

While records are on, the Game also sends a summary of how smoothly it ran, at the end of a puzzle and, if you leave mid-puzzle, when you switch away from it.

It is a summary and not a recording. What it contains is:

milliseconds, how many over 34, how many over 50) and the slowest one. Not a list of frames, and nothing that says when in the puzzle they happened.

started, as typical and worst values across the whole puzzle — not per move.

positions, and never which tiles or where they were.

Hz, whether the device is in battery-saver, whether you have asked for reduced motion, and a single word for how capable it is — low, standard, high or unknown.

coincidence.

What it deliberately does NOT contain: your device's model name, its graphics-hardware name, any advertising or device identifier belonging to the platform, your exact memory or processor count, your IP address, your browser's user-agent string, or a record of any individual gesture or frame. The capability word above is worked out on your device from numbers your browser already offers to every website, and only the word is sent — never the numbers it came from. No identifier of any kind is attached, so two reports from the same device cannot be recognised as such.

Our server additionally records the two-letter country the request came from, as reported by our network provider, and the time it arrived. Your IP address is not stored: it is used to count requests against a rate limit and then dropped.

Why: this game runs on phones, laptops, tablets, handhelds and TVs, and a release that is smooth on a fast machine can be unplayable on a cheap one. There is no way to know that from here without being told, and no way to tell a slow release from a slow device without knowing which kind of device it was.

Turning it off stops it immediately and for good; there is nothing stored to delete, because these reports carry nothing that could point back to you.

Pictures of the Game's own screens (the Android app only)

Added to this policy on 27 September 2026, when the app was first released. The website never does this, and earlier versions of this policy described only the website.

While records are on, the Android app photographs its own screens and sends the pictures to a server we run. What is captured is what the app itself draws — the board, the counters, the buttons — taken by the app from its own window. It is not a photograph of your screen as a whole: no other app, no notification, no part of the system is in it, and the app asks for no camera permission and no access to your photos (the only permissions it requests at all are internet access, vibration, and — since the crash reporting described below — the ability to check whether the device is online).

solved puzzle, the How-to-Play sheet and the Settings sheet.

size, up to twenty-four pictures for a version. A picture the app has already sent is not taken again; which ones it has sent is the one extra entry the app keeps in its own storage (section 3).

you switch away from the app while one is being sent, the send is abandoned.

the word android, which build of the app took it, the picture's size in pixels, and the same random game session identifier described above — the one you can reset in Settings.

photographed, and that sheet displays the random session identifier. So that picture contains that identifier — the same one already sent beside it, and nothing else about you.

Why: a release can look right on the machine it was built on and be wrong on a phone — a control off the edge of the screen, a board that does not fit, text in the wrong colour on a light theme. Every one of those has happened here, and each was found in a picture.

Turning records off stops this too, immediately: with the switch off the app takes no picture and sends none. Uninstalling the app, or clearing its storage, removes its record of which pictures it has sent along with everything else.

When the Game breaks (crash reports)

Added 27 September 2026. Earlier versions of this policy did not mention crash reporting, because the Game sent none.

This is the one thing the records switch does not control, and the reason is above: a game that fails on launch never reaches its Settings screen. So a crash report is sent whether the switch is on or off, and what makes that defensible is what is in one rather than what we intend by it.

What a crash report contains:

did not handle, a screen that stopped responding, or the app being killed.

file path, a long number or an identifier removed before it is stored.

location, all of them within the Game.

won) and which build of the Game it was.

records are on**. With the switch off there is no identifier of any kind, so two crash reports from the same device cannot be recognised as such.

It contains no device model, no advertising or platform identifier, no account (there are none), and nothing you typed — the Game has no text input. As with every other report, our server records the two-letter country and drops your IP address after counting it against a rate limit.

The Android app additionally uses Firebase Crashlytics (a Google service)

Only while records are on. As shipped, the app's crash service is switched off and collects nothing; it is turned on when you turn records on, and turning records off turns it off again.

Why a second service at all, when the above exists: an Android app can be killed by a failure below its own program — in the graphics or system code it runs on — and when that happens the process is gone before anything of ours can observe more than the fact that it died. Google's service installs a handler underneath ours and can report which line of native code failed. That single capability is the only reason it is here.

What Google receives when the app crashes, per its own documentation: the crash itself and the sequence of calls that led to it, your device model and operating system version, the app's version, a Crashlytics-generated installation identifier for the app on that device, the time, and the IP address the report was sent from. It also receives crashes and handled errors from the Game's own code, which duplicates what we collect ourselves.

What we do not give it: your name or email (we hold none), any advertising identifier, any platform device identifier, and anything about how you play. The only label of ours attached to a report is the random game session identifier described above — the one you can reset in Settings — so that a crash in Google's console and the same crash in ours can be recognised as the same run.

Google acts as our processor for this and processes the data in the United States (section 8). Its handling is described in the Firebase data-processing terms and Google's privacy policy.

We intend to remove it. Everything Crashlytics does for this app except that one native stack is already done by the reporting described above, which sends less and is ours. When we can produce that stack ourselves, this service comes out of the app and this subsection goes with it.

6. Visit measurement (web analytics)

Added 23 September 2026. Earlier versions of this policy said the Game used no analytics of any kind. That is no longer true, and this section says exactly what changed.

This section is about the website only. The Android app measures no visits, creates no analytics identifier and shows no cookie notice — there is no site to arrive at and nothing to count. Everything in this section can be read as not applying to it.

We measure visits to the website: which page you arrived on, which page you left from, roughly how long the tab was actually in front of you, the website that linked you here (its domain only — never the address of the page you were reading), any campaign tags on the link you followed, and coarse facts your browser reports about itself — browser family, operating system family, whether you are on a phone, a tablet or a desktop, whether the Game is installed, your screen and window size, your language and your time zone. Our hosting provider also tells us which country the request came from.

What we deliberately do not collect

requires it, and it tells us a country. The address itself is not written down.

as one of a short fixed list of families, so nothing unusual about your setup can be written into our records.

The one thing the cookie notice is about

The first time you visit you are offered a choice. It does not block the game, and you can ignore it for as long as you like.

linked to your name or to anything else about you; its only purpose is to let us tell a returning visitor from a new one, and to see whether people come back over several days.

never created, nothing is written to your device, and no marker connects one visit of yours to another. Everything in the list above is still measured, because measuring it stores nothing on your machine and identifies nobody.

If you allow it and later change your mind, the identifier is deleted from your browser at once — see section 11 for the browser signals that have the same effect.

Lawful basis (EU/UK). Storing and reading that identifier is done only with your consent (ePrivacy / GDPR Art. 6(1)(a)), which you may withdraw at any time. The measurement done without it stores nothing on your device and involves no personal data.

Turning it all off. The "Send gameplay records" switch in Settings governs this too. With it off, no visit is measured and nothing is sent at all — the cookie choice then makes no difference, because there is nothing to send.

7. What we do NOT do

optional identifier described in section 6 is used to count returning visitors on this site and for nothing else; it goes nowhere near an ad network.

sends data to Google as our processor, on our instructions and for that one purpose (section 5); it is not advertising, it is not a sale, and it is not shared with anybody else.

sensors (aside from an optional vibration "buzz" that sends no data).

requests three permissions and no others: internet access, vibration, and network state — the last one added in version 0.1.40, asked for by Google's crash library so it can tell whether there is a connection before trying to send a report. None of the three prompts you, because none of them is the kind Android asks about; you can see the full list on the store listing. The pictures in section 5 are of the Game's own screens, drawn by the Game.

which are about the puzzle rather than about you.

8. International transfers

Cloudflare is a United States company serving from a global network, so server-log data is processed outside the European Economic Area. Those transfers rely on the safeguards described in its privacy documentation — EU Standard Contractual Clauses and the EU-US Data Privacy Framework.

Google likewise, for the Android app's crash reporting described in section 5 and only while records are on: Google LLC is a United States company, and its Firebase terms rely on the same two safeguards.

9. Your rights (EU / EEA / UK — GDPR & UK GDPR)

You have the rights to access, rectify, erase, restrict, object to, and port your personal data, and to lodge a complaint with a supervisory authority.

Because we hold no personal data about you ourselves, most of these rights have nothing for us to act on. In practice:

your browser, or clear the app's storage or uninstall it, to erase it.

contact@pyatnashki.com and we will help direct your request, or contact the host directly.

You may complain to your local data-protection authority.

10. Your rights (United States — CCPA/CPRA & other state laws)

If you are a US resident (for example in California, Virginia, Colorado, Connecticut, Texas, or another state with a consumer-privacy law), those laws give you rights to know, access, delete, and correct personal information, to opt out of its "sale" or "sharing" and of targeted advertising, and not to be discriminated against for exercising them.

"share" personal information as those terms are defined under the CCPA/CPRA or other state laws. The optional identifier in section 6 counts returning visitors on this site and is disclosed to nobody, so there is nothing to opt out of — and we honour Global Privacy Control regardless (section 11).

opt out of selling/sharing**. Your saved game lives only in your browser; clear this site's storage to erase it.

profiling, and we do not knowingly process "sensitive personal information."

(Section 4). To make a request or ask a question, contact contact@pyatnashki.com.

11. "Do Not Track" (DNT) and Global Privacy Control (GPC)

Some browsers send "Do Not Track" or Global Privacy Control signals. We honour both, and they now change what happens.

If your browser sends either signal, the Game measures your visit in its anonymous form: the optional identifier described in section 6 is not created, and an identifier already stored from an earlier "allow" is deleted. The signal overrides a stored "allow" — a signal you are sending today is a more recent answer than a button you pressed last month.

We publish this commitment in machine-readable form at https://pyatnashki.com/.well-known/gpc.json.

We do not "sell" or "share" personal information as those terms are defined under the CCPA/CPRA, so there is nothing further for these signals to switch off.

12. Children (COPPA)

The Game is a casual puzzle for general audiences. It is not directed to children under 13, and because it collects no personal information from anyone, it does not knowingly collect personal information from children under 13 (COPPA) or under 16. The Game provides no way to submit personal information; if you nonetheless believe a child has done so, contact contact@pyatnashki.com and we will address it.

13. Changes to this policy

If the Game changes in a way that affects data processing (for example, if analytics or accounts are ever added), we will update this policy and its effective date before that change takes effect.

27 September 2026 — the Android app. This policy described a browser game, and an Android app had been published without it saying so. Three things were added: that the app stores its saved game in the app's own storage rather than in a browser (section 3), that the app photographs its own screens while records are on (section 5), and that the visit measurement and the cookie notice are the website's and not the app's (section 6). Nothing about the Game's behaviour changed on this date; what changed is that the policy now describes all of it.

14. Contact

dcp0 — contact@pyatnashki.com