Cookie Policy

1. Cookie settings

You can change your choice here at any time. Your latest choice applies to this browser, including when it is shared with another user. Essential cookies remain active with either choice.

The choice cookie records the choice, the notice version and when you made it. It is not a marketing profile and does not store your name or email address. We ask again when it expires or if a new purpose requires a fresh choice. Continuing to browse without choosing does not give consent.

2. Essential cookies

Cookies are small values stored by your browser and sent back to this website. The application sets the following cookies for this site's host and root path. They are restricted from JavaScript access, use SameSite=Lax and are transmitted securely on HTTPS.

__Host-console_session_id

Keeps an owner or manager signed in to their account. Contains an encrypted reference to a server-side authentication session, rather than business or order details. Expires 12 hours after sign-in; ordinary browsing does not extend it.

__Host-till_session_id

Keeps this device signed in to its authorised till. Contains an encrypted server-side session reference. Expires 12 hours after sign-in; ordinary browsing does not extend it. Till and management sessions are independent.

__Host-_jawa_menu_session

Rails' encrypted session cookie supports request-forgery protection and temporary messages, such as sign-in feedback. It also keeps a limited pending sign-up reference and temporarily holds confirmation and invitation link state while you explicitly confirm. These do not grant account or business access. It is a browser-session cookie, without a fixed expiry. A browser's session-restore feature may keep session cookies after it closes.

__Host-jawa_device

Recognises a browser for account security notifications. It contains an encrypted random device ID; the server keeps only a hash for each account. It is strictly necessary, expires one year after sign-in and does not enable analytics or advertising.

_jawa_menu_cookie_preference

Remembers whether you accepted or rejected optional cookies, together with the notice version and decision time. This signed cookie protects the choice against tampering. It expires six months after your choice.

Sign-out removes the relevant authentication cookie and revokes its server-side session; full sign-out ends both logins. It also resets Rails' session state. Your cookie preference is kept so that signing out does not repeatedly ask you the same question. The security device cookie is kept so a later sign-in from this browser is recognised. Clearing it makes the next sign-in a new-device alert.

3. Other browser storage and requested features

Local storage is different from a cookie: the browser keeps a setting locally rather than automatically sending it with every request. The application uses it for interface and till features. These settings are separate from optional analytics or advertising and are not enabled by accepting optional cookies.

Interface choices

jawa-menu-theme, jawa-menu-keyboard and jawa-menu-[business ID]-layout remember your chosen theme, on-screen keyboard state and till layout.

Receipt printing

jawa-menu-[business ID]-printer and jawa-menu-[business ID]-autoprint remember the printer you confirm, its paper width and your auto-print setting. jawa-menu-[business ID]-kitchen-prints keeps a local record of printed order-line identifiers and quantities to help avoid duplicate kitchen tickets.

Caller ID device settings

jawa-menu-caller-id-baud and jawa-menu-caller-id-metadata remember the connection speed and metadata setting selected when setting up a caller ID device.

Unsaved sale

jawa-menu-[business ID]-[till session]-draft is kept in session storage, which the browser clears when the tab closes. It holds the sale being built on the till, including any customer name, phone number or delivery address added to it, so a reload or a lost connection does not lose it. It is removed when the sale is saved or cleared, when you sign out or lock the till, and when a different till session opens in the tab.

Orders without a connection

While the till is online it keeps a copy of the menu, order settings, receipt details and open tables (with their orders) in the browser's IndexedDB database jawa-menu-offline, so it can take orders if the connection drops. Orders taken without a connection are kept there too, including any customer name, phone number or delivery address. They stay until they are synced, or, if the business has chosen never to sync them, until they are exported and cleared. Signing out deletes the database, and is refused while any of these orders have not been synced or exported. jawa-menu-[business ID]-offline-unsettled counts those orders for that check.

Till device code

jawa-menu-[business ID]-device keeps the code this browser was given as a till (for example T2) and the last number it gave an offline order, so offline order numbers are never repeated. It holds no order or customer details and stays after signing out.

Installed app

A service worker keeps a generic public offline page, a public till shell and the application's versioned styles, scripts and images in cache storage. The shell contains no business, customer, session or request-forgery data. Signed-in pages are never cached. A till reopens from its separately stored, authorised snapshot only before its existing session and staff-unlock deadlines.

Offline till access

jawa-last-till-v1 remembers the last prepared till address, business and session context, absolute deadline and last activity time. It contains no password or authentication token. Locking the till removes this reference and its public shell while preserving unsynced orders. Signing out clears the reference, shell, draft and offline database, and is refused while orders remain unsynced or unexported. Expired access does not delete orders needed for recovery.

These local settings have no automatic time expiry and can remain until you change them or clear the site's browser data. Printer and layout settings include a business identifier to keep different businesses' settings separate on a shared browser. Signing out does not clear these device settings.

When requested till features connect to a local printer or load an external map, additional information may be handled as described in the Privacy Policy. The map sends network requests to OpenFreeMap, and postcode lookup uses Postcodes.io. These are functional service requests rather than optional analytics cookies; this cookie choice does not authorise new third-party tracking.

4. Browser controls, privacy and contact

You can remove cookies and local storage using your browser's site-data settings. Blocking essential cookies can prevent sign-in or secure form submissions. Clearing the choice cookie makes this a browser with no saved choice, so the banner will appear again on the landing page. Clearing device storage can reset your interface, printer and caller ID settings.

The Privacy Policy explains the information we handle, the roles of JAWA and your business, sharing, retention and your rights. Cookie choices are separate from accepting the Terms and Conditions.

This website is operated by JAWA AI LTD. For cookie or privacy questions, email [email protected].