Compyl
Framework · GDPR

GDPR isn’t a policy you publish — it’s DSARs, data maps, and 72-hour clocks you run every day.

GDPR lives in operations: knowing where personal data sits, answering data subject requests on deadline, keeping Records of Processing current, and proving a lawful basis for everything. Compyl runs it continuously — data mapping, DSAR and DPIA workflows, and breach-ready evidence.

7 data principles
125+ integrations
Continuous data mapping
Home › Frameworks › GDPR Audit-ready AUDIT READINESS 96% audit-ready DATA PROCESSING · LIVE CORE GDPR OBLIGATIONS Lawful basis MAPPED RoPA (Art 30) CURRENT DSARs ON TIME DPIAs 1 GAP EVIDENCE COLLECTED · AUTOMATIC ● live AWS · CloudTrail access logs 2m ago Current Okta · MFA enforcement export 5m ago Current GitHub · change-management records 18m ago Current 1,284 evidence items current 0 manual screenshots · next refresh in 4 min Export pack
GDPR Readiness On track Evidence current 96% Controls passing 92% Obligations 6 / 7 Monitored continuously · updated live
What is GDPR — and how does Compyl help?

GDPR is the EU regulation governing the personal data of EU and EEA residents, built on seven principles and six lawful bases. Beyond policy, it imposes operational duties: Records of Processing (Article 30), data subject access requests answered within one month, Data Protection Impact Assessments (Article 35), and breach notification to regulators within 72 hours. Fines reach €20M or 4% of global turnover.

Compyl makes GDPR operational. It maps where personal data lives, runs DSAR and DPIA workflows, keeps your Records of Processing current, collects Article 32 security evidence, and flags drift — so you can prove compliance on demand instead of scrambling for a regulator or a 72-hour clock.

The problem

You can’t protect — or prove — data you can’t find

GDPR turns on operational reality: where personal data lives, who can access it, and how fast you respond. When that drifts from your paperwork, the regulator and the DSAR clock find it first.

Data maps go out of date

New tools and integrations move personal data constantly. A Record of Processing built once is wrong within a quarter — and wrong is exactly what a regulator audits.

DSARs arrive on a clock

A data subject access request gives you one month. Without knowing where their data lives, every request becomes a manual fire drill across teams.

The 72-hour breach window is brutal

From detection to regulator notification you have 72 hours. Scattered evidence and unclear scope make that deadline almost impossible to hit.

How it works

One continuous loop — from connected systems to audit-ready

Compyl runs your GDPR program as an always-on cycle — data mapping, lawful basis, and evidence stay in sync automatically.

01

Connect

Integrate cloud, identity, code, endpoint, and HR systems.

02

Collect evidence

Pull audit evidence automatically, in real time.

03

Map to obligations

Link every artifact to its GDPR article and lawful basis.

04

Monitor

Watch controls continuously and flag drift early.

05

Stay audit-ready

Hand auditors a current evidence pack on demand.

Automated evidence

Stop assembling GDPR evidence by hand

GDPR proof isn't a single report — it's a current data map, a lawful basis for every processing activity, and Article 32 security evidence. Compyl collects it continuously from the systems you already run.

  • Pull evidence automatically from cloud, identity, code, and endpoint tools
  • Every artifact mapped to the GDPR article it supports
  • No more screenshots, spreadsheets, or last-minute requests
  • Export a complete, auditor-ready evidence pack on demand
Evidence Studio · GDPR ● auto-collecting EVIDENCE CURRENT 1,284 items mapped to controls MANUAL EFFORT 0 screenshots this cycle SOURCE EVIDENCE ARTICLE STATUS AWS Access logs Art 32 Current Okta MFA enforcement Art 32 Current GitHub Change management Art 25 Current CrowdStrike Endpoint protection Art 32 Current Datadog Uptime monitoring Art 30 Current 125+ integrations feeding evidence — refreshed automatically
Evidence Health · New in 26.2

Know your evidence is audit-ready — automatically

Collecting evidence is only half the battle; stale or incomplete proof is where audits go sideways. New in Compyl 26.2, Evidence Health continuously scores every artifact the moment it changes, so weak evidence surfaces weeks before an audit — not during it.

  • Every artifact scored on relevance, freshness, and completeness
  • An AI summary spells out exactly what's missing and why
  • Re-scores automatically whenever the underlying evidence changes
  • Continuous control monitoring done right — gaps surface with time to fix
Evidence Health · Q2 Access Review New · 26.2 OVERALL HEALTH 84 / 100 Q2 ACCESS REVIEW SCORED ON THREE DIMENSIONS Relevance Healthy · 95 Freshness Aging · 58 Completeness Healthy · 88 AI SUMMARY Evidence is relevant and complete — but aging. Last refreshed 41 days ago; access reviews expected within 90. Auto-refresh scheduled — gap clears ~3 weeks before audit. Re-pull Scored automatically the moment evidence changes · continuous control monitoring
Continuous monitoring

Catch control drift before the auditor does

Regulators and DSARs don't wait for your annual review. Compyl monitors every obligation continuously, scores your posture in real time, and turns the moment something slips into a tracked task.

  • Live posture across every GDPR obligation and lawful basis
  • Automatic alerts the moment a control drifts out of compliance
  • Remediation tasks auto-assigned with owners and deadlines
  • A defensible, time-stamped trail across every processing activity
Control Monitoring · GDPR all obligations · live 92% passing OBLIGATIONS MET CONTROL STATUS Art 32 · Encryption at rest Passing Art 30 · Records of processing Passing Art 15 · DSAR fulfilment Drifting Art 33 · Breach reporting Passing Drift detected — Art 15 DSAR response SLA exceeded 2 access requests past the 30-day deadline Detected 6 min ago · before any audit sample Remediation task #GDPR-412 auto-created Assigned to IT Ops · due in 24h · evidence re-checks on close
Collect once, reuse everywhere

