Privacy Policy

Effective 8 October 2026

This policy explains what information RecipeBookManager (the app at recipebookmanager.com, “we”) collects, how we use it, who helps us run the service, and the choices you have. RecipeBookManager is a small, independently run recipe app. We do not sell your information, show advertising, or use it for advertising.

1. Information we collect

Account and sign-in information

• Email address — your account is identified by it.
• Password — if you sign in with email and password, your password is handled by our sign-in provider, Clerk, which stores it only in hashed form. We never see or store your password in readable form.
• Username (optional) and your account role.
• Earlier sign-in records — before October 2026 RecipeBookManager ran its own sign-in. For a limited time after the move to Clerk we keep the hashed password and sign-in status from that system so that we can return to it if the move has to be reversed; we then delete them.

Information from Google Sign-In

If you choose “Continue with Google”, Google shares the following with us (through Clerk) under the openid, email and profile permissions only:

• your Google account identifier,
• your email address and whether Google has verified it,
• your name and profile picture as set in your Google account.

We use this information only to sign you in, to recognise you as the same person on later visits, and to connect your Google sign-in to your RecipeBookManager account when the verified email addresses match. We do not request or access your Gmail, Google Drive, contacts, calendar, photos or any other Google data, and we cannot post anything to your Google account. RecipeBookManager’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: we do not sell it, use it for advertising, or transfer it to anyone except as needed to provide sign-in (our provider Clerk), to comply with law, or with your consent.

Content you create

Recipes (titles, ingredients, steps, notes and tags), recipe photos, cookbooks and their collaborators, pantry and inventory items with quantities and expiry dates, grocery lists, cooking history, ingredient substitutions you accept, comments, saved recipes, share links you create, friends, friend groups, muted users and any reports you file.

Activity inside the app

Simple records of what you do in RecipeBookManager — for example which recipes you open, cook or save — so that suggestions such as “What should I cook?” and your activity feed work. These records stay in RecipeBookManager and are not shared with advertisers or data brokers.

Technical information

• IP address — used briefly to limit repeated requests and protect the service from abuse; these records expire on their own after a short time.
• Request logs kept by our hosting provider for security and troubleshooting.
• Visit statistics — the app uses Cloudflare Web Analytics, which counts page views in aggregate (for example the page visited, the referring site, browser type and country). It sets no cookies and does not track you across other websites.
• Change history — a record of changes made to recipes and other content (which account changed what, and when), used for safety and support.
• Device information that Clerk uses to recognise a new device and ask for an emailed verification code.
• Push notifications — only if you turn them on: the notification address your browser gives us, which notifications are delivered through your browser’s push service (for example Google, Mozilla or Apple).

Recipe import

If you import a recipe from a web page, our server fetches the page at the address you give it in order to read the recipe. That website sees a request from our server, not from you.

2. How we use information

• To provide RecipeBookManager: your account, your recipes, cookbooks, pantry, suggestions and sharing.
• To show your shared content to the people you choose (friends, groups, collaborators, people with a share link) — and to keep private content private.
• To keep the service secure, prevent abuse and fix problems.
• To contact you about your account if needed.

We do not sell personal information, do not use it for advertising, and do not send your information to third-party artificial-intelligence services.

3. Service providers

We use these companies to run RecipeBookManager; they process information on our behalf:

4. Who can see your content

Content you mark private is visible only to you. Content you share is visible to the people you share it with — friends, a friend group, cookbook collaborators, or anyone holding a share link you created. Your username may be shown alongside content you share or comment on.

5. Security

Connections to RecipeBookManager are encrypted (HTTPS). Passwords are stored only in hashed form by Clerk. Access to the systems that hold your data is limited to the people who run the service. No system is perfectly secure, but we take reasonable steps to protect your information.

6. Keeping and deleting information

We keep your account and content for as long as your account exists, so that your recipe book is there when you come back. RecipeBookManager does not yet have an automatic “delete my account” feature, and removing or losing your sign-in (for example, your Clerk account) does not automatically erase your recipes or other content. To have your account and content deleted, email us at the address below; requests are handled by hand, and we will confirm when it is done. Copies may remain in backups for a limited time until they expire.

7. Your choices

• You can edit or delete your recipes and other content in the app.
• You can choose who sees what you share, and turn notifications on or off.
• You can sign in with email and password instead of Google, and you can remove RecipeBookManager’s access in your Google account’s security settings at any time.
• You can ask us for a copy of your information, or to correct or delete it, by email.

8. Children

RecipeBookManager is not intended for children under 13, and we do not knowingly collect their information.

9. Changes

If we change this policy we will update this page and its effective date. Significant changes will be announced in the app.

10. Contact

Questions or requests about your information: bagman08142025@gmail.com.