Cookie Policy

01. What cookies are

A cookie is a small text file a website stores on your device so it can recognise that device later. Similar technologies — local storage, pixels and SDK identifiers — do much the same job, and this policy covers them all.

Cookies are either session cookies, deleted when you close the browser, or persistent cookies, which stay until they expire or you remove them. They can be set by us (first-party) or by another domain embedded on the page (third-party).

02. The categories we use

On this website we do not use cookies to build advertising profiles. Advertising inside the free versions of our apps is a separate matter, handled through identifiers rather than cookies, and is described in section 06.

03. Cookies on this website

This site is a static page with no accounts, no forms and no analytics, and it currently sets no cookies at all — neither first-party nor third-party. Nothing is stored on your device when you browse it.

If we later add analytics, marketing or any other cookie, we will list it here with its name, provider, purpose and lifetime, and ask for your consent before it is set.

04. Third-party services

This website loads web fonts from Google Fonts. Doing so sends your IP address and browser information to Google so the font files can be delivered; Google states that it does not set cookies for this service. Google's handling of that request is governed by its own privacy policy.

Any other third-party service we add — analytics, a video embed, a support widget — will be listed in the table above before it goes live.

05. Identifiers in our mobile apps

Apps do not use browser cookies, but they do rely on identifiers that serve a similar purpose:

• Installation identifier — a pseudonymous ID generated on first launch, used for crash reporting and product analytics. It cannot be traced back to you by name.
• Advertising identifier (IDFA on iOS, Advertising ID on Android) — used to select the ads shown in our free apps and to measure which campaign brought you to us, and only while you have given permission. See section 06.
• Local storage — settings and cached content stored on your device so the app works offline and starts quickly.

Uninstalling an app removes its local storage and installation identifier from your device.

06. Ads in our free apps

The free versions of some of our apps are funded by advertising, served through Google AdMob. A paid subscription removes the ads and the data collection that goes with them.

None of this applies to apps we publish for children — see section 07.

AdMob requests the platform advertising identifier, your IP address and coarse region to choose an ad, and records impressions and clicks to measure it. Two permission layers sit in front of that:

• Consent form (EEA, UK, Switzerland) — Google's User Messaging Platform prompt appears before the first ad request. Decline and you still get ads, but non-personalised ones chosen from context rather than from an interest profile. You can reopen the form from the app's privacy settings whenever you want to change your answer.
• App Tracking Transparency (iOS) — Apple's prompt controls whether the advertising identifier is available to us at all. Declining it overrides everything else.
• Advertising ID controls (Android) — deleting or disabling the ID in Settings → Privacy → Ads has the same effect.

SDKs for our own campaigns

When we advertise our own apps on Google, Meta (Facebook and Instagram) or TikTok, their SDKs sit in the app so those platforms can attribute an install or a purchase to the campaign that produced it. They read the same advertising identifier and are covered by the same consent prompts described above — decline, and they do not run.

For ad serving Google also uses this data for its own purposes as an independent controller; the profiles it builds are outside our access and are covered by Google's own policies. Our Privacy Policy explains this split in more detail.

07. Apps made for children

Apps we publish for children — those in the App Store Kids Category, or whose primary audience is children — carry none of the technologies described above.

• no advertising SDK, so no ads and no ad measurement;
• no analytics or attribution SDK; the only third-party component is crash reporting, which takes no advertising identifier and nothing that identifies a child;
• no advertising identifier: the IDFA and the Android Advertising ID are never requested, no tracking prompt is shown, and Apple's AdSupport framework is not linked into the binary at all;
• only local storage on the device, for progress and settings — nothing that identifies a child leaves the device.

Section 13 of our Privacy Policy sets out the full regime, including the parental gates that sit in front of purchases and outbound links.

08. How to control cookies and identifiers

In your browser

Every major browser lets you see stored cookies, delete them, and block them entirely or per site. Look under Settings → Privacy. Blocking all cookies may break parts of some websites, though this one will continue to work.

On your phone

• iOS — Settings → Privacy & Security → Tracking, to revoke permission per app; and Settings → Privacy & Security → Apple Advertising.
• Android — Settings → Privacy → Ads, where you can delete or disable the advertising ID.

09. Changes to this policy

When we add or remove a cookie or an identifier, we update this page and the date at the top. Where the change requires your consent, we will ask for it before the new technology is used.

10. Contact

Questions about this policy: [email protected]. For how we handle personal data more broadly, see our Privacy Policy.