i-doit GRC Suite (INPRIVE / INDITOR)

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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? →

Link to this page

i-doit GRC Suite (INPRIVE / INDITOR): AI-assisted analysis on whats-best.ai i-doit GRC Suite (INPRIVE / INDITOR): AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

i-doit GRC Suite (INPRIVE / INDITOR) at a glance

Vendor
i-doit GmbH
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 16 Nov 2026
Panel verdict
The AI panel rates i-doit GRC Suite (INPRIVE / INDITOR) 2.5/5, the mean of 6 judges. The i-doit GRC Suite runs its INPRIVE data protection module on a shared data basis with ISMS, emergency planning and BCM. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

i-doit GRC Suite (INPRIVE / INDITOR) alternatives, European ones first →

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

The External DPO

Weighted verdict

Carries thirty client mandates and bills by the hour they save. Optimizes for multi-client capability, reusable templates, a RoPA that drives the rest, and client-ready reports. Rejects single-tenant tools that treat the consultancy as thirty separate customers.

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

Scored by The External DPO

Panel median The External DPO This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The External DPO
Records & DPIA depth 3 of 5 3.5 of 5
Data subject rights & incidents 2 of 5 2 of 5
Privacy regime coverage 2 of 5 2 of 5
Audit readiness & evidence 3.5 of 5 3.5 of 5
Integrations & automation 4 of 5 4 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 1.5 of 5 1.5 of 5

Records & DPIA depth

How this is scored

The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.

0 — Not a privacy management tool; at most a set of document templates with no structured records.

3 — A structured record of processing activities with templates, and a DPIA questionnaire or checklist.

5 — Records of processing and DPIAs as modules with templates, processors and their DPAs recorded, and TOMs documented and assigned to processing activities.

8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA need derived from the record, reusable templates across companies, and outputs (Art. 30 register, DPIA report) ready for a supervisory authority.

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

Report an error

The External DPO

This is the right shape for a thirty-mandate practice: a record of processing activities built on industry-specific templates with Excel/CSV import, data protection impact assessments, explicit multi-client capability (Mandantenfähigkeit), and the record of processing activities generated as a report at a click on one shared data basis with ISMS and emergency planning. Protection needs, risk assessment and ISO 27001 measures assigned from imported assets point to a connected model rather than isolated forms. I hold it below the top because we found no public information on processors with their data processing agreements modelled against processing activities, on legal bases, or on the DPIA need being derived from the record itself. 2 2 8

Report an error

Data subject rights & incidents

How this is scored

The operational half of the DSMS: handling data subject requests within the Art. 12 deadline, a breach register with the 72-hour notification of Art. 33, and deletion concepts that are carried out.

0 — No handling of data subject requests or data breaches in the product.

3 — A log of data subject requests and a register of data breaches, with templates for the responses.

5 — Request workflows with the one-month Art. 12 deadline tracked and reminders, a breach register with the 72-hour clock and a risk assessment per breach, and deletion periods recorded per processing activity.

8 — An intake form or portal for requests with identity verification, deadline escalation, breach severity assessment producing the authority notification, and deletion rules tied to the RoPA with execution tracked.

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

Report an error

The External DPO

The incident side is real work product: data protection incidents documented GDPR-conform with affected processing operations assigned, risks assessed per incident, measures derived centrally, plus deadline monitoring and automatic notifications — a usable breach register, not a log. The rights side is a single line item (management of data subject rights) with no workflow detail, and we found no public information on a 72-hour clock, authority notification output, identity-verified intake, or deletion periods tied to the record of processing. 6 2 3 8

Report an error

Privacy regime coverage

How this is scored

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

0 — No privacy regime built in; a generic task or document tool.

3 — GDPR implemented with its registers, templates and checklists.

5 — GDPR plus the national law of its market (BDSG, nDSG or UK GDPR) named and supported with their own templates or requirements.

8 — Several regimes on one record with requirements mapped across them, newer duties (AI Act, ePrivacy/TTDSG) covered as maintained content, and updates published when a regime changes.

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

Report an error

The External DPO

GDPR is deeply operationalised — registers, templates, DSFA, GDPR evidence tracking — and the GRC suite puts ISO 27001, NIS-2 and GDPR on one shared data basis, which is the multi-standard shape I want for clients carrying both privacy and security mandates. On privacy regimes specifically, though, only GDPR is named: we found no public information on BDSG, TTDSG/ePrivacy, Swiss nDSG, UK GDPR or AI Act privacy duties as supported content, so the one-record-maps-everywhere story holds for security standards, not for privacy law variants. 2 1 7 2

Report an error

Audit readiness & evidence

How this is scored

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

0 — No reports, history or evidence; the product only stores the current state.

3 — PDF or Word reports of the registers, and documents attachable to records.

5 — Versioned records or a change history, report generators for the core registers (RoPA, DPIA, TOMs), and evidence attached per processing activity or measure.

8 — A revision-safe change history, audit evidence packs generated on demand, management and data protection officer reports at a click, and read-only auditor access.

10 — Audit readiness as a standing state: documentation status shown continuously per regime and scope, proof packs an auditor accepts as they are, and any record reproducible as it stood on a given date.

Report an error

The External DPO

This is where they earn their fee: revision-safe document management with versioning, changes documented in audit-capable form and usable as audit evidence, GDPR evidence tracking, guided audit programmes from document review to implementation review, automatic standardized audit reports, and audit PDFs by location, user or cost centre made available centrally for auditors, management or departments. Documentation-gap detection plus customizable dashboards give a standing view of client status. We found no public information on read-only auditor access or on reproducing any record exactly as it stood on a given date, which is why I stop short of the top band. 2 8 9 10 1

