Cookie Policy
Last updated · 2026-06-09
This policy explains the cookies Brieflings uses and the choice you have over them. It sits alongside our privacy policy.
What cookies are
A cookie is a small file a site stores in your browser. Some cookies are needed for a site to work at all; others are optional.
How we use cookies
Brieflings sets first-party cookies for the site itself. On our public marketing pages only (home, pricing, signup) we also use the third-party Meta Pixel to measure advertising; it sets the cookies marked “advertising” below and loads only if you accept the Advertising category on the banner. The Meta Pixel never runs once you sign in. If you accept advertising, we also send Meta a set of conversion signals from our servers through the Meta Conversions API to measure conversions such as a signup or subscription. To help Meta match these to the right account, they carry a limited set of identifiers — a scrambled (hashed) version of your email and your country, the advertising cookies, and your IP and browser details — but never the topics you follow, the briefs you read, or your chats. On our marketing pages the Pixel also uses Meta's advanced matching, which hashes contact details you enter there (such as your email) in your browser and sends the hashed value to Meta. The privacy policy describes this. We would also like to use analytics cookies to understand how the site is used and to record sessions so we can diagnose problems users report; those load only if you accept the Analytics category. The privacy policy describes the analytics, session-replay, and advertising processing in more detail.
The cookies we set
| Name | Purpose | Type | Duration | Provider |
|---|---|---|---|---|
| brieflings_session | Keeps you signed in | Strictly necessary — exempt from consent | Up to 14 days | First-party |
| brieflings_consent | Remembers your cookie choice so we don't ask again | Strictly necessary — exempt from consent | 6 months | First-party |
| ph_* | Distinguishes visitors, remembers the consented analytics state, and links page interactions to the session replay we use to diagnose problems | Consent required | 12 months | First-party — data processor: PostHog (EU Cloud) |
| _fbp | Identifies the browser to measure Meta ad performance, on our public marketing pages only | Consent required (advertising) | Up to 90 days | Meta Platforms Ireland |
| _fbc | Stores the ad click that brought you to a marketing page, for ad-performance measurement | Consent required (advertising) | Session | Meta Platforms Ireland |
Strictly necessary vs. consent
The two named cookies above are strictly necessary — one keeps you signed in, the other records the choice you make on the consent banner — so they are exempt from consent and are always set. The banner offers two optional categories, Analytics and Advertising, each off by default; nothing in a category is set unless you turn it on. You can accept all, reject all, or choose per category.
Managing your choice
You can change your mind at any time: reopen the cookie banner to make a new choice. Withdrawing your consent is as easy as giving it — reopening the banner and turning a category off stops it straight away: no further analytics events or session recording, and no further advertising cookies or server-side Conversions API signals. You can also clear or block cookies through your browser settings; blocking the strictly-necessary cookies will stop you being able to sign in.
Changes to this policy
If our cookie use changes we will update the date shown above and, where it affects your choice, ask you again through the banner.