Privacy

Who operates this site

[REPLACE]
[REPLACE]
[REPLACE]

Information used by account features

Account records include your name, email, verified-email status, salted password hash, account role, terms receipt and timestamps, setup progress and saved sample menus. Optional cuisine or hosting preferences are saved only when you choose to save them. Do not enter medical information or guest details in those preferences.

A profile photo is optional. Uploaded JPEG, PNG or WebP photos are resized and re-encoded without the original image metadata. Your account photo is private to your signed-in account. You can replace or remove it from your profile, and download it in your account export.

Sessions and expiring authentication records support sign-in. Passwords are hashed by Better Auth; plaintext passwords are not stored. Customer verification links use keyed token hashes and encrypted verification payloads. Rate-limit keys are keyed hashes. Authentication links are passed in URL fragments and removed from the address bar before submission. Request bodies and tokens are not intentionally logged by the application.

Cookies and access

Essential session cookies are HttpOnly, SameSite=Lax and Secure on HTTPS. Sessions expire after seven days without refresh. Signing out revokes the current session; password reset revokes all sessions. Protected endpoints check your verified email and account permission. Retired chef accounts cannot sign in or use existing sessions; the configured owner retains account access.

The planner draft is held in browser session storage, separate from your account profile. Signed-in accounts save menus in their account; guest menu bookmarks stay in browser session storage. This version does not add advertising or marketing trackers.

Existing records

Removing chef features does not delete existing profiles, photos, menus, availability, invitations, applications or request history. They are no longer published as active chef listings. Account exports and authorized operator handling remain available for retained information. Existing request records may contain event details and past contact exchanges.

Service providers

Hosting: Vercel. Database: Neon (US East, Northern Virginia). Transactional email: Resend (owner-only test sender). These services process the information needed to host the app, store records and deliver requested account emails. Independent websites have separate policies.

Retention and deletion

Scheduled maintenance removes expired verification tokens, sessions and rate counters. Automatic deletion of account and marketplace content is paused while the operator reviews retention for the retired chef features. Existing profiles, applications, invitations, menus, photos, availability, requests, notifications and privacy records remain in the active database unless an authorized account deletion or operator action removes them. A retention schedule must be finalized before public registration.

Vendor retention is separate from active-database cleanup: backups — [REPLACE]; host logs — [REPLACE]; email records — [REPLACE]. Operator review and monitoring are required; these settings do not prove that cleanup or vendor deletion has occurred.

Your choices

Account Settings provides profile editing, optional preference removal, data export, privacy requests and account deletion after a recent sign-in. Deletion removes related active database records; it does not erase separately held recipient records, vendor backups or external agreements. For a retired chef account or pre-account record, use the operator contact above. Public registration remains closed while that contact is unfinished.