Privacy Policy

Nothing is transmitted

Likevekt wants nothing from you: no registration, no profile, no advertising, no measurement library riding along, no list that anyone joins. Five statements, and statements are easily made. A sixth can be confirmed without relying on the others — the published package declares no internet permission. An app receives from Android precisely the permissions its package requested; one that omitted the network cannot reach it, whatever its code contains. That declaration appears on the listing and can be read before you install.

What it keeps is your play: the grids behind you, the time each took, and the part-finished board you set aside. Android hands every app a private corner of storage and all of it stays in Likevekt's. Not a byte is duplicated onto any machine at this end. The consequence deserves saying flatly: since your play is held by you and by no one else, there exists no repository here that could be breached, no inventory that could be sold, and nothing that any demand addressed to us could extract.

Eleven clauses follow, in four parts. Together they deal with what the General Data Protection Regulation requires of a notice like this, and the last gives an address for objections.

Whose name stands behind it

The word controller is given by Article 4(7) to whoever determines the purposes a processing operation serves and the means of carrying it out. A company name belongs at the head of a document like this for that reason rather than in its closing lines. Strip the formality away and two undertakings remain: that nothing written below is untrue, and that a named person answers for whatever part of it proves to be.

No data protection officer has been appointed. The obligation to appoint one arises in three cases only: public authorities; operations whose central business is watching people systematically on a large scale; and large-scale processing of the special categories. One company shipping one puzzle that never connects fails every test by a wide margin, and installing an officer regardless would signal a safeguard that had nothing to do.

Everything stored, in full

Some memory is unavoidable, or every evening would open on the first grid again. This is the whole of it:

• Which grids are finished, listed by pack, so the level screen can show your position.
• Each grid's best time, since without one there is nothing to measure a better attempt against.
• The grid left unfinished — which cells hold a sun, which a moon, which are still blank, the undos remaining — so that an evening's reasoning survives the phone going into a pocket.
• What is left of the hint allowance.
• The choices on the tune screen — language, sound, the colour-blind symbol set, whether the quiet flag for a third-in-a-row is on, and the rest of the tune screen.

Now read that list for its silences. At no stage are you asked who you are. No field behaves like an address. The advertising identifier Android makes available is never looked at. Device characteristics are not combined into anything that could act as a fingerprint. And Likevekt issues itself no installation number, which is the omission the rest depend on: lacking one, nothing separates your copy from the ten-thousandth. Enclosing the whole of it, Android's own isolation prevents any other app on the phone from reading a byte.

Uninstalling takes all five entries with it. To keep the game but discard the record, the tune screen carries a reset, and Android's own "clear data" arrives at the same place.

Why no lawful basis is cited

Notices of this kind generally alternate: an item collected, the Article 6 ground that permits it, the next item. Here the alternation never completes, because no ground is named anywhere. The omission runs the full length of the page, and anybody who notices it is owed the argument rather than a shrug.

What a lawful basis answers is a single demand — produce your title to this. The demand assumes somebody holding something, and neither half is present. Everything clause 3 lists sits on equipment you own and we cannot reach, and it identifies no one: subtract identifiers that were never recorded and the residue is an account of one handset's evening with some balanced grids. The Regulation requires both halves at once, data that points at a person and a controller processing it. Remove the first and the second supports nothing.

Any argument lasts as long as its premise and no longer. The moment any of four things appears — somewhere to sign in, an advertisement, a library that measures, a place to pay — the premise is finished, and this text has to be written again and released in step with the version that introduced it, naming the ground for every item added. How to carry that out is set down in a comment at the foot of the file.

There is no cookie banner for a related reason. The rules in question govern anything placed on, or lifted from, a person's device over and above the needs of the service they asked for, and in practice that means a handful of carriers: an in-app browser view, a measuring pixel, a third party's tag. Not one of them is in Likevekt — and had one been slipped in, it would find nothing to report over. The Norwegian implementation therefore has no subject matter here at all.

One requested, the rest declined

The right-hand box is what the rest of this document rests on. Nothing can be sent without a route out and none was built, which means the destination of your data stops being something you have to take on trust and becomes a characteristic of the build, inspectable by anyone who troubles to look.

Decline any permission request that takes you by surprise, then send the build number to [email protected]. Exactly two possibilities exist. Either what is written here has drifted away from what was actually released, or the copy on your phone did not come from this company. Each needs clearing up without delay.

The store is a transaction of its own

The clauses above describe Likevekt in operation on your phone. Its arrival on the phone belongs to an earlier and separate transaction between you and Google, concluded before the game was ever launched. Whatever Google files about it — the install, subsequent updates, a star rating if you gave one — hangs off the account signed in at the time, under rules Google sets for its own marketplace. We can neither see into that record nor change a line of it.