Your GDPR work becomes a head start on every other framework

GDPR’s Article 32 security obligations overlap heavily with SOC 2, ISO 27001, and NIST. Compyl cross-maps each control so one piece of evidence satisfies every framework it touches.

  • One control mapped to its equivalent across 20+ frameworks
  • Collect evidence once and reuse it across every report
  • See instantly how GDPR readiness translates to SOC 2 or ISO 27001
  • Add the next framework without starting the program over
Cross Mapped Controls · Art 32 47 mapped Art 32 Security of processing 800-53 14 ISO 27001 12 NIST CSF 9 SOC 2 8 HIPAA 4 Evidence collected once · automatically satisfies 47 controls
Core obligations

The operational heart of GDPR

GDPR is built on seven principles, but compliance is proven through operational duties. Compyl maps evidence to each one.

Art 6

Lawful basis & consent

Establish and record a lawful basis for every processing activity — and manage consent where it applies.

Art 30

Records of Processing

Maintain a current RoPA describing what data you process, why, and where it flows.

Art 15–22

Data subject rights

Answer access, erasure, and portability requests (DSARs) within one month.

Art 35

DPIAs

Run Data Protection Impact Assessments for high-risk processing before it begins.

Art 32 / 33

Security & breaches

Implement appropriate security and notify regulators of a breach within 72 hours.

Two clocks that define GDPR

The deadlines that make GDPR operational

GDPR isn’t a once-a-year audit — it’s two clocks that can start any day. Compyl is built to help you beat both.

THE DSAR CLOCK

One month to respond

A data subject request starts a one-month deadline to find, compile, and deliver everything you hold on a person.

Trigger: any individual exercising their rights
Deadline: one month (extendable in limited cases)
Where Compyl helps: a live data map so you know where their data lives
THE BREACH CLOCK

72 hours to notify

From becoming aware of a breach, you have 72 hours to notify the supervisory authority — with scope, impact, and response.

Trigger: a personal-data breach
Deadline: 72 hours to the regulator
Where Compyl shines: breach-ready evidence and clear processing scope
Why Compyl for GDPR

Not a checkbox tool — a continuous compliance engine

Plenty of tools store a privacy policy. Compyl operationalizes GDPR — data maps, DSARs, and evidence that stay true every day.

01

Continuous, not point-in-time

Data maps, lawful basis, and evidence stay live year-round, so audits and DSARs never catch you out.

02

One connected system

Controls, evidence, risks, and policies in one platform — not a stack of disconnected tools.

03

125+ integrations

Pulls live data from the stack you already run, so posture reflects reality, not snapshots.

04

Agentic AI

AI maps controls, drafts remediations, and offloads busywork — your team stays in control.

05

Multi-framework by design

GDPR evidence carries over to SOC 2, ISO 27001, HIPAA, and NIST without redoing the work.

7
Core data-protection principles mapped to evidence
125+
Native integrations feeding evidence automatically
Real-time
Evidence collection — no manual screenshots
Year-round
Audit readiness instead of a pre-audit scramble
It has brought a sense of relief to my life because, for the first time, we have a real solution in place that is proactively keeping us protected.
JS
Jon Senior CTO · via G2
Recognized by users on G2

Rated a leader by the teams who use it

G2 High Performer, Mid-Market
G2 Momentum Leader
G2 Fastest Implementation, Go-Live Time
G2 Best Support, Quality of Support
G2 Best Meets Requirements, Mid-Market
Beyond GDPR

Protect personal data once — extend to every framework that follows

Compyl cross-maps controls so the work you do for GDPR carries straight into the next framework on your roadmap.

FAQ

GDPR questions, answered

GDPR is the EU regulation governing the personal data of EU and EEA residents. It is built on seven principles and six lawful bases, and imposes operational duties including Records of Processing (Article 30), data subject access requests within one month, Data Protection Impact Assessments (Article 35), and 72-hour breach notification (Article 33). Fines reach €20M or 4% of global turnover.

Any organization that processes the personal data of people in the EU or EEA — regardless of where the organization is based. That includes most SaaS companies and any business with EU customers, users, or employees.

A Record of Processing Activities (RoPA, Article 30) documents what personal data you process, for what purpose, and where it flows. A lawful basis (Article 6 — consent, contract, legitimate interests, and others) is the legal justification you must have and record for each processing activity.

Compyl maps where personal data lives, runs DSAR and DPIA workflows, keeps your RoPA current, collects Article 32 security evidence, scores evidence health, and flags drift — so you can prove compliance on demand instead of scrambling for a regulator or a DSAR deadline.

Compyl 26.2 introduced Evidence Health, which continuously scores every piece of evidence on relevance, freshness, and completeness, with an AI summary of what is missing — so gaps surface before a regulator or a 72-hour clock, not during.

Yes. Compyl cross-maps each control so a single control and its evidence can satisfy GDPR alongside SOC 2, ISO 27001, HIPAA, and 20+ other frameworks. Collect once, reuse everywhere it applies.

Security, privacy, and GRC teams — CISOs, DPOs, and IT leaders — at any organization that handles the personal data of EU or EEA residents and needs to run GDPR as an operational program, not a static policy.

GRC YOUR WAY

Make GDPR something you operate, not something you document

See how Compyl maps your personal data, runs DSARs and DPIAs on time, and keeps you ready for the 72-hour breach clock.

Request a Demo →
By clicking “Accept”, you agree to the use of cookies on your device in accordance with our Privacy and Cookie policies