Cookies and website tracking

This page describes the enquiry session cookie and the marketing integrations configured for the Phoenix51 website. The separate signup application may use additional cookies described in its own information.

Enquiry session cookie

The contact endpoint uses a cookie named p51_enquiry when preparing a secure form submission. It connects the submission with a temporary verification token. The cookie is scoped to /api/ and is configured as a session cookie, with HttpOnly and SameSite settings.

Analytics and marketing services

The production website is configured to load Google Tag Manager, HubSpot and LinkedIn Insight, together with a ForgeBOS visitor-tracking endpoint. These integrations can collect usage information and may set their own identifiers or cookies. Their behaviour also depends on the configuration held with each provider.

Google Tag Manager can load further tags configured by the website operator. A complete cookie inventory therefore needs to reflect the live configuration, rather than only the website files.

Visitor tracking

The ForgeBOS tracking integration sends the page path and a generated visit identifier to the signup application, including periodic visit signals. It is separate from the optional marketing checkbox on the enquiry form.

Your choices

You can manage cookies through your browser and use any consent controls presented by the enabled services. Blocking cookies or scripts may affect form submissions and other functions. The enquiry form’s optional marketing checkbox records a separate preference; it is not consent for all website tracking.

Further information

Read our privacy policy, Google’s privacy information, HubSpot’s privacy policy and LinkedIn’s cookie policy. Contact the data protection officer using the details in the privacy policy if you have questions.