Log in Hire talent

Legal

Cookie Policy

How and why NE Project Solutions uses cookies.

Last updated — no approved version has been published yet

Draft template — not yet legally reviewed

The structure of this document is in place, but every section below is placeholder text. Nothing here has been drafted or approved by a legal adviser, nothing on this page is binding, and none of it may be relied on. The final wording will be supplied by NE Project Solutions’ legal adviser before launch. Each section lists what that wording has to establish.

1. What cookies are

Placeholder — the wording for this section has not been written and will not be written by us. See the notice above.

To be supplied by the client

A plain-English explanation, and the distinction between strictly-necessary and optional cookies.

2. Cookies we use

Placeholder — the wording for this section has not been written and will not be written by us. See the notice above.

To be supplied by the client

A real inventory from a cookie scan of the deployed site: name, provider, purpose, duration, and first- or third-party. As built there are no optional cookies to list — the only cookies set are the authentication session and, while it is switched on, the pre-launch access gate. The scan still has to be run against the live site before this section is signed off.
Confirmation of which are strictly necessary — under PECR, everything else needs consent BEFORE it is set.
How to describe the consent record itself: the visitor's choice is held in the browser's local storage, not in a cookie, and is never sent to a server.

3. Analytics & measurement

Placeholder — the wording for this section has not been written and will not be written by us. See the notice above.

To be supplied by the client

Which analytics and marketing tags are actually deployed at launch. As built: none. The GA4 loader exists but is inert — it renders nothing while no measurement ID is configured, and nothing at all until analytics consent has been granted.
The GA4 measurement ID once the property exists, who controls that property, and the data-retention period selected in it.
Whether any tag fires before consent is given — if it does, that is a PECR problem to fix in the build, not to describe here.

4. Managing your preferences

Placeholder — the wording for this section has not been written and will not be written by us. See the notice above.

To be supplied by the client

Wording that matches the mechanism now in the build: a banner appears on the first visit with Accept and Reject presented identically, covering two categories — strictly necessary (always on, not refusable) and analytics (off until accepted). No optional script loads until analytics is accepted.
Wording for changing or withdrawing consent later. In the build that is the “Cookie preferences” control in the site footer, which re-opens the same banner; a withdrawal takes effect immediately and clears any analytics cookies already set.
Browser-level controls, and what happens if the visitor clears their browser storage — the stored choice goes with it and the banner asks again.

5. Contact

Placeholder — the wording for this section has not been written and will not be written by us. See the notice above.

To be supplied by the client

Where cookie and tracking questions should be sent.

Until a dedicated legal and data-protection address is published, questions about this document can be sent through the contact page.

Contact NE Project Solutions