Privacy policy
Effective date: October 23, 2026
Recikeeper is a recipe app for saving recipes, planning meals and cooking. This policy explains what we collect when you use Recikeeper on the web or on iPhone, why, who else handles it, and how to delete it. We don’t sell your data, and we don’t use it for advertising.
Who we are
Recikeeper is run by Rhett Raleigh, based in Arizona, United States. In this policy, “we” and “us” mean that operator.
For privacy questions or requests, email rhett@raleigh.dev. We aim to reply within 30 days.
What we collect
We collect what you give us, what’s needed to keep you signed in, error reports, and anonymous usage and performance data.
| What | Examples | Where it comes from |
|---|---|---|
| Account details | Name, email address, profile picture, provider account ID | Google, GitHub or Apple when you sign in. With Apple’s Hide My Email, we get a relay address, not your real one. |
| Your recipes and cooking data | Recipes, photos, notes, collections, meal plans, shopping list, pantry staples, cook logs, variations | You, including recipes you import from a web page, the iPhone share sheet, the bookmarklet or a photo |
| Sage conversations | What you ask Sage, photos you send it, its replies, recipe drafts and edits it proposes | You, while using Sage |
| Friends and sharing | Who you’re friends with, friend requests, what you share and with whom | You |
| Devices and sessions | Sign-in sessions, and a token for each connected device with its name and when it was last used, so you stay signed in | Created when you sign in |
| Error and crash reports | Crash logs and errors, device model, OS and browser version, app version, and recordings of some web sessions with all text and inputs masked | The iPhone app and the website, through Sentry |
| Usage and performance data | Pages viewed, referring site, country, device type, page load speed. Aggregate and cookieless, with no ID that follows you between days. | The website, through Vercel Analytics and Speed Insights |
| Technical logs | IP address, browser or app version, request times. A scrambled (hashed) IP address is kept for 24 hours to limit imports from the home page. | Our hosting provider, to run and secure the service |
When you import a recipe from a web page, we fetch that page to pull out the recipe. We don’t track the other sites you visit.
We don’t collect your location, contacts, health data or payment details.
How we use it
We use your data only to run Recikeeper for you:
- Sign you in and keep your account secure.
- Store, show and sync your recipes, plans and lists across your devices.
- Import recipes you send us and answer your questions in Sage.
- Share what you choose to share with friends.
- Fix crashes and bugs, and prevent abuse.
- Contact you about your account or important changes to this policy.
We don’t sell your data, share it for advertising, or build ad profiles. Your recipes, the pages you import and your Sage conversations are not used to train AI models, by us or by our AI provider.
Service providers
These companies process data on our behalf, only to provide Recikeeper. They aren’t allowed to use it for their own purposes.
| Provider | What they do | Data they handle |
|---|---|---|
| Vercel | Hosts the web app, the API and Sage; anonymous usage and performance analytics | Everything passing through the app, Sage sessions, plus technical logs |
| Neon | Database | Your account and all your Recikeeper data |
| Amazon Web Services (S3) | Stores images | Recipe photos, imported images and photos you send Sage |
| OpenAI, through Vercel AI Gateway | Runs Sage and pulls recipes out of pages you import | Your Sage messages and photos, the recipe you’re asking about, and the text of pages you import |
| OpenAI | Sorts your shopping list into aisles | The items on your shopping list |
| Sentry | Error and crash reporting for the website and the iPhone app | Crash logs, errors, device details and masked session recordings |
| Google, GitHub, Apple | Sign-in | They confirm who you are; we receive the account details listed above |
We may also share data if the law requires it, to protect people’s safety, or as part of a sale or transfer of Recikeeper, in which case this policy continues to apply to your data.
What other people can see
Your library is private by default. Others see only what you share:
- Friends see your name, profile picture, and the activity that appears in their Friends feed. Anyone signed in can find you by name or handle, and sees your name, handle and picture so they can send you a friend request.
- People you share a collection or meal plan with see what’s in it. You can keep individual items private inside a shared collection.
- Anyone with a share link can see what that link points to. Links to a recipe or a collection also show your name, or your handle if you haven’t set a name. A link to a collection or meal plan works until you stop sharing it; a link to a recipe works until you delete the recipe.
If someone copies a recipe you shared into their own library, that copy is theirs and stays with them, even if you later delete yours or your account.
Keeping and deleting your data
We keep your data while you have an account. You can delete your account at any time from the account menu in the app or on the web.
Deleting your account is immediate and permanent:
- Your account, recipes, photos, collections, meal plans, shopping list, pantry, cook logs, Sage conversations, friends and connected devices are deleted.
- Collections you shared are deleted for everyone you shared them with.
- Friend connections and pending requests are removed for both sides, and share links stop working.
- Copies other people saved to their own libraries stay with them.
- If you signed in with Apple, we also revoke Recikeeper’s access with Apple.
Some copies take longer to disappear:
| Where | How long |
|---|---|
| Database restore history (Neon) | Up to 1 day |
| Sage session storage (Vercel) | Up to 30 days |
| Hosting logs (Vercel) | Up to 1 hour |
| Error and crash reports (Sentry) | Up to 30 days |
| AI provider (OpenAI) | Up to 30 days, for abuse monitoring only |
We don’t restore deleted accounts from backups.
Your rights and choices
Wherever you live, you can:
- See and edit your data in the app.
- Delete individual recipes and items, or your whole account. A deleted recipe disappears from the app straight away, but we keep it, with its photos, until you delete your account.
- Disconnect devices you no longer use from the Import page on the web.
- Ask for a copy of your data, or ask a question, by emailing rhett@raleigh.dev.
Depending on where you live, laws such as the GDPR or California’s CCPA may give you further rights, like objecting to certain processing or complaining to a data protection authority. Email us and we’ll help. We won’t treat you differently for exercising them.
We use only the cookies needed to keep you signed in, plus one that holds a recipe you imported before signing up, for up to 7 days. We don’t use advertising or cross-site tracking cookies.
Security, children and changes
Security. Data is encrypted in transit. Device tokens are stored hashed on our side and in the iPhone Keychain on yours, and you can revoke any of them. No system is perfectly secure; if a breach affects you, we’ll tell you.
Children. Recikeeper isn’t directed at children under 13, and we don’t knowingly collect their data. If you believe a child has an account, email us and we’ll delete it.
Where data is stored. Recikeeper and its providers are based in the United States, and your data is processed there.
Changes. If we change this policy, we’ll update the effective date. For significant changes, we’ll tell you in the app or by email before they apply.