Privacy Policy
Last updated: June 2026
What we collect and why
| Data | Why |
|---|---|
| Email address | Account creation, sign-in, and transactional emails (e.g. subscription receipts). We never send marketing email without your consent. |
| Saved recipes | Stored on your device (localStorage) and, if you have an account, synced to our servers so you can access them across devices. Recipes are keyed to your account ID, not sold or shared. |
| Payment info | Processed by Stripe on the web and by Apple in the iOS app. We receive subscription status plus provider IDs such as a Stripe customer ID or RevenueCat app user ID — never your card number or bank details. |
| Anonymous usage events | We track events like "URL submitted" and "extraction succeeded" with PostHog to understand how the app is used. These events are tied to an anonymous client ID, not your name or email, unless you are signed in. |
| Recipe URLs you submit | URLs are fetched server-side to extract the recipe. They are not stored permanently — only the extracted recipe is saved. |
Cookies and local storage
We use browser localStorage to save your recipes and preferences on your device. Supabase (our auth provider) sets a session cookie when you sign in so you stay logged in across page loads. We do not use advertising or tracking cookies.
Third-party services
- Stripe — payment processing. When you subscribe, you interact with Stripe's checkout and billing portal directly on the web. Their privacy policy applies to that interaction.
- Apple App Store — iOS subscription billing. If you subscribe in the iOS app, Apple processes the purchase through your Apple Account and manages receipts, renewals, cancellations, and refunds.
- RevenueCat — iOS subscription entitlement management. We use RevenueCat to verify whether an iOS user has an active Pro subscription and to restore purchases across devices.
- Supabase — authentication and database hosting. User accounts and synced recipes are stored in a Supabase-hosted Postgres database (US region).
- PostHog — product analytics. Anonymous usage events. You can opt out via your browser's Do Not Track setting or a privacy extension.
- Vercel — hosting. Standard server access logs (IP, user agent, request path) are retained briefly by Vercel per their data policies.
- Anthropic (Claude API) — used to clean and structure extracted recipe text. Recipe text is sent to Anthropic's API; it is not used to train their models per their API data policy.
- InKind — optional referral offer. If you click the InKind dining credit link, you leave Print My Recipe and interact with InKind under their own terms and privacy policy. Print My Recipe may receive a referral reward.
Data retention
If you delete your account, your user record and synced recipes are deleted from our database. Stripe retains billing records as required by their policies and applicable law. Apple and RevenueCat may retain subscription records according to their policies and applicable law. Local data (localStorage) is stored only on your device and cleared when you clear your browser data.
Your rights
You can export all your saved recipes from the account menu at any time. You can delete your account from the account menu, which removes your email and synced recipes from our servers. To request a copy or deletion of any other data we hold, email us.
Children
Print My Recipe is not directed at children under 13. We do not knowingly collect personal information from children.
Changes to this policy
Material changes will be communicated by email to registered users before they take effect. The current policy is always at this URL.
Contact
Questions or data requests: hello@printmyrecipe.com