Privacy on the public Testament website

The application code does not load marketing analytics, advertising pixels, session replay, or a prospect enquiry form on public routes. It does not set marketing or analytics cookies. Public pages also do not initialize the authenticated client-data API.

The hosting provider may process limited network and security information such as IP address, request time, requested page, and user agent in operational logs. The final notice must identify that provider and the approved retention period once hosting is used.

The public site does not ask you to enter contact details directly. A booking link, when shown, takes you to an external provider. Review that provider’s privacy information before submitting anything.

An adviser firm’s client portal processes identity, family, will, LPA instruction, mirror-coordination, document, and workflow information under a separate service relationship. Each firm’s notice should identify the controller and processor roles, purposes, lawful bases, recipients, international transfers, retention, security, rights, complaints route, and contact details.

Testament’s application is designed to minimise searchable facts and encrypt the sensitive substance. Operational reports use authorised workflow facts rather than decrypting client answers, but technical design does not replace those notices or the required data-protection impact assessment.

If you use Testament through an adviser firm, use the privacy contact named in that firm’s service notice to exercise applicable access, correction, deletion, restriction, objection or portability rights. For information entered into an external booking service, use the contact route in that provider’s notice.