What we see is the Play Console's aggregate view and no more: a total of installs, a rough geographic spread, crashes grouped by kind, one averaged rating. Nothing in it comes down to a single person. Your account's own contents — where it bills, what card is attached, which handsets it has signed into — stay firmly on Google's side, and any control over them is operated from within the account rather than from this page.

A caveat about the listing. Reviews go public the moment they are posted, under whatever name your account carries, and they stay on the page for every later visitor to read.

Nobody stands downstream

A task that is not being carried out cannot be subcontracted. Work down the list of parties such a notice ordinarily has to identify and each line is empty: there is no server storing anything for the game, no analytics property trained on it, no crash reporter drawing from it, no ad exchange connected to it, no mail service keeping addresses for it, and no payment processor involved. These suppliers were never weighed up and rejected — the work they exist to do does not arise here. Asked by Article 13(1)(e) for the categories of recipient, the truthful response is to leave the entry blank.

Clause 6 comes first on purpose. The store marks where our responsibility stops, and that boundary belongs in the open rather than hidden further down: the dealing happens on Google's systems, under an agreement between Google and you, and it has concluded before the game is launched for the first time.

Nothing crosses a frontier

Transfers of personal data out of the European Economic Area are the subject of Chapter V, and a considerable set of instruments has grown around it — decisions declaring a country's protection adequate, the standard clauses written for contracts, corporate rules made binding across a group, and the limited exceptions Article 49 provides for everything the others miss.

All of it presupposes a transfer, and no transfer occurs. The minutes a grid took you were logged by the handset doing the timing and went no further — no copy in Norway, none in Ireland, none on any machine anywhere. Chapter V's question simply never arises.

Keeping this apart from clause 7 is deliberate, since the two are routinely merged and ought not to be. The first says no other party receives your data; this one says it does not travel. One fact makes both true today, but they remain separate undertakings, and whichever fails first will fail on its own account.

The term of it, and the audience

Duration. A figure in months appears in clauses like this because the data is usually sitting with a party the reader has no hold over. That is not the arrangement; you are the only party holding anything, which makes a figure pointless and a condition the honest answer. It lives as long as you want it to and ends the moment you decide otherwise, whether by the reset or by deleting the app. No nightly duplicate is made. No earlier version is set aside. We maintain nothing capable of preserving a trace against your wishes. And nothing decays with age — a time sitting undisturbed for three years is the same time, on the same device, read by you and no one else.

Age. Likevekt carries a general-audience rating, and placing suns and moons until a grid comes level is about as innocuous an hour as a child could spend. The familiar checklist has four entries — ads pointed at children, spending within reach of a careless tap, a channel by which strangers might make contact, and content contributed by other users. Each gets a no here, not because something was disabled but because none of the four was ever written into the app. Article 8 would also be expected to bite, since it marks the age under which a parent must back a child's agreement to an online service. Nothing gives it purchase: no agreement is collected from any player, of any age. Norway's figure is 13, and putting it in writing while it governs nothing ensures it is on the page already should advertising ever make it operative.

Eight rights, and what each produces

Every one of the eight survives intact. What is odd is that the handset has already disposed of most of them: it holds the entirety of what exists and will show it to you on demand. A formal request could only ever conclude in a single way — a note stating that we have no file on you — and a process with one available ending is ceremony dressed as safeguarding. The table below gives that ending straight.

No fee arises, no form has to be filled, and nobody will ask you to prove your identity. Proof of identity is what keeps one person's material from being released to another; with no material held it secures nothing, and demanding papers in order to show that we hold none would be a small comedy.

Where to take a disagreement

Write to [email protected]. It is a single inbox, opened by the person who drafted this, and nothing sits in the way. Use it to invoke a right, to dispute a line above, to report a permission dialog clause 5 does not account for, or out of plain curiosity about how something works.

Skriv gjerne på norsk — adressen er den samme, og du får norsk svar.

Personopplysningsloven is the statute through which the General Data Protection Regulation applies in Norway, and the body supervising its application to companies here is Datatilsynet. Post reaches it at Postboks 458 Sentrum, 0105 Oslo, although datatilsynet.no is a shorter road. You are not obliged to use Oslo at all. Under Article 77 a complaint may equally go to the authority for the country you live in, the country you work in, or the country where you consider the breach to have happened; three forums, freely chosen, with no reason required. That freedom cannot be reduced by anything written here, and a clause purporting to reduce it would be ineffective. Approaching us first is advice and not a condition — a complaint already running at Datatilsynet and a letter in this inbox coexist quite comfortably.

There is a version beneath the title, and it moves whenever anything above is altered. One inflexible rule governs when an alteration may ship. If the rewrite exists because the software has taken up a new behaviour — retaining something it did not retain, involving a party it did not involve, sending traffic over a border, serving a purpose it did not serve — the amended text is published in the same release and in no later one. An explanation never trails the thing it explains onto a handset. The useful upshot is that a glance at the version answers whether these words were written for your build. Superseded versions stay on file and go out to anyone requesting one.