Mango62 ← Back to site

Security

How we handle your data.

This page covers the website and the demo process. Security documentation for the Mango62 modules themselves is provided during procurement.

Last updated 9 September 2026

No client data at demo stage

You do not need to give us anything about your clients to see Mango62 working. When we run a demo on a real case, bring redacted documents — a ceding-scheme pack and statements with the client's identifying details removed. We do not need to know who they are to show you the platform.

This website

Demo enquiries

The demo form transmits over HTTPS to our CRM, HighLevel, where the enquiry becomes a contact record accessible only to us. What is collected, where it goes and how long it is kept is set out in the privacy notice.

The Chronicle modules

The platform itself is a separate matter from this marketing site, and its security posture is documented for firms going through procurement rather than published here. If you are evaluating Chronicle and need detail on hosting, data residency, encryption, access control, sub-processors, retention or breach procedures, ask us during the demo and we will provide it.

We know you are likely operating under FCA rules and Consumer Duty, and that your own compliance team will want this in writing. That is expected — ask.

Reporting something

If you believe you have found a security problem with this site or with Chronicle, please email scott@scottmackey.co.uk rather than disclosing it publicly, and we will work with you to get it fixed. We will not pursue anyone who reports an issue in good faith.