whats-best.ai
Search Sign in

Data Protection

i-doit GRC Suite (INPRIVE / INDITOR)

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 i-doit GmbH · www.i-doit.com

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 In-House Counsel

Weighted verdict

Answers personally when the authority writes. Optimizes for defensibility: request clocks that never slip, a breach workflow that produces the Art. 33 notification, regime coverage that matches where the company actually operates. Rejects tools whose legal content nobody maintains.

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

Scored by The In-House Counsel

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 In-House Counsel

INPRIVE names a record of processing activities, a data protection impact assessment and GDPR evidence tracking, and the shared data basis with ISMS and the CMDB is real — incidents get assigned to affected processing operations, measures link to target objects, and industry templates plus multi-client capability are stated. But we found no public information on legal-basis or TOM modeling or on DPIA triggers derived from the record, and without those connections I cannot treat the artifacts as one connected register at audit weight. 2 2 6 7

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 In-House Counsel

Data protection incidents are documented GDPR-compliantly with risk assessment, assignment to processing operations and centrally derived measures, and data subject rights management is named as a capability alongside generic deadline monitoring and automatic notifications. We found no public information on a 72-hour clock, an authority notification output under Art. 33, structured request intake with identity checks, or deletion concepts with execution tracking — the clock and the notification are what I must produce in a breach, so this sits below my defensibility bar. 2 3 6 8

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 In-House Counsel

Coverage is shaped to the German market — GDPR alongside BSI IT-Grundschutz, B3S, KRITIS, NIS-2 and TISAX — on one shared data basis, with a claim of EU-wide legally compliant documentation. We found no public information on Swiss nDSG, UK GDPR, ePrivacy or AI Act privacy duties, and no documented update cadence when the law moves, so for operations beyond the DACH footprint I would want confirmation before relying on the content. 2 1 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 In-House Counsel

Revision-safe document management with versioning, changes documented in an audit-capable manner, guided audit programs with document assignment, task and role assignment, and standardized automatic audit reports — including automatic register reports such as the VVT — give me an auditor file without weeks of assembly. We found no public information on auditor access roles or a point-in-time reconstruction of the state on a given date, which is the answer I need standing ready in an inspection. 2 7 8 9 10

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 In-House Counsel

A documented JSON-RPC API through which external systems read, create and update data with permissions respected and access traceable, directory import from LDAP and Active Directory, named connectors for ticketing, monitoring and discovery (Zammad, Nagios, Checkmk, JDisc, OCS), and event-based triggers plus no-code Flows make the recurring work automatable rather than re-typed. We found no public information on SCIM or webhooks specifically, or on human review of the AI assistance, so it holds at this level rather than higher. 1 10 11 12

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 In-House Counsel

The imprint shows i-doit GmbH with the Düsseldorf register court, register number 33104 and a German VAT identification, and the product runs on-premises or in cloud, so the register of processing can stay in-house. We found no public information on a published data processing agreement, a subprocessor list, or named data centers for the cloud variant — for the platform that maps my processing, I need that chain documented publicly before sign-off. 5 1 11

Report an error

Pricing transparency

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 In-House Counsel

One real number is public — INPRIVE "ab 599€/ Jahr" — alongside a free API add-on, a 30-day trial with no payment details, and an add-on bundle quoted only as "4 powerful add-ons for the price of 2". We found no public prices for the ISMS, BCM or emergency editions, nor for user and entity boundaries or setup fees, so the invoice for anything beyond the entry product is not computable from public pages. 2 6 11

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 — uncited Report an error
Subprocessors Not determined — 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 i-doit GRC Suite (INPRIVE / INDITOR)? Tell us Report an error on this page

Sources (12)

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

  1. 1 Vendor homepage www.i-doit.com Checked 5 Oct 2026 +2 earlier captures: 16 Sep 2026, 11 Sep 2026 Details →
  2. 2 INPRIVE data protection product page www.i-doit.com Checked 5 Oct 2026 +2 earlier captures: 15 Sep 2026, 31 Aug 2026 Details →
  3. 3 GRC suite overview www.i-doit.com Checked 5 Oct 2026 +3 earlier captures: 28 Sep 2026, 15 Sep 2026, 31 Aug 2026 Details →
  4. 4 Company page www.i-doit.com Checked 5 Oct 2026 +1 earlier capture: 31 Aug 2026 Details →
  5. 5 Imprint www.i-doit.com Checked 5 Oct 2026 +3 earlier captures: 28 Sep 2026, 16 Sep 2026, 31 Aug 2026 Details →
  6. 6 Data subject rights & incidents — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →
  7. 7 Privacy regime coverage — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →
  8. 8 Privacy regime coverage — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →
  9. 9 Audit readiness & evidence — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →
  11. 11 Integrations & automation — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →
  12. 12 Integrations & automation — found from sitemap www.i-doit.com Checked 5 Oct 2026 Details →