Privacy Policy

1. Information You Provide

• Account: email address and password, or, if you sign in with Google or Apple, the email and name those providers share with us.
• Profile: display name, avatar photo, bio, and up to three featured recipes — visible to your friends, (name/avatar/bio only) to members of any cookbook you share, and (name/avatar only) to anyone who has blocked you, in their blocked-users list.
• Content you create: recipes, ingredients and steps, photos you add to a recipe, meal plan entries, grocery lists, collections, cookbooks, likes, chat messages, and notification preferences.
• Friend connections: made by scanning or exchanging your friend code with another user — we do not access your contacts, and the camera is used on your device only to read the code, never recorded or uploaded. We also keep the list of people you have blocked.
• Support requests: anything you send to [email protected].
• Feedback: if you send feedback from Settings → Share feedback, we store your message and the type you chose (idea, issue, or other), together with your app version, device platform (iOS or Android), and app language, linked to your account. Only the Nabe team reads it; it is not shown to other users.
• Reports: if you report a user or a chat message, your email app sends us your email address, the reported person's name and account ID, and — for a message — its text and ID. If someone reports you, we receive the same information about you, and use it only to review the report and enforce our Terms of Service.

2. Information Collected Automatically

• Device push token: a Firebase Cloud Messaging identifier used to deliver notifications you've opted into (a friend liked your recipe, a cookbook you belong to changed, a new chat message), removed automatically once it's no longer valid.
• Crash reports: if the App crashes or hits an unexpected error, Firebase Crashlytics sends us a technical report — the error and where in the code it happened, device model, OS version, app version, and a random installation identifier. Crash reports are not linked to your account, and they are not affected by the Share usage data setting below, since they are how we find and fix bugs.
• Product analytics: we use PostHog to understand how the App is used — screens viewed, features used, app version, device/OS type, and general performance metrics. These events are linked to your account identifier so we can tell repeat use from new use, but they never carry your recipes, photos, chat messages, email address, or name. We do not use PostHog for advertising or cross-app tracking.
• You can turn product analytics off at any time in Settings → Share usage data. Turning it off stops collection on that device, including at launch — the App starts up with analytics disabled rather than sending events and going quiet afterward. Everything else in the App keeps working.
• Fonts: the App downloads its typefaces from Google Fonts, and a PDF export downloads the fonts of the theme you pick (and, for Chinese, Japanese or Korean text, a matching font) the first time you use them, then keeps them on your device. Google receives your device's IP address and which font was requested, and nothing from your recipes. The free Basic PDF theme uses fonts bundled with the App.
• We do not collect precise location, and we do not use advertising identifiers.

3. Information From Third Parties

• If you sign in with Google or Sign in with Apple, we receive the profile fields you authorize (typically email, and — for Apple, only on first sign-in — your name). For Sign in with Apple we also keep a token Apple issues for your sign-in, used only to revoke Nabe's access to your Apple ID when you delete your account.
• Apple and Google tell RevenueCat, and RevenueCat tells us, whether your subscription entitlement is active. Neither Nabe nor RevenueCat receives your card number or other payment details — that stays with Apple/Google as the merchant of record. We keep a record on our server of whether your account has an active subscription and when it ends, so your plan's limits apply on our side as well as in the App. It is refreshed from RevenueCat when you sign in, when you use an AI feature, and when RevenueCat notifies us of a change to your subscription (a purchase, renewal, cancellation, refund, or transfer to another account).
• If you extract a recipe from a YouTube link, we fetch that video's public title, description, and channel name from the YouTube Data API to help generate the recipe.

4. How We Use Information

We use the information above to: create and secure your account; provide the App's core features (saving, planning, and sharing recipes; grocery lists; chat); operate the friends and cookbook features you choose to use; send the notifications you've opted into; process AI recipe extraction/generation; verify and manage your subscription; respond to support requests; review the feedback you send and use it to decide how to improve the App; detect abuse and enforce our Terms of Service; and, unless you turn it off, understand product usage through PostHog to improve the App.

