whats-best.ai
Search Sign in

Data Protection

Akarion GRC Cloud

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by AKARION GmbH · akarion.com

Compare with caralegal → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Skeptic

Weighted verdict

Hunts certification logos that link nowhere, "AI-powered" features with no substance behind them, consulting bundled as software, legal-update promises with no named lawyer, and customer counts that disagree between pages. Exists to keep the rest of the bench honest.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Skeptic

Records & DPIA depth

How this is scored

The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.

0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.

3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.

5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.

8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.

10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client/mandate capability included, and the documentation is audit-ready without manual assembly.

Report an error

The Skeptic

The DSMS page claims a genuinely connected model — a dynamic VVT that updates from processes and assets, DSFA with data-flow visualization, central Auftragsverarbeiter management with contract/audit tracking, TOMs with authority-facing reports, and TIA documentation — plus mandate inheritance with template tenants that looks like real group reuse. It falls short of an 8 because nothing evidences legal bases living in the system, DPIA triggers derived from the RoPA, or authority-accepted outputs; this is one polished marketing page, not proof of depth. 3 1 2

Report an error

Data subject rights & incidents

How this is scored

The operational half of the DSMS: data subject request handling with statutory clocks, breach register and authority notification, deletion concepts that actually delete.

0 — Requests arrive by email and live there; breaches are a phone call and a memo.

3 — A request log and a breach list exist, but deadlines are manual, intake is unstructured, and deletion rules are documentation rather than workflow.

5 — DSR workflows with the Art. 12 clock tracked, structured breach register with the 72-hour clock, deletion concepts assignable to records; automation is reminders.

8 — Intake channels for requests (portal/form), identity-check support, deadline automation with escalation, breach severity assessment and authority-report output, deletion rules tied to the RoPA with execution tracking.

10 — Rights and incidents as operations: end-to-end request handling an authority audit walks through, breach workflows that produce the Art. 33 notification, and deletion automation with evidence that the deletion happened.

Report an error

The Skeptic

The breach half reaches the level-5 claim — a workflow that guides assessment and monitors the 72-hour GDPR clock — but the data-subject half is completely silent: no intake form, no Art. 12 clock, no identity check, no deletion concept, no Art. 33 report output anywhere in the captured pages. Half a criterion with no evidence is information, so this lands between the breach-5 and DSR-absence. 3 4 2

Report an error

Privacy regime coverage

How this is scored

Which privacy regimes the product actually operationalizes — GDPR, BDSG, Swiss nDSG, UK GDPR, ePrivacy, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.

0 — One regime, hard-coded; anything else is "on the roadmap".

3 — GDPR plus one national law as separate checklists; the same processing activity is documented once per regime.

5 — The major regimes for its market with partial cross-mapping; newer duties (AI Act, ePrivacy changes) present as content packs of varying depth.

8 — Broad current coverage with one-record-many-regimes mapping and visible maintenance as regimes evolve.

10 — Regime coverage as a living product: multiple privacy regimes on one data basis, per-country variants, and documented update cadence when the law moves.

Report an error

The Skeptic

The framework list is deep on the security side (BSI Grundschutz, NIS-2, DORA, ISO family) but the privacy-regime column is one entry: SDM (DSGVO) — no Swiss nDSG, no UK GDPR, no ePrivacy, no AI Act privacy duties, and no evidence of one-record-many-regimes mapping. '217 updates in 2024' is platform velocity, not a documented legal-content cadence, so I can't credit maintenance of regimes that aren't listed. 1 2 4

Report an error

Audit readiness & evidence

How this is scored

Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.

0 — Exports are screenshots; history is overwritten in place.

3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.

5 — Versioned records, standard report generators for the core registers, evidence attachments per activity; assembling a full audit file still takes days.

8 — Revision-safe change history, audit-scoped evidence packs on demand, management and authority reports current at a click, auditor access roles.

10 — Audit readiness as a standing state: continuous documentation status per regime and scope, exportable proof packs an auditor accepts as-is, and a defensible answer to "show me the state on date X".

Report an error

The Skeptic

The claims overshoot rubric level 5 — revisionssichere incident documentation, on-click reports for management and auditors, TOMs with customizable reports for Behörden, an audit trail, multi-stage approvals and a dedicated Audit module. But nothing evidences audit-scoped evidence packs, auditor access roles, or point-in-time reconstruction ('state on date X'), so it stays below 8 on claim-not-proof. 4 3 2 1

Report an error

Integrations & automation

How this is scored

Whether the platform feeds from the real IT estate — directory import, ticketing, API — and automates the recurring privacy work instead of re-typing it.

0 — A closed island: manual entry in, PDF out, no API.

3 — CSV/Excel import and export; no live connections, no API worth the name.

5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing or SSO); automation is reminders and recurrence.

8 — Real connector set (ticketing, HR or asset sources), webhooks, SSO/SCIM, workflow automation with delegation and escalation, useful AI assistance with human review.

10 — The platform behaves like infrastructure: API parity for the data model, event streams, bidirectional sync with the estate, and automation that measurably removes the recurring toil (reviews, attestations, evidence pulls) rather than renaming it.

Report an error

The Skeptic

The connector list is the hardest fact here — 13 native integrations spanning ticketing (Jira, ServiceNow, omnitracker), ECM and collaboration, plus custom connectors, SSO/MFA and real automation in top-down mandate inheritance and automated Schutzbedarfsvererbung. But 'Autoprovisioning' is a bare word with no SCIM named, and no documented REST API or webhook appears anywhere — the AI claims at least admit human review, but infrastructure this is not. 2 1 4

Report an error

European sovereignty

How this is scored

Where the compliance record of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. A platform that maps your processing is itself your most concentrated processing.

0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your RoPA.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.

5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.

8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.

10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.

Report an error

The Skeptic

What keeps this at 4 rather than 5+ is that no public DPA, no subprocessor list, and no TOMs publication are captured — for the system holding your RoPA, that's the missing half of the chain. 5 6 1 2

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.

0 — No public prices at all; every configuration is a sales conversation.

3 — An entry price exists, but module add-ons, entity counts or bundled consulting make the real total incomputable.

5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; only genuine corporate-group contracts are custom.

10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a 10-client consultancy is a two-minute exercise.

Report an error

The Skeptic

Five modules 'for your individual needs' and a module lineup are described across four captured pages, and not one number, edition, billing period or setup fee appears anywhere. Every configuration is evidently a sales conversation, which is the anchor-0 definition, however normal that is in this market. 1 2 4

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Akarion GRC Cloud? Tell us Report an error on this page

Sources (8)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage akarion.com Checked 16 Sep 2026 Details →
  2. 2 Platform overview page akarion.com Checked 16 Sep 2026 Details →
  3. 3 Data protection (DSMS) module page akarion.com Checked 16 Sep 2026 Details →
  4. 4 ISMS module page akarion.com Checked 16 Sep 2026 Details →
  5. 5 About page akarion.com Checked 16 Sep 2026 Details →
  6. 6 Imprint akarion.com Checked 16 Sep 2026 Details →
  7. 7 Audit readiness & evidence — found from sitemap akarion.com Checked 1 Oct 2026 Details →
  8. 8 Audit readiness & evidence — found from sitemap akarion.com Checked 1 Oct 2026 Details →