Cookie menu privacy
The public cookie menu maker does not require an account. Menu names, photos, ingredient notes and PDFs are processed in your browser memory. They are not uploaded, stored in a database or sent to an analytics service. Refreshing or closing the tab can lose them.
Anonymous activity counts
We send only one of five fixed event names (page view, editing started, template selected, PDF export succeeded, PDF export failed) and the chosen template (Classic, Rustic or Gold) to our own server. No menu content, filenames, user identifiers or error details are included. These events do not set cookies, use local storage or use a third-party tracking script. Offline events are not queued.
Events appear in structured server logs. Your hosting provider may separately process network information, including IP addresses, in its standard access logs. The deployment operator must choose and disclose log retention before public launch. Event counts are approximate, not unique visitor counts.
Private preview deployments may send existing same-origin access cookies to pass the hosting provider’s login protection. The event payload stays the same, and the event handler does not read or log these cookies. Public production builds omit credentials from activity requests.
Existing account pages
The optional account and dashboard routes use the existing Supabase authentication cookies. Using those pages is separate from making a cookie menu. No cookie-menu contents are linked to accounts.
Before sharing
Use only photos you have permission to use. Verify all ingredient and allergen information yourself; the tool does not validate food safety or legal labeling requirements.