5. AI Processing of Your Content

When you extract a recipe from a YouTube link, import one from a video you saved to your phone, generate a recipe from a dish name or from ingredients you have on hand ("What can I cook?"), ask AI to change one of your saved recipes ("Edit with AI"), or use automatic grocery-aisle sorting, the relevant content (video metadata or, if needed, the public video itself; the saved video you picked; your typed dish name or ingredient list; the recipe you are editing — its title, description, times, servings, ingredients and steps — and the change you type; or an ingredient name) is sent to Google's Gemini API to produce a result. We do not send your email, name, or other account identifiers as part of these requests.

How Google may use that content depends on which tier of its API the request goes to, and we want to be plain about this rather than leave it to a link. Two of these features always use the free (unpaid) tier: recipe extraction from a YouTube link, and grocery-aisle sorting. Recipe generation — from a dish name, from ingredients, or editing a saved recipe with AI — depends on your plan: free accounts use the unpaid tier, and Nabe Pro subscribers use Google's paid tier. Importing a recipe from a saved video works the same way: free accounts use the unpaid tier, and Nabe Pro subscribers use the paid tier.

That distinction matters. Under Google's API terms, content sent to the unpaid tier is used by Google to improve its products and machine-learning technologies, and human reviewers may read, annotate, and retain it — Google states that such content may be kept for up to three years, and that it is disconnected from your Google account before review. Google's own instruction is: "Do not submit sensitive, confidential, or personal information to the Unpaid Services." On the paid tier none of that applies: Google does not use the content to improve its products, and it is not subject to human review.

Practically: the ingredient names we classify, the public YouTube links you extract from, and — on a free account — the dish names, ingredient lists and changes you type, the recipes you choose to edit with AI, and the videos you import should be treated as content that may be reviewed by Google. Please don't type anything sensitive or personal into those fields, edit a recipe with AI whose notes hold anything private, or import a video that shows anything private. A Nabe Pro subscriber's dish names, ingredient lists, recipes edited with AI and imported videos are not used to train Google's models.

When you import a recipe from a saved video, the App first shrinks the video on your device, then uploads it to a private storage area that only your account can add to. Our server gives Gemini a link to it that expires within minutes, and deletes the video as soon as the recipe has been read, whether or not one was found. If an upload is interrupted before it can be read, it is deleted in a later clean-up. We never keep the video, and we never fetch anything from TikTok, Instagram, Facebook or any other site it came from. If you type the link where you found it, we store that link with the recipe as text and do not open it. The video's first frame becomes the recipe's photo and is stored like any other recipe photo (see section 8).

Matching the ingredients you have against your saved recipes happens within your own library and is not sent to Gemini; only asking Nabe to generate a new recipe from them is. Your recent ingredient searches are kept on your device only.

Nothing else in the App is sent to Gemini on any tier: your saved recipes (except one you choose to edit with AI, and only when you do), photos, chat messages, meal plans, and grocery lists are not used for AI training by us or by Google. If we move another feature between tiers, we will update this section to say which one before the change takes effect. Google's current terms are at https://ai.google.dev/gemini-api/terms.

6. How We Share Information

We share information only as follows:

• With other users, as you direct — a friend or cookbook member sees the profile fields, recipes, and messages you choose to share with them.
• With service providers who process data on our behalf: Supabase (database, authentication, file storage, and the server-side functions that power AI extraction and push delivery), Google (Sign-In, Gemini AI, YouTube Data API, Firebase Cloud Messaging, Firebase Crashlytics), Apple (Sign in with Apple, App Store billing), RevenueCat (subscription entitlement checks and notices of subscription changes), Resend (delivering account emails), and PostHog (product analytics, unless you turn it off).
• Learn more about how Google handles data through the Google APIs and services we use (Sign-In, Gemini AI, YouTube Data API, Firebase Cloud Messaging, Firebase Crashlytics) at Google's Privacy Policy: https://policies.google.com/privacy.
• If required by law, legal process, or to protect the rights, safety, or property of Nabe, our users, or the public.
• If Nabe is involved in a merger, acquisition, or sale of assets, as part of that transaction, subject to this Policy continuing to apply to your information.

