Germany

Germany Federal Data Protection Act (BDSG)

79 controls. 2 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

79 controls 2 frameworks share controls with it Germany verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
P1Part 1: common provisions (public bodies, video surveillance, data protection officers)0
P2Part 2: implementing provisions for processing under the GDPR (employment, special categories, rights, private-sector DPOs)0
P3Part 3: processing by competent authorities for law enforcement (Directive (EU) 2016/680)0
P4Part 4: processing outside the scope of the GDPR and the Directive0
X-bfdiThe Federal Commissioner and EU cooperation (ss 8 to 19, 82)0
X-penaltiesPenalties and liability (ss 41 to 43, 83, 84)0
X-remediesLegal remedies and complaints (ss 20, 21, 44, 60, 61)0
X-scopeScope and definitions (ss 1, 2, 45, 46)0
X-statusStatus: text version, amendments and case law (recorded 2026-09-30)0
X-supervisionLand supervisory authorities and accreditation (ss 39, 40)0
s16-4s 16(4) Give the Federal Commissioner access to premises, equipment, data and information1
s22s 22 Process special categories only on a listed national ground and with specific safeguards1
s23s 23 Public bodies further process data for another purpose only on a listed ground1
s24s 24 Private bodies reuse data for another purpose only for security, prosecution or legal claims1
s25s 25 Public bodies transfer data to other bodies only on the listed conditions and with purpose binding1
s26s 26 Data processing for employment-related purposes0
s26-1s 26(1) sentence 1 Process employee data only where necessary for the employment relationship, on a GDPR legal basis1
s26-1-s2s 26(1) sentence 2 Investigate suspected crimes by employees only on documented suspicion and proportionately1
s26-2s 26(2) Rely on employee consent only where it is genuinely voluntary, in the required form and with text-form notice1
s26-3s 26(3) Process employees' special category data only for labour and social law duties, or on explicit consent1
s26-4s 26(4) Where a collective or works agreement governs employee data, meet GDPR Art. 88(2)1
s26-5s 26(5) Take measures to ensure the GDPR principles are met in employee data processing1
s27s 27 Research and statistics: balance interests, safeguard, anonymise early and separate identifiers1
s28s 28 Archiving in the public interest: safeguard special categories and record counter-statements1
s29s 29 Apply the secrecy exceptions to information, access and breach notice narrowly1
s3s 3 Public bodies process personal data only where needed for their task or official authority1
s30s 30 Treat EU lenders' credit enquiries like domestic ones, and tell consumers promptly when credit is refused0
s31s 31 Use scores for contract decisions only on the statutory conditions1
s32s 32 Withhold collection-time information on further use only in the listed cases, with compensating steps1
s33s 33 Withhold information on data obtained from others only in the listed cases, with compensating steps1
s34s 34 Refuse access only on the listed grounds, document why and tell the data subject1
s35s 35 Restrict instead of erasing only in the listed cases, and tell the data subject1
s36s 36 Public bodies: honour objections unless a compelling public interest or a legal duty prevails1
s37s 37 Insurance: automated decisions only where the request is met or with human review rights1
s38s 38 Private bodies designate a data protection officer at 20 persons, or regardless of size for high-risk processing1
s4-1s 4(1) Video surveillance of publicly accessible spaces only where necessary for a listed purpose2
s4-2s 4(2) Make video surveillance and the controller identifiable at the earliest possible point1
s4-3s 4(3) Store and use video data only for the stated purpose, with narrow onward uses1
s4-4s 4(4) Inform a person when video data are attributed to them1
s4-5s 4(5) Delete video data without delay once no longer needed2
s40-4-5s 40(4), (5) Give the Land supervisory authority information and tolerate on-site inspections1
s47s 47 Apply the six principles to law enforcement processing1
s48s 48 Process special categories only where strictly necessary and with safeguards1
s49s 49 Further process for another purpose only within s 45 purposes or where a law allows1
s5s 5 Public bodies designate a qualified data protection officer and publish the contact details1
s50s 50 Use archival, scientific or statistical forms only in the public interest and with safeguards0
s51s 51 Where the law allows consent, obtain valid consent and be able to prove it1
s52s 52 Staff and processors act only on the controller's instructions1
s53s 53 Bind staff to data confidentiality on taking up duties1
s54s 54 Automated individual decisions only when authorised by law, never discriminatory1
s55s 55 Publish general information about the processing1
s56s 56 Where a law requires notification, include the minimum content, and defer only on listed grounds1
s57s 57 Answer access requests with the listed information, and handle refusals through the Federal Commissioner1
s58s 58 Rectify, erase or restrict on request, inform recipients and give written reasons for refusals1
s59s 59 Communicate clearly, free of charge, in the form of the request1
s6s 6 Involve, resource and protect the data protection officer1
s62s 62 Use processors only with sufficient guarantees and a binding written or electronic contract1
s63s 63 Joint controllers set out their responsibilities in an agreement1
s64s 64 Implement risk-based security measures, including the fourteen control objectives for automated processing1
s65s 65 Notify the Federal Commissioner of breaches within 72 hours and document all breaches1
s66s 66 Tell data subjects of breaches likely to pose a substantial risk1
s67s 67 Assess the impact before high-risk processing and involve the Federal Commissioner1
s68s 68 Cooperate with the Federal Commissioner1
s69s 69 Consult the Federal Commissioner before high-risk processing in a new filing system1
s7s 7 Give the data protection officer at least the statutory tasks and avoid conflicts1
s70s 70 Keep records of processing activities1
s71s 71 Build in data protection by design and by default1
s72s 72 Distinguish between categories of data subjects0
s73s 73 Distinguish facts from personal assessments0
s74s 74 Check quality before transmitting data and pass on processing conditions0
s75s 75 Rectify and erase, and set time limits for erasure or review1
s76s 76 Log collection, alteration, consultation, disclosure, combination and erasure1
s77s 77 Be able to receive confidential reports of data protection violations1
s78s 78 Transfer to third countries only to competent bodies with adequacy, and control onward transfers1
s79s 79 Without adequacy, transfer on appropriate safeguards, document it and report annually1
s80s 80 Transfer without safeguards only on the listed necessity grounds and document it1
s81s 81 Transfer directly to other third-country recipients only exceptionally and with purpose instructions1
s85s 85 Outside EU law, transfer for defence and crisis tasks only with purpose instructions, and apply the information exemptions narrowly0
s86s 86 State awards and honours: process only what is needed and safeguard special categories0

Tell me when Germany Federal Data Protection Act (BDSG) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Germany Federal Data Protection Act (BDSG), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition