Privacy Policy

Nothing is carried off the bench

Treblokk wants nothing from you. No registration, no profile, no advertising slot, no measurement library riding along, no list anybody joins. Five promises, and promises are cheap. The sixth is the one you can verify without anybody's help: the shipped package requests no internet permission. Android issues an app only the permissions its package declared, so one that never asked for the network simply has none, whatever its code might fancy doing. Anyone can read that declaration on the store page before they ever press install.

Your play is kept, of course — high score, lines cleared, best combo, and the board you abandoned mid-game exactly as you abandoned it. Every app on Android is given a storage area of its own, walled off from the rest, and all of that lives inside Treblokk's. Not one byte is copied to a machine at this end. The result is worth saying bluntly: nothing of your play is in anybody's keeping but your own, so there is no store here to breach, nothing to sell on, and nothing that could be handed over if somebody came asking.

Ten planks follow. Between them they cover what the General Data Protection Regulation expects of a notice like this one, and the last gives you somewhere to write if you disagree with any of it.

Whose name is on it

The label controller belongs, by Article 4(7), to whoever fixes both the ends a processing operation pursues and the means of pursuing them — hence a company name at the very top of a page like this instead of in the small print. Behind the formality are two undertakings: that nothing stated below is false, and that somebody with a name takes responsibility if any of it proves to be.

No data protection officer is appointed, and the absence is a conclusion rather than an oversight. Three circumstances make the appointment compulsory — a public authority, systematic large-scale monitoring as a core activity, large-scale handling of special-category data. One small company shipping one offline puzzle meets none of them by a very wide margin. Naming somebody anyway would imply a safeguard where there is nothing to safeguard.

Everything the game writes down

Some memory is unavoidable, or a score would never survive the night. This is the complete list:

• Your high score, along with total lines cleared and your best combo, so there is something to beat.
• The game in progress — which cells are filled, the three shapes currently in the tray, the running score — so putting the phone down costs you nothing.
• Your settings — sound, haptics, and the handful of options on the setup screen.

Three items. Now read the list for its silences. You are never asked a name. Nothing resembling an address goes anywhere. The advertising identifier Android exposes is left unread. Device characteristics are not swept together into any combination capable of acting as a fingerprint. And Treblokk never mints itself an installation number, which is the omission holding up all the others: lacking one, nothing at this end or anywhere else can tell your copy from the ten-thousandth. Around the whole lot, Android keeps that storage sealed against every other app on the handset.

Delete the game and the three items go with it. To empty them while keeping the game, the setup screen holds a reset, and Android offers the same outcome under "clear data".

Why no lawful basis appears

Notices of this kind usually advance two steps at a time: something gathered, the Article 6 basis for gathering it, then the next thing. Not one basis is quoted anywhere on this page, and a reader who notices every pair missing its second half is owed the argument rather than the silence.

A lawful basis exists to answer one challenge: by what right is this in your hands? That challenge needs somebody holding something, and here nobody holds anything. The three items in plank 03 live on equipment belonging to you, out of reach from this end, and they identify nobody: strip away identifiers that were never recorded in the first place, and all that remains is a record of one phone's afternoon with some wooden blocks. Two things have to be true at once before the Regulation applies: that personal data exists, and that a controller is processing it. Remove the first and nothing supports the second.

Any argument survives only while its premise does. Bolt on a login, an advert, a measurement library or a shop, and the premise collapses on the spot — and from that moment this text must be redrafted and go out alongside the release responsible, every addition accompanied by the basis that permits it. The working notes for doing that are kept in a comment at the end of this file.

There is no cookie banner either, by adjacent reasoning. Rules of that family bite on storing or retrieving something on a person's own equipment beyond what the service they asked for genuinely requires, and they generally arrive by embedded web view, measurement pixel or somebody else's tag. None of the three is in this game, and none would have a line out to report over if it were — which leaves the Norwegian implementation of those rules with nothing to govern here.

One asked for, the rest left alone

The right-hand box carries this whole document. No route out means no transmission, so whether your data goes anywhere stops depending on your trust in us and becomes a fact about the package itself — something an outsider can confirm, with no help from us at all.

Should some unexpected prompt ever turn up, turn it down and let us know the build number at kloss@valley.lat. There are only two possible explanations — the text here has fallen out of step with the build, or the copy you installed was not published by us. Either one deserves to be chased down straight away, not least for everybody who installs after you.

The store is a separate transaction

Everything so far concerns Treblokk once it is running on your phone. Acquiring it was a separate affair, concluded beforehand between you and Google. The install, every update that follows and any rating you leave go into Google's records under the account you happened to be signed into, governed by the terms Google writes for its own store. That ledger is neither visible to us nor ours to amend.

All that arrives at this end is the Play Console's summary view, pitched entirely at the level of totals — how many copies went out, roughly which countries, faults bundled by type, one averaged rating. It resolves to no individual at any point. The details sitting behind your Google account — where it bills to, what card is on it, which phones have used it — never cross over, and Google provides its own controls over them, operated from within the account. That is the only place such a question can be put.

Worth a word of warning about the listing: the instant a review is submitted it is on public view, carrying whichever name the account shows, and it stays there for every visitor who follows.

Nobody stands downstream

Work that is not being done cannot be given to a contractor. No server keeps anything for this game. No analytics property is trained on it. No crash service listens to it. No advertising exchange is wired in. No mailing platform holds a list for it. No payment agent has been retained. These are not suppliers that were weighed up and turned away — the task they would have performed never came into existence. Where Article 13(1)(e) asks for the categories of recipient, the truthful entry is none.

Export abroad runs aground on the same fact. An adequacy decision, the model contract clauses, the tightly drawn exceptions of Article 49 — the whole machinery presupposes that something is in transit. Nothing is. Your score was written to the phone that produced it, and no copy of it has ever existed elsewhere.

Plank 06 is placed ahead of this one on purpose, to mark where responsibility here stops rather than to bury the point: the whole of that dealing takes place on Google's machines, governed by the contract Google holds with you, and is complete before anyone launches the game.

The span of it, and who it is meant for

Duration. Clauses like this normally quote a period in months, because the data is sitting with a party the reader cannot order about. Here it is sitting with you, which makes a number meaningless and a condition the only truthful answer: it lasts precisely as long as you want it to, and both the reset and a plain uninstall finish it the moment you reach for them. Nothing is mirrored anywhere overnight, no earlier snapshot is filed away, and no arrangement exists at this end by which some remainder could outlast your choice. Nor does age wear it down — a high score left alone for three years is still a high score, on your phone, seen by you and by nobody else.

Age. Treblokk carries a general-audience rating, and sliding wooden blocks into a grid is about as harmless an hour as a child could have. Parents generally check for the same four hazards: ads pointed at children, a purchase a careless finger can reach, any opening through which an outsider might make contact, and content other users have uploaded. None of the four exists in this game. Article 8 would normally come into play too, marking the threshold below which a child's consent to an online service needs a parent behind it. Nothing gives it purchase: consent is collected from no one here, at any age. The Norwegian line sits at 13, and recording it now — while it changes nothing — guarantees it is already written down should advertising ever make it matter.

Eight rights, and what each actually yields

All eight stand at full strength. Only the venue is unusual: for most of them the phone in your hand has already settled the matter, and no correspondence need happen at all. Marching a request through a formal process that can finish in exactly one way — a note confirming we hold nothing of yours — would be ritual rather than protection, so what follows states the genuine result in each case.

Nothing costs anything, no form exists, and your identity will not be checked at any point. Identity checks are there to stop a controller releasing one person's file to another; with no file at this end such a check defends nothing, and running one would mean asking you for a document in the middle of a page insisting nothing is ever asked of you.

Arguing with any of this

Write, if you would like to, to kloss@valley.lat. One address and nothing routing behind it — write to claim a right, to challenge a line above, to report a permission dialog that plank 05 does not cover, or simply because you want to know how part of it functions.

Norsk går helt fint — bruk samme adresse, så svarer vi på norsk.

Personopplysningsloven is the act that brings the General Data Protection Regulation into force in Norway, and a company seated here answers to Datatilsynet under it. Letters go to Postboks 458 Sentrum, 0105 Oslo, and the fastest start is datatilsynet.no. Note, though, that Article 77 gives you three places to take a complaint, not one: where you ordinarily live, where you are employed, or wherever you consider the problem to have arisen. The choice is entirely yours and needs no justification. Nothing on this page may trim that list, and a clause attempting it would simply be void. Approaching us first is a suggestion, never a prerequisite — a case already open with Datatilsynet coexists quite happily with a correspondence here.

A version stands under the title and moves whenever anything above it is edited. A single rule fixes the timing of those edits and is never relaxed: if a revision exists because the software has started doing something new — retaining a fresh item, admitting a fresh party, sending traffic over a border, serving a fresh purpose — then the amended text forms part of that very release. A behaviour will not be on handsets in October with its explanation arriving in November. Reading the version line is therefore a two-second way to find out whether these words were written for the build you have installed. Older versions are archived and will be sent on request.