Cookie Policy

1. How we use cookies

Cookies are small text files stored on your device. We use strictly necessary cookies to provide requested website functions, protect forms and remember your cookie choice. These cookies do not require consent under PECR, but we explain them here.

We ask for consent before Meta Pixel, Meta advertising identifiers or related non-essential measurement operate. Visiting or continuing to use the website does not count as consent. Rejecting marketing cookies does not restrict access to the website or its forms.

2. Cookies and storage we use

Website cookie register
Name	Provider	Category	Purpose	Duration
cpd_marketing_consent	CPD Qualifications™	Essential	Records whether marketing technology is allowed or rejected.	180 days
cpd_consent_id	CPD Qualifications™	Essential	Random identifier used to apply a later withdrawal to Meta tracking attached to an enquiry. It does not contain your name or contact details.	180 days
_fbp	Meta	Marketing	Helps Meta measure visits and advertising conversions.	Up to 90 days
_fbc	Meta	Marketing	Records a Meta advertising click identifier when one is available.	Up to 90 days

Staff dashboard authentication may also use essential Supabase session cookies after an authorised staff member signs in. Their duration depends on the authenticated session. We found no Google Analytics, Google Tag Manager, Hotjar or Microsoft Clarity installation in the website application.

3. Your choices and withdrawal

The first time you visit, you can choose “Accept all”, “Reject non-essential” or “Customise preferences”. The choices have equal prominence and marketing is off in the custom settings unless you actively turn it on.

Your choice is remembered for 180 days. You can reopen the same controls at any time using “Cookie settings” in the website footer. Turning marketing off revokes Meta consent, removes the Meta cookies available to this website and prevents future browser and server-side advertising events associated with that choice. You can continue to use the website after rejecting or withdrawing consent.

4. Meta advertising measurement

If you consent, Meta Pixel may record page views, visits to relevant accreditation or directory pages and successful enquiry events. Meta Conversions API may send a matching server-side event after a successful enquiry. Browser and server events use the same random event identifier to avoid double counting.

We do not send enquiry text, names, telephone numbers, organisation names, websites or countries to Meta. A normalised email may be converted to a one-way SHA-256 hash on our server for matching when consent has been given. Meta may receive browser and network information, Meta cookie identifiers, the form type and non-sensitive lead classification data. See Meta's privacy policy for information about Meta's processing.

5. Changes to this policy

We will update this policy and request fresh consent where a material change introduces a new non-essential purpose or third party. The date at the top identifies the latest revision. Privacy rights and contact details are explained in our Privacy policy.