GDPR & cloud sovereignty

European data rules, engineered into the architecture.

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.

Our approach

Six commitments that shape every engagement

01

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.

02

EU-region architecture

Target architectures place data and backups in Nordic or EU regions by default. Any exception is documented, justified and approved in writing.

03

Processor agreements

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.

04

Encryption and access control

Encryption in transit and at rest, managed keys, named identities and least-privilege role assignments are baseline controls in our landing zones.

05

Defined retention

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.

06

Rights, honoured in writing

Access, correction, deletion, restriction and portability requests are handled through the same email channel that runs the engagement — no opaque portal.

Transparency

Sub-processors you should know about

The website uses static form delivery. In production, the notification inbox is configured for our intake address and replies come from [email protected].

ProviderPurposeCategories involved
Web3FormsContact form email deliveryName, email, company, message
FormspreeAlternative contact form deliveryName, email, company, message
hCaptchaSpam prevention on the contact formInteraction and challenge signals
Major cloud platformsClient cloud infrastructure we engineerDetermined by the client architecture
Sovereignty by design

Cloud choice is a compliance decision

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

Next step

Design the compliant cloud before you migrate into it

The Blueprint Audit includes region strategy, data boundaries and a NIS2/GDPR control map for your target platform.