Cookie Policy
Last updated: 21 April 2026 · Effective: 21 April 2026
This Cookie Policy explains how CueTheScene (operated by MARKETEZEAI LTD, company number 16787865, ICO registration ZC119363) uses cookies, browser local storage, and similar technologies when you visit cuethescene.com or use the Service. It sits alongside our Privacy Policy and Terms of Service.
It is written for compliance with the UK Privacy and Electronic Communications Regulations 2003 (“PECR”), the ePrivacy Directive (2002/58/EC) as implemented in EU member states, the UK GDPR, and the EU GDPR.
1. What cookies and similar technologies are
A cookie is a small text file that a website places on your device when you visit it. Related technologies include browser local storage and session storage (key/value data kept in your browser), and pixels or beacons (small requests used to measure page views without writing a cookie).
PECR and the ePrivacy Directive require your prior consent before any non-essential cookies or similar technologies are set on your device. Cookies that are strictly necessary to deliver a service you have actively requested (for example, keeping you signed in after you sign in) do not require consent, but we still list them here for transparency.
2. Categories we use
We group the items we set into two categories:
- Strictly necessary — required to deliver core Service functionality (authentication, security, abuse prevention, remembering your cookie choice). These are set without asking, because without them the Service cannot function.
- Analytics (consent-required) — help us understand which features are used and where the product breaks, so we can improve it. These are off by default and only activate after you click Accept in the cookie banner.
We do not use advertising cookies, cross-site tracking pixels, or third-party marketing trackers. We do not sell personal data.
3. The items we set
The table below lists each cookie or storage item, who sets it, why, how long it lasts, and whether it requires consent. If we add or remove any, we will update this page and, where required, re-prompt for consent.
| Name / pattern | Set by | Purpose | Duration | Category |
|---|---|---|---|---|
__session, __client_uat, __clerk_* | Clerk (authentication provider) | Keeps you signed in, protects the session against CSRF/replay, and rotates session tokens. | Session / up to 7 days | Strictly necessary |
cts_cookie_consent | CueTheScene (browser local storage) | Remembers whether you accepted or rejected analytics so we do not re-prompt you on every visit. | Until you clear it or change your mind | Strictly necessary |
cf_bm, cf_clearance | Cloudflare (our infrastructure provider) | Bot management and challenge verification — distinguishes humans from automated traffic and blocks abusive requests. | cf_bm: 30 minutes · cf_clearance: up to 1 year | Strictly necessary |
| None (beacon only) | Cloudflare Web Analytics | Counts aggregated page views using a cookieless beacon. No cookies or local storage; no cross-site identifier. | n/a | Strictly necessary (no personal data) |
ph_* and related local-storage keys (e.g. ph_{project}_posthog) | PostHog (analytics processor, EU region) | Measures feature usage, funnel steps, and errors so we can improve the product. Session replay and autocapture are disabled. | Up to 12 months | Analytics (consent-required) |
Exact cookie names from third parties can change when providers update their SDKs. The above reflects the names in use at the time of publication; the categories and retention windows are what matter for your rights.
4. Your choice and how we record it
On your first visit you will see a cookie banner with two equally prominent buttons: Accept and Reject. Neither option is pre-ticked. Closing the banner without choosing, or navigating away, does not count as consent — PostHog remains opted-out until you actively accept.
Your decision is stored in a browser localStorage key named cts_cookie_consent with the value accepted or rejected. We do not transmit this value to our servers. Because the value is tied to your browser, a different browser, a private window, or a cleared storage state will cause the banner to appear again.
5. Changing your mind
You can change your decision at any time by clearing the cts_cookie_consent key from browser storage — the banner will reappear on the next page load. A dedicated “Cookie settings” control will be added to the site footer ahead of public launch; until then, clearing site data for cuethescene.com in your browser settings achieves the same result.
You can also block or delete cookies through your browser. Instructions for the major browsers are here: Chrome, Firefox, Safari, Edge. Blocking strictly-necessary cookies may mean you cannot sign in or that the Service does not work correctly.
6. Do Not Track and Global Privacy Control
There is no single agreed standard for “Do Not Track” (DNT) signals, so most services (including ours today) do not respond to them. We do, however, keep analytics opted out by default, which achieves the same practical outcome. We will adopt Global Privacy Control (GPC) response once there is a stable, widely-used implementation path on our stack.
7. International transfers
PostHog is used via its EU region (eu.i.posthog.com). Clerk and Cloudflare operate global infrastructure; transfers outside the UK and EEA are covered by appropriate safeguards (UK International Data Transfer Agreement or EU Standard Contractual Clauses). See the processor table in our Privacy Policy for the full list, jurisdictions, and transfer mechanisms.
8. Changes to this Cookie Policy
We will update this page whenever we add, remove, or materially change a cookie or similar technology. Where a change affects analytics or any other non-essential category, we will re-prompt for consent via the banner. The “Last updated” date at the top of this page reflects the most recent change.
9. Contact
Questions about this Cookie Policy: hello@cuethescene.com. You have the right to complain to the Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint if you believe we have not complied with data protection law.