Sightadel

Solutions · Data protection

Accountability means evidence.
Not searching when someone asks.

As a data protection officer or data protection coordinator, your job is to advise and monitor, yet the documentation still ends up with you. Sightadel organises the record of processing activities, processing on behalf, technical measures, impact assessments and data breaches so that departments contribute and you can show the status at any time.

Starting point

What this role carries.

The GDPR does not only require data to be processed lawfully. Under Art. 5(2), the controller must also be able to demonstrate compliance. In practice this means: an up-to-date record of processing activities, agreements with all processors, evidenced technical and organisational measures, documented impact assessments and a register of all data breaches, including those not reported.

Usually much of this exists, just not in one place. The record sits as a spreadsheet on a shared drive, the agreements with procurement, IT describes the technical measures in a separate document, and the ISMS has a second version of the same measures. When the supervisory authority makes enquiries or a customer sends a questionnaire, the search begins.

Then there is your particular position. As a data protection officer you advise and monitor; responsibility for implementation lies with management and the departments. Sightadel reflects exactly that: departments work on their parts themselves, you review and see where something is missing. As an external data protection officer you work with your own role in your client's account.

Why now

Typical reasons to tackle the topic.

01

Enquiry from the supervisory authority

After a complaint or a data breach, the authority asks for the record, measures and agreements. The response deadline is short. If you have the status organised, you answer in days instead of weeks.

02

Data breach

A misaddressed mailing, a lost notebook, an attack on a mailbox. Reportable breaches generally go to the supervisory authority within 72 hours. For that, the assessment, responsibilities and reporting channel must be set in advance.

03

New software or a new service provider

A department wants to introduce a cloud tool. Before it goes live, it needs an entry in the record, a data processing agreement, a review of subprocessors and, if the risk is high, an impact assessment.

04

Use of AI tools

Employees use tools based on artificial intelligence, often without approval. This raises questions about the legal basis, transfers to third countries and impact assessments. An organised approval process replaces uncontrolled growth.

05

Customers ask about your measures

As a processor you constantly answer questionnaires on technical measures and subprocessors. A maintained status and a Trust Center answer the usual questions once for everyone.

06

Information security is being expanded

The company introduces an ISMS under ISO 27001 or falls under NIS2. Now is the moment to maintain the technical measures jointly rather than twice.

Relevant frameworks

What applies – and what it specifically requires here.

Summarised in our own words, not legal advice. The original text in its current version is authoritative.

GDPRMandatory

Applies to every organisation that processes personal data, supplemented in Germany by the Federal Data Protection Act (BDSG). The core of the documentation is the record under Art. 30, agreements under Art. 28, the measures under Art. 32, impact assessments under Art. 35 and the documentation of data breaches under Art. 33. There is no general GDPR certificate; the supervisory authorities carry out the checks.

View framework →
ISO/IEC 27001Recommended

The technical and organisational measures under Art. 32 can be evidenced with the same evidence as many controls from Annex A, for example on access control, encryption, backups or suppliers. Annex A also contains its own control on protecting personal data. Legal bases and data subject rights have no equivalent in the standard.

View framework →
NIS2Depends on the situation

If your company falls under the German BSI Act (BSIG), the incident process, access control and vendor management serve both sets of rules. A security incident can trigger a report to the Federal Office for Information Security (BSI) and to the data protection authority at the same time, with different deadlines and recipients.

View framework →
EU AI ActDepends on the situation

Anyone using AI systems with personal data must consider the requirements of both sets of rules. Impact assessments, transparency towards data subjects and the assessment of providers can be handled together.

View framework →

Recommended order

Where to start – and what comes next.

  1. 1

    Build or take over the record

    Existing records come into Sightadel via Excel import. For each processing activity, the purpose, legal basis, categories of data and persons, recipients, transfers and deletion periods are set. Departments add their entries, you review.

  2. 2

    Capture processors

    All service providers that process data on your behalf go into the vendor list with their agreement, subprocessors and evidence. Missing or outdated agreements become measures with a deadline.

  3. 3

    Evidence technical measures

    The measures under Art. 32 are answered as questions and linked to evidence, such as the authorisation concept, encryption, backup test or training record. If there is an ISMS, you link the existing evidence instead of creating new evidence.

  4. 4

    Assess high-risk processing

    Guiding questions show where a data protection impact assessment is needed. The supervisory authorities have published lists of processing operations for this. The controller carries out the assessment itself with your advice; Sightadel provides structure and records the result.

  5. 5

    Set procedures for breaches and requests

    Who assesses a data breach, who reports it, who notifies data subjects? Who answers access requests within the deadline? Responsibilities, deputies and templates are recorded and rehearsed once.

  6. 6

    Keep it up to date

    Follow-up reminders for the record, agreements and measures. Evidence carries an expiry date. New processing activities and service providers are added before they go live, not at the next audit.

