Last updated: September 25, 2026
This Privacy Policy describes how Cookbook ("the app," "we," "us") collects, uses, and shares information when you use our Android application.
Cookbook lets you browse and read recipes without an account. Creating an account unlocks publishing, liking, and saving recipes.
When you create an account (email/password or Google Sign-In), we collect:
If you only browse as a guest, none of this is collected.
If you publish a recipe, we store the recipe's title, description, ingredients, instructions, category, difficulty, prep/cook time, servings, and any photo you upload. Your display name and profile photo are shown publicly alongside recipes you publish, since recipes are public content by design — anyone using the app, signed in or not, can read them.
If you like or save a recipe, we record that action against your account (user ID) so your likes and saved recipes sync across devices and are private to your account.
Recipe photos you upload are stored in our cloud storage, in a location associated with your account, so we can attribute and manage them (e.g. if you edit or delete a recipe).
Cookbook shows ads through Google AdMob. AdMob and Google may collect your advertising ID and other identifiers to serve and measure ads, which may include personalized advertising. If you are in the European Economic Area, the United Kingdom, or Switzerland, the app asks for your consent before using your data for ads, using Google's User Messaging Platform; you can review or change that choice at any time from Settings → Ad privacy choices (visible when a choice applies to you). See Google's own policy for details: policies.google.com/technologies/ads
Cookbook uses Google Analytics for Firebase to count how often in-app features are used — for example how many cooking sessions are started and finished, how often a timer runs out, or which recipe category was being cooked. These events carry counts, durations and category names only. They never include recipe text, ingredient lists, photos, search terms, your name or your email address.
Analytics is switched off when the app starts and is only enabled after the consent step described above resolves. If you are in the European Economic Area, the United Kingdom, or Switzerland and you decline, analytics stays off for the whole session, the same as ads.
If you report a recipe, we record which recipe you reported, who published it, the reason you picked, the time, and your user ID. Your identity is never shown to the person you reported. Reports are retained after review so that repeat problems can be recognised, and they are not deleted when you close your account — see Data Retention and Deletion below.
Blocking is stored privately against your account as a list of user IDs and display names. Nobody else can read it, and the person you blocked is not told.
We use Firebase App Check (Play Integrity) to verify that requests come from a genuine copy of the app. This does not identify you personally — it attests to the app's integrity, not your identity.
We do not sell your personal information.
We share data with the following service providers, each under their own privacy terms:
We do not share your data with any other third party.
Recipes, likes, and saves are retained until you delete them or close your account. You can permanently delete your account at any time from Settings → Account → Delete account. This immediately and permanently removes your published recipes and their photos, your likes, your saved recipes, your public profile, and your sign-in record. This action cannot be undone. If you are unable to access the app, you may instead email hatemmahmoodsultan@gmail.com from the address associated with your account to request the same deletion.
Your block list is deleted along with your account. Reports you filed are not: they describe somebody else’s content rather than you, and a moderation queue that emptied itself whenever a reporter closed their account would be trivial to abuse.
Recipes are written by other users, not by us. We publish Community Guidelines setting out what is not allowed, and every recipe carries a Report recipe action and a Block this cook action in its ⋮ menu. Reported content is reviewed and may be removed; blocking takes effect immediately and is reversible from Settings → Safety → Blocked cooks.
Cookbook is not directed at children under 13, and we do not knowingly collect personal information from children under 13.
Data is transmitted over encrypted connections (HTTPS/TLS) and stored using Firebase's infrastructure. Firestore and Storage security rules restrict writes to the account that owns the content — no user can modify or delete another user's recipes.
We may update this policy from time to time. Material changes will be reflected by updating the "Last updated" date above.
Questions about this policy or your data: hatemmahmoodsultan@gmail.com