FoodLore — Terms of Use

Last updated: 14 October 2026

These terms are the agreement between you and FoodLore for using the app. By using FoodLore you accept them. If you do not accept them, please do not use the app. Our Privacy Policy explains what happens to your data and forms part of this agreement.

Your archive is yours

The recipes, photos and words you keep in FoodLore belong to you. You give us only the permission needed to run the features you turn on: to store your archive on your phone, to send a scan image to our scan service when you scan, to keep your profile when you sign in and make its fields readable to other signed-in cooks, and, with an active Premium subscription, to copy your archive to your cloud and to keep it and your collections in sync across the devices you sign in on. You are responsible for having the right to keep and upload the content you put into the app.

Your account

An account is optional. The local-only app needs none.
FoodLore is intended for adults. You must be at least 18 years old to create an account or use its signed-in services. Parental permission does not make someone under 18 eligible for an account.
Use an email address you control, and keep your sign-in credentials safe. You are responsible for activity that happens through your account.
Your editable profile fields are visible only to you while reviewed community profiles are being prepared. Other signed-in cooks can check whether a handle is taken without reading your profile. Only you can request a new temporary link to your profile photo; older links may work until they expire.
One account per person unless we agree otherwise. Do not share an account or resell access to it.
Tell us promptly if you believe your account has been used without your permission.

Using FoodLore fairly

Do not use FoodLore or the scan service for anything unlawful, or to store content you have no right to.
Do not try to break, overload, probe or bypass the service or the scan quota, and do not access data that is not yours.
Do not copy, resell or redistribute the service or the scan results as a product of your own.
We may suspend or end an account that abuses the service.

Free scans and Premium

Every account includes three free scan credits, for life. Each credit allows up to three upload attempts across its lifetime. Free accounts may submit up to 3 accepted uploads per rolling hour; Premium accounts may submit up to 30 accepted uploads per rolling hour and have unlimited scan credits. The hourly allowance does not restore free credits or attempts. The on-device archive and the local features other than collections are free, with no account needed, and that will not change. Collections are the exception: they need an account and an active Premium subscription. A cook who never signs in still has a complete archive, just without collections. Premium is the optional paid tier, and it unlocks four things: cloud backup and sync, relatives sharing, collections, and unlimited scans. Premium is tied to the store account you bought it with, and the plan currently offered, its price and its billing period are shown in the app before you subscribe.

Subscriptions, renewal and cancellation

Auto-renewal. A Premium subscription renews automatically for the same billing period until you cancel it. Your store account is charged when you confirm the purchase and again at each renewal, within 24 hours before the current period ends.
Price and period. The exact price and billing period for your store account are shown on the paywall before you buy, in your store's local currency. If the price changes, the store will show you the new price and ask for your agreement before it applies to you.
Cancellation. Cancel any time in your store's subscription settings — Google Play → Payments & subscriptions → Subscriptions, or the App Store → your account → Subscriptions. Cancel at least 24 hours before the current period ends to avoid the next renewal. Deleting the FoodLore app or your FoodLore account does not cancel the subscription; cancel it in the store.
Refunds. Payments are handled by the app store, and refunds are given under that store's policy. We cannot process store refunds ourselves, but we are glad to help you find the right door.

Relatives sharing

Relatives sharing is an optional Premium feature, and it is read only. You invite a relative, and they can read the shelf you share, but the app has no copy mechanism: a relative can never copy a recipe into an archive of their own, and can never change your recipes or your archive. You can revoke a relative's access at any time, and a relative can leave the shared shelf at any time.

Invite only, owner controlled. You decide who is invited, and you can revoke an invitation at any time. Revoking it ends that relative's access.
Read only for the relative. Your whole archive appears to the invited relative as a shared shelf they can read. They cannot change your recipes or your archive, and they cannot copy a recipe out of it.
Owner revokes. You can revoke access at any time. A relative cannot save, copy or take your recipes with them.
The relative can leave. A relative can remove the shared shelf at any time. Leaving ends their own access only: it does not delete or change your recipes, and it changes nothing else on your side. You can invite them again.
Never public. There is no public feed, no public link, no comments, and relatives cannot reshare your archive with anyone else.

Publishing, retention and your rights

Nothing is published today. FoodLore has no public feed and no public links, and your archive is not made public by subscribing, by letting a subscription lapse, or by going inactive. If a future version offers a way to make a recipe publicly searchable, it will be an explicit choice you make for that one recipe, and never a consequence of your subscription status or inactivity.

Future community features

The community feed is not active in the current version. There are no feed posts, comments, reactions, in-app report controls or block controls today. If FoodLore later enables community publishing, that feature will be governed by the rules below and will launch only with the reporting, blocking and moderation operations needed to support them.

Community content must be lawful and respectful. Do not bully, harass, threaten, intimidate or target a person for abuse or ridicule. Do not post sexual exploitation, child sexual abuse material (CSAM), or content that sexualises or endangers a child. Do not use the community features to share illegal content, impersonate someone, publish private information, or evade a restriction. We may remove content and restrict accounts when these rules are broken. If you see a problem after community launches, use the in-app report or block control, or write to legal@foodlorefamily.com.

Enforcement is based on verified strikes, recorded by a human moderator. A first low-level violation normally receives a warning. Two low-level strikes in 90 days, or one serious violation, may result in a temporary suspension. Three low-level strikes in 90 days, repeated serious violations, or one severe violation may result in permanent-ban review. Severe cases, including CSAM, credible threats or sexual exploitation, may skip lower steps. A moderator makes the decision; automated screening, if introduced, may assist triage but does not itself create a strike or ban.

We will tell you the reason for an enforcement decision where it is safe to do so. You may appeal by writing to legal@foodlorefamily.com; an appeal is reviewed by a human who was not the original decision-maker where practical. These future processes do not mean that community moderation or its tools are operating today.

Your recipes are kept for you, not for a subscription. If Premium lapses, or you stop using FoodLore for a while, the recipes you own stay stored and stay readable by you. We do not delete your recipes because a subscription ended or an account went quiet.

You are in control of deleting what you own. You can delete any recipe you own inside the app at any time; if it has a copy in your cloud, that goes with it, whether or not Premium is still active. You can also ask us what recipes and what personal data we hold for you. If you cannot sign in, write to legal@foodlorefamily.com and we will help you delete your data or answer an access request.

Removal is bounded, and we will not overstate it. We remove the entry you ask us to remove, and because the app has no copy mechanism we can account for what was held through FoodLore. If a recipe is ever made public in a future version, we could remove the original entry, but we could not prevent someone else from recreating it or writing their own version from what they saw. We say that plainly rather than promise a removal we cannot deliver.

Changes and availability

We may update the app and these terms over time, and we may change or end cloud features (accounts, sync, scanning) as the service evolves. Cloud backup, sync, relatives sharing and collections require an active Premium subscription. Your profile does not: a signed-in free account can set a display name and handle, add a profile photo, and fill in a bio and a website. If a change is significant, we will be clear about it in the app or by email. The cloud features need a working network and our providers; they are provided as they are, without promises of uninterrupted availability. The phone-only app keeps working offline regardless.

Ending this agreement

You can stop using FoodLore at any time, and you can delete your account and its data from the app. We may end this agreement if you break these terms or abuse the service. Sections that by their nature should survive — content ownership, liability and this one — survive.

Liability

To the extent the law allows, FoodLore is provided as is and we are not liable for indirect or consequential losses, or for content you lose through misuse or through deleting something. Nothing in these terms limits the rights you have under mandatory consumer law, or our liability where it cannot lawfully be limited.

Contact

Anything about these terms: write to legal@foodlorefamily.com.