Service · Software development

Custom GDPR compliance platform development

Custom software that puts your GDPR obligations into practice within your own system landscape: record of processing activities, DPIA flow, data subject rights, consent management, retention, breach procedure and the DPO cockpit where it all comes together. Not a policy CMS or training portal, but a platform that makes Article 30, Article 35 and Articles 12 to 22 work in practice.

Record of processingDPIA toolingData subject rightsDPO cockpit

What a GDPR compliance platform is in practice.

The GDPR (Regulation 2016/679, supplemented in the Netherlands by the Dutch GDPR Implementation Act) consists of roughly a hundred articles that together demand one thing: organisations must demonstrably have a grip on the personal data they process. What happens to that data, on what legal basis, for how long, with whom it is shared, with what security, and how data subjects can exercise their rights. That is not a single document or a single tool, but a collection of interrelated processes.

A GDPR compliance platform is the software layer that supports those processes. It contains the record of processing activities from Article 30, the DPIA methodology from Article 35, the consent mechanism from Articles 6 and 7, the handling of access, rectification and erasure requests from Articles 12 to 22, the breach procedure from Articles 33 and 34, and the retention rules that follow from Article 5. All of it is linked to your own systems (HR, CRM, ERP, marketing platform, ticketing) so that a question from a data subject or an auditor can be answered within a workable timeframe.

We don't replace widely available off-the-shelf products such as OneTrust, TrustArc, Securiti.ai or DataGrail when they do the job. We build custom software when you need deeper integration, when your sector has additional requirements, or when your DPO or privacy officer runs into the limits of a commodity tool in practice. This fits within broader programmes around ISO 27001 compliant software and DORA compliance software, and is a logical building block in an enterprise software programme.

Three flavours of GDPR platform we build.

Most projects start in one of these three flavours. In the first conversation, we advise which approach best fits the scale of your processing, the number of systems to be connected and the maturity of your privacy organisation.

Compact project · fixed sprint budget

Record of processing and data subject rights portal

A compact platform in which your record of processing activities (Article 30) is maintained by process owners rather than by a single privacy officer in an Excel file. Linked to it is a data subject rights flow: a data subject submits a request, it runs through a ticket flow with SLA monitoring, and the handling is recorded for the Dutch Data Protection Authority (Autoriteit Persoonsgegevens). Suitable for organisations that have only just started serious GDPR operations.

Article 30 registerDSAR portalSLA monitoringAudit log
Mid-sized project · fixed sprint budget

DPIA, consent and third-party register

The compact package extended with DPIA tooling (Article 35): a structured assessment flow with risk scoring, purpose limitation check, necessity analysis and mitigating measures, linked to an organisation-specific risk framework. Plus consent management at processing level with granular withdrawal, and a third-party register (Article 28) in which processors, sub-processors, data processing agreements and international transfers are traceable. Suitable for organisations with an active DPO and multiple business units.

DPIA flowConsent per processingProcessor registerRisk scoring
Larger project · fixed sprint budget

End-to-end privacy platform with deep integrations

The full platform connected to your core systems (HR system, CRM, marketing stack, ERP, ticketing, data warehouse, email archive), so that an erasure request or access request is searched automatically across ten or more sources. Including breach management with the 72-hour notification timer towards the Dutch Data Protection Authority, anonymisation and pseudonymisation tooling, a retention engine, Schrems II tracking and the DPO cockpit in which your privacy officer oversees the entire organisation. Suitable for healthcare institutions, financial players, media houses and large retailers.

10+ system integrationsBreach timerAnonymisationRetention engineSchrems II

What you get at the end of a project.

