Skip to content
Stribog

Compliance

All writing

GDPR Compliance Statement Examples: What You Can Claim

A GDPR compliance statement is a claim anyone can test. Example sentences worth copying, wording to cut, and when 'GDPR certified' is actually true.

Stribog16 min read

Most published GDPR statements read the same: "We are committed to protecting your personal data and complying with the GDPR." Nobody can test that sentence, so it tells a reader nothing. The sentences that follow it are the problem. "Fully GDPR compliant." "GDPR certified." "Your data never leaves the EU." Each is a factual assertion that a regulator, a customer's data protection officer or a competitor can check.

This article treats the statement as an engineering artefact: every sentence derived from a record, every record row backed by something in the system. The wording below is illustration, not legal advice; the choice of lawful basis for any processing remains the controller's call.

What a GDPR Compliance Statement Is, and What It Is Not

There is no article of the GDPR titled "compliance statement", and no duty to publish one. That is the practical answer to "GDPR compliance meaning": compliance is not a declaration, it is a state you must be able to prove. Article 5(2) makes the controller "responsible for, and be able to demonstrate compliance with" the processing principles — the accountability principle.

The duties that shape a public statement are elsewhere. Article 12(1) requires the information in Articles 13 and 14 to be provided "in a concise, transparent, intelligible and easily accessible form, using clear and plain language." Article 13 lists what must be given when data is collected from the person; Article 14 is its counterpart for data obtained elsewhere. Where a DPO has been designated — mandatory in the Article 37(1) cases, optional under Article 37(4) unless national or Union law requires it — Article 37(7) requires the controller or processor to publish the DPO's contact details.

So a working definition: a GDPR compliance statement is a public summary of claims that must each be true under those articles. It does not replace the Article 13 notice, and publishing one does not make anything compliant. It can point to evidence; it must not assert what the evidence does not support.

Eight Sentences Worth Copying, Mapped to Article 13

The examples below are for a fictional controller, Example Helpdesk GmbH, running a hosted helpdesk product. Each carries the Article 13 point it discharges. Copy the shape, not the facts.

  1. Controller and contact — 13(1)(a). "Example Helpdesk GmbH, Beispielstraße 1, 10115 Berlin, Germany, is the controller for the account and billing data described here. Contact: privacy@example.com."
  2. DPO, where designated — 13(1)(b), 37(7). "Our data protection officer can be reached at dpo@example.com." A named mailbox, not a web form that routes to sales.
  3. Purpose and lawful basis, per purpose — 13(1)(c)-(d). "We use your email address and company name to run your account and send invoices, because this is necessary to perform our contract with you (Article 6(1)(b)). We record which features each workspace uses to decide what to fix first; our legitimate interest (Article 6(1)(f)) is improving the product." One purpose, one basis, and the interest named where 6(1)(f) is used.
  4. Recipients — 13(1)(e). "Invoices are sent through Example Mail Relay Ltd and payments handled by Example Payments SA. The current list of processors, with each one's role and location, is at /legal/processors and changes there before they take effect."
  5. Transfer — 13(1)(f), only where one is intended. "Payment data goes to [recipient] in [third country]. No adequacy decision covers that country, so the transfer relies on standard contractual clauses under Article 46; you can request a copy at privacy@example.com." Article 13(1)(f) asks for the fact of the intended transfer, whether an adequacy decision exists, and otherwise a reference to the Article 46, 47 or 49(1) second-subparagraph safeguard and how to obtain a copy. It does not itself require the country to be named; WP260's fairness guidance adds that this "will generally mean that the third countries be named", so name it. A sentence such as "data is stored in Germany and not transferred" is not a 13(1)(f) element. It is an accountability claim: publish it only if you can evidence it, as the infrastructure section below shows.
  6. Retention — 13(2)(a). "Account data is deleted 90 days after the workspace is closed; invoices are kept for [N] years from the end of the year they were issued, as [named accounting law] requires." Fill both brackets from the applicable law: WP260 says a statutory criterion "should be phrased in a way that allows the data subject to assess" the period; a bare "statutory retention period" gives nobody a date.
  7. Rights and complaint — 13(2)(b)-(d). "You can ask for access, rectification, erasure, restriction or portability at privacy@example.com. We answer within one month, or tell you within that month why we need up to two more. You also have the right to lodge a complaint with a supervisory authority."
  8. Right to object — 21(4). "You can object at any time to our use of feature-usage data to improve the product. Write to privacy@example.com." Where processing rests on 6(1)(f), Article 21(4) requires this right to be "presented clearly and separately from any other information" — its own sentence, never folded into the rights list.

