Application behaviour
Advertising pixels, social-media embeds and marketing cookies are not installed. A technical local-storage entry remembers your privacy choice, notice version and date for 180 days. Optional GPIRL analytics only start when you select Site analytics and save your preferences. They use a random session identifier in session storage, renewed after 30 minutes of inactivity. No analytics identifier is stored before consent. Reopen Cookie preferences to reject or withdraw; withdrawal removes the current session's events and analytical enquiry association. Choices are separate for each website. Blog filters and form status remain in page memory.
Optional analytics and enquiry attribution
Analytics remain off unless offered in Cookie preferences and explicitly enabled. When enabled, GPIRL measures pages, source categories, campaign codes and clicks using a pseudonymous session identifier, on the basis of consent. No IP address, email address, full URL, form text or screen recording is stored in analytics. Events and journey associations are retained for 90 days. Session control and suppression records may be retained for 180 days to prevent late events from restoring a withdrawn session. You can reject or withdraw through Cookie preferences.
Where the enquiry form offers a separate optional attribution checkbox, choosing it allows your consented journey to be associated with an enquiry reference after the enquiry register records the request. This is not a marketing subscription and is not required to receive a reply. Enquiry details are held in the protected GPIRL enquiry register; any email correspondence remains in the mailbox under the enquiry retention rules. The enquiry-register privacy notice at /lead-privacy.html explains the separate, optional request for updates, which remains pending confirmation and does not start a campaign. Analytics are stored in the Hostinger database used by GPIRL. Automatic housekeeping runs hourly while the application is running, at startup and before data exports. GPIRL may securely import these records into its private reporting system; the same deletion and retention rules apply to imported records. Each website uses a separate session, without cross-site identity matching.
Hosting and external services
The hosting platform may use technical security mechanisms needed to serve the site. Email links open your chosen mail application. External sites have their own cookie and privacy practices.
Future changes
If optional analytics or marketing tools are introduced, this information and any necessary consent controls will be updated before they are enabled.
Read the privacy notice →