Cookie policy

1. About this policy

Gooblies is a game of hide-and-seek played outdoors, offered as an installable web application. This policy describes the cookies we set, the information the game keeps on your device, and the third-party services that may set cookies of their own.

It supplements our privacy policy, which sets out all of the processing of personal data.

2. What is a cookie or a tracker?

A cookie is a small file placed on your device when you visit a site. It makes it possible, for instance, to recognise you from one page to the next or to remember your preferences.

Equivalent technologies exist: the browser's local storage (localStorage, sessionStorage) and the browser's databases (IndexedDB), which keep information directly on your own device. In this document, the word “tracker” refers to all of these technologies together.

3. The cookies we set

The first two are set by us alone, on our own domain, and are there from the moment you arrive: they do not make it possible to follow you from one site to another and serve no form of measurement or advertising.

The third is the measurement one. It is set only if you have agreed to it, and section 5 explains where the question is put to you and what your answer covers.

4. What the game keeps on your device

Gooblies is designed to work offline: your child must be able to play at the far end of the garden, where there is no signal. That means the game has to keep everything it needs on the device itself.

Browser database (`IndexedDB`) — this is the game's main memory: the creatures, the garden, the games, the cupcake ledger. If you have an account, this data is also synchronised with our servers; if not, it never leaves the device. Our authentication provider also keeps your sign-in session there.

Local storage (`localStorage`) — the preferences (sound, vibration), the game in progress, the fact that you may have declined the invitation to install the application, and your answer to the measurement question. If you accepted it, the few counters emitted at the bottom of the garden, out of network range, wait there until the connection comes back.

Application cache (service worker) — a copy of the pages, images and sounds of the game, so that it starts without a network connection. It contains no personal data.

You can erase all of it at any time: see section 7.

5. The question of consent

One single thing asks for your agreement: measurement. We use Google Analytics to know how many people read the home page, where they arrive from, and what actually gets used in the game — how many games are started, how many run to the end, at what point people give up. These are counters, and nothing more: no location, no garden outline, no account identifier goes to Google.

A banner puts the question to you on your first visit, with two buttons of the same size: declining costs not one gesture more than accepting. Until you accept, nothing is loaded — Google's script does not enter the page, and no measurement cookie is set. Your answer is remembered on this device, including when it is a refusal: the question does not come back at every visit.

Your answer covers this site and the game, which live on the same domain. That is why the question is put only once, here, to an adult: the game never puts it. Asking a seven-year-old who has just pressed PLAY would not collect consent.

One direct consequence, and it deserves saying: if the question has never been put to you, nothing is measured. Someone who opens the game without going through this site — from the icon installed on their home screen, or from a link they were sent — has not seen the banner; no answer counts as a refusal.

For the rest, there is nothing to consent to: no advertising, no advertising pixel, no profiling, no recording of your screen, no social sharing button. Even the site's fonts are hosted by us, rather than loaded from a third-party service.

You can go back on your answer at any time by clearing this site's data in your browser settings: the question will be put again on your next visit.

6. Third-party services and location data

Three third-party services are involved, each at a specific moment. The first two set cookies of their own on their own domains:

Stripe, our payment provider, when you open the shop in the parents' area. The Stripe script is only loaded at that point: it is never present in the child's interface. The payment page itself is hosted by Stripe.

Mapbox, our map background provider, when you draw or view the garden. Mapbox receives your IP address and the coordinates of the area being viewed.

Location is not a cookie, it is a device permission. Your browser asks you for it explicitly, and you can withdraw it at any time in its settings. What the game records — the outline of the garden, the hiding places from the games — is described in our privacy policy.

7. How to manage or erase everything

From the game. The parents' area includes a button that erases all of the data kept on the device.

From your browser. Your browser settings allow you to block or delete cookies and local storage. Be careful: erasing this data signs the account out and, if you have not created one, permanently deletes the game progress, since it lives only on the device.

From your device settings, for location.

8. Changes to this policy

We may update this policy to reflect changes in the service or in the regulations. Any change is published on this page with an updated revision date.

9. Contact

For any question relating to this policy or to the exercise of your rights, write to us at info@jackandmani.com. You also have the right to lodge a complaint with the Autorité de protection des données (the Belgian data protection authority).