The deadline in sentence seven is not a courtesy. Article 12(3) requires information on action taken "without undue delay and in any event within one month of receipt of the request," extendable "by two further months where necessary." If processing relies on consent, Article 13(2)(c) adds a sentence on withdrawing it at any time.

Every one of these sentences is falsifiable. A reader can email the DPO mailbox, read the processor page, file a request and time the reply. Where sentence four meets processor contracts, the mechanics are in the data processing agreement as an architecture decision.

Moving up the ladder makes a claim more testable. Certification sits at the top, is optional, and still leaves the controller fully responsible.

Sentences to Cut: Vague Qualifiers and Status That Does Not Exist

The Article 29 Working Party's transparency guidelines (WP260 rev.01), last revised on 11 April 2018, give a ready-made strike list. Their poor-practice examples include "We may use your personal data to develop new services", "...for research purposes" and "...to offer personalised services", because it is unclear what the services or the research are, or what the personalisation entails. They add that qualifiers such as "may", "might", "some", "often" and "possible" "should also be avoided". A controller that does use them should be able to demonstrate why that language could not be avoided and how it does not undermine the fairness of processing.

Their good-practice counterpart says exactly what is kept and why: "We will retain your shopping history and use details of the products you have previously purchased to make suggestions to you for other products which we believe you will also be interested in." Data, use and consequence, in one sentence. Then strike these:

  • "Fully GDPR compliant." Compliance is a property you demonstrate under Article 5(2), continuously, per processing activity. "Fully" claims a completeness one counter-example disproves.
  • "Bank-grade" or "military-grade" security. Not a standard. Replace with the measures themselves, or a link to the Article 32 description — see GDPR Article 32 technical measures an auditor can verify.
  • "Your data never leaves the EU" when an email relay or support tool sits elsewhere. One recipient disproves it.
  • "GDPR certified" without an Article 42 certificate. This one deserves its own test.

When "GDPR certified" is actually true

GDPR certification exists, but it is narrow. Article 42(5) says a certification "shall be issued by the certification bodies referred to in Article 43 or by the competent supervisory authority, on the basis of criteria approved by that competent supervisory authority" or by the Board; Board-approved criteria "may result in a common certification, the European Data Protection Seal." Article 43(1) requires those bodies to be accredited by one or both of two routes: the competent supervisory authority, or the national accreditation body named under Regulation (EC) No 765/2008, "in accordance with EN-ISO/IEC 17065/2012" plus the authority's additional requirements. The 17065 standard belongs to the second route only; under Article 43(3), both routes use accreditation requirements approved by the competent authority or the Board.

Three more limits apply. Certification is voluntary (Article 42(3)). It is issued "for a maximum period of three years" and may be renewed (42(7)), so a certificate has an expiry date the statement must respect. And under 42(4) it "does not reduce the responsibility of the controller or the processor for compliance." A certificate is evidence, not immunity.

The practical check is the EDPB register of certification mechanisms, seals and marks. At the time of writing it lists 17 items — schemes, criteria and some accreditation requirements for certification bodies, not certified organisations. They include Europrivacy, an EU Data Protection Seal, and national schemes such as Lexing (France) and TÜV NORD's Trusted Site Data Privacy (Germany, North Rhine-Westphalia). The EDPB first approved the Europrivacy criteria as a seal in Opinion 28/2022 on 10 October 2022. The register now carries three Europrivacy rows: that original EU Data Protection Seal (core criteria v60, Opinion 28/2022, register entry dated 7 November 2023); Europrivacy Main Criteria v2.0 (also called v82) for regular Article 42 certification, linked to Opinion 14/2026; and a separate extension for certifying data importers under Article 46 (also v2.0/v82, Opinion 15/2026), an EU Data Protection Seal flagged as a tool for transfers. A Europrivacy claim should name the row, version, scope and expiry the certificate uses.

So "GDPR certified" is accurate only if a named certificate, under a scheme on that register, issued by an accredited body or the authority, covers the processing the statement describes and has not expired. Say all of it: scheme, body, scope, expiry. An ISO 27001 certificate is not a GDPR certification and should never be worded as one — the distinction is the subject of ISO 27001 vs SOC 2: certificate or auditor's opinion.

Why the Vague Version Is the Riskier One

