Privacy Policy

Nothing leaves the car park

There is no registration step in Myldretid, no profile attached to you, no table of times kept anywhere off the device, no advertising slot, no counting library and nobody on a mailing list. Underneath that list of absences sits one that turns the rest from assurance into fact: the published package asks Android for no internet permission. Without it the operating system will not open a connection, however the code might be written, and anyone who cares to inspect the package can see as much before installing.

What the game remembers — jams solved, move counts, the board you abandoned halfway — goes into the private storage Android reserves for this application and no further. There is no copy of it on any machine of ours, which means there is nothing here belonging to you that could be lost, sold, leaked or demanded by anybody.

Eleven bays follow. Together they cover what the General Data Protection Regulation expects of a notice like this, and the last one gives the address for disagreeing with any of it.

The controller, and how small it is

Article 4(7) gives the word "controller" to whoever decides the purpose of a processing operation and the means of carrying it out. Here the title comes with a single real duty: that these bays were written honestly, and that one named person answers for any of them that proves otherwise.

You will find no data protection officer named, and the absence is deliberate. The obligation to appoint one arises in three defined situations: processing by a public body, a core activity consisting of regular large-scale monitoring, and large-scale handling of the special categories. A single person publishing a puzzle that opens no connection does not come near any of the three, and naming an officer anyway would be decoration.

The complete list of what is written down

A puzzle with hundreds of levels has to remember a few things or it would start from scratch each evening. This is all of them:

• Which jams you have cleared, and in which pack, so the level screen can show how far along you are.
• Your move count on each, kept so the next attempt has something to beat and so a clean solve can be recognised.
• The jam you are part-way through, with its undo history for the current sitting, so closing the app does not throw away the thinking.
• Hints left in the allowance.
• Settings: sound, haptic feedback, whether move counters are shown, reduced motion.

Then read that list for what is missing from it. No name is requested. No address of any kind is retained. The identifier Android offers for advertising purposes goes unread. No collection of device characteristics is assembled into anything resembling a fingerprint. And no installation number is minted — the quiet omission that matters most, because without one nothing distinguishes your copy of Myldretid from the ten-thousandth copy, not to us and not to anyone. On top of that, the system keeps one application's private area closed to every other application installed alongside it.

Delete the game and the list goes with it. To empty it but keep the game, the settings screen has a reset, and Android offers the same under "clear data" in its own application settings.

Why no lawful ground appears below

Most notices of this kind set a ground from Article 6 beside each item they gather. This one sets none beside anything, which calls for an argument rather than a silence.

Grounds are answers to a challenge: on what footing do you keep this? The challenge presumes a keeper and a thing kept, and this page has neither. Bay 03's items live on hardware you own and we cannot touch, and they single nobody out — remove the identifiers, which were never there to begin with, and what is left is a tally of how one telephone got on against a car park. For the Regulation to engage there must be a controller, and there must be personal data; here the second is missing and so, in consequence, is the first.

That argument stands only while its premise does, so the premise bears watching. Let some future version add a login, or a banner, or a library that counts things, or a till, and the premise is gone — and this page must be rewritten in the release that introduces the change, with a ground named for each new item. Instructions for doing exactly that are kept in a comment at the foot of this document.

The missing consent banner follows from the same emptiness. Those rules reach the storing or reading of information on a person's equipment beyond what is needed to deliver the service asked for, and in practice the vehicles are an embedded browser, a measuring pixel, or a third-party component that writes a marker of its own. Myldretid carries none of the three and has no line out of the handset over which one could report, so the Danish implementation finds no subject matter here.

One thing asked of Android, and a long list not asked

The whole document leans on that first refusal. An application with no way out cannot send anything anywhere, so a sentence about where data goes stops being something you are invited to believe about our intentions and becomes a property of the package, open to anyone willing to look inside it.

If a prompt ever appears for something outside that right-hand column, turn it down and tell us which version you have at udvej@jsmu2.world. There are only two explanations — the page has gone stale, or the package is not one of ours — and either is worth settling quickly.

What happens before the game is opened

Every bay so far concerns Myldretid in use. Obtaining it happens earlier and elsewhere, between you and Google. The download, each later update and any rating you leave go into Google's own record of the account you used, under the terms Google publishes for its services. We are not a party to that and have no say in what it keeps.

