Nothing leaves the table
Brikker asks you for nothing at all. No registration, no profile, no advertising, no measurement library travelling along with it, no list anyone is put on. Five assurances, and assurances cost nothing to give. The sixth is the one open to inspection without taking anybody's word: the published package requests no internet permission. Android issues an app precisely the permissions its package declared, so an app that never asked for the network has none of it, whatever its code might wish. That declaration appears on the store page, readable before you install.
Your play is remembered, naturally — which figures you have solved, your best time on each, the puzzle you abandoned half-assembled. Android gives every app a private corner of storage and the whole of that sits in Brikker's. Nothing is copied to a machine at this end. So the plain consequence: your play belongs to you and to nobody else, which means there is no store here to be breached, nothing to sell on, and nothing that could be produced if someone came asking for it.
Ten pieces follow. Between them they cover what the General Data Protection Regulation asks a notice of this kind to cover, and the last one names the place to write if you want to argue with any of it.
Whose name is on this
ControllerPearlconvert AS
Formaksjeselskap, registered in Norway
Signs for itIngar Melby
Registered atLysaker torg 45, 1366 Lysaker, Norway
This pagebrikke@pearlconvert.space
AppBrikker — com.formbrikk.brikker
The word controller belongs, under Article 4(7), to whoever fixes both the purposes a processing operation serves and the means by which it is carried out. That is why a company name sits at the top of a page like this rather than in its small print. Behind the formality stand two undertakings: that nothing written below is false, and that a named person carries it if any of it turns out to be.
There is no data protection officer, and the absence is reasoned rather than careless. The appointment becomes compulsory in exactly three circumstances — a public authority; systematic monitoring on a large scale as the core activity; large-scale handling of the special categories. A small company shipping one offline puzzle falls short of all three by an enormous distance. Naming somebody regardless would imply a protection where there is nothing whatever to protect.
The complete inventory
A puzzle game has to remember something, or every evening would begin at the first figure. Here is all of it:
- Which figures you have completed, pack by pack, so the figure list can show how far along you are.
- Your best time on each completed figure, so a quicker attempt can be recognised as one.
- The figure you are part-way through — where each of the seven pieces is sitting, how it is turned, whether it has been flipped — so putting the phone down does not throw away what you had worked out.
- Hints remaining out of the allowance.
- Your options — language, sound, and the handful of switches on the options screen.
Now read the list for what is absent from it. You are never asked a name. No address, postal or otherwise, is written down at any point. Android's advertising identifier is simply never consulted. Device characteristics are not gathered into any combination that would serve as a fingerprint. And Brikker issues itself no installation number, which is the omission carrying all the rest: absent such a number, neither we nor anyone else possesses a way of separating your copy from the next person's. Over and above that, the operating system keeps the storage closed to every other app installed.
Remove the game and the inventory goes with it. To empty it and keep the game, the options screen holds a reset, and Android offers the same result under "clear data".
Why no lawful basis is cited
Notices of this shape usually travel in pairs: a thing collected, the Article 6 basis permitting it, then the next thing. You will search this page in vain for a single one, and anyone who spots that the second half of each pair is simply absent is entitled to the reasoning behind it.
A lawful basis answers a single demand — show your title to this. The demand presupposes somebody holding something, and here nobody holds anything. What piece 03 lists rests on hardware you own and nobody at this end can reach, and it singles out no one: take away identifiers that were never recorded, and the residue is a note of how one handset got on with seven flat shapes. Two conditions must hold at once for the Regulation to engage — personal data, and a controller processing it. Remove the first and nothing holds the second up.
Every argument lasts exactly as long as its premise. Introduce a login, an advert, a telemetry library or a shop, and the premise disappears within the hour — and from that moment this text must be redrafted and published in the release that causes the change, each addition arriving with the basis that permits it. The working notes for doing so are kept in a comment at the foot of this file.
Nor is there a cookie banner, by closely related reasoning. Rules of that family engage on storing or reading something on a person's own equipment beyond what the service they requested genuinely needs, and the vehicles are nearly always one of three: a web view embedded in the app, a pixel placed for measurement, or a tag belonging to a third party. Brikker contains no such thing, and were one smuggled in it would find no connection over which to report. The Norwegian rules on this therefore have no subject matter here.
One requested, the remainder declined
Requested
Vibration, for the small click as a piece snaps into position, and only while that switch is left on. No prompt is shown, because there is nothing to ask about: a vibration motor discloses nothing concerning whoever is holding the phone.
Declined
First and foremost the network — and then, in its train, every one of the camera, microphone, location, contacts, storage beyond this app's own folder, telephony state and notifications.
That right-hand column carries this entire document. Sending anything requires a way out, and none was built — which lifts the question of your data's whereabouts off the ground of trusting us and sets it on the package itself, where an outsider can settle it unaided.
Should a prompt you were not expecting ever appear, decline it and send the build number to brikke@pearlconvert.space. Exactly two explanations are available: this page has fallen out of step with the build, or your copy of Brikker was not published here. Either deserves chasing down at once, not least for whoever installs it next.
The store is its own arrangement
Everything so far concerns Brikker once it is running on your handset. Obtaining it was a separate matter, settled beforehand between you and Google. The download, every update afterwards and any rating you leave go into Google's records against whichever account was signed in at the time, under the terms Google writes for its own marketplace. That ledger is not visible here and not ours to alter.
The Play Console hands this end a summary and nothing finer: a count of installs, a scattering by country, bug reports collapsed into groups, an average star rating. At no point does it narrow to a person. Your Google account's own contents — the billing address, the stored card, the roll of devices it has signed into — stay where they are, managed through controls Google provides inside the account itself. Questions about them belong there and can be settled nowhere else.
A word of warning about the listing itself: the instant a review is posted it is public, carrying whichever name the account displays, and it stays visible to every visitor who comes afterwards.
There is nobody downstream
Work nobody is doing cannot be handed to a contractor. Name the usual parties and each is absent: not a server storing anything for the game, not an analytics property watching it, not a crash reporter collecting from it, not an ad exchange plugged into it, not a mailing service holding anyone's address on its behalf, and not a payment agent of any kind. These are not suppliers that were considered and rejected — the task they would perform simply never came into being. Where Article 13(1)(e) asks for the categories of recipient, an honest answer leaves the line empty.
The question of sending data out of the EEA dissolves for the identical reason. Adequacy findings, model clauses, the narrow permissions of Article 49 — every one of those instruments is built around a shipment, and there is no shipment. The minute and a half you took over a figure was recorded on the phone that timed it, and has lived nowhere else since.
Piece 06 stands ahead of this one deliberately, to mark where responsibility at this end finishes rather than to bury the point: the whole of that dealing runs on Google's systems, under the agreement Google holds with you, and is over before anyone opens the game for the first time.
The span of it, and who it is for
Duration. Clauses like this usually quote a period in months, because the data is lodged with a party the reader cannot instruct. In this case it is lodged with you, so quoting months would be theatre and the truthful answer is conditional: it endures for precisely as long as you let it, and either the reset or an ordinary uninstall ends it the second you choose. There is no nightly mirror, no snapshot held back, and no mechanism at this end through which a fragment could survive your decision. Nor does mere time erode it: a best time left alone for three years remains a best time, sitting on your phone, read by you alone.
Age. Brikker carries a general-audience rating, and fitting seven wooden shapes into a silhouette is about as harmless an hour as a child could have. The checklist a parent runs through is familiar enough — are there ads aimed at the child, is there anything buyable a stray finger could trigger, can a stranger get a message through, is there material posted by other users? Brikker answers no four times over, because none of those things was built. Article 8, which sets the age below which a parent's authority is needed for a child to agree to an online service, would normally matter too; it has nothing to grip, since agreement is requested of no one here whatever their age. Norway puts that age at 13. The number is written down now, while it is inert, so that it is already on the page if advertising ever brings it to life.
Eight rights, with their real outcomes
Nothing here cuts any of the eight down. What is unusual is where they get exercised. For most of them the answer is already in your hand — the figure list, the reset, the options screen — and no letter has to travel in either direction. A request routed through a formal procedure could only ever arrive at one destination, a reply stating that no file on you exists, which is a performance rather than a safeguard. The table gives the destination directly.
Access · 15A two-line reply confirming there is nothing to disclose. The figure list already shows everything the game retains, and it needs nobody's permission to open.
Rectification · 16Wrongness belongs to records; none are kept. Should a stored time understate you, beat it.
Erasure · 17Yours outright and immediate — reset, or uninstall. Since nothing is asked of us, nothing of yours waits in a queue or comes back refused a month later.
Restriction · 18Designed to halt an operation during a dispute. No operation on your data is under way, so the halt would apply to nothing.
Portability · 20Concerns what a person surrendered to a controller, so they can take it with them. You surrendered nothing, and the game's record is a file on equipment you already own.
Objection · 21There has to be an activity in view to object to. Its unrefusable branch deals with direct marketing, and none is dispatched from here.
Consent · 7(3)No agreement is requested anywhere, and nothing in the game rests on having been given one. Withdrawal presupposes a permission that is live; there is none.
Automated decisions · 22Checking a placement means comparing one outline with another. The verdict concerns a shape on a table, never the person moving it.
No fee is charged, no form has to be completed, and you will not be asked to prove who you are. Proof of identity exists so that one person's file is not released to somebody else; where no file exists it guards nothing, and demanding a document to establish that nothing is held would be a small absurdity.
Taking issue with any of this
The address is brikke@pearlconvert.space, and there is only the one, with no sorting machinery behind it. Anything belongs there: exercising a right, disputing a sentence on this page, reporting a permission request piece 05 has no explanation for, or plain curiosity about how some part of it operates.
Du må gjerne skrive på norsk. Samme adresse, og du får norsk svar tilbake.
Supervision of a Norwegian company falls to Datatilsynet, acting under personopplysningsloven — the statute through which the General Data Protection Regulation took effect in this country. Its postal address is Postboks 458 Sentrum, 0105 Oslo; in practice datatilsynet.no is the easier door. Worth knowing: Article 77 opens three of them, not one. A complaint may go to the supervisory authority of the country you live in, of the country you work in, or of the place where you believe the infringement happened, and you need give no reason for preferring one. That choice is beyond this page's power to narrow, and any clause claiming otherwise is simply unenforceable. Coming to us first is advice, not a step you are obliged to take: a file already open in Oslo and a letter arriving here can run side by side without difficulty.
Beneath the title there is a version, and it advances on any edit above it. The timing of such edits obeys one unbroken rule. Where the trigger for a rewrite is a change in the software itself — a new thing kept, a new party involved, traffic crossing a frontier for the first time, a purpose added — the rewritten page ships as part of that release and not of any later one. We will not let a new behaviour sit on phones for weeks with its account of itself still pending. Which turns the version line into a quick check: were these sentences composed for the build you are running? Superseded editions are kept, and we will send one over if you ask.