Skip to content
SimpleAct Logo

Consistency check

Finds contradictions between modules, for example between AI inventory, RoPA, vendor register and third-country transfers.

Many details live in several places in SimpleAct: an AI system processes personal data, the record of processing names recipients, the vendor register knows third countries, the privacy notice names the controller. The consistency check compares what several modules record about the same thing and shows where they contradict each other. It is computed anew on every call, writes nothing and blocks nothing.

At a glance

Included from
In all plans; only booked modules are checked
Where in the app
Overall overview and checklist; also as a hint directly in the forms
Output
Findings with priority, severity, legal reference, records concerned and suggested fix
Legal basis
Art. 5(2), Art. 30, Art. 35 GDPR; Art. 9 et seq. AI Act
API
/api/v1/consistency/findings

Severities

Each finding also has a priority from P1 to P3. No finding blocks saving or a status change.

SeverityMeaning
Error (ERROR)The record states the opposite of what its links prove.
Contradiction (WARNING)Records contradict each other.
Please check (HINT)Worth a check, but may be correct in the individual case.

What is checked

The rules are numbered (R1 to R51, plus a few special rules). An overview by topic:

Core rules (R1–R14)

Checklist items saved as done that are no longer supported; DPIA threshold against the AI Act classification; automated decisions; controller in RoPA, profile and privacy notice; third-country transfers; vendor role; training data; data subject categories; DPO contact; Annex IV after its sources changed; overdue reporting of serious incidents (Art. 73 AI Act); missing DPIA; TOM without a description.

Personal data, recipients, transfers (R15–R24)

Contradictory personal data flag of an AI system; "no recipients" although processors exist; processors or third-country transfers of the AI system missing in the RoPA; recipient in a third country without a transfer; national legal basis without special categories; retention in days does not match the text; differing SCC module; transfer in the tracker, but the service provider has no third country; person instead of organisation as controller.

Likely contradictions (R25–R39)

§ 26 BDSG without employees; retention shorter than the cited retention duty or different from the deletion concept; data categories of service providers or AI systems the RoPA does not name; profiling and automated decision without a DPIA; special categories from the risk assessment; responsible person and email do not match; destination in the tracker differs from the service provider; deciding system without automated decision in the RoPA; recipients not informed after erasure or rectification (Art. 19 GDPR); processors without a DPA in approved processing activities; controller looks like a person name; data subject groups; credit bureau recorded as a processor.

Further checks (R40–R51)

AI system out of operation, but processing active; statutory retention without the legal basis lit. c; data breach concerns data the RoPA does not name, or names a contact other than the DPO; consent banner service missing in the vendor register; DPF as the basis without a recorded certification; SCC module does not fit the role; automated decision without an exception under Art. 22(2) GDPR; consent of employees; recording conversations (§ 201 StGB); training with user data (change of purpose); AI system with personal data without a RoPA record.

How to read a finding

  • Title, explanation and legal reference (GDPR or AI Act with article and paragraph).
  • The records concerned with a direct link and the fields concerned ("Fix here").
  • Where unambiguous, a one-click fix, for example "Take the value from the processing activity". It is only saved once the form is saved.
  • Only modules you may read and your organisation has booked are checked. The view names explicitly what was not checked. Records you may not read appear in a finding without a name.
  • If details are missing to evaluate a rule, the note "Not checkable" appears instead of a finding.

"Intended": keeping a finding with a reason

Some findings do not apply in the individual case. With "Intended" you record that the details are correct.

  • A reason is mandatory (10 to 1,000 characters). It is internal: it is kept in the audit log, but appears neither in the Art. 30 export, nor in the authority pack, nor in privacy notices.
  • A finding marked this way no longer counts in the GDPR score, on the dashboard or in the open checklist items.
  • If the data the finding refers to change, the mark lapses and the finding is active again.
  • Not possible for errors (ERROR) and not for the duties of the data protection impact assessment (Art. 35 GDPR) and of the DPO contact (Art. 37(7) GDPR).
  • Whoever may edit the module of the record concerned, or an admin, may set and revoke it. It is a personal decision: only signed-in people can set or revoke "Intended"; API keys receive 403.
  • Setting and revoking are recorded in the audit log.

Endpoints

CallPurpose
GET /api/v1/consistency/findingsAll findings of the organisation ("read dashboard" permission), optionally only for one AI system (aiSystemId) or a single record (subjectType and subjectId). Findings marked as intended are listed under "acknowledged".
POST /api/v1/consistency/acknowledgementsMark a finding as "Intended", with a reason.
DELETE /api/v1/consistency/acknowledgements/{id}Revoke the mark; the finding is active again.

AI suggestion for a finding

With the AI assistant switched on, “AI suggestion” on a finding explains in plain language what does not fit and recommends: change the entry, probably intended, or review manually. You take proposed values over into the form with “Adopt the AI’s suggestion” and save yourself. If the AI considers the finding intended, “Mark as intended with the AI’s draft reason” opens the dialog with the reason prefilled; you confirm it yourself. Via the API: POST /api/v1/consistency/findings/ai-suggestion (also with an API key, at most 10 requests per minute).

Related pages