What arrives on our side is the Play Console's summary view, which Google has already rolled up before we see it: how many installations, in which countries, which faults cluster together, what the rating averages out at. Nothing in it descends to a single person or a single device. The account itself stays entirely on Google's side of the wall: its email address, any card stored against it and the handsets it has been used on are all invisible to us. Whatever say Google grants you over its own records is exercised from inside that account, so a request of that kind belongs there and would only lose time here.

Worth a word of caution: anything you write in a review goes up in public straight away, signed with whatever name the account displays, and every visitor the listing ever receives can read it afterwards.

An empty list, and no border crossed

Before data can be passed to a processor there has to be data being processed. Nobody stores anything for this game, nobody counts anything in it, no service collects its crashes, no network fills a slot in it, no platform mails on its behalf and no agent handles money for it — not because those arrangements were declined, but because the activities they would serve do not exist. Article 13(1)(e) wants the categories of recipient named. Named honestly, the list has no entries whatever, with no quiet qualifier attached.

Transfer abroad closes on the same fact. An adequacy decision, the standard contractual clauses, a derogation under Article 49: every one of those instruments authorises data in motion, and nothing here is in motion. A move count recorded on your telephone was written there and stayed there.

Set down as a boundary rather than an omission: the distribution described in bay 06 runs on Google's equipment under Google's own agreement with you, and it has finished before anybody opens the game for the first time.

How long it lasts, and who it is fit for

Duration. A clause of this kind usually quotes a term, which makes sense where somebody other than the reader holds the clock. Here you hold it. The record lasts exactly as long as you leave it, and resetting it or deleting the game ends it that second. Nothing is duplicated overnight into a backup, nothing older is kept in an archive, and no server of ours holds a version capable of outliving the decision.

Age. Myldretid carries a general-audience rating, and shunting toy cars around a grid is a reasonable thing to hand a child. The four worries a parent usually has to check — advertising aimed at the child, a purchase one careless tap away, messages from strangers, material other players have uploaded — are none of them built into this game. There is also Article 8, which sets the age under which a parent must stand behind a child's consent to an online service. It finds nothing to operate on here: no player of any age is asked to consent to anything. Denmark draws that line at 13, and the number is recorded now so that it is already in the text on the day advertising arrives and the question stops being academic.

Eight rights, and what each would actually produce

You hold the whole set, in full. The only thing that differs from the usual is where each is used: for this game, in nearly every case, on the telephone itself rather than by writing to us. Setting out a formal request route whose only possible output is a letter saying "there is nothing here" would pad the page and assist nobody, so the lines below say what would really happen.

There is no fee, no form, and no identity check anywhere in this. Verification exists so that a controller does not hand one person's file to another; where no file exists the step is empty ceremony, and performing it would have us collecting a document from you in the course of explaining that we collect nothing.

Taking a complaint past us

Being a Danish company, Jsmu 2 ApS answers to the General Data Protection Regulation together with databeskyttelsesloven, the national act that sits alongside it. Oversight belongs to Datatilsynet: the office is at Carl Jacobsens Vej 35 in 2500 Valby, and everything needed to file is at datatilsynet.dk.

Writing to Valby is not compulsory. Article 77 gives a complainant a choice of forum: your own country of residence will take it, so will the country you are employed in, and so will the one where you say the breach happened. The right is yours to exercise wherever it is least trouble. No wording on this page can restrict it, and wording that attempted to would be struck down.

On sequence, offered and not imposed: a letter here is usually answered the same day, while any supervisory authority has procedures and a caseload. Treat that as a practical suggestion rather than a step you owe us. Nothing stops you lodging with Datatilsynet first, or doing both at once while we are still writing back.

Where to write, and how this page is revised

One address carries all of it: udvej@jsmu2.world. Send it a right you want exercised, a line on this page you think is wrong, a permission request that bay 05 does not account for, or an ordinary question about how the thing works. Letters in Danish and in English are both read by the same person.

Du er velkommen til at skrive på dansk — samme adresse, og svaret kommer på dansk.

The stamp under the heading carries the version and moves whenever a word below it does. There is one rule about when, and it does not bend. Where a change actually alters what happens — some class of information retained that was not retained before, an outsider let into the process, traffic leaving the country, an extra purpose taken on — the revised text is published in the very release that performs the change. It does not arrive two weeks later, once the new behaviour is already sitting on people's telephones. So the stamp answers the question that actually matters to a reader: does this text describe the copy installed on my telephone? Earlier versions are not thrown away, and one will be sent to anybody who asks for it.