A production-ready GDPR compliance platform, in your own environment, connected to your own systems, with the documentation your DPO and your auditor expect.

  • Record of processing in line with Article 30For every processing activity: purpose, legal basis, categories of data subjects, categories of personal data, recipients, retention period, international transfers and the associated security measures. Maintainable by process owners themselves, not only by your DPO.
  • DPIA tooling based on Article 35Structured assessment flow with necessity and proportionality test, risk register, mitigating measures and residual risk scoring. Linked to an organisation-specific risk framework, not a one-size-fits-all checklist.
  • Data subject rights portal (Articles 12 to 22)Request flow for access, rectification, erasure, data portability, objection and restriction. Automated searching across the connected source systems, structured case building, audit trail, SLA monitoring and standardised response templates that have been legally reviewed.
  • Consent management at processing levelGranular consent per processing purpose, a withdrawal flow, explicit age verification where relevant, and an audit log of what was accepted, when, and under which version of the privacy statement. Standard integration with your cookie banner (CMP under TCF 2.2) and your marketing stack.
  • Third-party register in line with Article 28Every processor and sub-processor with contract version, purpose limitation, data categories, processing location, certifications, SCC status and transfer mechanism. Workflow for new data processing agreements and periodic review.
  • Breach management with a 72-hour timerIncident flow with severity classification, impact analysis for data subjects, a template for notifying the Dutch Data Protection Authority (Article 33), a template for notifying data subjects (Article 34), a lessons-learned archive, and the statutory timer visibly counting down from the moment the breach is established.
  • Retention engine and data minimisation controlsRetention rules per dataset and per processing activity, automated deletion or anonymisation jobs, periodic data minimisation reports and an exception flow for statutory retention obligations. Particularly useful for HR data, where data minimisation and transparency must go hand in hand.
  • Anonymisation and pseudonymisation toolingAutomatic PII detection in new datasets, configurable anonymisation strategies (k-anonymity, generalisation, suppression, tokenisation) and a pseudonymisation vault for reversible cases. Usable by data teams in BI and AI projects.
  • International transfers (Articles 44 to 49)Tracking of data flows outside the EEA, with SCC status, EU-US Data Privacy Framework status, proof of EU data residency and the transfer impact assessment that follows from Schrems II. A warning when a supplier changes region.
  • DPO cockpitA single dashboard where your Data Protection Officer or privacy officer sees everything on the organisation's plate: open data subject requests, ongoing DPIAs, expired data processing agreements, open breach incidents, retention overruns and the status of international transfers.
  • Privacy-by-design tooling for your development teamsAn API scanner that checks new endpoints for PII, automatic detection of personal data in datasets, and build-time checks that stop a new feature from processing personal data without a registered legal basis. This is how Article 25 becomes operational in practice.
  • Codebase, documentation and operations runbookFull source code in a Git repository, an architecture overview, integration documentation per source system and operational runbooks for your IT partner or in-house IT. Plus an optional maintenance contract covering monitoring, patch management, regulatory updates and further development.

When a custom GDPR platform is the right choice.

Four patterns we see in organisations that approach us about a custom privacy platform. If you recognise one of them, we would be glad to talk further.

Integration depth

Off-the-shelf tools don't integrate deeply enough

You have OneTrust, TrustArc or a similar tool, but a right-to-erasure request still means searching manually through ten or more internal systems. The off-the-shelf tool covers the governance layer, but not the operational handling on your own data. That wears out your DPO and makes turnaround times too long.

Industry requirements

Additional regime on top of the GDPR

You fall under a sector overlay: NEN 7510 for healthcare, DNB and Wft requirements for the financial sector, BIO for government, or the GDPR link from the AI Act for your AI systems. One architecture has to cover several frameworks at once, with a shared source of evidence and no separate Excel files per regime.

Scale and volume

A lot of personal data, a lot of processes

You are a media company, retailer, marketing agency, recruiter or platform organisation holding personal data on hundreds of thousands or millions of data subjects. At these volumes an Excel-based approach is unsustainable; data subject rights requests arrive weekly and need to be handled in an automated way across multiple systems.

Incident context

After a fine, complaint or audit finding

The Dutch Data Protection Authority has investigated a complaint, imposed a fine or reported an audit finding. Or a major business customer has concluded in its due diligence that your operational privacy controls cannot be sufficiently verified. There is now pressure, both internally and externally, to invest structurally in tooling, not just in policy.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How an engagement works.

1

Introduction and scoping

A conversation in which we understand which processing activities you carry out, which systems are involved, what your privacy organisation looks like today (DPO, privacy officers, legal, security) and which standard tools are already running. We also map the additional regimes, such as NEN 7510, the AI Act, DNB requirements and BIO, and determine which flavour of platform fits.

2

Discovery and architecture

A workshop with your DPO, security officer and the business owners of the core systems. We run a data-mapping session (which personal data lives where, on what legal basis, with what retention), write down the priority processing activities, and choose architecture patterns that connect to the source systems at scale. At the end you have a data architecture, an initial platform architecture and a sprint plan that puts the high-risk integrations first.

3

Building in sprints, with legal review alongside

We work in two-week sprints. Your DPO and legal adviser join the review of the processes the tool supports: a DPIA template has to be legally sound, a DSAR response template has to stand up legally, and a record-of-processing field has to match the way your supervisory authority thinks about it. We build, they test, and the iteration in between makes the platform usable.

4

Rollout, training and ongoing maintenance

A phased rollout (first the record of processing activities goes live, then the DSAR flow, then DPIA, then breach, then the deeper integrations) so that your organisation grows along with the tool. Two training sessions for your DPO and privacy officers, a short video explainer for process owners, and a DPO cockpit overview for your board. From go-live we handle monitoring, patch management, dependency updates and the changes that follow from new Dutch DPA guidance or EDPB guidelines.

Frequently asked questions about a GDPR compliance platform.

The questions DPOs, privacy officers and compliance managers ask us before a project starts.

