Cookie Policy

This policy explains cookies and similar technologies used on the SalesGamez website, application, public boards and checkout. It should be read with the Privacy Policy.

SalesGamez operates from 80A Ruskin Ave, London, DA16 3QQ, United Kingdom, and trades as SalesGamez. Privacy and cookie questions can be sent to privacy@salesgamez.com. This policy and the use of cookies described in it are governed by the law of England and Wales.

Under PECR, storing information on or accessing information from a user’s device normally requires consent unless the technology is used solely to transmit a communication or is strictly necessary to provide a service the user explicitly requested. UK GDPR also applies where the information is personal data.

Strictly necessary technologies are essential for a requested service, such as secure authentication, fraud prevention, session continuity or remembering an action needed to complete checkout. They do not require PECR consent, but we still explain them.

Preference technologies remember choices such as interface or sound settings. Some may qualify for an exemption where they are necessary to provide a feature the user explicitly requested. Otherwise, consent is required.

Analytics or performance technologies measure use or performance beyond what is strictly necessary. Consent is normally required before they are set or accessed.

Advertising or tracking technologies profile users or track activity across services. Consent is required. SalesGamez does not use advertising, social media, heat-map or analytics technologies.

Authentication session storage, backend authentication provider, local storage and related browser storage, used for sign-in, session continuity and password recovery across sign-in and the app. Category: strictly necessary for authenticated service access. Duration: controlled by the authentication session, which expires and is refreshed while you stay signed in.

`sidebar_state`, first-party cookie, used to remember whether the signed-in app sidebar is open or closed. Duration: seven days in the source code. Category: preference, set only because you moved the sidebar.

`salesgamez.cookie-notice`, first-party local storage, used to remember that the cookie notice was seen. Duration: until browser storage is cleared. Category: necessary for the notice experience if the notice is retained.

`salesgamez:app-theme:{userId}`, first-party local storage, used to remember the signed-in user’s chosen light, dark or system theme. Duration: until cleared or changed. Category: preference.

`competition-music-muted`, `entry-celebration-muted`, `rafflez-muted`, `spin-wheel-muted` and `salesgamez:charadez-muted`, first-party local storage, used to remember sound choices. Duration: until cleared or changed. Category: preference.

`gamez-selected-teams`, first-party local storage, used to remember selected teams in app flows. Duration: until cleared or changed. Category: preference or app-state storage.

`active-site-id`, first-party local storage, used for Master users to remember the selected active site. Duration: until cleared or changed. Category: preference or app-state storage.

`salesgamez.edit-mode`, first-party local storage, used for Master website-edit mode. Duration: until cleared or changed. Category: preference or administrative app-state storage.

`sg-device-id`, first-party local storage, used to create a stable browser identifier for shared-login detection. The server stores hashed device and network values for this feature. Duration: until browser storage is cleared; server-side login-sharing events are actively cleared after 90 days by source code housekeeping. Category: security and misuse prevention, used because sharing a single login is not permitted.

`sg-sharing-notice-dismissed`, first-party local storage, used to remember dismissal of a shared-login warning until the risk score worsens. Duration: until cleared or overwritten. Category: security notice preference.

`salesgamez.studio.layout.*` and `studio-recent-templates`, first-party local storage, used to save Studio layouts and recent templates. Duration: until cleared or deleted in Studio. Category: user-requested feature storage.

`salesgamez.learn.{token}`, first-party local storage, used on shared learning links to remember anonymous progress on that device until completion. Duration: until browser storage is cleared. Category: user-requested feature storage.

`suspectz.pin.{code}`, first-party local storage, used on Suspectz private player links to remember that the PIN was entered on that device. Duration: until browser storage is cleared. Category: security and access-flow storage.

`gamez-live-choice-dismissed`, first-party session storage, used to hide a signed-in live-entry prompt for the current browser session. Duration: browser session. Category: short-lived interface state.

`salesgamez:charadez-used` and `salesgamez:charadez-best`, first-party local storage, used for Charadez play history and best score on that device. Duration: until cleared. Category: game-state or preference storage.

Payment checkout storage, set by Stripe inside our embedded checkout, used for checkout, payment authentication and fraud prevention. Category: strictly necessary for a payment you have asked to make. Duration and exact technologies are set by Stripe and described in Stripe’s own cookie information.

Our hosting, backend and email providers also create operational logs needed to run and secure the service. These are server-side records rather than storage on your device.

Everything listed above is either strictly necessary to provide the service you asked for, or a setting you chose yourself inside the app, such as sound, theme or sidebar state. Because SalesGamez sets no advertising, profiling, social-tracking, heat-map or analytics storage, we show an information notice rather than an accept or reject banner.

If we ever introduce a technology that needs consent, we will block it until consent is given, give clear information first, make accepting and rejecting equally easy, avoid pre-ticked or bundled controls, record the choice, allow withdrawal as easily as it was given, and ask again if purposes change materially.

Users can block or delete cookies and browser storage through browser settings. Doing so may sign a user out, reset preferences, remove device-only game or learning progress, or require a PIN again. It does not itself delete account or Customer Data held on SalesGamez servers.

SalesGamez uses Stripe for payment checkout and billing. Stripe may set or access device information for checkout, payment authentication, fraud prevention and related payment purposes. Stripe publishes its own cookie and privacy information, and the technologies it uses are controlled by Stripe rather than by us.

If you choose to sign in with Google or Microsoft, you are taken to that provider’s own sign-in pages, where the provider sets and reads its own cookies to sign you in and keep your provider account secure. That storage is strictly necessary for the sign-in you asked for, is set on the provider’s own pages rather than by SalesGamez, and is controlled by Google or Microsoft under their own cookie and privacy information. The sign-in applications are registered to SalesGamez in our own name, but we do not place or read any advertising or tracking storage through them, and no Google or Microsoft tracking scripts are embedded in this website or the app.

Our fonts are served from SalesGamez rather than loaded from a third-party font service. Any future externally hosted font, video player, map, analytics product, tracking tool or similar third-party content must be assessed, disclosed and, where required, blocked until valid consent before it sets or reads device storage.

SalesGamez contains no embedded advertising networks, social media widgets, heat-mapping tools or analytics tools.

We will update this policy and the inventory when technologies or purposes change. Privacy and cookie questions can be sent to privacy@salesgamez.com. You may complain to the Information Commissioner’s Office at ico.org.uk.