Cookie Policy
The cookies and browser storage Dinebase uses, and how to control them.
Version 1.0 · Last updated 2026-07-27
Dinebase uses a small number of cookies and browser storage entries. We do not use advertising cookies and we do not track you across other websites.
1. What we use
| Name / purpose | Type | Why | Retention |
|---|---|---|---|
| Authentication session | Local storage / cookie | Keeps you signed in and lets the app call the backend as you | Until sign-out or session expiry |
| Keep me signed in preference | Local storage | Remembers whether the session should survive closing the tab | Until changed |
| Shared device flag and device identifier | Local storage | Marks a tablet as a shared restaurant device so Host View activates automatically | Until the device is unmarked |
| Active restaurant selection | Local storage | Remembers which workspace you last used | Until changed |
| Language preference for legal pages | Local storage | Remembers whether you read these pages in English or Swedish | Until changed |
| Load balancing and security | Cookie set by our hosting provider | Routes requests and protects against abuse | Session |
All of the above are strictly necessary for the service to work or are direct preferences you set yourself. We do not currently run analytics or marketing cookies on the application. If that changes, this page will be updated and consent will be requested where required.
2. Public booking pages
A restaurant's public booking page uses only what is needed to complete a booking. If the restaurant enables card holds, the payment provider sets its own cookies to prevent fraud. If a map is shown, the maps provider may set cookies when the map loads.
3. Controlling cookies
You can clear or block cookies and local storage in your browser settings. Blocking the strictly necessary entries will sign you out and prevent the application from working.
4. Questions
Write to [PRIVACY EMAIL].