What is the difference between GDPR and ISO 27001 in this context?
The GDPR is a legal framework for the protection of personal data and covers legal bases, data subject rights, purpose limitation, data minimisation and the organisation of privacy governance. ISO 27001 is an international standard for an Information Security Management System and covers information security in a broader sense: not just personal data, and not specifically focused on the legal rights of data subjects. They overlap on security controls (access, encryption, logging, breach response) but are not interchangeable. An ISO 27001 certificate does not automatically cover the GDPR, and vice versa. We are happy to build a single architecture that accommodates the requirements of both frameworks. See also our page on ISO 27001 compliant software.
Do you replace OneTrust or TrustArc?
For the broad range of privacy governance features, almost never. OneTrust, TrustArc, Securiti.ai and DataGrail cover a large part of the market well, with an active roadmap for new regulation. We build custom when you hit the limits of those tools: deep integration with your own source systems for automated DSAR handling, sector-specific overlays (healthcare, financial, government), or a DPIA flow that has to fit tightly with your organisation-specific risk framework. In some cases a commodity tool runs the register and we build the operational layer around it. We give that advice in the first conversation, honest about what you can better buy yourself.
How does the platform support data minimisation and transparency in HR data?
HR is one of the most sensitive types of processing under the GDPR: application data, performance review data, sickness data, salary data, and sometimes special categories of data too (medical, race, religion). In practice, data minimisation means the HR system only stores the fields that are operationally necessary for the stated purposes, and that expired data is automatically deleted or anonymised. Transparency means an employee can, on request, see immediately what data is held about them, on what legal basis, for how long, and with whom it is shared. The platform integrates with your HR system (AFAS, Visma, Workday, Personio or another), applies retention rules per dataset, gives employees a transparency portal and provides HR with the tooling to delete applicant data on time, a common finding by the Dutch Data Protection Authority (AP).
How often do AP fines or complaints occur, and how does the platform help?
Every year the Dutch Data Protection Authority (AP) publishes hundreds of investigations and fines, with large amounts for matters such as unlawful profiling, insufficient security of personal data, an incorrect legal basis for marketing and retaining applicant data for too long. The platform helps in two ways: preventively, by making the GDPR obligations operationally enforceable (no processing without a legal basis, no marketing without an opt-out option, no data kept beyond the retention period), and reactively, by letting you present a clean file in the event of a complaint or audit investigation in which all DPIAs, breach notifications, data processing agreements and data subject rights requests are easy to find. The burden of proof is a large part of the discussion for the Dutch Data Protection Authority.
What does the platform do about the overlap between the AI Act and the GDPR?
The AI Act sets requirements for AI systems that in many cases work with personal data, and that is where the GDPR also applies. For high-risk AI systems under the AI Act, a fundamental rights impact assessment is mandatory, which in practice is often combined with the DPIA under Article 35 of the GDPR. The platform supports that combined assessment flow: AI-specific risks (bias, explainability, training data provenance) are assessed in the same tool as the privacy risks. For organisations that develop or procure AI systems, that is a more efficient route than keeping two separate processes running.
What determines the cost of a GDPR compliance platform?
Four things: the scope (only the register and data subject rights, or the full platform with DPIA, breach, retention and integrations), the number of source systems we connect the platform to, the additional regimes (NEN 7510, AI Act, DNB, BIO) and the maturity of your privacy organisation. An organisation where the DPO is active and the policy is in place is a faster project than one where the DPO has just been appointed and the policy is being written in parallel. We outline the range in the first conversation and always work with fixed sprint prices, so you won't face any surprises.
Do you also build for healthcare, financial services, marketing and government?
Yes. For healthcare, the platform almost always runs alongside the NEN 7510 requirements (patient logging, authorisation, purpose limitation) — we build one architecture that covers GDPR and NEN 7510 at the same time. For the financial sector, it overlaps with our work on DORA compliance software and KYC and AML compliance software, because operational resilience and customer data management are closely intertwined with the GDPR. For marketing and media companies, the emphasis is on consent management, profiling checks and granular retention. For government, it ties in with BIO and with reporting to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens). For organisations that also report on ESG and sustainability obligations alongside privacy, we sometimes build a combined governance platform with our CSRD/ESG reporting software.
What do you do in the event of a data breach after go-live?
The maintenance contract includes operational support for incidents. The platform itself contains the breach flow with the 72-hour timer, severity classification and the notification templates for the Dutch Data Protection Authority (Article 33) and the data subjects (Article 34). We support you with technical triage, impact analysis and communication. Lessons learned are fed back into your DPIAs, your record of processing activities and, where necessary, the controls of the connected systems, so the same scenario doesn't happen twice.

Talk to us about your GDPR compliance platform.

A no-obligation introductory call of half an hour. We listen to which processing activities you carry out, which standard tools are already running, what your DPO and privacy organisation currently look like and which additional regimes apply — and we give you direction you can use straight away, even if we don't end up working together.

Edit content