Cookie Policy

Cookies and similar browser storage are small pieces of information saved on your device. They can help a website remember choices, keep features working, or understand how visitors use a site.

This page explains the current MHA Developers cookie and analytics setup. It is a practical implementation summary, not a guarantee of complete legal compliance.

Necessary storage is used for core website behaviour, security, and remembering your cookie preferences. This category is always on because the website needs it to operate properly.

The consent choice itself is stored under mha_cookie_consent and contains the consent version, category choices, and the time the choice was made. It does not contain personal details.

Analytics is off by default. If you choose to allow analytics, the website creates random first-party visitor and session IDs so MHA Developers can understand consented website activity such as page views, CTA clicks, pricing interactions, and booking request events.

Analytics events are sent to the MHA Content API only after analytics consent is granted. If analytics consent is later revoked, future events stop and the visitor/session IDs are cleared from the browser.

Marketing cookies are disabled by default. No advertising cookies, Google Analytics, Meta Pixel, or marketing pixels are currently active on this website.

If marketing tools are added in the future, this policy and the consent controls should be updated before those tools run.

The current analytics foundation does not use fingerprinting, advertising identifiers, Google Analytics, Meta Pixel, or cross-site tracking pixels.

Analytics metadata should not include personal form details. Booking and contact form submissions are handled separately from analytics events.

You can reopen Cookie settings from the website footer or this page at any time. From there you can accept all optional categories, reject non-essential categories, or save a custom preference.

Changing preferences affects future tracking. It does not automatically delete records that may already have been stored by the Content API before the change.

For questions about cookies or privacy on this website, contact MHA Developers at enquiries@mhadevelopers.co.uk.