Terms

Lutong Bahay is a cookbook product for saving recipes and, if you choose, sharing them with other home cooks. The public website is the origin configured for this product (see the Website line on this page).

TODO. Add the legal statement that using the service means the reader agrees to these Terms, once counsel drafts that language.

TODO. State who may create an account, including age and any geographic limits. Do not invent a minimum age or restricted countries.

Some features require an account. You create one with an email address and password. You can update profile fields such as username, display name, bio, and cooking level. You can download your own data and request account deletion from Account Settings.

Keep your sign-in details to yourself. The product uses session cookies so a signed-in visit can continue across pages.

TODO. Add rules for account security, one-person-per-account, and what happens if sign-in details are misused.

User content includes recipes, photos, comments, questions, answers, reports, and cooking notes that people add to the app. You should only upload material you have the right to share.

TODO. Define what users may upload, what they must not upload, and the license (if any) granted to operate the service. Do not invent a broad content assignment.

In the product, recipes you create are stored on your account. You can keep them private or publish them. The app is a place to store and share cooking instructions. It does not decide, by itself, who owns a family recipe or a photograph.

TODO. Add the operator’s position on recipe text, photos, and third-party material. Do not invent copyright ownership claims.

If you mark a recipe public and publish it, other people may find it in Discover, Search, and on your public profile. They may also comment, ask questions, like, or save it, according to the features on that page. By publishing a recipe, you give the app permission to display that public recipe on those surfaces.

Private recipes and drafts remain non-public under normal application behavior. They are not listed in Discover, Search, or another cook’s public profile.

TODO. Clarify whether public sharing can be reversed, and what other people may do with a public recipe (save, cook, or copy) once legal language exists.

Community spaces are for cooking help and kitchen conversation. The Community Guidelines describe expected behavior, including respect, spam, harassment, hate, scams, copyright, inappropriate content, and intentionally dangerous cooking information.

Cooking information on Lutong Bahay is written by users and may contain mistakes. The app does not provide medical, nutrition, or professional food-safety advice, and it does not claim food-safety authority.

You are responsible for following appropriate food-safety practices and reliable official guidance when handling potentially hazardous food. Cooking involves heat, ingredients, and allergens. Use your own judgment and seek professional advice when you need it.

TODO. Add any extra food-safety or allergen disclaimer language required by counsel. Do not invent certifications or inspection claims.

The Lutong Bahay name, layout, and product design belong to the people who operate the app, except for user content and third-party marks. Users should upload recipes and photos they have the right to share. The Copyright page explains how suspected infringement can be reported.

TODO. Name the rights holder and any licensed assets. Do not invent trademarks, patents, or company registration numbers.

Do not upload photos or recipe write-ups that you know belong to someone else unless you have permission. Family recipes and personal adaptations can be credited in the recipe itself. Signed-in users can report suspected copyright infringement from the app.

TODO. Provide the official copyright contact email and any statutory notice procedure when those details are supplied.

Signed-in users can report certain content from the app. Staff tools can hide or remove community-facing material. Reports are reviewed with the product’s moderation features. There is no promised review time on this page.

TODO. Describe the reporting process, review timelines, and appeal options once they are defined. Do not invent SLA times.

Staff can restrict an account when moderation tools are used. The product can show a signed-in person when their account has a moderation restriction.

TODO. Explain when accounts may be limited or closed, and whether access to private recipes continues during a restriction.

The app may change over time and may be unavailable for maintenance, errors, or hosting issues. Features can be added, limited, or removed.

TODO. Add any uptime, backup, or “as available” language the operator wants, without promising a service level that has not been offered.

TODO. Supply warranty disclaimer language reviewed by counsel. Do not paste a generic “AS IS” clause as if it were already adopted.

TODO. Limitation of liability, indemnity, and related risk-allocation clauses have not been supplied. Leave this section empty of invented dollar caps, venue, or governing-law text until counsel provides them.

You can request account deletion from Account Settings. A request is reviewed before final removal and is not completed instantly. You can cancel while it is pending. After processing, your recipes, profile, community activity, and other account data may be removed.

The operator may also restrict or close accounts through moderation tools. Details of residual copies, backups, or legal holds have not been published here.

TODO. Describe any additional operator termination rights and what may remain after deletion once those practices are defined.

The product and these pages may change as the cookbook grows.

TODO. Explain how these Terms may be updated and how notice will be given.

TODO. Provide a terms-of-service contact. Do not invent an email address or mailing address.