Nothing leaves the handset
Glattis has no sign-up, no profile, no advertising, no analytics and no mailing list. Five claims, and any company can make them. The sixth is the one you can check without us: the published package requests no internet permission. Android hands an app only the permissions its package asked for, so an app that never asked cannot reach the network no matter what its code would like — and the full permission list is shown on the store page before you install.
The game does remember your play. Levels finished, your best slide counts, the board you abandoned halfway. Android gives every app a private corner of storage, and all of that stays in Glattis's corner. None of it is copied to a machine belonging to us. Which gives a blunt corollary: your play is not in our custody, so no breach of ours could expose it, no buyer could be sold it, and no demand addressed to us could produce it.
Ten sections follow. Between them they deal with the matters the General Data Protection Regulation requires such a notice to deal with. The last one says where to write if you disagree with any of them.
The company behind the page
ControllerLight Pear AS
Formaksjeselskap, registered in Norway
Signs for itYuan Yu Phoon
Registered atCamilla Colletts vei 18, 0258 Oslo, Norway
This pageis@lightpear.online
AppGlattis — com.frostbane.glattis
Article 4(7) attaches the word controller to whoever settles what a processing operation is for and how it gets done. That is why a company name heads a page like this. Shorn of formality it commits us to two things: the statements below are true, and a named person carries it if one of them is not.
There is no data protection officer, and we would rather explain that than leave a blank. The appointment becomes mandatory in exactly three cases — a public authority, large-scale regular monitoring as a core activity, or large-scale processing of the special categories. One small company shipping one offline game sits nowhere near any of them. Naming somebody anyway would dress the page in a protection that protects nothing.
Everything the game writes down
A puzzle game has to remember something, or every session starts at level one. This is the lot:
- Levels you have completed, pack by pack, so the menu can mark your position in a run.
- Your fewest slides on each finished level, with crystals collected, so the game can tell when you have done better.
- The board you are part-way through — where the stone is sitting, which crystals you already picked up, the undo steps available — so putting the phone down does not throw away the route you worked out.
- Hints remaining from the limited allowance.
- Your settings — language, glide speed, sound, arrow pads, whether the track is drawn, reduced motion.
Then read the list for what it leaves out. You are asked for no name. Nothing that counts as an address is written anywhere. The advertising identifier Android exposes goes untouched. Device properties are not swept together into anything that could work as a fingerprint. And Glattis gives itself no installation number, which is the omission carrying all the others: without one there is no mechanism, ours or anybody else's, for telling your copy apart from the next person's. The operating system seals that storage off from every other app besides.
Delete the game and it all goes. Keep the game and empty it instead using the reset in the settings screen, or Android's own "clear data" control.
Why no legal basis is given
Notices of this kind normally alternate: a thing collected, the Article 6 basis for collecting it, the next thing. Not one basis appears anywhere on this page, and a reader who spots the pattern breaking deserves the reasoning rather than silence.
A legal basis answers one question — by what right is this in your possession? The question needs a possessor and a possession. Neither exists here. Section 03's list sits on hardware you own, beyond our reach, and it identifies nobody: take away identifiers that were never present, and what is left is a note of how one handset got on with some frozen puzzles. The Regulation engages when there is personal data and a controller processing it. Remove the first and the second has nothing to stand on.
That reasoning survives only as long as its premise. Add a sign-in, an advert, a measurement library or a shop, and the premise is gone the same day — at which point this document must be rewritten and shipped in the release that makes the change, every new item arriving with its basis named. A comment at the very bottom of this file holds the working instructions for that.
No cookie banner appears either, by related logic. Those rules apply to writing to or reading from a person's own device beyond what the requested service needs, and they usually arrive by embedded web view, measurement pixel or third-party tag. Glattis contains none of the three, and has no line out they could report over in any case, so the Norwegian implementation of those rules finds nothing here to govern.
One granted, everything else refused
Granted
Vibration — the short knock when the stone lands against a rock, and only while that switch stays on. Android grants it without a prompt, and a vibration motor has nothing to say about whoever is holding the phone.
Refused
The network, first and most importantly — and following from it, the camera, the microphone, positioning, contacts, any file outside the app's own folder, phone state and notifications.
That second box does the structural work for everything written here. An app with no route out cannot send anything anywhere, so a claim about destinations ceases to depend on our good faith and turns into a characteristic of the build itself — checkable by a stranger, without our cooperation.
If a prompt you were not expecting ever appears, refuse it and send the build number to is@lightpear.online. Exactly two explanations are possible: the text here is out of step with the build, or your copy of Glattis was not published by us. Each one needs running down quickly, for everybody else's sake as much as yours.
Google Play is a separate matter
Everything above concerns Glattis once it is running. Obtaining it was a different transaction, settled earlier, between you and Google. Google notes the download, every subsequent update, and any star rating you give, filing all of it under whichever account was signed in at the time, on terms it sets for its own marketplace. None of that is visible to us and none of it is ours to alter.
Our side of it is the Play Console's summary, which only ever deals in aggregates: copies delivered, a rough country spread, crashes grouped by type, an averaged rating. None of it narrows to a person. What hangs off your Google account never crosses to us: the billing details, the payment method, the list of phones it has signed into. Google's own controls over those records live inside the account itself, not on this page. A question of that sort has to be taken there; we could not answer it even if asked.
One warning about the listing itself. A review becomes public the instant it is posted, under whatever name your account shows, and stays visible to everyone who looks afterwards.
There is no one downstream
Work nobody is doing cannot be subcontracted. There is no server holding data for this game, no analytics property pointed at it, no crash-reporting service listening, no ad exchange connected, no mailing platform keeping a list on its behalf, and no payment agent engaged. We did not evaluate these suppliers and turn them away — the work they do simply does not arise. Where Article 13(1)(e) asks for categories of recipient, an honest answer leaves the field blank.
Transfer abroad closes on the same fact. The entire apparatus for moving data lawfully over a border — adequacy decisions, the standard contractual clauses, the narrow derogations of Article 49 — assumes something is being moved. Nothing is. A slide count produced on your handset was saved to that handset, and no copy of it has existed anywhere since.
The ordering is deliberate: section 06 comes first so the store is visible as the boundary of what we answer for, not tucked away behind it. That exchange runs on Google's infrastructure, under the agreement Google holds with you, and concludes before Glattis is launched for the first time.
How long it lasts, and who it is for
Duration. A figure in months usually appears in this clause because whoever is doing the keeping is beyond the reader's authority. Here the keeping is yours, so a figure would be dishonest and a condition is the truthful answer: the data survives for exactly as long as you allow it to, and both the settings reset and a plain uninstall end it the instant you use them. No overnight job copies it anywhere. No archive preserves a previous state. There exists no system of ours in which some remnant could outlast what you decided.
Age. Glattis carries a general-audience rating, and sending a stone skidding across frozen boards is a perfectly reasonable thing for a child to do for twenty minutes. The four things a parent tends to check for are ads directed at children, purchases a clumsy finger can reach, any route by which a stranger could make contact, and user-submitted content. Not one of them was ever built into this game. Article 8 ought to be relevant as well, setting as it does the age at which a child can agree to an online service without a parent's backing. It finds no purchase here, for the simple reason that no player, child or adult, is ever asked to agree to anything. In Norway the threshold is 13. Writing the number down while it is irrelevant means it will already be here on the day advertising makes it relevant.
Eight rights, each with its real answer
None of the eight is narrowed here. The difference lies in where you exercise them: almost every one is already settled by the phone in front of you, and no correspondence is needed. Routing a request through a formal process that could only ever conclude with us writing "we have no file on you" would be pure ceremony, so this table reports what each right genuinely produces.
Access · 15The reply would be a two-line note confirming we hold no file on you. What the game itself remembers is printed on the level list, open to you at any moment.
Rectification · 16Only records can be inaccurate, and none are kept. If a saved slide count does you less than justice, the remedy is to finish that board in fewer slides.
Erasure · 17Instant, and under your control alone: use the reset, or uninstall. Because no request is made to us, none can be turned down, left waiting, or returned on the final day of the statutory month.
Restriction · 18It exists to freeze processing while a dispute runs. No processing of yours is under way, so there is nothing available to freeze.
Portability · 20Its subject is material a person gave to a controller, so that they may move it on. Nothing was ever given, and the game's own memory is a file sitting on equipment that belongs to you.
Objection · 21There must be some activity to object against. The unanswerable form of the right targets direct marketing, and nothing marketing-shaped is sent from here at all.
Consent · 7(3)You are never asked to agree to anything, and no part of the game leans on your having agreed. Withdrawal needs a live permission, and none exists.
Automated decisions · 22Working out where a sliding stone halts is a check of what sits in the next cell. It stops a stone on a drawing; it concludes nothing whatever about you.
Nothing is charged, nothing has to be filled in, and no proof of identity is requested. Identity checks are there to keep a controller from giving one person's file to another; since no file exists on this side, such a check defends nothing — and running one would have us asking you for papers in the middle of a page insisting we ask for nothing.
Arguing with any of the above
Write first, if you like, to is@lightpear.online. One address, with nothing routing behind it. Write to claim a right, to dispute a sentence on this page, to report a permission dialog that section 05 cannot explain, or merely to ask how some part of it works.
Du kan gjerne skrive på norsk — samme adresse, og du får svar på norsk.
A company seated in Norway comes under the General Data Protection Regulation through personopplysningsloven, the act carrying it into Norwegian law, and Datatilsynet supervises the result. Its postal address is Postboks 458 Sentrum, 0105 Oslo; the easiest starting point is datatilsynet.no. Oslo is not your only option. Article 77 offers three venues — your country of residence, your place of work, or the location you believe the breach occurred — and the choice between them is yours alone, on whatever grounds suit you. No wording on this page may narrow those three, and any clause pretending to would simply have no effect. Nor is writing to us a precondition: a file already open with Datatilsynet sits perfectly comfortably alongside an exchange of letters here.
A version number sits under the title and moves whenever anything above it changes. One rule governs the timing, and we hold to it: when the reason for a revision is that the software now behaves differently — a category newly retained, another party let into the chain, data beginning to cross a border, a purpose added — the revised wording ships with that release and not at some later convenience. We will not ship a change on Monday and describe it a fortnight later. Which makes the version line a quick way to ask whether these words were drafted for the build you are actually running. Superseded versions are archived, and one can be sent to you on request.