Privacy Policy

Last updated: October 19, 2026

Daily Bread is a personal cookbook app — iPhone and web — operated by an individual, Ryan Pliske, not a company. It keeps the recipes you cook, lets the friends you choose browse them, and lets you chat with those friends. This page explains what the app stores about you, what it does with it, and how to remove it.

What we collect

• Sign-in identity. You sign in with Google or Apple. From that provider we receive your name, email address, and (with Google) your profile photo, plus a unique user ID. We never see or store a password.
• What you write. The recipes you add — titles, ingredients, steps, notes, and any photos you attach or generate — and the handle, display name, intro line, and cookbook skin you set on your profile.
• Your friend graph. Friend requests you send or receive and the friendships that result, so the app knows whose cookbook you may see and who may see yours.
• Chat messages. What you send in a chat with friends — text, photos, videos, GIFs, and recipe cards — along with your name as the sender, your reactions to messages, when you last opened each chat, and who is in it. Messages are kept so the conversation is there for everyone in it the next time they open it.
• Device tokens for notifications. If you allow notifications, a Firebase Cloud Messaging token for each device, used only to deliver friend-request and new-message notifications to you.
• Usage data. On the iPhone app, which screens you open and which buttons you press, recorded through Google Analytics for Firebase and linked to your account. This tells us which parts of the app are actually used, so we know what to improve. It is not used for advertising, not sold, and never used to track you across other companies' apps or services. Google Analytics also estimates your general location (such as city and country) from your IP address, which it masks first.
• Approximate location. When you open one of our apps, sign in, link an app or send us a request, our servers use your IP address to estimate your approximate location: city, state or region, and country. We work this out on our own servers using an offline database, keep only that approximate location with the time it was seen, and do not keep your IP address. We use it to help with support requests and to understand where our users are. We never collect your precise location.

We do not collect your precise location or your contacts, and the app carries no advertising or cross-app tracking SDKs.

Recipe text and photos are processed by AI providers

Only the content needed for that one task is sent — never your friend list, email, or account details. The providers process it under their own privacy policies (Anthropic, OpenAI) and, under the API terms we use them on, do not train their models on it.

Our API keeps a temporary server-side log of import results for debugging — the parsed recipe and, for link imports, the cover-photo candidates it fetched from the page, tagged with your user ID. It is written only to the server instance's local disk, which Google discards whenever that instance is recycled; it is never written to our database, and photos you scan or upload are not kept in it.

How we use it

Everything above is used to run the app and nothing else: to show you your cookbook, to show your friends the recipes you've marked as visible to them, to list your name and handle so people can find and friend you, to deliver your chat messages to the people you sent them to, and to send friend-request and new-message notifications. We do not sell, rent, or share your information for marketing or advertising, and we never use it to build a profile of you.

Who can see what

• Your recipes are private to you unless you mark them public. Public recipes are visible to your friends — the people whose friend request you accepted, or who accepted yours — and to no one else.
• Your display name, handle, profile photo, intro line, and cookbook skin are visible to other signed-in users in the app's directory, so friends can find you.
• A friend who saves a copy of your recipe gets their own editable copy in their cookbook, with a credit line pointing back to you.
• Recipe text is protected by friendship. Cover photos are stored at an unguessable address that any signed-in user can load if they already have it, so a private recipe's photo isn't discoverable — but it isn't friendship-gated the way the recipe itself is.
• Chats are between friends only. Everything in a chat — messages, photos, videos, GIFs, recipe cards, and reactions — is visible to everyone who is a member of that chat, and to no one else. Any member can add another friend to a group chat, so a message you send to a group may be read by a friend of a friend who is added later. A message you send can be deleted by you for everyone in the chat; the text and any photo or video are then removed. A recipe card shows the recipe only while the owner still shares it with that reader.
• If someone reports your recipe or profile, the report — which item, the reason, and any note they wrote — is visible only to the developer.
If you block someone, the block is stored on your account and readable by the person you blocked, so that both apps can hide the two of you from each other; it is not shown to them as a notice.

Where it lives

Your data is stored in Google Firebase (Authentication, Firestore, Cloud Storage, and Cloud Messaging) on Google Cloud infrastructure in the United States. Access is scoped to your signed-in account and enforced server-side by database security rules.

Third parties we share with

Daily Bread relies on a small number of service providers, and shares the minimum each needs:

• Google Firebase — hosts your account, your cookbook, your photos, your chats, and the messages that deliver notifications. Firebase privacy.
• Google Analytics for Firebase — records the screens-viewed and buttons-pressed usage data described above, on the iPhone app only, to help us see which parts of the app get used. Not used for advertising and not shared for cross-app tracking. Firebase privacy.
• KLIPY — supplies the GIF search in chat on iPhone. When you search for a GIF, the words you typed, your region, and a content rating are sent to KLIPY; your account and identity are not. KLIPY privacy.
• Google Sign-In and Sign in with Apple — authenticate you. Only the name, email, photo, and user ID they return is stored on our side.
• Anthropic and OpenAI — power the import, estimate, and cover features, as described above.

There are no advertising or crash-reporting SDKs in the app. We do not sell your data, and nothing you do in Daily Bread is used to train AI models.

Security

Data is transmitted over HTTPS and stored encrypted at rest by Google Cloud. We never see or store a password; sign-in is handled by Apple, Google, and Firebase Authentication.

Data retention

We keep your data for as long as your account exists. Deleting your account removes it from our database and storage immediately; the temporary import log described above is discarded with the server instance that wrote it.

Deleting your account

You can delete your account from inside the iPhone app at any time: open Settings, tap the (i) next to Account, then Delete account. You'll sign in once more to confirm. That removes your recipes and photos, your profile and handle, your friendships and pending friend requests, your notification tokens, and your sign-in record. It cannot be undone. Copies of your recipes that friends already saved to their own cookbooks stay with them, since they are now those users' content. Messages you sent in chats also stay in those chats, because they are part of a conversation your friends still have; to remove them, delete them in the chat before you delete your account, or email us and we will remove them for you. If you can't reach the app, email us at the address below from the address on your account and we'll delete it within 7 days.

Children

Daily Bread is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has created an account, contact us and we will remove it.

Changes to this policy

If this policy changes, the date at the top will change with it and the current version will always be at this address.

Contact

Questions about this policy, or requests about your data, can be sent to tplisk@gmail.com.