Vague wording feels safer. The fine structure says otherwise. Under Article 83(5)(b), infringing "the data subjects' rights pursuant to Articles 12 to 22" sits in the upper tier — up to 20 000 000 EUR or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher. Articles 12 to 14 are the transparency duties, so an unclear Article 12-14 notice is not a cosmetic issue.

That tier has been used for transparency. On 2 September 2021 the Irish Data Protection Commission announced a 225 million EUR fine on WhatsApp Ireland after a transparency inquiry covering users and non-users. An EDPB Article 65 binding decision had instructed the DPC to reassess and increase its proposed fine. On 10 February 2026 the Court of Justice, in Case C-97/23 P, set aside the General Court's inadmissibility order on WhatsApp's challenge to that EDPB decision and referred the case back; it did not annul the DPC's decision, the source of the figure.

Certification cuts the other way. Article 83(2)(j) lists "adherence to ... approved certification mechanisms pursuant to Article 42" among the factors weighed when setting a fine. It is weighed, not automatic: the EDPB guidelines 04/2022 on calculating fines say adherence "may in some circumstances constitute a mitigating factor." A claimed certificate that does not exist is an untrue statement about the controller's own compliance — the opposite of the accountability Article 5(2) asks for. How a supervisory authority investigates is covered in GDPR compliance audits under Article 58.

Generate the Statement From the Article 30 Record

Article 30(1) already requires a record of processing activities with almost everything the statement needs: controller and DPO contact details, purposes, categories of data subjects and personal data, categories of recipients "including recipients in third countries", transfers, "where possible, the envisaged time limits for erasure", and "where possible, a general description of the technical and organisational security measures." Article 30(3) says the record "shall be in writing, including in electronic form," and 30(4) that it must be made available to the supervisory authority on request. Article 30(5) exempts organisations employing fewer than 250 persons, but not where the processing is likely to result in a risk, is not occasional, or includes special-category or criminal-offence data.

Electronic form includes YAML in git. Keep one file per processing activity, with keys that mirror 30(1)(a)-(g) plus the Article 13 extras the record does not require — lawful basis and the rights route:

yaml
id: support-tickets
controller:
  name: Example Helpdesk GmbH
  address: Beispielstraße 1, 10115 Berlin, Germany
  contact: privacy@example.com
dpo_contact: dpo@example.com
purpose: Answer and resolve support requests from customer users
lawful_basis:
  article: "6(1)(f)"
  note: >-
    Legitimate interest in resolving support requests from the
    customer's users. Not 6(1)(b): the customer organisation, not
    the user, is party to the contract.
data_subjects:
  - Customer users who open a support ticket
data_categories:
  - Name
  - Email address
  - Ticket text and attachments
recipients:
  - name: Example Mail Relay Ltd
    role: processor
    service: Outbound notification email
    location: DE
processing_location:
  - DE
transfers: []
retention:
  rule: Delete 24 months after ticket closure
  enforced_by: cronjob/ticket-retention in namespace helpdesk
security_measures_ref: security/article-32.md#helpdesk
rights_contact: privacy@example.com
ropa/support-tickets.yaml — one processing activity. Keys mirror Article 30(1)(a)-(g); lawful_basis and rights_contact serve Article 13.

The published statement is then a rendering of these files, not a document someone edits in a CMS. A small CI check keeps its processor list and processing locations equal to the record. It needs Mike Farah's yq v4 and jq, and reads the statement's facts from the JSON file the page is rendered from:

bash
#!/usr/bin/env bash
# Usage: check-statement-drift.sh <ropa-dir> <statement.json>
# statement.json: {"processors": ["..."], "processing_locations": ["..."]}
set -euo pipefail

ropa_dir="$1"
statement="$2"

