What happens to what you submit.
A plain technical description of how our marketing forms work.
What we collect
Forms on this site collect the fields you type: name, email, organisation (where asked), your role, answers to questionnaires, scorecard answers, and your consent choices. We also record an optional source and campaign from the page address, and the local path of the page you started on.
How it is sent
Submissions are sent from your browser to our server and passed to a customer relationship management system when one is connected. If that connection is temporarily unavailable, your saved enquiry remains queued for our team.
What stays in your browser
We do not save your form details in browser storage. When you read Insights, we save the article source in session storage so a later enquiry can be attributed to that article. Analytics preferences are saved in local storage.
First-party readership counts
Insights uses a hashed, HttpOnly visitor cookie to count views and shares once per article, visitor and day. The database stores a further keyed hash rather than the cookie value. Known bots, signed-in editors and previews are excluded.
Updating an enquiry
After an application is saved, a signed, HttpOnly first-party cookie lets the same browser update that enquiry for seven days. This essential cookie contains no form answers and is separate from optional analytics consent. If it expires or is unavailable, reply to our email to request a change.
Optional analytics and advertising tags
If configured for Credentialcraft, Google Analytics, Google Ads, Meta, LinkedIn and Microsoft Clarity load only after you give consent. Clarity records interactions to help us understand how the site is used. You can change your choice at any time using Cookie preferences. Withdrawing consent after LinkedIn or Clarity has loaded refreshes the page to remove its running script. Without permission, none of these scripts are loaded.
Campaign and click identifiers
When you arrive from an ad or campaign link, campaign parameters and click identifiers (such as gclid or fbclid) from the page address are kept in session storage and attached to any form you submit, so we can understand which campaign led to an enquiry. They are not form fields you fill in.
Cookies and third parties
If you consent, enabled Google, Meta, LinkedIn and Microsoft tags may set their own cookies and receive information about your visit, which those providers process under their own terms. Our own readership and enquiry-edit cookies are first-party and are not shared.
Email delivery is not currently configured. A confirmation or welcome email is not sent automatically, and we will not claim otherwise.
Marketing consent
Optional updates are only intended when you tick the separate consent box. Requesting a resource or application does not depend on it. The newsletter requires opting in.
Spam protection
A hidden form field helps detect automated submissions. Real visitors never see or fill it.
Public resource links
Resource links that point to PDFs are public links, not secure gating.
What this page is not
This page describes technical handling only. It is not a verified legal policy and does not state a legal entity, address or retention period. Please contact us through the contact page with any question or request about your data.
Meeting bookings
Our booking page, paid landing pages and application confirmation use an embedded HubSpot calendar. On the application confirmation, your name and email are passed to HubSpot to prefill the calendar. They are not added to this website’s URL or booking analytics. The scheduling tool works without optional advertising cookies; we pass your analytics choice to the embed. With optional consent, a successful booking sends appointment events to GA4 and Meta and a separate Google Ads booking conversion when configured. It does not count as another application enquiry.