Privacy Policy

Nothing is poured out of the handset

Kolbe asks you for nothing: no registration, no profile, no advertising, no measurement library, no mailing list. Five assurances, and assurances come cheap. The sixth is the one that can be checked without taking anyone's word for it — the published package asks for no internet permission. Android grants an app only the permissions written into its package, so an app that never asked for the network has no network, whatever ambitions its code might harbour. The permission list is printed on the store page before installation.

Your play is remembered, naturally. Levels completed, the pour counts you managed, the half-sorted shelf you walked away from. Android reserves each app a private area of storage and every bit of that lives in Kolbe's. Nothing is duplicated to any machine belonging here. Which produces one blunt result: none of your play is in anyone's custody but yours, so there is nothing on this side to leak, nothing to sell and nothing to surrender to a request.

Eleven bays follow. Together they address what the General Data Protection Regulation requires a notice of this kind to address, and the last gives the address for disputing any of it.

Who stands behind this page

Stone Bruzs is a publishing name, not a staffed organisation, so the controller named here is a person rather than a company. Under Article 4(7) the title lands on whoever decides the ends a processing operation serves and the machinery used to reach them, and here it deliberately lands on an individual: the statements below are either true or they are somebody's to answer for, and vagueness about which would defeat the purpose of writing them down.

No data protection officer is appointed, and that is a conclusion worth showing rather than a blank to notice. Three situations make the appointment compulsory: being a public authority; running systematic monitoring at scale as the main business; handling special-category data at scale. One offline puzzle from one person falls short of all three by an enormous margin. Naming somebody regardless would suggest a layer of protection that protects precisely nothing.

The full contents of the cupboard

Some memory is unavoidable, or every session would restart at the first shelf. This is all of it:

• Levels you have sorted, by pack, so the level screen can mark your position.
• Your fewest pours on each sorted level, with the stars earned, so a neater run can be recognised as one.
• The shelf you are part-way through — what sits in each flask, how far you have got, the undos you still have in hand — so setting the phone aside costs you none of the thinking you had done.
• Hints left out of the allowance.
• Your preferences — colour-blind shades, optional patterns, sound, reduced motion.

Now notice the silences in that list. No name is sought. Nothing that functions as an address is recorded anywhere. The advertising identifier Android exposes is never consulted. Device characteristics are not collected into any combination that would work as a fingerprint. And Kolbe issues itself no installation number — the omission that holds the others up, because without one no mechanism exists, here or anywhere, for distinguishing your copy from somebody else's. Around all of it, Android keeps that storage closed to every other app on the device.

Removing the game removes the lot. To empty it while keeping the game, there is a reset in the settings screen, and Android provides an equivalent under "clear data".

Why no lawful basis is quoted

Notices of this shape normally proceed in couples: here is something gathered, here is the Article 6 basis for gathering it, here is the next thing. On this page no basis appears at all, and a reader who spots the second half of every couple missing is owed the argument rather than the silence.

Every lawful basis is a reply to a single demand: show your title to this. A demand of that shape presupposes somebody holding something, and here nobody holds anything. What bay 03 lists sits on hardware you own and nobody else can reach, and it singles out no one: remove identifiers that were never present to begin with, and the residue is a note of how a single handset fared against some mixed-up flasks. Two conditions must hold together for the Regulation to take hold: personal data on one side, a controller processing it on the other. Delete the first and the second collapses with it.

An argument built on a premise lives exactly as long as the premise does. Bring in a login, an advert, a measurement library or a till, and it is over by the end of that day — whereupon this text has to be redrawn and shipped in the release that introduces the change, with every new item carrying its basis. The working notes for doing that sit in a comment at the bottom of this file.

Nor is there a cookie banner, and the reasoning is adjacent. The trigger for those rules is storage or retrieval on a user's device going past what the service they actually asked for needs, and they typically arrive inside a web view, a tracking pixel, or a tag belonging to someone else. Not one of the three is present in Kolbe, and even if one were, it would find no connection to report down. The Norwegian rules in this area consequently have nothing to bite on.

One asked for, the rest declined

The right-hand column is load-bearing for every other page of this document. Transmission requires a route, and there is none; so the question of where your data ends up is settled by the package rather than by our sincerity, and anybody minded to check can do it without asking us a thing.

If a prompt you did not expect ever appears, decline it and send the build number to glass@stonebruzs.lol. Precisely two things could account for it: this page has drifted out of step with the code, or your copy of Kolbe was not published here. Both want tracking down quickly, for the sake of whoever meets it next.

Google Play is its own transaction

Everything so far concerns Kolbe once it is running on your phone. Acquiring it happened earlier and between other parties: you and Google. Google logs the download, each later update and any star you leave, all of it recorded against whichever account happened to be signed in, on whatever terms govern its own store. We see none of it and can alter none of it.