Your role

Advise and monitor, not write everything yourself

The GDPR assigns advice and monitoring to the data protection officer. The obligations themselves fall on the controller. This separation should also be reflected in how you work.

Departments contribute

HR, sales and IT know their processing activities best. With the Contributor role they maintain their entries in the record and upload evidence. You review and approve.

You see where something is missing

Processing without a deletion period, service providers without an agreement, measures without evidence. Open points appear as issues and action plans with an owner, not as a note in your calendar.

Your advice stays on record

If you advise against a processing activity or recommend an impact assessment, this is recorded with a date in the activity log. If management decides otherwise, that is traceable too.

External data protection officers

With the External Consultant role you work in each client's account. Every client has its own separate status, and the log notes that the access came from outside.

How Sightadel helps

The features that make the difference here.

Effort and duration

An honest estimate.

Taking over existing documentation2–6 weeks
Import the record and service provider list, assign agreements and measures, make gaps visible. How long it takes depends on how up to date the documents are.
Building basic documentation from scratch2–4 months
For a mid-sized company, if someone in-house drives the work and departments contribute. Impact assessments for individual high-risk processing activities come on top.
Ongoing maintenancea few hours per month
Add new processing activities and service providers, work through follow-ups, document requests and breaches. More with many departments or clients.

The ranges are based on experience, not a promise. The biggest factors are how well the departments cooperate and whether there is already an ISMS whose evidence can be reused.

What you license · typically Basic

For data protection alone, the Basic edition with five users and ten vendors is usually enough. If you are building an ISMS at the same time, add ISO 27001 and use the evidence for both. If ISO 27001 is included, there is a permanent discount on GDPR. With many processors, the Professional edition with 25 vendors is a better fit.

Licence per framework, minimum term one year, payable monthly or annually. You will find all prices, discounts and a calculator on the pricing page. Fees of a certification or audit body are charged separately.

Questions and answers

Questions about data protection

More in our FAQ or directly via our contact form.

When do we need a data protection officer?

In Germany, under § 38 of the Federal Data Protection Act (BDSG), generally when at least 20 people are constantly involved in the automated processing of personal data. Regardless of headcount, the obligation applies, for example, when processing requires an impact assessment, or under Art. 37 GDPR for certain core activities such as large-scale processing of health data. Clarify the classification in your individual case with your legal advisers.

How quickly must a data breach be reported?

Reportable breaches go to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of them. No report is needed if the breach is unlikely to result in a risk to the data subjects. If the risk is high, the data subjects are notified as well. Every breach is documented, even without a report.

What deadline applies to access requests?

In principle one month from receipt. For complex or numerous requests, the deadline can be extended by two further months, but the data subject must be informed of this within the first month. In Sightadel you record receipt, handling and response as evidence.

How do the TOMs relate to ISO 27001?

The measures under Art. 32 GDPR and many controls from Annex A cover the same topics, such as access, encryption, backups and suppliers. In Sightadel you link one piece of evidence to both. We deliberately do not give a figure for the overlap, because it depends on the scope.

Can external data protection officers look after several clients?

Yes. Each client has its own account and invites you with the External Consultant role. The statuses stay separate, and the activity log notes that the access came from outside.

Does Sightadel replace legal advice?

No. Sightadel provides structure, templates and an evidenced status. Questions on legal bases, balancing of interests or third-country transfers you assess yourself or with your legal advisers. For difficult cases, consulting can be added as a package in the app.

Is there a GDPR certificate?

There is no general certificate confirming compliance with the GDPR. What you can show is organised, evidenced documentation in line with the accountability principle. Sightadel does not certify.

Where is the data stored in Sightadel?

Sightadel is developed in Germany and operated in Germany. We conclude a data processing agreement under Art. 28 GDPR with every customer. Sightadel holds the documentation of your measures, not the personal data of your customers or employees.

Content reviewed by experts on 8 October 2026 · Not legal advice. The standard or law in its current version is authoritative.

Start with one standard.

14 days, full access, no payment details. Everything you set up carries over into the paid plan.