Building software for a German business, or for the German market, means working within several overlapping sets of rules at once. Data protection law is the obvious one, but it now sits alongside cybersecurity duties, accessibility requirements, e-invoicing rules and, increasingly, regulation of AI and connected products.
Compliance rarely fails because a company ignored the law altogether. It fails because the requirements were discovered after the architecture was already fixed. This guide sets out the main regimes to consider, when each one tends to apply, and how to build them into the development process rather than bolting them on at the end.
It is written with UK readers in mind: UK companies building for German customers, working with German development partners or running a German subsidiary. Nothing here is legal advice, and the position on several regulations is still moving, so treat the dates and thresholds below as a starting point to confirm with a specialist.
The Main Compliance Areas at a Glance
Not every rule applies to every project. A customer portal for a German retailer faces a different set of obligations from an internal HR tool or a connected device. The table below summarises the regimes that come up most often.
| Regime | Who it affects | What it means for development | Key figure or date |
|---|---|---|---|
| GDPR (DSGVO) and BDSG | Anyone processing personal data of people in the EU | Privacy by design, processor contracts, records of processing, breach handling | Fines up to €20 million or 4% of worldwide annual turnover |
| TDDDG (cookies and device access) | Websites and apps using cookies, trackers or device storage | Consent management before non-essential tracking loads | In force since 2021 as TTDSG, renamed in 2024 |
| NIS2 (German implementation) | Entities in listed sectors above certain size thresholds, plus some digital providers | Security risk management, supply chain controls, incident reporting | In force since 6 December 2025 |
| Cyber Resilience Act | Makers of products with digital elements sold in the EU | Secure development, vulnerability handling, software bills of materials | Reporting duties from 11 September 2026, main duties from 11 December 2027 |
| EU AI Act | Providers and deployers of AI systems | Risk classification, transparency, documentation | Phased, with high-risk dates postponed to 2027 and 2028 |
| BFSG (accessibility) | Certain consumer-facing products and services, including e-commerce | Accessible design and testing | Applies since 28 June 2025 |
| E-invoicing | Businesses issuing or receiving B2B invoices in Germany | Structured invoice formats such as XRechnung or ZUGFeRD | Receiving since 1 January 2025, issuing phased in from 2027 |
Data Protection: The Foundation for Most Projects
The General Data Protection Regulation applies to almost any application that handles personal data, and Germany adds its own Federal Data Protection Act (BDSG) on top. The practical effect on development is that data protection has to be a design input, not a review step.
Article 25 of the GDPR requires data protection by design and by default, which in practice means collecting only the data you need, setting privacy-friendly defaults and being able to delete or export a person's data on request.
A few points catch development teams out regularly:
- Processor agreements. If a third party hosts, supports or analyses personal data on your behalf, you need a data processing agreement. This includes cloud hosting, error-tracking tools and customer support platforms.
- Data protection impact assessments. A DPIA is required where processing is likely to result in a high risk to individuals, which can include large-scale monitoring or profiling. It is far cheaper to carry out during design than after launch.
- Breach notification. Serious personal data breaches must generally be reported to the supervisory authority within 72 hours, so logging and alerting need to be capable of supporting that.
- Data protection officers. Under German law, a company must appoint one if at least 20 people are regularly involved in automated processing of personal data, a lower trigger than the GDPR alone would suggest.
Cookies and tracking are governed separately. Since 2021 Germany has required consent before storing or reading information on a user's device, unless it is strictly necessary for the service, and the law now carries the name TDDDG.
Consent management tools such as Usercentrics or Cookiebot can handle this, but the application must also actually stop non-essential scripts from loading until consent is given. A banner that records consent while trackers fire anyway does not satisfy the rule.
For UK teams, data flowing between the UK and the EU currently relies on adequacy arrangements, which are reviewed periodically, and transfers to other countries such as the US need a recognised mechanism, for example standard contractual clauses or the EU-US Data Privacy Framework, which has faced legal challenge.
Check the current position with your data protection adviser before finalising hosting and vendor choices. There is no general rule that German personal data must stay in Germany, though some customers will require it by contract.
Cybersecurity: NIS2 and Secure Development
Germany's law implementing the NIS2 Directive came into force on 6 December 2025, later than the EU's original deadline and without a general transition period.
It extends security obligations to a much wider group of organisations than the old rules did, covering both "essential" and "important" entities across sectors that include energy, transport, health, digital infrastructure, managed services and certain online platforms.
Whether a business is in scope depends on its sector and size, so it is worth checking against the official criteria rather than assuming. For development teams, the most relevant elements are risk management measures, supply chain security and incident reporting. Significant incidents must be reported in stages: an early warning within 24 hours, a fuller notification within 72 hours and a final report within a month.
Management bodies must approve and oversee the security measures, and fines can reach €10 million or 2% of turnover for essential entities and €7 million or 1.4% for important ones.
Software suppliers to in-scope companies feel the effect indirectly. Customers will increasingly ask about secure development practices, vulnerability management and certifications such as ISO 27001 or the BSI's C5 attestation for cloud services. Having these answers ready can shorten procurement considerably.
Products with software: the Cyber Resilience Act
If you are building a product with digital elements, such as a connected device or software shipped with hardware, the Cyber Resilience Act adds product-level duties. Reporting of actively exploited vulnerabilities applies from 11 September 2026, and the main requirements follow from 11 December 2027.
In practice, this pushes teams towards maintaining a software bill of materials (SBOM) in a format such as CycloneDX or SPDX, scanning dependencies with tools like Snyk, Trivy or OWASP Dependency-Check, and having a clear process for receiving and fixing vulnerability reports.
AI Features and the EU AI Act
Many business applications now include AI features, from chatbots to scoring and recommendation tools, and these bring the EU AI Act into scope. The Act classifies systems by risk. Some practices are prohibited outright, some uses are classed as high-risk, and others carry transparency duties, such as telling users they are talking to an AI.
The timetable has shifted. The EU agreed in 2026 to postpone high-risk obligations for stand-alone systems to 2 December 2027 and for AI embedded in regulated products to 2 August 2028, while prohibitions and the rules for general-purpose models already apply. Confirm the final adopted dates before relying on them.
Whatever the timing, the underlying data work is the same: knowing where your data comes from, how clean it is and who can access it. Guidance on how to organise Business Data for AI Applications is a useful companion at the planning stage, because poor data governance undermines both AI quality and GDPR compliance.
Accessibility and E-Invoicing
Two further requirements are easy to overlook because they sound like design or finance issues rather than software ones.
The Barrierefreiheitsstärkungsgesetz (BFSG), Germany's implementation of the European Accessibility Act, has applied since 28 June 2025. It covers certain consumer-facing products and services, including e-commerce, banking services and e-books, with an exemption for micro-enterprises providing services (fewer than 10 staff and turnover or balance sheet total not above €2 million).
Fines can reach €100,000. Building to WCAG 2.1 AA, a commonly used reference standard, and testing with screen readers and keyboard-only navigation, is much cheaper at design stage than retrofitting.
On invoicing, all German businesses have had to be able to receive structured electronic invoices since 1 January 2025. The obligation to issue them is phased in: from 1 January 2027 for businesses with prior-year turnover above €800,000, and from 1 January 2028 for everyone else.
Accounting and ERP integrations should therefore support formats such as XRechnung or ZUGFeRD, rather than treating a PDF as the invoice.
Open-Source Licences and Third-Party Code
Most modern applications contain far more third-party code than first-party code, and each component comes with a licence. Permissive licences such as MIT and Apache 2.0 are generally straightforward, while copyleft licences such as the GPL can impose obligations on how you distribute your own code, depending on how the component is used.
The right approach is to keep an inventory from the start. Tools such as FOSSA, Black Duck or the open-source FOSSology can generate licence reports, and the same inventory feeds the SBOM mentioned earlier.
Working Out What Applies to Your Project
A short sequence of questions will narrow the list quickly:
- Does the software handle personal data of people in the EU? If yes, GDPR and BDSG apply, and TDDDG applies if you use cookies or similar technologies.
- Is your customer, or are you, in a regulated or critical sector? If yes, check NIS2 scope, and for financial entities the Digital Operational Resilience Act (DORA), which has applied since 17 January 2025.
- Is it a product with digital elements, such as a device? If yes, plan for Cyber Resilience Act requirements.
- Does it include AI features? If yes, classify the system under the AI Act and record the reasoning.
- Is it consumer-facing, or does it handle B2B invoices? If yes, check BFSG and e-invoicing duties.
Where the answer is unclear, it is often sensible to bring in a development partner with local knowledge early. A team familiar with German requirements, such as the specialists offering software entwicklung hamburg, can help translate regulatory requirements into concrete user stories, architecture decisions and test cases before they become expensive to change.
Making Compliance Part of the Development Process
The most reliable way to avoid late surprises is to put compliance checks where developers already work. Add a short compliance questionnaire to project kick-off. Record data flows and vendors in a shared register that doubles as your GDPR record of processing.
Run dependency and licence scans in your CI pipeline so issues appear in pull requests, not audits. Keep accessibility checks in your definition of done.
If you take one step this week, map the personal data your product handles and the third parties that touch it. That single exercise feeds almost every other requirement in this guide, and it will show you quickly which of the other regimes you need to look at next.