Contributor policy

Terms and privacy expectations

Our Heritage Kitchen is built for preserving family recipes with clear ownership, intentional publishing, and limited data collection.

Contributor content

Only add recipe text, family notes, stories, and images that you created, own, have permission to use, or can replace with your own material.

Published recipes can be viewed by anonymous visitors. Draft recipes are intended to stay private to your signed-in dashboard until you choose to publish them.

If a content ownership concern comes up, the maintainer can review, correct, unpublish, or remove the recipe content. Use the project repository issue tracker or maintainer contact channel to request a correction, unpublishing, or removal.

Data and privacy

The app uses Google sign-in through Supabase Auth so recipes, drafts, ratings, and uploads can be tied to the signed-in contributor who owns them.

Recipe fields, ingredients, steps, timing, family or origin details, draft status, published status, ratings, and uploaded recipe images are stored to support the recipe archive workflow.

Uploaded recipe images are stored in owner-scoped paths. Stored images are public-read assets so published recipes can load for visitors without requiring sign-in.

Retention

Contributor content remains in the project until it is edited, unpublished, deleted, or removed by the maintainer for ownership, privacy, or project-maintenance reasons.

Back to recipes