Last updated: 11 May 2026 — version 2026-05-11
Cookies are small pieces of data that your browser stores so a website can remember things like whether you're logged in. MimWise uses cookies in four categories. Only the first one (strictly necessary) runs automatically. Everything else — statistics, functional extras, and marketing — stays off until you say yes in the banner.
This page tells you what cookies and similar storage technologies
(such as localStorage and web beacons) MimWise uses, why
we use them, and how you can control them. It supplements our
Privacy Policy and forms part of the
information we are required to give you under the UK Privacy and
Electronic Communications Regulations 2003 (PECR) and the UK General
Data Protection Regulation (UK GDPR).
MimWise groups storage into four categories. The cookie banner that appears on your first visit lets you accept or reject the non-essential categories one by one. We never set non-essential cookies before you choose.
These keep MimWise working — signing you in, keeping your session open, protecting against cross-site request forgery. Under PECR Regulation 6(4) they don't need consent.
| Name | Purpose | Lifetime |
|---|---|---|
sessionid | Keeps you signed in across pages. | Session / 2 weeks |
csrftoken | Protects forms against cross-site request forgery. | 1 year |
mimwise_cookie_consent | Remembers your cookie preferences so we don't ask again. | 12 months |
mw_anon_id | First-party anonymous identifier used to deduplicate behavioural events. Contains no personal data. | 12 months |
First-party measurement of how the site is used (pages viewed, features clicked). The data is aggregated and we do not attempt to identify individual visitors from it.
UK DUAA 2024 note: Section 113 of the UK Data (Use and Access) Act 2024 amends PECR so that qualifying first-party analytics no longer require prior consent. That amendment has not yet been commenced by statutory instrument; until it is, we keep these cookies behind explicit consent.
| Name | Purpose | Lifetime |
|---|---|---|
| First-party analytics events | Counts of feature usage, errors, performance timings. Sent to /api/insights/event/ as statistical. | 24 months |
Powers optional embedded media such as Spotify podcast episodes on our blog. These embeds set cookies controlled by the third party. They stay off until you click the “Load Spotify embed” placeholder.
| Provider | Purpose | Cookie policy |
|---|---|---|
| Spotify | Click-to-load podcast/episode embeds. | spotify.com/legal/cookies-policy |
Third-party advertising and conversion tracking. We do not load any marketing tag, pixel, or beacon unless you have specifically opted in. The pixel identifiers are configured per environment; if you see this page in an environment where no marketing IDs are set, these cookies simply do not exist.
| Provider | Purpose | Cookie policy |
|---|---|---|
| Meta (Facebook) Pixel | Measure ad performance and audience signals for Meta campaigns. | facebook.com/policy/cookies |
| LinkedIn Insight Tag | Measure ad performance for LinkedIn campaigns. | linkedin.com/legal/cookie-policy |
We implement Google's Consent Mode v2 in default-denied mode. That
means: on first page load, every Google signal
(ad_storage, ad_user_data,
ad_personalization, analytics_storage,
functionality_storage,
personalization_storage) is denied, and only
security_storage is granted (so CSRF / session
protection works). When you accept categories in the banner, we call
gtag('consent', 'update', …) to flip the relevant
signals to 'granted'. We never load Google Analytics or
Google Ads tags speculatively.
If we add a new cookie category or a new third party we'll bump the version stamp shown at the top of this page and re-prompt you for consent. Material changes are announced in-product and, where you have opted in to product emails, via email.
Email privacy@mimwise.co.uk. You also have the right to complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint.