What this site does with data.

Contact details move only when you choose.

Completing the form does not send information to Blancc. Your browser first builds a human-readable brief from the fields you complete.

Read this notice before sending: return to the project brief →

Two preference entries, no application cookies.

The current application code does not set cookies, advertising identifiers or cross-site tracking pixels. Browser storage is used only for the experience described below.

Cloudflare security features could set or access a security cookie if the account owner enables them or a protection is triggered. The live security-product configuration has not been verified, so this page does not claim that infrastructure-level cookies can never occur.

The ICO treats local and session storage as storage and access technologies even when data stays on the device. The motion control is always available, and the control below removes both Blancc entries. If you later choose a motion setting or revisit the homepage, the relevant preference entry may be created again.

Current measurement boundary

The site creates allow-listed page, link, form-intent, contact-handoff, tool-completion, result-export and web-vital events in an in-memory dataLayer and browser event bus. During the current page context, each event can include an in-memory first-touch snapshot: first landing pathname, external referrer hostname, and bounded utm_source, utm_medium, and utm_campaign values. That snapshot is not placed in local storage, session storage, or a cookie, and it ends on a full page load or when the page context ends. It never includes a query string or full referrer URL. Result-export properties are limited to the tool slug and action—copy, download, print or copy-and-open-enquiry. Website and AI opportunity tool answers are not included. The MVP scope planner and branding brief builder accept short project text locally; that text can appear in the result the visitor chooses to copy, download, print or carry to the contact page through their own clipboard, but application code does not send or store the answers, and tool answer text is excluded from analytics. The content production brief builder accepts 12 controlled selections without free text; its completion and export events exclude selections, counts and brief text, and its result is generated locally without network submission or browser storage. Choosing “Copy brief + open project enquiry” first asks the browser to copy the locally generated Markdown. Only after the modern Clipboard API confirms that copy does the site open the canonical contact page with an allow-listed service selection. If that confirmation is unavailable or copy is blocked, the visitor stays on the tool and the result appears in a local, read-only manual-copy field; the visitor must copy it and open the contact page themselves. Answers are not placed in the URL, browser storage, analytics event or network request, and nothing is attached, pasted or sent automatically. The visitor must paste the brief into the message field, review it and choose a sending route. The social media audit accepts 18 controlled radio selections without handles, profile URLs, account access, customer data or free text; its completion event includes no answers or counts, and its result and export are generated locally without network submission or browser storage. All six planning tools keep their inputs and generated results in the visitor’s browser unless the visitor deliberately copies, downloads, prints or pastes a result into another service. Contact-handoff events distinguish an attempt from a clipboard-ready brief, but neither means a message was sent or received. The bridge does not read contact names, email addresses, company fields, form values or message text from the site interface. UTM parameters are supplied in the landing URL, however, so a visitor or campaign operator could place unexpected text in them; normalisation and length limits do not guarantee that a UTM value is non-personal.

No tag manager, advertising pixel, analytics provider or remote measurement endpoint is connected. The locally bundled web-vitals library observes CLS, INP, LCP and TTFB and writes only the allow-listed measurements to the in-memory dataLayer and browser event bus described above; it does not send them off-device. Those in-memory events disappear when the page context ends and are not useful as a visitor record. A future analytics integration would require a fresh privacy and PECR review, an owner-approved UTM value allowlist, and updated disclosure before activation.

What stays here, and what leaves.

External services can determine their own purposes after you choose to use them. Read the privacy information shown by the relevant service before sending personal information.