whats-best.ai
Search Sign in

Data Protection

audatis MANAGER

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

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

by audatis Group GmbH · www.audatis-manager.de

Compare with Robin Data ComplianceOS → Compare with preeco | datenschutz → 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 IT Integrator

Weighted verdict

Has to feed the compliance platform from the estate that already exists: Entra ID, Jira, the CMDB. Optimizes for directory import, a real API, webhooks and SSO — compliance data that stays current because it syncs, not because someone retypes it. Rejects data islands with a CSV drawbridge.

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

Scored by The IT Integrator

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 IT Integrator

RoPA, DSFA with risk management, AVV and TOM modules all exist, and the RoPA layer is unusually deep — industry template packs of 65-77 activities, group templates, delegation to responsible users, and export as an official register — plus real multi-tenancy from 2 to 46 Mandanten. What's missing is evidence of the connected data model: no statement that activities drive DPIA triggers, TOM coverage or legal bases from one record, so it sits between rubric level 5 and 8. 4 2 3

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 IT Integrator

DSR management with central templates and a deletion-concept builder (deadlines, storage locations, deletion classes) are confirmed, which is more than a log. But the evidence is completely silent on a breach register, the 72-hour clock, authority notification output, and statutory deadline automation — missing evidence that a German DSMS should have surfaced loudly — so it can't clear rubric level 5. 2 3

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 IT Integrator

DSGVO/BDSG/DSG/EKD/KDG plus current legal texts and the curated Infodienst update feed is genuine coverage of its actual market, and regular updates are claimed. Nothing evidences one-record-many-regimes mapping, and UK GDPR, ePrivacy and AI Act duties are absent, which caps it at the anchor that describes market coverage with partial cross-mapping at best. 1 2 3

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 IT Integrator

An edit history explicitly for Eingabekontrolle, revisionssicher-confirmed employee attestations, a report generator pulling KPIs from the DSMS, and CSV/Word export as an internal or authority-facing register clear rubric level 5's versioned-records-and-reports bar. No evidence of audit-scoped evidence packs, auditor access roles, or a point-in-time reconstruction, so the gap to 8 is unsubstantiated rather than just unclosed. 4 2

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 IT Integrator

This is the CSV-drawbridge island I reject: the only confirmed machine interface is CSV/Word export of the RoPA, employee management is manual records rather than directory sync, and the sole integration gesture is an 'own ticketsystem einbindbar' option in the whitelabel tier. There is not one mention of a REST API, webhooks, SSO/SCIM, AD/Entra import or any connector to the estate — the internal task workflow and delegation is the only automation on the evidence. 4 2 3

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 IT Integrator

A German GmbH at a German court, product hosting in a German datacenter with an own-server option, and a DPA with IONOS (Montabaur) are solid European facts. But the disclosure is website-shaped, not platform-shaped: no published DPA or TOMs for audatis MANAGER itself, no product subprocessor list, ownership unknown, and Elastic APM with a San Francisco address sits in the disclosed chain. 5 3 6

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 IT Integrator

Every edition and every add-on — Standard, Group, Whitelabel, extra users, storage, ISMS, the employee-tier flatrates — reads 'Auf Anfrage', with only billing-by-invoice and a 30-day trial public. That is rubric level 0 verbatim: not a single number from which any invoice could be computed. 3

Report an error

European sovereignty — proven facts

1 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.

Sources (6)

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

  1. 1 Vendor homepage www.audatis-manager.de Checked 16 Sep 2026 Details →
  2. 2 Features page www.audatis-manager.de Checked 16 Sep 2026 +1 earlier capture: 24 Aug 2026 Details →
  3. 3 Vendor pricing page www.audatis-manager.de Checked 16 Sep 2026 +5 earlier captures: 24 Aug 2026, 24 Aug 2026, 24 Aug 2026, 23 Aug 2026, 23 Aug 2026 Details →
  4. 4 RoPA feature page www.audatis-manager.de Checked 16 Sep 2026 +5 earlier captures: 31 Aug 2026, 24 Aug 2026, 24 Aug 2026, 23 Aug 2026, 23 Aug 2026 Details →
  5. 5 Imprint www.audatis-manager.de Checked 16 Sep 2026 Details →
  6. 6 Privacy policy www.audatis-manager.de Checked 16 Sep 2026 +1 earlier capture: 31 Aug 2026 Details →