Cookies and Browser Storage Policy
Last updated: 29 October 2026
This Cookies and Browser Storage Policy (the "Policy") sets out the cookies and browser storage items used on this website, Qder.ai (the "Site"). References in this Policy to "Qder" are to the operator of the Site. The Site uses no advertising cookies, no tracking cookies and no identifying analytics cookies. The Site uses five cookies (qder_session, qder_privacy, qder_next, qder_ref and, for Qder staff only, CF_Authorization) and a small number of items held in the browser storage of the person using the Site (the "User") in connection with the Qder service (the "Service"), all of which are listed in this Policy. No banner requesting consent is displayed, since nothing that requires consent runs before the User has switched it on, as set out below in respect of the items in the table.
This English version is provided for convenience. The Hebrew version of this document is the governing version: מדיניות עוגיות ואחסון בדפדפן.
1. Cookies and browser storage items in use
| Name | Type | Purpose | Duration |
|---|---|---|---|
qder_session | Cookie | To record that the User is signed in. It is sent only over HTTPS, cannot be read by JavaScript and is never sent from another site. | Until the User signs out or the session lapses |
| Table session | Browser storage (sessionStorage) | To record the table at which the User is seated as the User moves between screens. It is not a cookie and is therefore never sent automatically with a request. | Until the tab is closed and, in any event, the server ends the session after 4 hours |
| Random visitor string | Browser storage | To give the conversation on the home page a random "name", so that the server can apply rate limits without identifying the User. It is linked to nothing else. | Until the tab is closed |
| Allergens named by the User in the conversation | Browser storage (sessionStorage) | Sensitive information. When the User informs the digital waiter of an allergy, the User's browser records which allergens were named, so that the menu can mark them at once. It is kept on the User's device only, is never sent to any measurement tool and never leaves that table. | Until the tab is closed |
| The User's basket | Browser storage (sessionStorage) | The items the User has chosen but not yet sent to the kitchen, so that they are not lost if the page is refreshed. It is tied to the table session. | Until the tab is closed |
| Menu language | Browser storage (sessionStorage) | To record the language in which the User asked to view the menu. | Until the tab is closed |
| Transfer of the conversation from the concierge to the table | Browser storage (sessionStorage) | So that what the User typed before scanning the code is carried over with the User to the table screen. | Deleted as soon as it is read |
| The User's place on the waiting list | Browser storage (localStorage) | The identifier of the User's entry on the branch's waiting list, so that Qder can show the User the queue after the page is refreshed. | Until the User leaves the list or clears the Site's data |
| Site language | Browser storage (localStorage) | To record whether the User chose Hebrew or English on the diner pages. | Until the User clears the Site's data |
qder_privacy and the preference stored alongside it | Cookie and browser storage (localStorage) | The User's decision in the settings panel further down this page (section 5). It holds one letter and one digit per category and nothing else: no name, no identifier and no link to any account. The server reads it only in order to decide whether a measurement script may run at all. | One year, or until the User clears the Site's data |
| Message the User has started typing | Browser storage | So that the question the User wrote on the home page is carried over with the User to the chat screen. | Deleted as soon as it is read |
| Assistant panel state (staff only) | Browser storage | To record whether the assistant panel was open. | Until the tab is closed |
| Copy of the conversation with the digital waiter | Browser storage (localStorage) | So that the conversation at the table is not lost if the User locks the phone or refreshes the page. It is kept on the User's device only, and for that table only. | 48 hours, after which it is deleted from the device |
| First-time hints at the table | Browser storage (localStorage) | To record which short explanations the User has already seen, so that they are not shown again. It does not identify the User. | Until the User clears the Site's data |
| Payment processor selected on the setup screen (staff) | Browser storage (localStorage) | To record which payment processor was selected on the setup screen, so that the selection is not lost if the page is refreshed. No keys are stored in it. | Until the User clears the Site's data |
qder_next | Cookie | When signing in with Google or Microsoft: to record the page to which the User is to be returned once the provider has confirmed the sign-in. It contains a page address and nothing else. | 10 minutes; deleted as soon as the sign-in is completed |
qder_ref | Cookie | Created only when the User opens a personal referral link (an address of the form qder.ai/r/...), as set out in the referral program terms: to record the referral code and when the link was opened, signed, so that a business application later sent from the same browser is attributed to the referrer. It contains nothing about the User, is sent only over HTTPS and cannot be read by JavaScript. A further referral link opened during that period does not replace it. | 60 days, or until the User clears the Site's data |
| "Not now" on the passkey suggestion | Browser storage (localStorage) | To record that the User asked not to be shown the passkey suggestion on the account page again. | Until the User clears the Site's data |
| Website chat | Browser storage (localStorage) | The identifier of the User's conversation with Qubi and a random key for it, so that the conversation continues as the User moves between pages, together with a record of which reply from the team the User has already seen. It contains nothing about the User. | Until the User starts a new conversation or clears the Site's data; the conversation itself is deleted on the server 90 days after its last message |
| Status page language | Browser storage (localStorage) | On status.qder.ai: to record whether the User chose Hebrew or English. | Until the User clears the Site's data |
| CF_Authorization (Qder staff only) | Cloudflare cookie | Created only for a person signing in to Qder's internal operations console through Cloudflare Access. Diners and restaurants never receive it. | Up to 12 hours |
Most of the items listed above are necessary for the Service that the User requested. Some items keep a preference or convenience only (the language of the Site, of the menu and of the status page, the tutorial hints, "Not now" for the passkey offer, the state of the assistant window and the selected payment provider): they are created only as a result of the User's own action, serve that action only, are kept on the device only, and may be cleared at any time in the settings panel in section 5. The measurement tool (see section 2) runs by default in Israel and may be switched off in the settings panel; for a visitor from the European Economic Area, the United Kingdom or a country that cannot be identified, it runs only after the User has switched it on in the settings panel. The conversation with the digital waiter is kept in three places: (a) a copy in the User's browser, for 48 hours (see the corresponding row of the table above); (b) the most recent messages, on the server, for 24 hours, linked to the table rather than to the User; and (c) a scrubbed log of the conversation (containing no name, email address or telephone number), for 90 days, for the purpose of improving the digital waiter: in the first instance at the restaurant at which the conversation took place, and recurring failure patterns are also examined across restaurants, after the names have been replaced with a generic marker. All of this is explained in the Privacy Policy.
2. Technologies and practices not used
- The Site uses neither Google Analytics nor any analytics tool that identifies the User. The only means of measurement is Cloudflare Web Analytics, which counts page views without any cookie, device identifier or profile, being an aggregate count made at the infrastructure that serves the Site in any event. It appears in the settings panel below under "Measurement", and the User may switch it off there.
- No pixels of Facebook, TikTok or any advertising network are used.
- No third-party cookies are used, save for CF_Authorization, which Cloudflare Access sets solely for Qder staff signing in to Qder's internal operations console.
- There is no cross-site user profile, and no information is shared with advertisers.
The pages of the Site operate under a Content Security Policy that blocks scripts from external sources, so that a tracking tool cannot be loaded, even inadvertently. The Content Security Policy follows the User's setting: when the User switches "Measurement" off, the address of the measurement script ceases to appear in the Content Security Policy and the browser itself blocks the script, even if the infrastructure attempts to add it to the page. The setting is thus a genuine switch, and not a mere request.
3. No resources loaded from external sources
Even the Site's fonts are served from Qder's own server. In order to display these pages, the User's browser does not contact any third-party server (neither Google Fonts nor any advertising network), and the User's IP address is transmitted only to Qder and to the infrastructure that hosts Qder.
4. The payment page
When the User makes a payment, the User is directed to the page of the restaurant's payment processor. Anything stored in the User's browser by that page is governed by that page's policy, and not by Qder's.
5. The User's settings
The settings panel below is live: it shows what may be kept on this device and allows the User to change it. Categories containing nothing are marked as such, since Qder does not display a switch that does nothing.
6. Additional control through the browser
The User may at any time delete anything stored in the User's browser by means of the browser's settings. Where the table session is deleted, the User will need to scan the code on the table again. None of the foregoing affects any order already sent to the kitchen.