Privacy Policy

Keepsake (also listed as "Keepsake: Recipe Manager") Provider: GreenVine Cloud LLC Contact: support@keepsake-recipe.app

Effective date: 2026-09-22 Last updated: 2026-09-19

The short version

Keepsake keeps your cookbook on your devices. There is no account to create, nothing to log in to, and no server of ours that holds your recipes. If you turn on iCloud sync, your recipes sync through your own iCloud account, which we cannot read.

The one thing that does leave your device is diagnostics — crash reports and technical logs that help us fix bugs. They never contain your recipes. There is no way to turn them off in this version, and this policy says so plainly rather than implying a control that does not exist.

We do not sell data, show ads, use analytics or advertising SDKs, or track you across apps or websites.

One point of precision, because the App Store label and this page have to say the same thing. Some of those technical log events name an action you took — cooking.started, grocery.added. Under Apple's definitions that counts as usage data, so the App Store privacy label declares it. We read those events to find bugs, not to study you; there is no analytics product behind them and no dashboard of your behaviour. If that ever changes, this page and the label change first.

What Keepsake stores, and where

On your device

Everything you create lives in a database on your device:

• recipes — titles, ingredients, instructions, notes, tags, ratings, favourites
• photos you add to a recipe, and images saved from a page you imported
• your grocery list
• cooking history (which recipes you have cooked, and when)
• app settings, and whether you have purchased Keepsake Pro

We have no copy of any of it.

In your iCloud account, if you turn sync on

With iCloud sync enabled, that same data syncs through Apple's CloudKit into the private database of your own iCloud account. "Private database" is Apple's term and it is the important part: the data is held under your Apple Account, governed by Apple's privacy policy, and GreenVine Cloud LLC has no access to it. We cannot read it, export it, or hand it to anyone, because we hold no credentials for it.

Sync is off until you turn it on, and you can turn it off in Settings at any time. Turning it off leaves the data on your device.

What leaves your device

Four things, and nothing else.

1. Diagnostics — crash reports and technical logs

Keepsake sends crash reports and technical log events to Sentry (sentry.io), which processes them on our behalf so we can find and fix bugs.

What is sent:

• crash reports: the stack trace, device model, OS version and app version
• technical log events: short event names and simple values — for example cooking.timerStarted with a duration in seconds, spotlight.indexed with a count, watch.command.applied with a command name

What is never sent:

• recipe titles, ingredients, instructions, notes, photos or any other content you create
• your name, email address, Apple Account, or any identifier for you personally
• your location

This is not only a promise. Keepsake's engineering rules require log events to carry counts and identifiers rather than content — a recipe is logged as an event with a number, never a title — and the function that would attach a user identity to a report (setUser) is never called anywhere in the shipped app.

There is no way to turn diagnostics off in this version. If that matters to you, please write to us at the address above; we are recording the request.

Sentry acts as our data processor. See Sentry's privacy policy for how they store and retain what they receive.

How long we keep diagnostics. Crash reports and log events are retained for 30 days, after which Sentry deletes them automatically. We keep no separate copy — when the 30 days are up, the report is gone from everywhere we could reach it.

2. Importing a recipe from a website

When you import a recipe from a link, your device fetches that page directly from whatever website you chose. There is no proxy or intermediary of ours: we never see the address, and we do not learn which sites you visit.

Keepsake keeps the source address alongside the imported recipe so that the page can be credited and reopened. That is stored with your recipe, on your device.

The same is true of the share extension — sharing a page into Keepsake fetches it on your device.

3. Buying Keepsake Pro

The one-time Keepsake Pro purchase is handled entirely by Apple through the App Store. Apple processes the payment; we never see your payment details, and we do not receive a list of who has bought the app.

All Keepsake stores is whether this Apple Account is entitled to Pro — a yes or no on your device.

4. Rating prompts

Keepsake may occasionally ask whether you would like to rate it. That prompt is Apple's, shown by the system; we do not receive your rating or your review through the app.

Recipe scanning and on-device intelligence

Scanning a recipe card uses Vision and, where the device supports it, Apple's Foundation Models. Both run on your device. The photograph and the text read from it are not uploaded anywhere — not to us, not to Apple, not to any other service.

Where a device does not support on-device models, the feature does less rather than sending your photograph somewhere to make up the difference.

What Keepsake does not do

• No accounts. There is nothing to sign up for and no profile.
• No analytics SDK. No Firebase Analytics, no Amplitude, no Mixpanel, nothing of that kind.
• No advertising, and no ad SDKs.
• No tracking. Keepsake does not track you across other companies' apps or websites, and does not use the Advertising Identifier (IDFA). Its privacy manifest declares NSPrivacyTracking = false.
• No sale or sharing of personal information, under any definition, to anyone, ever.
• No data brokers.

Children

Keepsake is not directed at children under 13, and we do not knowingly collect personal information from children. There is no account system, so there is no registration through which a child's details could reach us. If you believe a child has sent us information through a support email, write to us and we will delete it.

Your rights and your data

Because your recipes are on your device and in your own iCloud account, you already hold them:

• Access and export. Settings → Data → Export Cookbook writes every recipe, collection and photo out as a backup file you keep.
• Deletion. Deleting a recipe deletes it. Deleting the app removes its on-device data; if you used iCloud sync, manage or delete what remains through your Apple Account settings, which is the same place you manage every app's iCloud data.
• Correction. Everything is editable in the app.

For the diagnostics we do receive, write to support@keepsake-recipe.app and we will do what we can — bear in mind that crash reports carry no identifier for you, so we may be unable to locate reports as "yours".

Depending on where you live you may have further rights under laws such as the GDPR or the CCPA. Write to us and we will honour them. Our lawful basis for processing diagnostics is our legitimate interest in keeping the app working.

Where your data is processed

Your recipes are on your device and, if you enable sync, in your iCloud account — wherever Apple stores that for your region.

Diagnostics are processed by Sentry on servers in the United States. If you are in the EU, EEA, UK or Switzerland, that is a transfer outside your region; Sentry's data processing terms cover it.

Changes to this policy

If this policy changes we will update it here and change the effective date. Material changes — for example, if Keepsake ever began sending something new — will be announced in the app's release notes rather than made quietly.

Contact

GreenVine Cloud LLC — support@keepsake-recipe.app