Cookie Policy
Last updated
Concept project. Dummy Waiter is a concept and portfolio project built by an independent developer. It is not a commercial service. No hardware is for sale, no payments are taken, and nothing on this site is an offer to sell. This page describes how the demonstration site and working prototype actually behave.
This page lists each cookie and browser storage item Dummy Waiter uses, what it is for, how long it lasts, and what falls into each category. The list is short because the site sets only what it needs to work.
On this page
In short
- Dummy Waiter uses strictly necessary cookies and browser storage only. They keep you signed in, run the demo, and remember small interface choices.
- There are no analytics, advertising, social media, or cross-site tracking cookies or scripts.
- Visiting the landing page or the legal pages sets no cookies. Cookies appear only when you sign in or open the demo.
2.What we use
Everything below is strictly necessary: the site or the feature you asked for cannot work without it. Under the EU ePrivacy Directive (Article 5(3)) and UK PECR (regulation 6), strictly necessary storage does not need your consent, which is why the cookie notice is informational and has no accept or reject switches.
Cookies
| Name | Purpose | Set when | Duration | Category |
|---|---|---|---|---|
sb-[project-ref]-auth-tokenMay appear as | Keeps you signed in. Holds your session so the server knows which account a request comes from. | When you sign in to the prototype (email link, password, Google, or a staff access code). Refreshed while you use the dashboard. | Up to 400 days (the browser maximum), or until you sign out. | Strictly necessary |
sb-[project-ref]-auth-token-code-verifier | A short-lived security value that lets email-link and Google sign-in finish safely (PKCE). | When you start signing in. | Removed once sign-in completes. It is not used for anything else. | Strictly necessary |
dw_demo | Remembers that you chose the no-login demo, so the dashboard shows sample data instead of asking you to sign in. It grants no access to real data and contains no personal information (its value is 1). HttpOnly, SameSite Lax, and Secure in production. | When you open the demo. | 24 hours, or until you leave the demo. | Strictly necessary |
In the cookie names, [project-ref] stands for the identifier of the Dummy Waiter database project.
Browser storage
| Name | Type | Purpose | Duration | Category |
|---|---|---|---|---|
dw_cookie_notice | Local storage | Remembers that you dismissed the cookie notice. It stores only a version label, v1, so the notice can return if this policy changes materially. | Until you clear your site data. | Strictly necessary (remembers your choice) |
dw_staff_session | Session storage | Remembers which staff member has unlocked the dashboard in this tab (staff ID, name, role, restaurant ID, and whether they may close a shift), so a page refresh does not lock you out. | Until the screen locks, after 10 minutes of inactivity, or when you close the tab. | Strictly necessary |
dw_open_record_after_onboarding | Session storage | A one-time flag that opens the recording window right after first-time setup. | Removed as soon as it is used, or when you close the tab. | Strictly necessary |
dw_demo_state_v1 | Session storage | Keeps the changes you make in the demo (for example, orders you add) while you click around in the same tab. It holds sample data only. | Discarded after 90 minutes, or when you close the tab. | Strictly necessary |
3.Third parties, analytics, and advertising
We do not use analytics, advertising, or tracking technologies. On the effective date of this policy we checked the site’s source code and dependencies and found none of the following:
- Analytics or measurement tools, including Google Analytics and Vercel Analytics.
- Advertising networks, retargeting pixels, or conversion tracking.
- Tag managers, session replay, heat-mapping, or A/B testing tools.
- Social media buttons, embedded videos, or third-party chat widgets.
Typefaces are self-hosted, so loading a page does not contact Google Fonts or any other font service. Our hosting providers keep standard server logs (such as IP address and the page requested) to deliver the site and keep it secure. We do not use those logs to track visitors.
If you choose “Continue with Google” on the sign-in page, your browser goes to Google’s sign-in screen, and Google may set its own cookies there under the Google cookie policy (opens in a new tab). We have no control over those. Links to other sites, such as GitHub, work the same way.
If we ever add non-essential cookies, we will ask for your opt-in consent before they are set and update this policy first.
4.Managing cookies and browser storage
You can view, block, and delete cookies and site data in your browser settings, and clear local and session storage there too. Because everything we use is strictly necessary, blocking it will stop some features working: you will not be able to stay signed in, and the demo will ask you to start again.
To see the cookie notice again, clear this site’s data in your browser. Signing out of the dashboard, or leaving the demo, removes the matching cookie.
We do not track you across sites, so a Do Not Track or Global Privacy Control signal has nothing to switch off. We treat those signals as honored by default.
5.Changes and contact
We will update this page, and its date, if the cookies or storage we use change. How your personal information is handled more generally is explained in the Privacy Policy.
Questions about cookies: hello@dummywaiter.com.