Cookie Policy
Everything we store on your device, why, for how long, and how to change your mind.
Last updated: · version 2026-08-01
1. The short version
We store a handful of things on your device. Four of them are needed for the site to work and to remember the choices you have already made. One optional category: analytics, which sends your visit to Google Analytics so we can see how the site is used. It stays off until you switch it on.
Nothing optional runs before you choose. Refusing costs you nothing and changes nothing about the site. You can change your mind at any time with the Cookie settings link at the bottom of every page.
2. The full list
This is everything — cookies, and the browser-storage keys that are not technically cookies but do the same job and deserve the same disclosure.
| Name | Purpose | Duration | Type | Provider | Category |
|---|---|---|---|---|---|
cc_cookie | Stores your cookie choices and the version of the cookie policy you saw, so we do not ask again on every page and can prove what you agreed to. | 6 months (182 days) | Cookie | SocialPostxr (first party) | Strictly necessary |
sy-preferred-currency | Remembers which currency prices are shown in (USD, GBP or EUR) — either the one you picked from the selector, or the one we inferred from the country your network reported, so we do not have to work it out again on every page. | Until you clear your browser storage | localStorage | SocialPostxr (first party) | Strictly necessary |
__cf_bm | Set by Cloudflare, our CDN and security layer, to tell automated traffic from human visitors so that attacks, scraping and abuse can be blocked before they reach us. It carries no account identifier and is not used to track you between sites. | 30 minutes | Cookie | Cloudflare, Inc. | Strictly necessary |
sy-network-assessment | Caches a one-off measurement of your connection speed for the current tab, so we can turn heavy animations down on slow connections instead of re-measuring on every page. | Until you close the tab (session only) | sessionStorage | SocialPostxr (first party) | Strictly necessary |
_ga | Google Analytics. Assigns a random identifier to your browser so repeat visits can be counted as one visitor rather than several. | 2 years | Cookie | Google Ireland Limited | Analytics |
_ga_ZFVKPDKDKK | Google Analytics. Tracks the state of your current visit (when it started, how many pages you viewed). | 2 years | Cookie | Google Ireland Limited | Analytics |
sy-detected-country retired | No longer used. Until August 2026 this cached a country code guessed from your IP address by a third-party lookup service. That lookup has been removed; we now read the country your CDN already reports, and nothing is stored. This entry remains listed only because we actively delete any leftover value on your next visit. | Deleted on sight | localStorage | SocialPostxr (first party) | Strictly necessary |
2.1 Why storage keys are listed too
Some of what we store uses localStorage and sessionStorage rather
than cookies. The law does not care about the mechanism — the Privacy and Electronic
Communications Regulations cover storing or accessing information on your device however
it is done. Listing only cookies would leave things out, so we list everything.
3. Changing your mind
- On this site: use the Cookie settings link in the footer. Turning a category off deletes what it stored, immediately.
- In your browser: every browser can block or clear cookies and site data. Blocking the strictly necessary ones means we cannot remember your cookie choice, so you will be asked again on each visit.
- For Google Analytics specifically: the opt-out browser add-on blocks it across every site you visit.
4. When we ask you again
Every consent we record is stamped with the revision number of the cookie policy you were shown. We increase that number whenever what we store on your device changes in a way you would care about: a new cookie, a new company receiving data, a longer retention period, or a cookie moving between categories. When the number goes up, previously recorded choices stop counting and we ask again, because you cannot have consented to something that did not exist when you chose. We do not increase it for wording or layout changes that leave the actual storage untouched — re-asking for no reason trains people to click "Accept all" to make the banner go away.
The current cookie policy revision is 1.
5. Why we do not keep a server-side record of your cookie choice
Your choice is recorded in a cookie on your own device, called cc_cookie. It holds which categories you allowed, the version of this policy you were shown, the time you chose, and a random identifier that is not linked to your account or to anything else we hold. We do not copy that record to our servers.
We could log every consent decision server-side, and some sites do. We have decided not to, because doing it would mean creating a new database of visitor records — tied to an identifier, timestamped, and retained — for people who have often done nothing but visit the home page and click "Reject optional". That is more personal data collected about more people than we hold today, gathered specifically from those exercising a privacy choice. Building it would work against the principle it is meant to serve. Article 5(1)(c) of the UK GDPR asks us to collect the minimum necessary, and a server-side consent log is not necessary here.
We can still show what we asked and what a visitor would have seen. This policy is versioned, the version number is stamped into the consent cookie, and the banner wording and cookie table for each version are in our source control history with the date each went live. That establishes what was presented and when. Combined with the record on the visitor's own device, it is proportionate to a marketing site that sets one analytics cookie with consent, and it is a position we are content to explain to the ICO.
If our processing changes so that this reasoning no longer holds — special category data, consent for something with a real effect on someone, or a volume of consent-dependent processing that makes device-side records inadequate — we will build proper consent logging and say so here. Until then, adding it would be collecting more data to look more compliant, which is not the same as being more compliant.
6. More
Our Privacy Notice covers everything else: what personal data we hold, our lawful basis for each use, who receives it, and the rights you have. Questions about either go to privacy@socialpostxr.com.