Skip to main content

GDPR-Compliant Software Development

We architect products for GDPR and UK GDPR compliance: data minimization, DSAR support, lawful basis, retention controls. Built in, not bolted on.

Our status against GDPR

Compliant builds

We architect products so you can achieve GDPR compliance. We are typically your data processor; you remain the data controller and own those responsibilities.

Our status for each GDPR requirement
RequirementStatusNote
GDPR-compliant buildsMetDefault for every product we ship with EU/UK users.
UK GDPR / Data Protection Act 2018MetSame architecture; UK-specific nuances handled.
Lawful basis documentationMetWe architect to support whichever lawful basis you choose.
DSAR (Data Subject Access Request) supportMetBuilt into data architecture from day one.
Data minimizationMetWe collect what's needed, not what's easy.
Cookie consentMetGDPR-compliant cookie banner deployed on the Robust Devs site (production reference).
Records of Processing Activities (RoPA)PartialWe help clients build the initial RoPA; ongoing maintenance is their responsibility.
DPO appointment (Robust Devs)PartialNot applicable: we are not required to appoint a DPO ourselves.

Thirty days, and who is doing what in them

DSAR support is one row in the table above. It is also the control most likely to fail, because the clock is legal and the work is split across three parties.

A data subject access request across three lanes and a thirty-day statutory clock. The subject may request on any channel on day zero. The controller verifies identity on day one without over-collecting. From day two to twenty-five the controller searches its own systems while every subprocessor is queried separately, each on its own service level — this is the stage that overruns. By day thirty the controller delivers or refuses in writing with reasons.
Twenty-three of the thirty days are spent locating data. A current data map is the control; the policy document is not.

What this means for your build

  • We architect products with GDPR principles baked in: data minimization, purpose limitation, retention, accuracy, and security.
  • We support whichever lawful basis you've chosen: consent, contract, legitimate interest, and the rest.
  • We architect DSAR endpoints so subject access, rectification, erasure, and portability requests can be fulfilled programmatically.
  • We are typically your data processor, not your controller; a Data Processing Agreement (DPA) is available on request.
  • We follow EU data residency requirements when required, selecting deployment regions accordingly.

How we ship GDPR-compliant code

Data minimization

We collect only what is specified, not "everything just in case."

Lawful basis architecture

Architecture supports lawful basis tracking per data category.

DSAR endpoints

Subject access, rectification, erasure, and portability: programmatically supported.

Retention controls

Automated retention policy enforcement, not manual cleanup.

Cookie consent integration

GDPR-compliant banner with granular preferences (used on the Robust Devs site).

Audit logging

Who accessed what data, and when, for DPO and DSAR purposes.

Data residency

EU / UK deployment regions when required.

Cross-border transfer mechanisms

SCCs (Standard Contractual Clauses) and adequacy decisions handled at the architecture level.

What GDPR does NOT cover

  • GDPR is EU/UK only; the US has different state laws (CCPA, CPRA, Virginia VCDPA, and others).
  • GDPR does not replace HIPAA; US healthcare data has separate rules.
  • GDPR does not replace PCI DSS; payment card data has separate rules.
  • GDPR compliance is not ISO 27001 certification; that covers information security management.
  • GDPR is a legal framework; our role is technical architecture, not legal opinion.

When you need a separate consultant

We engineer for GDPR; we are not a law firm or a certifying body. Bring in a specialist when you need:

  • Data Protection Officer (DPO) appointment: required for some organizations.
  • DPIA (Data Protection Impact Assessment) for high-risk processing: a privacy attorney or DPO.
  • Cross-border transfer legal analysis: a privacy attorney.
  • DSAR response handling at scale: dedicated tooling (OneTrust, DataGrail) or an in-house process.
  • Privacy policy and cookie policy drafting: a privacy attorney.

Free tool

Tech Audit Checklist

A founder-grade checklist for pressure-testing your architecture before it scales: security, data handling, and the gaps that bite later.

Get the free checklist

Compliance lives in the architecture, not in a policy document

Encryption at rest, access controls, audit logging, and immutable decision trails are wired into the build from the first sprint. The posture on this page reflects how we actually ship.

Rows of server racks in a data centre corridor

Frequently asked questions

  • We ship GDPR-compliant builds. We are typically your data processor; you are the data controller. A DPA is available on request.

Serving EU or UK users? Schedule a meeting.

No account managers. No compliance theatre. A direct conversation about your data architecture and what GDPR-by-design takes to ship.