You are reading a superseded version of this document, kept for reference. Read the current version.

Cookie Notice

In plain English: The cookies and similar technologies the DashPoint website actually uses, by category, and how to grant or withdraw consent for each.

SupersededVersion 2Effective Last updated
  • Website visitors
On this page

1. Introduction

This notice explains what the DashPoint website stores on your device, why, and how you control it. It covers cookies and technologies that work like cookies, such as local and session storage.

It applies to the dashpoint.uk website. The DashPoint mobile app is covered by the Privacy Notice.

Nothing optional is stored until you choose. Analytics are off unless you turn them on, and you can change your mind at any time from the Cookie settings link in the footer of every page.

3. Strictly Necessary

Always on. Without these the site cannot remember your choice or keep you signed in.
WhatWherePurposeKept for
dp_cookie_consentLocal storageRemembers the cookie choice you made and the version of this notice you made it underUntil you clear it or a materially changed notice is published
Sign-in storageLocal storageKeeps you signed in to your DashPoint account (Amazon Cognito)Until you sign out or the session expires
dp_previewCookieGrants access to unreleased partner preview pages, for invited reviewers onlyThe browsing session

4. Analytics

These are optional and off unless you turn them on. If you do not consent, none of the scripts below load and no events are sent.

These are not anonymous. Session replay records what an individual visitor did, and visitor identification exists specifically to work out who is behind a visit. We would rather say so plainly than describe them as anonymous when they are not.

LogRocket — session replay

Records a replay of your visit: the pages you view, and your clicks, scrolls and other interactions with them. We use it to find and fix problems people hit on the site.

A replay is a record of one person's visit, so it is personal data. LogRocket processes it on our behalf as our processor. It uses its own cookies and local storage to link the pages of a single visit together.

Apollo.io — visitor identification

Loads a script that attempts to identify the organisation a business visitor is browsing from, so we can understand which kinds of brands and clubs are looking at DashPoint.

This is identification tooling by design. It is not anonymous analytics, and it is the reason the analytics category is presented as a real choice rather than a formality.

DashPoint page events

Our own measurement, sent to DashPoint rather than to a third party. Each event records:

  • The page you were on and the kind of page it is
  • How you arrived, including any campaign tags in the link you followed
  • Whether you are on a mobile or a desktop-sized screen
  • A random identifier that groups the pages of a single visit together

That identifier is held in session storage under dp_session_id and is discarded when you close the tab. It is not linked to your DashPoint account.

7. Changes to This Notice

When we make a material change — adding a tracker, or changing what an existing one does — we publish a new version of this notice and ask everyone to choose again. A choice made under an older version is not carried over.

Minor corrections that do not change what is stored or why are published without re-asking.

8. Contact

Questions about this notice, or about anything the site stores, can go to our support team. The Privacy Notice covers personal data more broadly, and Your Data Rights explains how to make a request about your data.

Previous versions

What changed in version 2

  • Names the actual non-essential trackers for the first time: LogRocket session replay, Apollo.io visitor identification, and first-party page-event beacons.
  • Removes the statement that analytics information is collected anonymously, which did not match what those trackers do.
  • Adds a table of what is stored, by category, with purpose and duration.
  • Describes the categorised banner and the Cookie settings control in the footer, replacing v1's instruction to clear browser storage.
  • Records that a choice is stored against the Cookie Notice version it was given under, and that publishing a materially changed version re-asks everyone.

Related documents

Contact

Questions about this document? Contact DASHPOINT LIMITED (company no. 16792461) at support@dashpoint.uk.

Back to Legal Centre

Integrity fingerprint: 7ed722d678e4