Cookie Policy

Cookies are small text files stored on your device by your web browser when you visit a website. They serve various purposes including remembering your preferences, enabling functionality, and helping us understand how visitors use our site.

In addition to traditional cookies, we also use localStorage and sessionStorage (two browser storage mechanisms) to persist certain preferences locally on your device. Everything either mechanism holds is listed by name in section 04 — the table is meant to be the complete inventory, not a sample of the notable entries.

We use cookies and similar technologies for the following purposes:

• Analytics: to understand how visitors interact with our website, including a replay of your session (only with your consent — see section 06)
• Advertising and conversion measurement: to tell whether an ad we paid for actually led to a download or a purchase, and to build the audiences we advertise to (only with your consent)
• Bot Protection: Cloudflare Turnstile uses cookies to distinguish legitimate users from automated bots
• Preferences: to remember your cookie consent choice and theme preferences
• Session Management: to maintain your login session in the account portal
• Support Chat: to keep your conversation with the support assistant across a page reload, and to avoid re-asking you the same thing twice
• Error and performance monitoring: to find out that a page crashed, or was unusably slow, for a real visitor rather than only in testing (see section 07)

Everything on this page belongs to one of three categories. Two of them are yours to switch on and off. The first is not, and we would rather say so plainly than present you with a toggle that does nothing.

• Strictly necessary and functional— the account session, Cloudflare's bot protection, the record of the consent choice itself, your support-chat transcript, and the small preferences that stop the site re-asking you things (which edition you last looked at, which banners you dismissed). These are not optional: there is no version of this site that signs you in, protects a form from bots, or remembers that you declined, without storing something on your device. None of them is used for analytics or advertising, and none is shared with an advertising network. The preference centre shows them as a single locked Functional (always on) row for that reason.
• Analytics — PostHog product analytics, including session recording (section 06), and Google Analytics 4. Off until you accept.
• Marketing — the Meta, Microsoft Advertising, X and LinkedIn advertising tags, and Google Ads conversion measurement. Off until you accept.

Analytics and Marketing are independent of each other. “Accept all” and “Decline all” in the banner set both at once; “Customize” in the banner, and the preference centre in section 09, set them one at a time.

A note on what “off” means in practice, because it is not quite the same for every vendor. The Meta, Microsoft, LinkedIn and X tags are not fetched at all until you have accepted marketing — not fetched and then told to stay quiet, but never requested, because requesting a script from an advertising network already tells that network your IP address, your browser and the page you are on, and no consent flag evaluated afterwards can reach back and undo that. Google's tag is the exception: it loads under Consent Mode v2 defaults of denied (section 08), which means it sends an identifier-free, cookieless ping and writes nothing to your device until you accept. “The script is on the page” and “the script is collecting” are different statements, and this policy should not blur them in either direction.

Several of the advertising tags named in this policy only render when their account ID is configured for the deployment you are visiting; where it is not set, the component returns nothing and the vendor's script is never requested. They are named here anyway, because the code that loads them ships on every page and only an environment variable stands between it and being live. A policy that listed only the tags that happened to be switched on this week would be wrong again the moment one was switched on.

Changing your mind. Your choice is stored on this device, not against your account, and the banner does not reappear once you have answered it. To revise it, open the preference centre at https://www.cuesync.live/legal/cookies#preferences. Changes apply immediately on this device with no page reload and no separate save click: turning Analytics off stops PostHog capturing and stops the session recorder in the same click. Clearing your browser's site data for this domain removes the stored choice entirely and brings the banner back on your next visit.

Browser signals. If your browser sends Global Privacy Control or Do Not Track, we treat that as a standing refusal of both Analytics and Marketing — it overrides whatever is stored on this device, and nothing has to be clicked for it to take effect. Section 10 sets out exactly how it interacts with a choice you make yourself.

Every cookie and browser-storage entry this site sets, or that a third party sets through it. Rows marked Marketing * carry a caveat that is explained under the table; please read it, because it is the one place where something is written to your device before you have chosen.

We use PostHog for website and product analytics: which pages are opened, which features are used, how far people get through a flow, and — separately and more significantly — a replay of the session itself, which has its own section below.

PostHog is not started at all until you have accepted the Analytics category specifically. Accepting Marketing on its own does not start it, and neither does a Global Privacy Control or Do Not Track signal that you have not explicitly overridden. It runs in identified-only person mode, which means a person profile is only ever created for someone who signs in; a visit by someone who does not sign in is recorded against a random device identifier and is not assembled into a profile.

PostHog is hosted at us.i.posthog.com, in the United States. Requests from your browser are sent to a path on this domain (/ingest) which our server forwards to PostHog. That is a deliberate choice and worth stating plainly: it exists so that content blockers which filter requests to PostHog's own domain do not silently break our analytics. It does not change who receives the data, and it does not override your consent choice — nothing is sent down that path until you accept.

