Last updated: 11.08.2026

Effective: 11.08.2026

1. The short version

Cookie Jar does not collect your personal data.

There are no accounts, no sign-up, and no login. We run no servers. The App contains no analytics, no advertising, no tracking, and no third-party data-collection tools. What you write stays on your device and, if you use iCloud, in your own private iCloud account — where we cannot see it.

The rest of this document explains that in detail, because you deserve specifics rather than a promise.

2. Who is responsible

Cookie Jar is published by “Plumya” Tomasz Milczarek, Warsaw, Poland. For any question about this policy, contact [email protected].

Where the GDPR applies, we are the data controller for the App — but as set out below, the App is designed so that we hold no personal data about you at all.

3. What the App stores, and where

3.1 Your achievements

Everything you create in Cookie Jar consists of:

• the text note you write on each cookie,
• the appearance of each cookie (dough type, chip style, size, and position),
• the jars you create, their shape, and the labels you give them.

This is stored in two places:

On your device. A local database inside the App's own storage area, protected by iOS app sandboxing and by your device passcode and encryption.

In your private iCloud database. If you are signed in to iCloud and have iCloud enabled for Cookie Jar, iOS syncs that data to a CloudKit private database belonging to your Apple Account, so your jars appear on your other devices.

The word private is technical, not marketing. A CloudKit private database is scoped to the end user's Apple Account. We, as the developer, have no credentials, no dashboard, and no API that would let us read, list, export, or restore its contents. We do not receive a copy. We could not hand your notes to anyone even if compelled, because we do not have them.