Recipe Reformatter uses role-based access controls and row-level security so users can access only their own profile and planner records unless a feature is explicitly marked public.
Imported recipes, pasted text, uploaded URLs, and image intake metadata are stored as user-associated content for parsing, review, and meal-planning workflows.
Operational logs, error reports, and deployment infrastructure may temporarily process technical metadata required to keep the service available.
- Sensitive credentials must be stored only in environment variables, never in source code.
- Account data may be reset, migrated, or corrected as the schema evolves.
- Backups and retention periods follow the Supabase project configuration selected by the operator.