Floke — untangle puzzle for Android com.repstrekk.floke · published as Frost Audio by Thomas Arill Eriksen Frost · in force from 15 October 2026
Floke is a game about threads: where each one starts, where it ends, and whether it crosses anything on the way. This notice is written the same way. Rather than a list of topics, below is every thread that could run between you and anyone else while you play — fifteen of them, each with its two ends named. Some are tied. Most are not tied at all. The ones that are tied, I say exactly where they land.
your fingertip→the glass
Every move you make is a touch on the screen, handled by the game and then gone. The coordinates are not logged, not timed against you and not kept once the peg has settled. Nothing about how you play — how fast, how hesitantly, in what order — survives the moment.
Ends on your devicethe game→a private folder on your phone
So a half-untangled web survives an interruption, Floke writes a small file: which packs you have opened, your best move count and time on each web, the position you walked away from, and your settings — sound, haptics, thread colour, whether crossings are highlighted. It sits in the app's own private storage area, which Android keeps apart from other apps, and I never see it. There is no cloud save and no backup that I operate. Android Settings → Apps → Floke → Storage → Clear data removes it, as does uninstalling; nothing of it survives anywhere else, because it was never anywhere else.
Ends on your devicethe game→the internet
The published package declares no internet permission. Not a restricted one, not an unused one — none. You can see this for yourself on the Google Play listing under App permissions before you install anything. Every thread below that would need a connection is severed by this single fact, which is why so many of them are. Floke works identically in flight mode, and if that is ever not true the build has changed and this page is wrong.
Never tiedthe game→a name for you
Registration, sign-in, profiles, nicknames, an e-mail box to fill in — none of it exists. Floke opens straight onto a tangle. With no login there is no handle, and with no handle two people who both play Floke are indistinguishable to the software and to me. Your name, your postal address, your telephone number and your date of birth are never asked for at any point, including the first launch.
Never tiedthe game→the advertising identifier
The advertising ID, the Android ID, the device serial, the IMEI, the MAC address and the list of your other installed apps are not read. Several would need permissions that are not requested; the rest would be useless to software that cannot transmit anything. No substitute identifier is generated on the device either — no install UUID, no fingerprint assembled from device characteristics.
Never tiedthe game→the rest of your phone
None of these is requested, so none can be reached. A puzzle played with a fingertip on a blank canvas has no business with your photographs, your address book, where you are standing or what the room sounds like, and the manifest reflects that. If a permission prompt ever appears, something is wrong and you should write to me before granting it.
Never tiedthe game→a payment
Nothing inside Floke can be bought. The build contains no billing library at all, which rules out purchases, subscriptions, paid hints and paid anything-else in one go. The consequence for you is that card details, billing addresses and order histories are not merely unshared but absent — there is no store of them to protect, not even the truncated digits a receipt would normally carry. Were the listing itself ever to be priced, the money would move between you, Google and your bank, and the paperwork would live with them.
Never tiedthe game→an advertising network
Floke shows no advertising of any kind. No ad SDK is present, no ad slot exists on any screen, no banner or interstitial can appear between webs, and nothing is disclosed to an advertising network because there is no network connection to disclose it over. You are not profiled, segmented or placed in an audience.
Never tiedthe game→an analytics or crash service
No analytics library and no crash reporter are embedded — not Firebase, not Crashlytics, not a counter of my own. Which webs people abandon, how long a session runs, how many hints get taken: facts I do not have and have decided not to acquire. If Floke stops unexpectedly I find out because somebody writes to me, which is slower and was the point.
Never tiedGoogle Play→your Google account
Downloading anything from Google Play means Google records the installation against your Play account. That processing is Google's own, under Google's privacy notice, with Google as controller in its own right — I am not a party to it, cannot switch it off and cannot see into it. It exists whether or not you ever open the game.
Ends at GoogleAndroid itself→Google
Depending on settings you chose when you set up the handset, Android may send Google diagnostic, usage and crash information about apps running on it, Floke included. This is the platform's thread, not the game's. It is governed by your device's privacy settings and by Google's notice, and both are reachable from Android Settings without going through me.
Ends at Googlethis page→Google Fonts
No cookie is set here, no analytics script runs, and there is no tracking pixel anywhere on the page. One request does leave, and it is this: the two typefaces are served by Google Fonts, so your browser calls Google for them and Google consequently sees the address it was called from. I neither receive that nor have any way to connect it to you, but a thread is a thread and it belongs on the list.
Ends at Googlethe Play Console→me
Google shows me a dashboard: how many installs and uninstalls, in which countries, on which Android versions and device models, and an average rating. It is aggregated and anonymous, assembled by Google from many people at once, and there is no view in it that resolves to one person. I cannot find you in it and could not look you up if I wanted to.
Reaches mea public review→me, with a name attached
Leave a review and four things become visible to me: whatever display name sits on your Play profile, the rating, the words, and when they were written — with a public reply box underneath. Of all fifteen threads this is the only one that arrives with a recognisable person at the far end, and you are the one who ties it. Untying is yours too, and mine not at all: edit or remove the review inside the Play Store and it goes. Treat it as a notice board, because that is what it is, and keep private matters for thread 15.
Reaches meyour e-mail→my mailbox
Write to me and I have your address and whatever you put in the message, for as long as the matter takes. It is kept to answer you and for nothing else: no list, no newsletter, no sharing with anyone. When the exchange is finished and there is no longer a reason to hold it, it is deleted rather than filed. The legal basis for that short holding is my legitimate interest in replying to people who write to me, under Article 6(1)(f).
Reaches meCounted up, and this is the whole of it — every one of the fifteen falls into exactly one of these four piles, and the figures below are generated from the list above rather than typed in by hand.
Which makes the short version easy to state: I hold no personal data about you unless you write to me or write a review. In the game, a web is solved when no thread crosses another. Here there is nothing to cross, because almost nothing is tied.
Norway is bound by the GDPR through the EEA Agreement, enacted domestically as personopplysningsloven (LOV-2018-06-15-38). Eight entitlements follow from it, and they belong to you regardless of anything written on this page. Below is each one together with what it would actually produce if you aimed it at me — which, fifteen threads later, is usually an empty envelope.
Pointed at Google the same eight have genuine force, because threads 10, 11 and 12 end in Google's hands and not in mine — use the privacy controls in your Google account, or Google's published contact route for data requests. Asking costs nothing, takes no prescribed form and gets an answer inside a month. Two caveats the Regulation itself provides for: where a request is so vague that I cannot establish whose data is meant, I am allowed to come back with a question first, and where one is manifestly excessive or simply repeated without end, I am allowed to say as much rather than answer it again.
Under personopplysningsloven § 5, a Norwegian child of 13 or over may give their own consent to an information society service. That threshold decides nothing here, for the plain reason that Floke asks no one of any age to agree to anything — consent is a lawful basis for processing, and threads 3 to 9 explain why there is none to be based on. The puzzle is not aimed at children, is not listed in a children's programme, and carries no content rated otherwise; it simply happens to be the sort of thing a nine-year-old can play without anybody learning that they did. The only way a child could reach me at all is thread 14 or thread 15, and should a message turn out to have come from one, it is deleted on sight rather than answered.
You are entitled to take it to a regulator, and nothing obliges you to warn me first — though if you would rather start with me, floke@frostaudio.garden is the address and the thread runs no further than my mailbox.
The Norwegian supervisory authority is Datatilsynet, at Postboks 458 Sentrum, 0105 Oslo, online at datatilsynet.no. Residents of other EEA states may lodge the same complaint with their own national authority, and a court action can be brought in the country where you are. One suggestion, offered seriously: every factual claim on this page is testable against the package Google serves you, so ask a regulator to check the manifest rather than to take my word for the manifest.
Thomas Arill Eriksen Frost
Controller · private individual
Tristilvegen 21
2008 Fjerdingby, Norway
floke@frostaudio.garden
Skriv gjerne på norsk — norsk eller engelsk går like bra.
Frost Audio is a publishing name with no registered legal form, so there is no organisation
number to quote and no company standing behind it. Whoever the Play listing names as developer and whoever is named on this tag
are one and the same man. No data protection officer has been
appointed; Article 37 does not require one here, and the address above reaches the only human involved.
Fifteen threads, four piles, and exactly one that carries a name — tied at your end, not mine. Any release that moves a thread from one pile to another gets this page rewritten first and uploaded second, with a new date beneath the title. Nothing has been superseded yet; version 1.0 is the only version there has been.