Cookie Notice

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 and marketing are both off unless you turn them on, separately, and you can change your mind at any time from the Cookie settings link in the footer of every page.

2. The Three Categories

We use three categories. Two of them are optional, and they are asked separately.

Strictly necessary — needed to make the site work at all, including remembering your cookie choice. These are always on and cannot be switched off.
Analytics — helps us understand how the site is used. Off by default. These only ever load after you have said yes.
Marketing — measures our advertising and lets Meta build audiences from your visit. Off by default, and a separate choice from analytics.

We do not sell what we collect. We use one advertising tracker, the Meta Pixel, described in full below.

3. Strictly Necessary

Always on. Without these the site cannot remember your choice or keep you signed in.
What	Where	Purpose	Kept for
dp_cookie_consent	Local storage	Remembers the cookie choice you made and the version of this notice you made it under	Until you clear it or a materially changed notice is published
Sign-in storage	Local storage	Keeps you signed in to your DashPoint account (Amazon Cognito)	Until you sign out or the session expires
dp_preview	Cookie	Grants access to unreleased partner preview pages, for invited reviewers only	The 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.

Google Analytics — site measurement

Measures how the site is used overall: which pages are visited, how people move between them, which links and buttons are used, and roughly where in the world visitors are. We use it to understand which parts of DashPoint are useful and which are not.

When it is on, each page you view sends Google:

The address of the page you are on and the page you came from
Your IP address, browser, device type and approximate location
Google's own cookies, which link the pages of a single visit together and recognise a returning visitor
The name of any tracked action you take, such as opening an event page or selecting a download button

Measurement, not advertising. Google Analytics is set up so that advertising features stay switched off unless you also turn marketing on. Consenting to analytics alone lets Google measure your visit; it does not let Google use it to personalise adverts, and we do not send it to Google Ads.

Google processes this on our behalf as our processor. Google is based in the United States, so consenting involves an international transfer under Google's standard contractual clauses.

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.

5. Marketing

Optional, off unless you turn it on, and a separate switch from analytics. Turning analytics on does not turn this on.

This one leaves DashPoint. Everything in the analytics category is either our own or handled by a supplier working only on our instructions. The Meta Pixel is different: it sends information about your visit to Meta, who also use it for their own purposes.

Meta Pixel — advertising measurement

We advertise DashPoint on Facebook and Instagram. The pixel is how we find out whether those adverts actually bring anyone to the site. Without it we can see that people arrived, but not which advert, if any, sent them.

When it is on, each page you view sends Meta:

The address of the page you are on and the page you came from
Your IP address, browser and device type, as with any web request
Meta's own cookies, including any that already identify you from being signed in to Facebook or Instagram
An event when you choose to download the DashPoint app, described below

Meta can join this to an existing Facebook or Instagram account, and does so where it has one to join it to. That is what makes it cross-site tracking rather than analytics, and it is the reason it is asked for separately.

For measuring and reporting on our adverts, we and Meta decide together what happens to this data, so we are joint controllers with Meta for that part. For Meta's own product and advertising purposes, Meta acts on its own account and its own terms govern what it does. Meta is based in the United States, so consenting involves an international transfer under Meta's standard contractual clauses.

You can also control advert personalisation from your Meta account settings, independently of the choice you make here — but declining marketing on this banner stops the pixel from loading on this site at all.

What we can and cannot see about app downloads

When you select a download button, we record that you chose to go to the App Store or Google Play, or to open the app if you already have it. That is an intention, not an installation.

The website cannot see whether you went on to install DashPoint. Apple and Google do not report that back to a website, and the DashPoint app does not contain any Meta tracking. If we ever add install measurement inside the app itself, that is a material change and this notice will be re-issued.

6. How Consent Works

The first time you visit, a banner asks you to choose. Nothing in the analytics or marketing categories loads before you answer — not while the banner is open, and not if you ignore it.

Accept all — turns analytics and marketing on.
Reject all — leaves both off. Just as prominent, and one click, the same as accepting.
Customise — choose category by category, so you can allow one and refuse the other. Strictly necessary is shown as always on, because it is.

Your choice is stored on your own device, not on our servers, together with the version of this notice you were shown when you made it.

7. Changing or Withdrawing Your Choice

Select Cookie settings in the footer of any page. The same panel opens and your new choice takes effect immediately — turning a category off stops its scripts from loading, and the page reloads so that anything already running stops running.

Withdrawing is exactly as easy as consenting: one control, in the same place, on every page.

You can also block or delete cookies in your browser settings, though that is a blunter tool and may affect how the site works.

8. 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.

9. 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

Version 3 — effective 17 August 2026
Version 2 — effective 4 August 2026
Version 1 — effective 14 January 2026

What changed in version 4

Adds Google Analytics 4 to the analytics category, naming Google as a recipient.
Describes what GA4 receives, that it is measurement rather than advertising, and that advertising signals stay off unless marketing consent is given separately.
Records that DashPoint's two consent categories are mapped onto Google's consent signals, so analytics consent alone never enables ad personalisation.

Contact

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