Community Guidelines

Talk about food the way you would in a shared kitchen. Disagree about a recipe if you need to, but keep the person on the other side of the comment in mind.

TODO. Add any extra examples of respectful and unwelcome tone the operator wants listed.

Public recipes, comments, and questions work best when they help someone cook. Clear ingredients, steps, and kitchen context are more useful than vague or teasing replies.

Do not use Personal Recipe Memory to insult, threaten, or target people. Community features are for cooking, not for attacking identity, origin, or anyone’s home kitchen.

TODO. Supply a reviewed definition of prohibited harassment and hate, including how reports are assessed.

Do not flood comments, questions, or recipes with ads, repetitive posts, or attempts to trick people.

TODO. List any commercial or promotional rules once they exist.

Home cooking has real risks. Do not post instructions that are meant to cause harm, or that you know are unsafe, as if they were a recipe to follow.

Ordinary family recipes and honest technique notes are welcome. This section is about deliberate harm, not every kitchen disagreement.

TODO. Clarify how food-safety reports are reviewed. Do not invent a certification or inspection process.

Share cooking you have the right to share. Do not upload photos or recipe write-ups that you know belong to someone else if you do not have permission.

The Copyright page describes how ownership concerns can be raised once a contact method is provided.

Keep recipes, photos, comments, and questions suitable for a family cookbook. Sexual content, graphic harm, and material that does not belong next to dinner instructions should not be posted.

TODO. Add any additional content categories the operator will prohibit, after review.

When you are signed in, you can report another person’s content from the recipe community tools in the app. Use reports for genuine safety, spam, or rights concerns.

TODO. Describe what happens after a report, and any contact channel besides in-app reporting. Do not invent a support email.

The product includes staff moderation tools that can remove community-facing content and restrict accounts. Those tools exist; the exact ladder of warnings and penalties has not been published here.

TODO. Publish enforcement steps, timeframes, and appeal options only after they are decided. Do not invent strike counts or automatic bans.