What Every Site Collects

Server and security logs

Our sites are served through Cloudflare (edge security and delivery) and hosted on Google Firebase App Hosting. Standard technical data (IP address, browser, requested pages, timestamps) appears in short-lived infrastructure logs used for security, abuse prevention and reliability.

• Legal basis: our legitimate interest in operating secure websites (GDPR Art. 6(1)(f)).
• Retention: no more than 30 days: see retention.

Cookieless analytics

On every website, the documentation sites, clients.cuesoft.io and account.cuesoft.io included, we measure aggregate traffic with Cloudflare Web Analytics, a script that uses no cookies, no persistent identifiers, no fingerprinting and no cross-site tracking. It tells us page views and performance, not who you are.

Performance and error monitoring

Every website loads Datadog’s browser monitoring: the seven above, clients.cuesoft.io and account.cuesoft.io. It is operational telemetry, so it does not wait for the consent banner, and declining the banner does not stop it: it measures how quickly a page loads and records the errors it hits, so that we can keep the pages working. Each site’s own page states what Datadog receives there, the one cookie it sets, how long the data is kept and the legal basis: CueTA™, CueLABS™, CueHIRE™, Cueprise™, Storefront™, Cuelearn™, cuesoft.io, Client Work and account.cuesoft.io.

Ace, the assistant

If you chat with Ace, the messages you type are processed by our AI platform provider to generate an answer.

• Conversations live in your browser session and are not linked to an account: there are no accounts on our websites.
• Under our agreement with our AI provider, chat inputs are not used to train AI models.
• Please do not submit sensitive personal data through the chat.
• Legal basis: our legitimate interest in providing the assistant you choose to use (GDPR Art. 6(1)(f)).

Form acknowledgement email

Submit a form on CueTA™, CueLABS™, CueHIRE™ or Cueprise™ and we email you a confirmation. It is copied to the department that will handle it, and replies go there too, because the message is sent from an address nobody reads.

We send it through Brevo, our email provider, which receives your name and email address for that purpose, and on CueLABS™ the CV you attached, which travels with the message.

Brevo also records when you open the message and which links in it you click. We use that to tell whether confirmations are arriving and being read.

• Legal basis: sending the confirmation rests on the same basis as the form itself, set out on each site’s page. The open and click measurement rests on our legitimate interest in knowing our own mail reaches people (GDPR Art. 6(1)(f)): you may object at any time.
• The message loads images from our sites and from Brevo. Blocking remote images in your mail client prevents the open measurement.
• Retention: see retention.

What no site does

Nine websites (CueTA™, CueLABS™, CueHIRE™, Cueprise™, Storefront™, Cuelearn™, cuesoft.io, clients.cuesoft.io and account.cuesoft.io) carry analytics and advertising tags, and on every one of them those tags are gated behind a consent banner: until you press Accept, the site sets no advertising or analytics cookies and loads no advertising scripts and no third-party analytics beyond the cookieless Cloudflare measurement and the performance and error monitoring above. One further exception, on cuesoft.io only: the Spotify player for The CueShow™ loads if you click it and may then set Spotify’s own cookies, which the banner does not govern: see cuesoft.io. Each website’s own page lists exactly which tags it loads and who receives the data: CueTA™, CueLABS™, CueHIRE™, Cueprise™, Storefront™, Cuelearn™, cuesoft.io, Client Work and account.cuesoft.io. The documentation sites carry none of them, only the cookieless analytics above and the performance and error monitoring described on their page. No website ever asks for payment data: see the Terms of Service.