Cookie Policy

AThe one cookie this website writes

It is called pixelpact, and it records your answer to the consent dock so that the dock does not ask again on every page. Until you press one of its two buttons, it does not exist: arrive, read a campaign guide, leave again without touching the dock, and your browser goes home carrying nothing of ours.

Notice what the value is not. It holds no identifier for you, no visit history and no link to an account — one of two words, and the date it expires.

BWhat each button on the dock does

Essentials only

Your answer is stored, the dock disappears, and that is the end of it. Every page of the site, every guide and every campaign category stays open to you; declining costs you nothing here.

Allow analytics

This grants permission for first-party measurement — counting which publisher guides get read and where readers stop. Being straight about the current state: no measurement script runs on this website today, so for the moment the permission is recorded and unused. Should that change, the script will be first-party, it will load only for readers whose answer was analytics, and this page will be updated in the same breath, naming what it sets.

Neither button is dressed to be the easy one. They are the same size, the same weight and the same shape, because a refusal that costs an extra click is not a choice.

CWhat is deliberately absent

No advertising network has a tag on this site. No social pixel, no remarketing list, no third-party script writing a cookie of its own on our pages. Nothing here builds a profile of you, sells one, or hands one to a data broker, and the campaign data our publishers generate is used to pay them and to catch fraud — never resold.

How placements and advertiser tags are vetted before a campaign goes live is a separate discipline, described on our compliance and brand-safety page.

DAttribution, and whose cookie is whose

A tracking link is the URL a publisher shares. It carries the click identifier inside the address itself, and the sale that follows is confirmed by the advertiser's server-to-server postback rather than by anything stored in a reader's browser on this domain. That is why the list above is one row long: the money is settled between two servers.

A reader who clicks a tracking link lands on the advertiser's own site, which may set cookies of its own. Those are the advertiser's to declare in the advertiser's notice — we do not set them, and we cannot read them. What we do hold, and for how long, is the click and postback record described in the Privacy Policy; the mechanics are on the tracking links and postbacks page.

One question comes up often enough to answer here: blocking cookies in your own browser does not affect your earnings. Payouts follow the clicks your audience makes, not the session you happen to browse in.

EThe signed-in area of the platform

Logging in to the platform starts a session, and a session needs a cookie to exist — that one is strictly necessary in the legal sense of the phrase and is not offered as a choice, because refusing it means refusing to be logged in. It lasts as long as the session does and carries no marketing purpose whatsoever.

FChanging or withdrawing your answer

The answer lives in your browser, which means you are the one holding it. Delete this site's cookies and pixelpact goes with them; the dock returns on your next visit and whatever you press then replaces what you pressed before. Leave it alone and it expires by itself twelve months after you gave it.

Every current browser can block or clear cookies for a single site, usually in the privacy or site-permissions part of its settings, and most can be told to clear them automatically at the end of a session. We deliberately do not reproduce a list of vendor help pages here: they move, they go stale, and your browser's own settings screen is more current than any list we could keep. Blocking cookies for this domain leaves the public site fully readable; it only becomes a problem in the signed-in area described in section E.

If you would rather ask a person what is stored against your account, write to [email protected] and we will tell you, and delete it where the law allows.

GCookies as personal data, and changes to this page

Where something stored in your browser connects to an account, it stops being merely a cookie question and becomes a data-protection one: the lawful bases, the retention rows and the rights that go with them are in the Privacy Policy, and the agreement behind the account is in the Terms & Conditions.

This page is rewritten whenever what the site stores changes — a new cookie, a different lifetime, a measurement script switched on — and the date at the head of it moves at the same time. It is a description of the code as it stands, so it is only worth reading if it stays true to the code.