Costs and internal effort
Data protection incurs ongoing costs, not one-off ones. For the tool, the Sightadel licence for the GDPR is charged monthly per edition, with a minimum term of one year. If your Sightadel licence includes ISO 27001 or ISO 9001, you receive a permanent discount on the GDPR. You will find all prices and a calculator on our pricing page.
On top of that comes the data protection officer, if you must or want to designate one. They can be internal or external. An internal officer needs time, further training and enjoys special protection against dismissal, which must be taken into account in workforce planning. An external officer charges according to their own model. Both are independent of Sightadel.
The largest item is the internal effort for the core documentation: record of processing activities, contracts with service providers, technical and organisational measures, processes for data subject requests and personal data breaches. Two to four months is realistic if one person works on it regularly and the business units contribute. After that, it is about maintenance: adding new processing activities, reviewing contracts, implementing erasure periods, training employees. If you need support with individual questions, you can add consulting as a package in the app. Sightadel does not replace legal advice.
Fines, compensation and accountability
The GDPR has two ranges of fines: up to €10 million or 2% of worldwide annual turnover, for example for violations of obligations relating to security, the record of processing or processing on behalf, and up to €20 million or 4% for violations of principles, legal bases or data subject rights, whichever is higher in each case. Supervisory authorities set fines on a case-by-case basis and also take into account how cooperative and well prepared a company is.
Claims for compensation by data subjects are at least as relevant. They can also be asserted for non-material damage, for example after a data breach or a late response to an access request. In addition, there are orders from the supervisory authority that can restrict or prohibit processing, and cease-and-desist letters from competitors, whose admissibility is disputed in individual cases.
The core is accountability. You must not only work in compliance with data protection law but be able to prove it. In the event of a complaint, the supervisory authority asks about the record of processing, legal basis, contracts and measures. If you can present these documents quickly and consistently, you are in a much better position. That is exactly what the state of evidence in Sightadel is intended for.
What documentation is required
The GDPR explicitly requires some documents: the record of processing activities, data processing agreements, documentation of personal data breaches, data protection impact assessments for processing likely to result in a high risk and, where necessary, the designation of the data protection officer. Others follow from accountability: a description of the technical and organisational measures, privacy notices, an erasure concept, evidence of consent, balancing tests for legitimate interest and training records.
The record is the backbone. For each processing activity, it describes the purpose, categories of data and data subjects, recipients, transfers to third countries, erasure periods and measures. If it is well maintained, privacy notices, the erasure concept and responses to access requests can be derived from it. If it is created once and then forgotten, after two years it describes a different organisation.
In Sightadel, the industry template suggests typical processing activities; you confirm, add or remove them. You maintain contracts and sub-processors in the Vendors module, and measures as guided questions with evidence. Scheduled reviews ensure the record is checked regularly.
Data subject requests and data breaches in everyday practice
Two processes determine whether data protection works day to day: handling requests from data subjects and handling personal data breaches. As a rule, you must respond to an access request within one month. For complex or numerous requests, an extension of up to two further months is possible if you give notice of this, with reasons, within the first period. The response covers the data itself, purposes, recipients, storage period and source, as well as a copy.
For this to work, it must be clear who receives requests, how identity is verified, where data is held and who approves the response. Requests often arrive through unexpected channels: to sales, via a contact form, as part of an employment dispute.
For personal data breaches, the 72-hour period starts when you become aware of the breach. Define who assesses whether there is a risk to data subjects, who reports and who informs the data subjects. If there is also a NIS2 incident, both reporting channels run in parallel. In Sightadel, responsible persons and templates are on record, and requests and breaches are recorded as evidence with time and assessment.
Service providers, cloud and third-country transfers
Hardly any organisation processes data only by itself. Payroll, email, CRM, ticketing, web analytics and hosting run with service providers. Each of them that processes data on your behalf needs a data processing agreement, and you must have selected them carefully. That includes knowing their measures and sub-processors.
Transfers to countries outside the European Economic Area deserve particular attention. They need a basis, such as an adequacy decision by the European Commission or standard contractual clauses with an assessment of the situation in the destination country. Even if a provider hosts in the EU, access from a third country may be possible, for example through support or a parent company.
In the Vendors module, you record service providers with contract, sub-processors, transfers and evidence including validity dates. Missing contracts become action items. Sightadel itself is developed in Germany and hosted in Germany, and every customer receives a data processing agreement under Art. 28 GDPR.
Interplay with ISO 27001, NIS2 and AI
The GDPR requires security of processing but does not say in detail how. This is where an ISMS based on ISO 27001 helps: access control, encryption, backup, logging and incident handling are governed systematically there. The technical and organisational measures under Art. 32 can be proven with the same evidence. What ISO 27001 does not cover are legal bases, purpose limitation, data subject rights and the record of processing activities.
Entities subject to NIS2 use the incident process, vendor management and training for both frameworks. If you use AI with personal data, you assess risks for data subjects in the data protection impact assessment and, if introduced, in the impact assessment under ISO 42001. The two can be run together but do not replace each other.
In Sightadel, you link a piece of evidence once to all matching requirements. Your internal or external data protection officer works with their own role. In the Trust Center, you show customers measures, documents and sub-processors instead of filling in a new questionnaire for every request.