shopt -s nullglob
files=("$ropa_dir"/*.yaml)
if [ "${#files[@]}" -eq 0 ]; then
  echo "no record entries found in $ropa_dir" >&2
  exit 1
fi

# One compact JSON document per record file, slurped into one array.
record="$(yq -o=json -I=0 '.' "${files[@]}" | jq -s '.')"

want_processors="$(jq -r '[.[] | (.recipients // [])[] | select(.role == "processor") | .name] | unique | .[]' <<<"$record")"
have_processors="$(jq -r '.processors | unique | .[]' "$statement")"
want_locations="$(jq -r '[.[] | (.processing_location // [])[]] | unique | .[]' <<<"$record")"
have_locations="$(jq -r '.processing_locations | unique | .[]' "$statement")"

status=0
if ! diff -u <(printf '%s\n' "$want_processors") <(printf '%s\n' "$have_processors"); then
  echo "DRIFT: processors in the record and the statement differ" >&2
  status=1
fi
if ! diff -u <(printf '%s\n' "$want_locations") <(printf '%s\n' "$have_locations"); then
  echo "DRIFT: processing locations in the record and the statement differ" >&2
  status=1
fi
exit "$status"
check-statement-drift.sh — fails CI when the record and the statement's fact file disagree.

The check is deliberately dumb. It does not judge whether a lawful basis is right; that is a human decision, made in the pull request that changes the record. It only proves that statement.json matches the record. The page itself is covered only if the same build renders it from that file and nobody can edit it by hand; a hand-edited page can go stale behind a green build. Rendered from the record above, the before-and-after looks like this:

markdown
## Before

We take your privacy seriously and are fully GDPR compliant.
We may share some data with trusted partners to improve our services.
Data is kept only as long as necessary.

## After: support requests

- When you open a support ticket, Example Helpdesk GmbH processes your
  name, email address and the ticket content to answer it. <!-- 13(1)(c) -->
- We rely on our legitimate interest in resolving support requests
  from our customers' users, Article 6(1)(f). Your organisation, not
  you, is party to our contract, so Article 6(1)(b) does not apply.
  <!-- 13(1)(c),(d) -->
- Notification emails go out through Example Mail Relay Ltd, our
  processor in Germany. <!-- 13(1)(e) -->
- Tickets are stored and processed in Germany and are not transferred
  outside the EEA. <!-- not an Article 13 element: an accountability
  claim, evidenced by the record and the region snapshot -->
- Tickets are deleted 24 months after they are closed. <!-- 13(2)(a) -->
- You can object at any time to this use of your data:
  privacy@example.com. <!-- 21(4), its own sentence -->
- Access, rectification, erasure and restriction requests:
  privacy@example.com. Data protection officer: dpo@example.com.
  <!-- 13(1)(b); part of 13(2)(b) -->
Before: a vendor template. After: the support-tickets section rendered from the record, annotated with the Article 13 point each sentence discharges.
The record is the single source; the statement is a build output. 'GDPR certified' wording has exactly one valid input, and it sits outside your own system.

Evidencing Each Sentence on Self-Hosted Infrastructure

A record that matches the statement can still be wrong about the system. The next layer ties record fields to artefacts. On a self-hosted stack the artefacts are yours to produce, which is the sovereignty argument in miniature: nobody else's dashboard stands between you and the evidence. But be precise about what each artefact proves.

Take "processed in Germany." It is not an Article 13 element, but it is a claim a reader can test. Kubernetes defines the well-known label topology.kubernetes.io/region, used on Nodes and PersistentVolumes; its entry points to topology.kubernetes.io/zone. There the Kubernetes documentation says that on a Node the kubelet or external cloud-controller-manager populates the label from the cloud provider, only when one is used, and that otherwise "you can consider setting this on nodes". Without a cloud provider, a region label is whatever someone chose to set. On a PersistentVolume, the same page says topology-aware provisioners set node affinity constraints, and that volumes not labelled automatically can be labelled manually. A capture script records what the cluster claims about both:

bash
#!/usr/bin/env bash
# Usage: capture-region-evidence.sh <kube-context> <output-dir>
set -euo pipefail

ctx="$1"
outdir="$2"
mkdir -p "$outdir"
out="$outdir/region-evidence-$(date -u +%Y-%m-%d).txt"

{
  echo "# captured $(date -u +%Y-%m-%dT%H:%M:%SZ) context=$ctx"
  echo "# Without a cloud provider nothing populates these labels; any value was set by hand."
  kubectl --context "$ctx" get nodes -L topology.kubernetes.io/region -L topology.kubernetes.io/zone
  kubectl --context "$ctx" get pv -L topology.kubernetes.io/region
  echo "# PersistentVolume node affinity:"
  kubectl --context "$ctx" get pv \
    -o custom-columns='NAME:.metadata.name,NODE_AFFINITY:.spec.nodeAffinity.required.nodeSelectorTerms'
  echo "# nodes without a region label:"
  kubectl --context "$ctx" get nodes -l '!topology.kubernetes.io/region' -o name
} >"$out"

echo "$out"
capture-region-evidence.sh — a dated snapshot of node region and zone labels, PersistentVolume region labels, and each volume's node-affinity terms (where it can attach).

That file is evidence of intent, not proof of location. A label is a string someone typed. Pair it with what does prove location: the hosting contract and the datacentre address for each node, kept beside the snapshot. Any node in the unlabelled list is itself a finding: the record claims a location the cluster cannot show for that node. A missing region label on a volume is not proof either way. Follow the volume's node affinity to the nodes it can attach to, then check those nodes and the hosting contract.

  • Recipients: the processor contracts. Under Article 28(2) a processor may not engage another processor without the controller's prior written authorisation and, under general authorisation, must inform the controller of intended changes so it can object. Each recipients entry should link to that contract.
  • Retention: the job named in enforced_by, its schedule and its last successful run. A retention sentence with no job behind it is a policy, not a fact. Deletion that must also reach backups is covered in the CCPA deletion architecture piece.
  • Transfers: if transfers is empty, no egress path to a third-country processor should exist. Where one does, the safeguard sentence belongs in the statement; the mechanics are in Schrems II and EU data on US clouds.

Exit Ramps and the Moving Text: The Digital Omnibus Proposal

A statement generated from the record is also an exit ramp. Replacing a processor or moving a workload to another region is a pull request against the record; the statement follows on the next build, and the diff is the change log. No one has to remember which web page still names the old provider. Optionality is cheaper when the paperwork is code.

The law is also moving. The Commission's Digital Omnibus proposal, COM(2025) 837, would replace Article 13(4) so that Article 13 information need not be given where data is collected in "a clear and circumscribed relationship" with a controller whose activity "is not data-intensive" and the person presumably already has the controller's identity and contact details and knows the purposes and legal basis. The exemption would not apply where the controller transmits the data to other recipients or categories of recipients, transfers it to a third country, carries out automated decision-making, including profiling, referred to in Article 22(1), or the processing is likely to result in a high risk to the rights and freedoms of data subjects within the meaning of Article 35.

It is a proposal, not adopted law. Do not cut a sentence from a statement on its strength — and on its own wording, a service that passes data to other recipients would stay outside the exemption.

The Long Game: A Statement You Can Still Defend in Five Years

Statements decay. Processors change, regions move, retention jobs get disabled during an incident and never re-enabled, certificates expire after at most three years. Review the record whenever infrastructure changes and on a fixed cadence regardless, re-run the evidence capture, and check any certificate's expiry against the statement that cites it.

§FAQ/Common questions

Frequently asked

What does GDPR compliance mean?

There is no single compliance certificate or declaration in the GDPR. Under the Article 5(2) accountability principle, the controller is responsible for, and must be able to demonstrate, compliance with the processing principles. A compliance statement is a public summary of claims that must each be true under those duties and the Article 12-14 transparency rules.

Is a GDPR compliance statement legally required?

No article requires a document called a compliance statement. What is required is the information in Articles 13 and 14, given concisely and in plain language under Article 12(1), and, where a DPO has been designated under Article 37(1) or 37(4), publication of the DPO's contact details under Article 37(7). A statement can summarise these but does not replace the Article 13 notice.

Can a company say it is GDPR certified?

Only if it holds a certification under Article 42, issued by an Article 43 accredited body or the competent supervisory authority on approved criteria, such as a scheme listed on the EDPB's register of certification mechanisms, seals and marks. Certification lasts at most three years and, under Article 42(4), does not reduce the controller's or processor's responsibility for compliance.

What should a good GDPR compliance statement include?

The controller's identity and contact details, the DPO's contact where one is designated, each purpose with its lawful basis, recipients, any intended third-country transfer with its adequacy decision or safeguard, retention periods or the criteria for them, and how to exercise rights and complain to a supervisory authority. That is the core of Article 13(1) and 13(2), not all of it: 13(2)(e) on whether providing the data is required, and 13(2)(f) on Article 22 automated decision-making, apply when relevant. A processing location is not an Article 13 item; state one only if you can evidence it.

gdpr compliance statement examplesgdpr compliance meaninggdpr compliance definitiongdpr certified claim article 42gdpr article 13 privacy notice contentseuropean data protection seal europrivacy

Executive Briefing

Thirty minutes to clarify your infrastructure risk

Walk us through your vendor footprint and regulatory constraints. We will tell you honestly where sovereignty creates leverage — and where it does not. No pitch deck. No obligation.