Privacy Policy

Service data

GuardHubUK processes personal data to operate accounts, job matching, messaging, and compliance workflows. We store only what is needed for the service and protect it with industry-standard security controls.

First-party registration source attribution

When you arrive from a campaign link that includes UTM parameters (for example Facebook Ads, WhatsApp, or organic social), we may store a first-party cookie named gh_ft_attr. That cookie records first-touch acquisition details such as source, medium, campaign, landing path, and a normalised channel. It is HttpOnly, SameSite=Lax, Secure on HTTPS, and lasts up to 30 days.

Purpose: understand which marketing channels lead to new Guard or Company registrations (internal measurement / reporting). If you later click a different campaign before registering, we keep the original first-touch values. On successful registration we store those values with your account for admin reporting. Accounts created before this feature have no attribution row and appear as Historical / Unknown.

This first-party attribution does not require the marketing consent banner and does not send your name, email, phone, SIA details, or documents to Meta or other advertising platforms.

Marketing consent cookie

When optional Meta advertising technologies are configured on the site, we show a marketing consent banner. Your choice is stored in a first-party cookie named gh_mkt_consent with value granted or denied (SameSite=Lax, Secure on HTTPS, up to 365 days).

Purpose: remember whether you allow Meta Pixel / Meta technologies for ad performance measurement. Declining keeps Meta Pixel from loading. You can change your choice later by clearing site cookies for this domain (the banner may appear again when Pixel is configured).

Meta Pixel and Meta technologies

GuardHubUK may use Meta Pixel (Meta / Facebook technologies) only when both of the following are true: the feature is enabled in our environment configuration, and you have granted marketing consent via the banner. If either condition is missing, Meta Pixel does not load.

Purpose of marketing measurement: help us understand whether ads and campaigns lead to completed registrations (for example a standard CompleteRegistration event after a successful new signup). We do not intentionally send name, email, phone, SIA licence numbers, documents, or other sensitive profile data to Meta through this integration.

Meta may process technical data according to its own policies when the Pixel runs. Review Meta's terms and your browser controls if you want further restrictions.

Your choices

• Marketing / Meta Pixel: Accept or Decline on the consent banner when shown; clear cookies to reset.
• First-party attribution cookie: used for internal registration source reporting; clear site cookies to remove it before you register if you prefer not to retain first-touch UTM data in the browser.
• Account data: contact us through normal support channels for access or deletion requests relating to your account.