Cookie policy
Cookies are small text files a website saves in your browser. This page lists every cookie and similar technology lavine.dev uses, and shows you how to change your choice.
Last updated 22 September 2026
Your choice
On your first visit we ask whether you accept analytics cookies. Until you say yes, we load no analytics code and set no analytics cookies. Declining changes nothing else about the site.
You can change your mind at any time. This button deletes your saved choice and any Google Analytics cookies it can reach, then reloads the page and asks you again.
Cookies we always use
These are strictly necessary. The site needs them to work or to remember your choice, so they do not need your consent.
| Cookie | Set by | What it does | Expires |
|---|---|---|---|
analytics_consent | lavine.dev | Remembers whether you accepted or declined analytics cookies, so we do not ask on every page | 1 year |
payload-token | lavine.dev | Keeps us logged in to the site's admin area, along with other login cookies. Visitors never receive them | When the login session ends |
Analytics cookies
Google Analytics sets these only after you accept analytics cookies. They let us count visits and see which pages people use. Google explains how it handles the data in how Google uses information from sites that use its services.
| Cookie | Set by | What it does | Expires |
|---|---|---|---|
_ga | Google Analytics | Tells one browser apart from another, so a return visit is not counted as a new visitor | 2 years |
_ga_0C8S2HWBKT | Google Analytics | Keeps track of the current visit | 2 years |
Spam protection
Pages with a form (the contact page, blog posts and the AI Visibility Scan) load Google reCAPTCHA Enterprise. It runs in a frame served from google.com, where Google can set its own cookie, _GRECAPTCHA, to tell people apart from bots. It sets no cookies on lavine.dev. We treat it as strictly necessary, because we cannot keep the forms free of spam without it.
Local storage
Your browser's local storage works like a cookie but never travels to our server. We use it for one thing. When you like a post or case study, we save a key such as liked:posts:42 so the button stays lit on your next visit. It stays until you clear your browser data.
Controlling cookies in your browser
Every major browser lets you block or delete cookies in its settings. If you block the analytics_consent cookie, we will ask about analytics on every visit.
Our privacy policy explains how we handle personal data more widely. Send questions about cookies to steve@lavine.dev.