Cookie Policy

Last updated August 21, 2026

This Cookie Policy explains how DndPlaybook, an independent project operated by Charles Bowen in the United Kingdom ("we," "us," and "our"), uses cookies when you visit our website at https://dndplaybook.com ("Website"). It explains what cookies we set, why we set them, and how you can control them.

The short version: we set a small number of first-party cookies needed to run the site, plus one first-party cookie that records how you found us. We also use Microsoft Clarity to see how people actually use the site, and that sets cookies of its own, some of them third-party. We do not run advertising here and we do not sell your data.

What are cookies?

Cookies are small data files that are placed on your computer or mobile device when you visit a website. They are widely used to make websites work, keep you signed in, and remember your preferences between visits.

Most cookies on this Website are "first-party cookies" — set by DndPlaybook itself. The exception is Microsoft Clarity, the tool we use to watch how the site gets used, which sets both first-party and third-party cookies. They are all listed below.

The cookies we use

Essential cookies

These cookies are strictly necessary for the Website to function and cannot be switched off in our systems:

  • Session cookie — keeps you signed in and maintains your session as you move around the site.
  • XSRF-TOKEN — a security cookie that protects forms and requests against cross-site request forgery attacks.

Attribution cookie

We set one non-essential, first-party cookie named acquisition. When you first arrive at the Website, it records where you came from — for example a search engine, a link on another site, or a tagged link we published. If you later create an account, we use it to understand which channel brought you to us. It is not shared with anyone, is not used for advertising, and does not track you across other websites.

Analytics cookies

We use Microsoft Clarity to record how people move around the site, so we can find the parts that are confusing or broken. Clarity sets the cookies below. The first two are first-party; the rest are set by Microsoft on their own domains.

  • _clck — stores a pseudonymous Clarity user ID, so return visits are recognised as the same browser.
  • _clsk — joins several page views together into a single session recording.
  • CLID — records the first time Clarity saw this browser on any site that uses Clarity.
  • MUID — identifies a browser across Microsoft sites. Microsoft also uses this cookie for advertising on its own services. We do not advertise and we do not use it for that, but we would rather tell you it is there than leave it out.
  • ANONCHK, MR, and SM — housekeeping cookies Microsoft uses to manage and synchronise MUID.

If you are signed in, we also tell Clarity which account a session belongs to, so we can trace a problem you report back to what actually happened on screen. What we send is your account number and your username. Your account number is scrambled by Clarity in your own browser before it is sent, so Microsoft never receives it in a readable form. We do not send your name or your email address.

Microsoft applies its own consent rules to visitors in the UK, the EEA, and Switzerland: in those regions Clarity waits for a consent signal before setting any cookies. We do not currently run a cookie banner, so if you are in one of those regions Clarity sets no cookies. It still records the page you are on, but without those cookies it cannot join your page views into a single session or recognise you on a return visit.

What about analytics?

We use two analytics tools, and they behave quite differently.

Fathom Analytics tells us how many people visit and which pages they land on. It is privacy-focused, sets no cookies, and does not track you across websites.

Microsoft Clarity records how people use the site — clicks, scrolling, and where things go wrong — and plays it back to us as an anonymised session. This is what we use to find bugs and fix awkward parts of the interface. Clarity does set cookies, listed above, and Microsoft masks text content by default. Their privacy statement covers what they do with it.

How can I control cookies?

You can control and delete cookies through your web browser settings. Because the essential cookies are required for signing in and security, blocking them will prevent parts of the Website from working. The following is information about how to manage cookies on the most popular browsers:

How often will you update this Cookie Policy?

We may update this Cookie Policy from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal, or regulatory reasons. Please therefore revisit this Cookie Policy regularly to stay informed about our use of cookies and related technologies.

The date at the top of this Cookie Policy indicates when it was last updated.

Where can I get further information?

If you have any questions about our use of cookies or other technologies, please contact us at admin@dndplaybook.com.