Cookie policy
Effective 7 July 2026 · last updated 14 July 2026 · UK PECR
The short version
- We use one kind of cookie: the one that keeps you signed in. That 's it.
- No advertising cookies, no analytics cookies, no third-party trackers, no "we value your privacy" pop-up.
- Because our cookies are strictly necessary to run the service, UK law doesn't require a consent banner — so we don't show one.
This box is a summary; the sections below are the full policy.
What cookies we use
A cookie is a small file a website stores in your browser. Under UK law (the Privacy and Electronic Communications Regulations, PECR), a site must get your consent before setting cookies that aren't strictly necessary to provide the service you asked for. LinkWatch only sets strictly-necessary cookies, so no consent banner is required.
| Cookie | Purpose | Type |
|---|---|---|
Clerk session | Keeps you securely signed in as you move between pages of your dashboard. Set by our authentication provider, Clerk. | Strictly necessary |
Clerk may set one or more related cookies as part of the sign-in flow (for example a short-lived CSRF or session-refresh cookie). These exist solely to make authentication work securely and are all strictly necessary.
What we don't use
- No advertising or marketing cookies. We don't run ads and we don't retarget you.
- No analytics cookies. We don't use Google Analytics or similar in-browser trackers.
- No tracking pixels in our emails. Our digests don't report back when you open them.
Managing cookies
Because our only cookies are strictly necessary, blocking them will break sign-in — you won't be able to use your dashboard. You can clear or block cookies in your browser settings at any time; doing so simply logs you out. When you delete your account we no longer set any cookies for you.
More detail
How we handle personal data more broadly is covered in our privacy notice. Questions about cookies or anything else: [email protected].
Changes
If we ever introduce non-essential cookies (we have no plans to), we will update this page, add a proper consent mechanism first, and never set them without your consent.