Browser Transparency

Cookie & Browser Storage Policy

Clear breakdown of the essential session tokens and local browser storage keys getmenuqr uses—and what we never run.

Updated: November 12, 2026

1. How getmenuqr Uses Cookies & Local Storage

Unlike advertising-heavy SaaS sites, getmenuqr keeps browser storage strictly minimal and functional. We use only essential session cookies (from Supabase Auth when you log in) and browser localStorage to save drafts and make the studio responsive.

2. Categories of Storage We Use

MechanismPurposeScope
Supabase Auth Session TokensKeeps restaurant managers authenticated securely across page reloads and OAuth logins.Strictly Necessary (Owners)
Menu Studio Draft & Cache KeysStores unsaved guest edits in /editor and caches your active menu snapshot locally for instant loading.Functional (Cleared on Sign Out)
Onboarding Completion FlagRemembers whether you finished the 5-step setup wizard so the modal does not reappear unexpectedly.Functional (Per User ID)

3. Third-Party Advertising & Analytics Trackers

getmenuqr does not embed third-party ad-retargeting pixels, Meta/Google Ads cookies, or cross-site diner tracking scripts on public QR menu pages (/m/[slug]). Guests can scan table QR codes privately without cookie popups blocking their meal order decisions.

4. Managing or Clearing Browser Storage

Signing out from getmenuqr automatically clears cached restaurant menu entries from localStorage. You can also inspect, block, or delete cookies and site data at any time through your browser's Privacy & Site Settings. Note that disabling essential session cookies will prevent restaurant dashboard authentication.

For related details, see our Privacy Policy.