Lawful, minimal processing
We collect only the data needed to answer an enquiry or deliver an agreed engagement. Contact forms never request more than name, work email, organisation and project brief.
Three pillars. Twelve focused engagements.
We treat data protection as a system property: region selection, identity, retention and evidence are designed into the platform rather than written into a policy PDF.
We collect only the data needed to answer an enquiry or deliver an agreed engagement. Contact forms never request more than name, work email, organisation and project brief.
Target architectures place data and backups in Nordic or EU regions by default. Any exception is documented, justified and approved in writing.
Where we act as a processor, a written data processing agreement defines instructions, confidentiality, security measures, sub-processors and deletion at the end of the engagement.
Encryption in transit and at rest, managed keys, named identities and least-privilege role assignments are baseline controls in our landing zones.
Enquiry records are kept only as long as needed to respond and maintain a business record. Backup retention is configured explicitly and documented in the engagement pack.
Access, correction, deletion, restriction and portability requests are handled through the same email channel that runs the engagement — no opaque portal.
The website uses static form delivery. In production, the notification inbox is configured for our intake address and replies come from [email protected].
| Provider | Purpose | Categories involved |
|---|---|---|
| Web3Forms | Contact form email delivery | Name, email, company, message |
| Formspree | Alternative contact form delivery | Name, email, company, message |
| hCaptcha | Spam prevention on the contact form | Interaction and challenge signals |
| Major cloud platforms | Client cloud infrastructure we engineer | Determined by the client architecture |
We compare major cloud platforms against your residency, contractual and operational constraints during the Blueprint Audit. Region pinning, private networking, managed keys and audit logging are delivered as infrastructure-as-code, so the decision stays enforceable after handover.
Region and backup location fixed in Terraform/Bicep
Private endpoints and managed identities instead of static keys
Audit logs centralised and retained to an agreed schedule
Remediation backlog handed over with the Blueprint
The Blueprint Audit includes region strategy, data boundaries and a NIS2/GDPR control map for your target platform.