Security & data
Understand how this website handles enquiries and the security questions we work through before a client engagement.
The contact form requests your name, work email, company, and project summary. Phone and budget are optional. Configured online delivery passes these details to Resend for email delivery to our team. The application does not save enquiries to an application database or browser storage.
Email provider credentials remain server-side. The form validates inputs on the server and limits repeated requests. Its availability check returns only whether online sending is configured; it does not expose credentials or account details.
Before sensitive data is shared, we agree the project’s access needs, hosting, approved providers, retention requirements, and responsibilities. A public enquiry form is for an initial project outline; use an agreed secure channel for production credentials or confidential records.
AI engagements
Model and hosting choices depend on the project. We scope which data can enter an AI service, who can access it, provider retention and training settings, and where human review is needed. These decisions belong in the agreed architecture and project terms.
Sensitive sectors
For healthcare, financial, or other sensitive workflows, discuss regulatory requirements, processing agreements, access controls, audit needs, and incident contacts before implementation. Certifications and contractual safeguards must be verified for the specific engagement.
If online sending is unavailable or fails, your details remain in the current form. The email fallback prepares text for you to review and send through your own email app; preparing or copying it does not submit it to our team. Hosting and email providers may maintain their own operational records.
For privacy requests, deletion questions, a suspected vulnerability, or a project security review, contact our team. Please describe the concern without sending passwords, health records, or other sensitive files. See our Privacy Policy for website information handling.
Last reviewed: 24 October 2026
