There is no way to run an ad-supported site without cookies. Rather than bury that, KetoDrip lists each one it sets and the reason it exists.
Revisions
This page is rewritten when the set of cookies changes, which happens when a service is added or dropped rather than on a schedule. The date at the top is when that last occurred.
The cookies on this site
- Site function. Loading pages, keeping the connection secure, and storing the cookie choice you already made.
- Traffic measurement. Through Google Analytics we see totals: pages opened, time spent, where the visit came from. Never a name.
- Advertising. AdSense cookies decide which ads are worth showing you and cap how many times each one appears.
How long this is kept
Lifetimes vary: the technical cookies expire with the session, while Google’s analytics and advertising cookies are kept for a period Google sets, typically counted in months.
Which cookies, specifically
- _ga and _gid come from Google Analytics and exist to tell browsers apart when counting visits.
- __gads and __gpi come from Google AdSense, which uses them to pick ads and limit repeats.
- wordpress_test_cookie and the wp-settings-* family are WordPress internals: a capability check and your display preferences.
- comment_author_* appears only after you comment, and only so the form is pre-filled the next time.
None of these cookies can read your documents, reach outside the browser, or be sold on. None of them is intended to attach a name to a visit.
Third-party embeds
An embedded player or map is served by its own operator, and it can set cookies when it loads. Refusing third-party cookies in your browser is what stops that.
The opt-out links
- Google’s own controls sit at adssettings.google.com and cover personalised advertising wherever you meet it.
- Analytics measurement is refused site-wide by installing Google’s opt-out add-on from tools.google.com/dlpage/gaoptout.
- Nothing above depends on us: your browser can block third-party cookies outright, or clear this site’s cookies alone.
On Do Not Track
Browser signals such as Do Not Track are not honoured consistently across the web because there is no agreed standard for what they oblige a site to do. We rely on the cookie controls described above, which do have a defined effect.
Asking first
Anything beyond the strictly necessary is set only after you have answered, in the regions where that is required. Your answer is stored in your browser and nowhere else.
Refusing them
Browser settings let you refuse cookies site by site or across the board. Reading stays exactly the same without the analytics and ad cookies.
Questions
Questions go to the contact page.