storefront.cuesoft.io: Storefront™

A storefront we have built for somebody else is a different matter: it is that business’s own website, they are the controller of whatever their customers enter on it, and this policy does not describe it. Where that storefront runs on a licensed Cueprise™ deployment, what Cuesoft holds as their processor is set out in the Cueprise™ privacy notice. Where it was built as a CueHIRE™ engagement against their own back office instead, that notice does not reach it and the engagement’s own data terms govern what we hold and for how long.

Enquiry form

• What: your name, work email, business name, the sector you picked from the list, and anything you added in the message box. We also record the country Cloudflare’s edge places you in: derived from your IP address as you submit rather than asked for on the form, and stored as the country name, not the address itself. It tells us which of our two entities should answer you.
• Why: to reply to your enquiry and scope the site you are asking for.
• Where: records are stored in Airtable, our forms database, in the same table as CueHIRE™ enquiries: building a storefront is a CueHIRE engagement, so it is one pipeline rather than two.
• Legal basis: our legitimate interest in responding to the business enquiry you sent us (GDPR Art. 6(1)(f)), and the equivalent legitimate-interest basis under the NDPA: you may object at any time. An engagement that follows is between Cuesoft and your business rather than with you: if you enquired as an employee or representative you are usually not a party to it, so contract performance cannot become the basis for your own name and work email. Where an engagement is signed with you as an individual, processing under it rests on that contract (Art. 6(1)(b)).
• Confirmation: we email you a receipt, copied to storefront@cuesoft.io: see what every site collects.

Analytics and advertising tags: opt-in only

This site uses analytics and advertising tags, gated behind a consent banner. None of them loads, and none of their cookies is set, until you press Accept (the cookieless Cloudflare measurement described in what every site collects and the performance and error monitoring below are separate and run either way):

• What they receive: a cookie or device identifier, your IP address, the page URLs you visit on this site and the referring URL, plus basic device and browser metadata and the page-view events themselves. Google Analytics uses the IP address in passing to derive an approximate location and then discards it: the address itself is not stored, and the location is what is kept. Google Analytics keeps this for 14 months: see retention. We do not send your form contents to any of them.
• One event beyond page views: when you send us a brief, Google Ads, Meta, LinkedIn and X are told that it happened, so they can credit the ad you arrived from. Google Analytics is not: it receives the page views described above and nothing more. The event records the fact of the brief and nothing else: not your name, not your email, not your phone number, and not what you wrote.
• If you are signed in to Google: we have Google signals switched on, so where you are signed in to a Google account that has Ads Personalisation enabled, Google may connect this visit to that account and combine it with what Google already holds there: location, search history, YouTube history and activity on sites that partner with Google. What that does, precisely: it lets us see age, gender and interest summaries, and it lets Google build advertising audiences that can reach you across your devices. It does not merge your devices together in our own reports (since February 2024 Google signals is not part of how Analytics counts users), so we do not see your phone and your laptop as one person. And Google uses the visit for its own ads personalisation as well as for our measurement. You control it on Google’s side, independently of us, at myadcenter.google.com and Google’s activity controls: switching Ads Personalisation off there stops it for every site, not just ours. Declining our banner prevents it entirely.
• Decline and none of them load. The site works identically either way.
• Withdraw any time via the site’s Cookie preferences link. Withdrawal stops the tags loading from that point on; it does not delete cookies already set (you can clear those in your browser). What happens to data already collected differs by provider: Google Analytics holds it as our processor, on our instructions, so the rights page reaches it. The exception is what Google signals feeds into Google’s own ads personalisation, which Google controls rather than us: manage that in your Google account. The four advertising platforms hold what they collected as independent businesses under their own policies: see processors and platforms.
• An opt-out preference signal (Global Privacy Control) overrides a stored opt-in for as long as your browser sends it.
• Legal basis: consent (GDPR Art. 6(1)(a)); California treatment is on the United States page.

Performance and error monitoring

This site loads Datadog’s browser monitoring. 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.

• What Datadog receives: the page addresses you visit and the page that referred you, load and resource timings, your clicks (which element, never anything you type), script errors and failed requests, your browser, device and operating system, and your IP address, from which it derives an approximate location. Nothing links a session to your name or email. No session is recorded as a replay, with one exception: if a page fails to render correctly, Datadog records that session as a replay so we can see what went wrong. A replay shows the page as it appeared to you, and the contents of form fields are masked.
• Cookie: one first-party session cookie, _dd_s_v2, holding a random session identifier that lapses after 15 minutes of inactivity (4 hours at most).
• Role and retention: Datadog acts as our processor, on our instructions, and keeps the data in the United States for no more than 30 days, under the safeguards on the transfers page; see processors and platforms and retention.
• Legal basis: our legitimate interest in keeping the pages working (GDPR Art. 6(1)(f)); you may object at any time.

What this site does not do

It takes no payment and quotes no price: a storefront is included with a Cueprise™ licence, and built as a CueHIRE™ engagement otherwise. Apart from the performance and error monitoring above, nothing loads before you accept, and the cookieless Cloudflare measurement described in what every site collects stays outside the consent gate because it sets no cookie.