Last updated: October 14, 2026
Cookcut is a digital scrapbook for recipes. We have no servers, and we hold none of your content.
What we collect
Nothing. Cookcut has no accounts and no separate sign-in. It collects no personal data, uses no analytics or tracking, and contains no third-party SDKs.
Where your collection lives
By default, only on your device. Your cuttings, boxes, notes and pictures are stored in the app’s own space.
If you turn on iCloud sync, or create or join a share, your content is also stored in Apple’s iCloud, as described in the next two sections. Either way, nothing is sent to us, because there is no “us” to send it to.
iCloud sync (optional)
With sync on, your collection syncs between your own devices through Apple’s iCloud (a private CloudKit database).
- It is stored in your own iCloud account and uses your own iCloud storage. We cannot read it.
- Pictures uploaded to iCloud are scaled to the photo quality you choose: about 1280px on the longest side for Save Space, about 2048px for the higher setting. The originals stay on your device.
- Videos are never uploaded.
- Your data is protected in transit and at rest by Apple’s iCloud and CloudKit. Cookcut does not claim end-to-end encryption of its own.
Shares
You can create one share and invite up to 5 people, and you can join other people’s shares.
- Everything in a share is visible to all its members: cuttings, pictures, notes, cooking logs and boxes. What you add or edit in a share, the other members see.
- Members see each other’s names, as set on their iCloud account. If an account has no name, the email address or phone number used for the invitation is shown instead.
- When a member asks the creator to delete a cutting, the creator sees who asked.
- A share’s content is stored in the creator’s iCloud account, uses the creator’s storage, and is uploaded at the photo quality the creator chooses.
- Creating or joining a share never shares your own collection (“Mine”). The two are kept apart.