This is the most intrusive thing on the site, so it gets a section of its own rather than a row in a table. When you have accepted analytics, PostHog records a replay of your visit that we can play back afterwards.

We use Sentry to find out when a page has actually broken for a real visitor rather than only in testing. It loads on every page, after the page has finished loading, and it is deliberately not behind the analytics toggle: a site that only learns about its crashes from the visitors who agreed to be measured does not learn about its crashes. We think that is a fair basis for running it; if you disagree, say so and we will tell you what we can exclude.

Sentry sets no cookies here. What it captures is the error itself with its stack trace, the URL it happened on, your browser and operating system version, and your IP address. Authorization headers, tokens and query-string credentials, sensitive request fields, and local variable values are stripped before an event is sent.

Every page on this site sets Google Consent Mode v2 defaults before any Google tag runs, for compliance with the EU Digital Markets Act (DMA). This happens whether Google Analytics is loaded directly by our own tag or through a Google Tag Manager container. Until you accept, all four signals are set to denied, and each is then resolved from the category it belongs to rather than from one collapsed yes-or-no — accepting analytics does not grant advertising storage, and vice versa:

• analytics_storage — denied until you accept analytics
• ad_storage — denied until you accept marketing
• ad_user_data — denied until you accept marketing
• ad_personalization — denied until you accept marketing

These signals are updated to granted only for the categories you accept, whether that is through the banner or the preference centre, and are set straight back to deniedif you withdraw. The same update is pushed to the Microsoft UET tag and to the Meta Pixel, which have their own consent mechanisms rather than reading Google's. A browser privacy signal is applied before any of this: if Global Privacy Control or Do Not Track is being sent and you have not explicitly overridden it here, the stored record is not consulted at all and every signal stays denied.

A denied Google tag is not a silent one: it still sends an identifier-free, cookieless ping, so Google can model aggregate traffic without storing anything on your device or identifying you. That is what Consent Mode is, and it is the reason the Google tag is allowed to load before you have chosen when the LinkedIn and X tags are not.

We honour two browser-level privacy signals, and we treat both the same way: as a standing refusal of Analytics and Marketing, not as one preference to be weighed against another.

• Global Privacy Control — the Sec-GPCrequest header and the matching browser property. California's CCPA/CPRA regulations name it as an opt-out preference signal a business must honour, and Colorado and Connecticut followed.
• Do Not Track — the older DNT header. No law compels it. We have always honoured it and could not find an honest reason to stop.

While either signal is being sent, the stored consent record on this device is not consulted at all: PostHog does not start, session recording does not start, none of the Meta, Microsoft, LinkedIn and X advertising tags is requested, and every Google Consent Mode signal stays denied. Nothing needs to be clicked for that to be true, and it applies even if you accepted everything on a previous visit.

This page used to carry an exception here: the LinkedIn and X tags consulted the raw stored record rather than the signal-adjusted answer, so they kept loading for a visitor who had accepted Marketing and switched a signal on afterwards. They no longer do. All four advertising tags now ask the same question, and a check in our build refuses to pass while any of them consults the raw record — which is also why this paragraph exists rather than the exception simply disappearing: a fixed defect is worth recording, and the same check fails if this paragraph is left claiming a problem that has been dealt with.

The signal reaches our servers too, which matters for the part of this that does not happen in your browser. Requests our own back end sends to an analytics or advertising platform read the Sec-GPC and DNTheaders on your request before they read anything you stored, and an asserted signal denies. That includes the conversion report our server sends when a purchase completes: the decision is captured at the moment the checkout opens, from your browser and from that same request, and both halves have to say yes. Without it, a signal switched on months after an “Accept all” would have stopped the tags on the page and left the server-side reporting running on a stale grant.

You can still override it.The preference centre in section 09 used to replace itself with a notice when a signal was detected, which honoured the signal but also left anyone sending one with no way to say “actually, analytics is fine”. The toggles are live now. They sit at off while the signal stands, and switching one on is recorded as an explicit choice for this browser that takes precedence over the signal. The panel tells you which state you are in either way, because a signal that is respected and a signal that is quietly ignored look identical from the outside.

That override is per-signal and does not carry forward. If you overrode Do Not Track a year ago and have since switched on Global Privacy Control, the new signal is a request we have never asked you about, so it takes effect as a fresh refusal rather than inheriting the old permission — that is the whole job of the cuesync-consent-signal-ack entry in section 04. And if that record cannot be read at all, for instance in a private window that blocks storage, the refusal stands rather than the permission.

We may update this Cookie Policy from time to time. Changes will be reflected in the "Last updated" date at the top of this page.

For more information about how we handle your data, see our Privacy Policy.

If you have questions about our use of cookies, contact us at contact@cuesync.live.