We do not sell your personal information, and we do not share it with third parties for their own advertising purposes.

7. Data Retention and Deletion

We keep your information for as long as your account is active. Deleting your account (Settings → Account → Delete Account) requires a fresh identity check. Your account is closed immediately — you are signed out on every device and can no longer sign in — and is permanently deleted 14 days later. Until then, you can restore it as it was from the link in the email we send you. Once the 14 days have passed, your profile, recipes, meal plans, grocery lists, friendships, messages, any feedback you have sent, our record of your subscription status, and RevenueCat's record of your purchases are erased and cannot be recovered afterward, and if you used Sign in with Apple, Nabe's access to your Apple ID is revoked. Deleting your account does not cancel a Nabe Pro subscription: Apple or Google keeps billing it until you cancel it in your App Store or Google Play subscription settings. A cookbook you own is deleted for all of its members. In a cookbook someone else owns, what belongs to the group stays with its remaining members: another member's recipe that you added, and the cookbook's shared grocery list, remain there without your name attached, while your own recipes and your messages in its chat are erased. Before deleting, you can export your recipes and collections from Settings → Export recipes, and bring them into a new account later with Import recipes; that export deliberately does not include friends, cookbooks, chat, or meal plan entries, since those describe relationships with other accounts that a file can't restore on its own.

One exception: product-analytics events already collected by PostHog are not erased by deleting your account. They record app usage (screens viewed, features used) against an account identifier — never your name, email, or anything you created — and once the account is gone that identifier no longer corresponds to a person we can look up. To have those events deleted too, email [email protected], ideally before you delete the account, while we can still match the identifier to your request.

8. Data Security

Data in transit and at rest with Supabase is encrypted. Access to your database records — recipes, meal plans, grocery lists, messages — is restricted by row-level security policies scoped to your account.

Uploaded files work differently, and it is worth being precise about it: recipe photos and profile avatars are served from a public storage bucket at long, randomly generated URLs. Anyone holding the exact URL for one of those files can open it without signing in, so they are protected by being unguessable rather than by an access check. We do not publish or index those URLs, but treat a photo you upload as shareable-by-link rather than strictly private.

Your session is stored on-device using the platform keychain/keystore, not plain storage. So the App can open without a connection, a copy of your recipe library, calendar, and grocery list is cached on your device; it is erased when you sign out or delete your account. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

9. Your Rights and Choices

You can access and edit your profile, control per-category push notifications, turn off product analytics (Settings → Share usage data), export your recipes and collections, and delete your account at any time from within the App.

If you are in the European Economic Area, the United Kingdom, or Switzerland, you have the right to access, correct, delete, restrict, or port your personal information, and to object to certain processing. If you are a California resident, you have the right to know what personal information we collect, to request its deletion or correction, and to opt out of any "sale" or "sharing" of it — rights that already reflect our practice, since we do not sell or share personal information. To exercise any of these rights, or if you cannot do so in-App, contact us at [email protected].

10. International Data Transfers

Nabe and its service providers may process your information in countries other than the one you live in. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for these transfers.

11. Children's Privacy

The App is not directed at children under 13 (16 in the European Economic Area, the United Kingdom, and Switzerland), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact [email protected] and we will delete it.

12. Third-Party Links

Recipes may link to their original source (for example, a YouTube video). Those third-party sites and services have their own privacy practices, which this Policy does not cover.

13. Changes to This Policy

We may update this Policy from time to time. If a change is material, we will notify you in the App or by email before it takes effect.

14. Contact Us

Privacy questions or requests: [email protected]. General support: [email protected].