What reaches this end is the Play Console's summary, and it deals strictly in aggregates — copies out, a rough spread by country, crashes grouped by type, a rating averaged. Nothing in it narrows to an individual. Anything attached to your Google account remains on that side of the line — billing address, payment method, the phones it has been used on. Those records are managed from within the account itself, never from here, which is where a question about them has to go.

A caution about the listing itself: a review is public from the moment it is posted, under whatever name the account displays, and remains visible to every later visitor.

There is nobody further down

Work that is not being performed cannot be passed to a contractor. There is no server keeping data for this game, no analytics property trained on it, no crash service listening, no advertising exchange connected, no mailing platform holding a list for it and no payment agent retained. We did not assess these suppliers and decline them — the task they would perform never arose. Where Article 13(1)(e) calls for the categories of recipient, the truthful entry is nothing at all.

Transfer across a border fails at the same step. Everything built to make a cross-border transfer lawful — an adequacy decision, the model clauses, the tightly drawn exceptions in Article 49 — exists on the assumption that a transfer is taking place. None is. A pour count arrived at on your phone went into that phone's own storage, and has never been duplicated anywhere else.

Bay 06 sits ahead of this one on purpose, to mark the edge of what is answered for here rather than to tuck it away: that exchange runs on Google's systems, under Google's agreement with you, and is over before Kolbe is opened for the first time.

For as long as you allow, and no longer

A number of months usually appears in this clause because the keeping is done by somebody the reader cannot instruct. That is not the arrangement here, so a figure would be a fiction and a condition is the honest form: what is stored survives exactly as long as you let it, since the reset and an uninstall each finish it immediately. No overnight process mirrors it anywhere. No archive preserves an earlier copy. There is no system on this side in which a remnant could outlive the decision you made.

Nor does the passage of time alter anything. A pour count left untouched for two years is still a pour count on your phone, visible to you and to nobody else, and it will still be there on the day you reset it or on the day you remove the app, whichever you reach first.

What a parent would want to check

Kolbe holds a general-audience rating, and pouring colours until a shelf comes right is an unobjectionable way for a child to spend an afternoon. The four things a parent usually looks for in a game of this sort are advertising aimed at children, a purchase sitting within reach of an imprecise finger, any channel a stranger could use to make contact, and material contributed by other players. Not one of the four was built into it.

Article 8 ought to be relevant here as well, since it marks the point under which a parent must stand behind a child's agreement to an online service. There is nothing for it to govern, because no agreement is collected at all — not from a child, not from an adult. The Norwegian threshold is 13. Setting the figure down while it is still beside the point means it will already be written here on the day advertising makes it the point.

Eight rights, and what each actually yields

Not one of the eight is narrowed on this page. The venue is what changes: almost all of them are resolved on the handset itself, and no correspondence need pass in either direction. Putting a request through a formal procedure whose only available ending is a note saying nothing of yours is held would be pure ceremony, so this table gives the real outcome instead.

Nothing costs anything, no paperwork is involved, and your identity will not be checked. The point of an identity check is to prevent one person's file being released to another; absent any file, it guards nothing — and carrying one out would mean collecting a document from you halfway through a page whose whole claim is that nothing is collected.

Where to write, and when this page changes

Write, if you would like to, to glass@stonebruzs.lol. One address, nothing routing behind it — write to exercise a right, to take issue with something stated here, to flag a permission dialog bay 05 fails to explain, or just to ask how some piece of it works.

Du kan skrive på norsk om du vil — samme adresse, og du får svar på norsk.

Personopplysningsloven is the Norwegian act bringing the General Data Protection Regulation into force here, and a controller based in Norway answers to Datatilsynet under it. Post reaches the authority at Postboks 458 Sentrum, 0105 Oslo, and datatilsynet.no is the quickest route in. That said, Oslo is only one of three doors Article 77 leaves open: your country of residence, the country where you are employed, or whichever covers the place you believe the trouble occurred. Pick between them on whatever grounds suit you. Nothing written on this page may shorten that list, and a clause pretending otherwise would have no effect whatsoever. Nor is writing here first a condition of anything: a complaint already lodged with Datatilsynet sits perfectly well alongside an exchange of letters.

Under the title stands a version, and it moves whenever anything above it is edited. One rule governs when those edits ship, and it is not departed from: when a revision is prompted by an actual change in what the software does — something newly kept, somebody newly in the chain, traffic newly crossing a frontier, a fresh purpose — then the new wording travels in that same release rather than at some later convenience. We will not put a change on phones in October and get round to describing it in November. So the version line is a quick test: were these words drafted for the build you have installed? Older versions remain on file and can be sent over if you want one.