Designed around controlled access.
Ardent systems are scoped to the tools, permissions, and operating rules agreed with each client.
Updated 31 July 2026
Principles
We aim to minimise access, separate client environments, keep credentials out of public code, and use secure configuration from our providers for deployment secrets.
Human handoff and escalation rules are defined before launch so a system does not act beyond its approved operating boundary.
Website protections
The public website sends contact enquiries through a secure server endpoint. Provider credentials are stored as deployment secrets and are not exposed to the browser.
The contact endpoint validates required fields, limits input length, and includes a hidden field to reduce automated submissions. No payment or account credentials should be submitted through it.
Report a concern
If you believe you have found a security issue involving this website, use the Contact page and begin the message with “Security report.” Do not include active credentials or exploit personal data.
We will review credible reports and coordinate a responsible response.