Cookie Policy

Last updated: 2026-08-10 · Effective immediately

This page lists every cookie and localStorage value that beavr (https://beavr.xyz) sets or causes to be set on your device. The high-level summary lives in the Privacy Policy; this page is the per-cookie disclosure that satisfies Google AdSense's transparency requirement.

1. First-party storage (set by this site)

These are values this site writes directly into your browser. They are not shared with any third party; no data is transmitted to our servers. Site-wide preference values contain no personal data; optional tool state may contain text you choose to enter. They can be cleared from your browser's developer tools at any time without affecting your ability to use the tools.

1.1 Theme preference (localStorage)

  • Key: site-theme
  • Value: "light" or "dark"
  • Purpose: Remembers your chosen colour scheme between visits so the page renders in the right palette on first paint.
  • Lifetime: Persistent (until you clear site data or the browser does).
  • Personal data: None.

1.2 Consent record (localStorage)

  • Key: beavr:consent:v1
  • Value: JSON object with ads, analytics, ts, method, and version fields.
  • Purpose: Records your advertising-cookie choice (accept or reject) so the site does not show the consent banner again on every visit. The record is also used to decide whether to inject the AdSense loader.
  • Lifetime: Persistent (until you clear site data).
  • Personal data: None — the choice itself is a boolean flag plus a timestamp.

1.3 Language preference (HTTP cookie)

  • Key: beavr-lang
  • Value: "en" or "es"
  • Purpose: Remembers your chosen interface language so a repeat visitor is taken straight to the matching version of the site. Without it, you would see the language switcher every visit.
  • Lifetime: 1 year (set with max-age=31536000).
  • Personal data: None — the value is a single two-letter code.

1.4 Optional tool state (localStorage)

A tool writes these keys only when you use the corresponding persistence feature. The English and Spanish pages use the same keys. Values remain on this device and are never uploaded by the tools.

  • Sidebar: beavr-sidebar-cats and beavr-sidebar-collapse-all remember navigation groups.
  • Breathing: beavr:breathing:v1 stores the selected pattern, duration, sound preference, and local session history.
  • Date Countdown: beavr-date-countdown-saved-v1 stores saved countdown events.
  • Dice Roller: beavr-dice-roller-history stores recent rolls.
  • Emoji: beavr.emoji.recents.v1 stores recently used emoji.
  • Pomodoro: pomodoro.config.v1, pomodoro.day.v1, pomodoro.count.v1, pomodoro.focus.v1, pomodoro.streak.v1, and pomodoro.lastday.v1 store settings and local counters.
  • Random Picker: beavr-random-picker-history stores recent draws.
  • Time Tracker: tt:v1:sessions and tt:v1:projects store sessions, project labels, colours, and notes you enter.
  • Speed Reader: sr-state-v1 stores reader settings and bookmarks; sr-text-v1 stores text you choose to keep between visits.

2. Third-party cookies (Google AdSense, consent-gated)

If — and only if — you click Accept on the consent banner and the operator has enabled advertising for that build, the Google AdSense loader runs and Google may set its own cookies. Because this static site cannot determine a visitor's country before consent, the conservative consent flow applies to every first visit, including visits from outside the EEA, UK, or Switzerland. Ad serving, frequency capping, and conversion measurement on AdSense are performed by Google's DoubleClick advertising platform (now part of Google Ad Manager), which sets a subset of the cookies listed below. The exact list is controlled by Google and changes over time; the canonical, up-to-date enumeration is at Google's cookie policy. Google also explains how it uses information from sites that use its services in its partner-sites notice.

Common categories set by AdSense:

  • IDE / _ga / _gcl_*: pseudonymous browser identifier used for ad selection, capping, and frequency measurement.
  • NID / ANID: preference cookies that remember settings such as preferred language, ad count per page, and whether the user has Google's "Personalised ads" toggle on.
  • 1P_JAR / APISID / HSID / SAPISID / SID / SSID / SIDCC: session and security cookies that authenticate the user's requests to Google and protect against abuse.
  • DSID / FLC / AID / TAID / FPAU / FPGCLAW / FPGCLGB / FPGCLDC: advertising-measurement cookies used to count conversions and build aggregate reports for advertisers.

You can opt out of personalised advertising set by Google at Google Ads Settings or by visiting www.aboutads.info for industry-wide opt-out. Rejecting advertising cookies through this site's consent banner has the same effect for the cookies that this site itself triggers.

3. What we do not set

To be exhaustive about what is not on this list:

  • No first-party analytics cookies (no _ga, no _gid, no Matomo, no Plausible, no Cloudflare beacon).
  • No advertising cookies from networks other than Google AdSense.
  • No session cookies for the tools themselves — the tools are pure client-side JavaScript and do not authenticate or send your local tool state anywhere.
  • No cross-site tracking pixels (no Facebook Pixel, no LinkedIn Insight, no X pixel).
  • No fingerprinting of your browser or device.

4. Clearing cookies on your side

You can clear everything this site has stored at any time from your browser's developer tools:

  • Chrome / Edge / Firefox / Safari: open DevTools → Application (or Storage) → Clear site data.
  • This removes the theme preference, consent record, optional tool state, and language cookie. The next page load will show the consent banner again and use the default theme.
  • To clear AdSense cookies specifically, follow the Google Ads Settings opt-out link above.

5. Changes to this policy

If we add a new cookie or localStorage value, we will update this page and bump the "Last updated" date at the top. We will also surface a notice on the home page for at least 30 days when the change is material (for example, adding a new third-party integration).

6. Contact

Questions, concerns, or requests about cookies can be sent through the contact form linked from the home page.

← Back to beavr