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. Courtesy belongs in comments, questions, answers, and public recipe write-ups.

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 Lutong Bahay to insult, threaten, or target people. Do not attack someone for who they are, where they come from, or how they cook at home. Community features are for cooking, not for harassment or hate.

TODO. Supply a reviewed legal definition of prohibited harassment and hate if the operator wants one published here.

Do not flood comments, questions, or recipes with ads, repetitive posts, or attempts to trick people. Do not use the community to phish for passwords, sell unrelated products, or send people to harmful links.

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. Cooking information is user-generated and may contain mistakes; cooks should still follow reliable food-safety guidance.

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. Family recipes and personal adaptations can be credited in the recipe.

The Copyright page explains how ownership concerns can be raised. A designated copyright contact email is not published until it is supplied.

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.

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, copyright, or rights concerns — not to harass someone you disagree with about a dish.

TODO. Describe any contact channel besides in-app reporting. Do not invent a support email.

Staff can review reports, remove community-facing content, and restrict accounts. Public recipes, comments, questions, and answers may be hidden from the community when they break these rules.

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