Report an error

Integrations & automation

How this is scored

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

0 — No import, export or integration; data is typed in and printed out.

3 — CSV or Excel import and export, and reminders for recurring reviews.

5 — Single sign-on, a documented API or a few named connectors (directory, ticketing), and recurring tasks with reminders and assignment.

8 — A documented REST API for the core objects, a named connector set (directory, ticketing, HR or asset sources), webhooks, SSO with SCIM provisioning, workflow automation with delegation and escalation, and AI assistance with human review.

10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, two-way sync with the estate, and recurring work (reviews, attestations, evidence collection) automated and documented.

Report an error

The External DPO

The estate feeds the tool, which is exactly what keeps thirty clients' records from rotting: a JSON-RPC programming interface through which all data can be read and written with permissions respected, automatic read/create/update from external systems, Active Directory and LDAP for users and rights, discovery via JDisc and OCS, ticketing via Zammad, OTRS and KIX, imports from ServiceNow, Matrix42, vmware and Excel, monitoring from Nagios and Checkmk, plus event-triggered and scheduled no-code automations and AI add-ons. The captured pages give different figures for the add-on catalogue size, but either number represents a substantial ecosystem. We found no public information on single sign-on with SCIM provisioning or on AI assistance with mandatory human review. 11 12 1 1 6

Report an error

European sovereignty

How this is scored

Where the compliance record of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. A platform that maps your processing is itself your most concentrated processing. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.

0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or EU hosting is offered only on request or on top tiers.

5 — EU hosting stated as the default, a data processing agreement and a subprocessor list published; a parent company or a subprocessor may sit outside the EU.

8 — EU entity, EU hosting in named data centres, a subprocessor list with no non-EU processor touching customer content, and the DPA and TOMs published.

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

Report an error

The External DPO

The contracting side is clean and proven: i-doit GmbH registered at the Düsseldorf court with a German VAT ID and a Düsseldorf address, and an on-premises option alongside cloud, so a client's compliance record can stay inside its own four walls — which for a consultancy is often the whole ballgame. The rest of the chain is unstated: we found no public information on hosting location, on a data processing agreement, or on the subprocessor list behind the cloud variant. 5 12 11 1

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 — A public "from" price or one priced edition; the other editions, modules or entity counts are not public.

5 — Public prices per edition or tier with the billing period (monthly or annual) stated and the main inclusions listed.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated, software separated from consulting, and VAT treatment given; 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 External DPO

One public starting figure exists for the data protection module — quoted as "ab 599€/ Jahr" — alongside a free 30-day trial with no payment details and full functionality, a free API add-on, and licence terms for rental and purchase licences published without prices. Everything a multi-client practice needs to compute a real invoice — the Suite+ module prices, tenant and entity boundaries, setup fees, VAT treatment — we found no public information on, so budgeting thirty mandates still begins with a sales conversation. 2 11 6 5

Report an error

European sovereignty — proven facts

2 of 6 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.

Hosting location Not determined — uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

The self-hosting claim appears only in homepage marketing copy without any deployment details.

1/1 pts 1 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about i-doit GRC Suite (INPRIVE / INDITOR)

Is i-doit GRC Suite (INPRIVE / INDITOR) European?

Yes. whats-best.ai classifies i-doit GRC Suite (INPRIVE / INDITOR) as EU-Made. Its vendor, i-doit GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does i-doit GRC Suite (INPRIVE / INDITOR) store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does i-doit GRC Suite (INPRIVE / INDITOR) have a free plan?

Yes. i-doit GRC Suite (INPRIVE / INDITOR) has a free plan, per the vendor’s page captured 16 Nov 2026.

What are the best alternatives to i-doit GRC Suite (INPRIVE / INDITOR)?

As of 19 Nov 2026, the panel rates preeco | datenschutz (3.5/5), caralegal (3.5/5) and Dastra (3.5/5) highest among the other 46 Data Protection products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | datenschutz (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: i-doit GRC Suite (INPRIVE / INDITOR) alternatives.

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 (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 16 Nov 2026 +6 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 5 Oct 2026, 16 Sep 2026, 11 Sep 2026 Details →
  2. 2 INPRIVE data protection product page www.i-doit.com Checked 16 Nov 2026 +3 earlier captures: 5 Oct 2026, 15 Sep 2026, 31 Aug 2026 Details →
  3. 3 GRC suite overview www.i-doit.com Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 28 Sep 2026, 15 Sep 2026, 31 Aug 2026 Details →
  4. 4 Company page www.i-doit.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 31 Aug 2026 Details →
  5. 5 Imprint www.i-doit.com Checked 16 Nov 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 16 Nov 2026 Details →
  7. 7 Privacy regime coverage — found from sitemap www.i-doit.com Checked 16 Nov 2026 Details →
  8. 8 Privacy regime coverage — found from sitemap www.i-doit.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  9. 9 Audit readiness & evidence — found from sitemap www.i-doit.com Checked 16 Nov 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap www.i-doit.com Checked 16 Nov 2026 Details →
  11. 11 Integrations & automation — found from sitemap www.i-doit.com Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
  12. 12 Integrations & automation — found from sitemap www.i-doit.com Checked 16 Nov 2026 Details →