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 panel's verdict

The i-doit GRC Suite runs its INPRIVE data protection module on a shared data basis with ISMS, emergency planning and BCM. It scores strongest on integrations and automation at 7–8 — a JSON RPC API reading and writing all data under on-screen permissions, with connectors across directories, ticketing, discovery and imports — and on audit readiness at a flat 7, with revision-safe versioned documents and automatic audit reports and PDFs. Weakest are pricing transparency at a flat 3 — only 'ab 599€/ Jahr' for INPRIVE is public — and rights and incidents at a flat 4, where data subject rights appear as a single function line. The judges genuinely split on privacy management, from 4 to 7: the external DPO credits multi-client capability and industry templates for a thirty-mandate practice; the skeptic found no public information on processors, data processing agreements or measures tied to activities. Sovereignty and framework coverage sit at 3–4: a German contracting entity and on-premises option, but no public information on hosting location, a data processing agreement or subprocessors, and GDPR the only privacy regime named on the captured pages.

Report an error

Speaks for it

  • JSON RPC API reads and writes all data with the on-screen permission model enforced and custom categories exposed
  • Named connectors span Active Directory, LDAP, Zammad, OTRS, KIX, JDisc, OCS, Nagios, Checkmk and importers including ServiceNow and Matrix42
  • Revision-safe, versioned documents with automatic audit reports and audit PDFs by location, user or cost centre
  • Record of processing activities built on industry-specific templates with Excel/CSV import, a DPIA module and multi-client capability on a data basis shared with ISMS
  • Incidents documented GDPR-conform with affected processing operations assigned, risks assessed and deadline monitoring with automatic notifications

Report an error

Held against it

  • Only one public figure exists — INPRIVE 'ab 599€/ Jahr' — with no public information on module, edition or add-on prices, user or entity boundaries, or setup fees
  • Data subject rights management appears as a single line in the function list with no workflow, deadline or identity-verification detail shown
  • We found no public information on cloud hosting location, a data processing agreement or a subprocessor list
  • We found no public information on privacy regimes beyond GDPR — BDSG, Swiss nDSG, UK GDPR or AI Act duties — on the captured pages
  • We found no public information on single sign-on with SCIM provisioning or webhooks

Report an error

Best for

  • You already run i-doit for IT documentation or an ISMS and want the GDPR record on the same shared data basis
  • You carry GDPR alongside security regimes such as ISO 27001, NIS-2, KRITIS or TISAX and want one platform for both
  • You are a multi-client DPO or consultancy managing many mandates with industry templates and multi-client capability
  • You must keep the compliance record on your own infrastructure — on-premises deployment is offered alongside a cloud variant

Report an error

Avoid if

  • You need a data subject rights workflow with intake, deadlines and identity verification — the pages show the function only as a single line
  • You must budget without a sales conversation — only one figure is public, 'ab 599€/ Jahr' for INPRIVE
  • Your privacy scope covers national regimes beyond GDPR such as BDSG, Swiss nDSG or UK GDPR

Report an error

The scores

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

Records & DPIA depth

panel disagrees Show reasoning
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

The In-House Counsel

The core artefacts are documented: the record of processing activities on industry templates, data protection impact assessments, risk analysis and treatment, measures linked to target objects with owners and deadlines, multi-client capability, and the register generated per click on a data basis shared with the ISMS and emergency modules. What the captured pages do not show is processors with their data processing agreements recorded as such, technical and organisational measures assigned specifically to processing activities, or the impact-assessment need derived from the record — so I cannot place it at the fully connected-model level. 2 2 8 7

Report an error

The Drafted Generalist

The processing register comes with industry-specific templates, an Excel/CSV import for what we already have, and a DPIA module, and the register can be generated as a report at a click — that's more than a checklist. Risks and measures are tracked and multi-client capability is listed, but I found no public information on legal bases modelled per activity or processor contracts in the GDPR sense, so it sits between a plain module set and a fully connected model. 2 2 7 8 2

Report an error

The Lead Auditor

The data protection module records processing activities on branch-specific templates, runs DPIAs and risk treatment, generates the register of processing activities at a click, and sits on a shared data basis with the ISMS and emergency modules, with multi-client capability listed. I found no public information on processor records with their data processing agreements, legal bases linked to activities, or DPIA need derived from the record, so the connection between the legal artefacts is asserted at the platform level rather than demonstrated. 2 2 8

Report an error

The IT Integrator

The record of processing activities is structured and real — industry-specific templates, a DPIA module, risk analysis and treatment, automatic register reports at a click, multi-client capability — and it sits on a shared data basis with the ISMS and emergency planning, with protection needs and measures derived from imported assets, which is exactly the wiring I want. I found no public information on a processor register with data processing agreements or on technical and organisational measures assigned to processing activities, so the connected record is proven only in part. 2 2 8

Report an error

The Skeptic

The record of processing activities comes with industry-specific templates, a named DPIA function, automatic generation of the processing register at a click, and multi-client capability on a data basis shared with the ISMS modules — real structure, not document templates alone. But the function list stops at naming the DPIA, and no captured page shows processors with their data processing agreements or technical and organisational measures assigned to processing activities; the three-day implementation promise is marketing that outruns the documented depth. 2 2 7 2

Report an error

Data subject rights & incidents

Show reasoning
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

The In-House Counsel

Breach handling is substantiated: incidents documented GDPR-conform, assigned to the affected processing operations, risks assessed and measures derived centrally, with deadline monitoring and automatic notifications. Data subject rights management appears only as a single capability line, and nowhere do the captured pages show the 72-hour clock, an authority notification, the one-month request deadline or identity verification — for a breach workflow I must defend, that depth is unproven. 2 6 3 8

Report an error

The Drafted Generalist

Incident handling is described in real detail: incidents documented GDPR-conform, assigned to the affected processing operations, risks assessed and measures derived centrally. Data subject rights appear only as a feature name and deadline monitoring is described generically; I found no public information on the one-month reply clock, the 72-hour authority notification, or deletion periods per activity. 2 6 3 8

Report an error

The Lead Auditor

The breach side is real: incidents are documented GDPR-conform, affected processing operations assigned, risks assessed, tasks derived and tracked, with deadline monitoring and automatic notifications. Data subject rights management appears as a single line in the function overview, and I found no public information on intake or identity verification, the one-month deadline, the 72-hour notification, or deletion periods. 2 6 3

Report an error

The IT Integrator

The breach half is solidly built: incidents documented centrally and GDPR-conform, affected processing operations assigned, risks assessed, measures derived, deadlines monitored with automatic notifications. Data subject rights appear only as a named function without workflow detail, and I found no public information on the one-month deadline clock, the 72-hour notification, an intake portal with identity verification, or deletion execution. 2 6 3

Report an error

The Skeptic

The incident half is documented in some depth: incidents are recorded GDPR-conform, affected processing operations are assigned, risks assessed and measures derived centrally. Data subject rights management, by contrast, exists as a single line in a function list with no workflow, deadline or identity-verification detail behind it, and we found no public information on a 72-hour breach clock, the one-month response deadline, or deletion concepts. 6 3 2 8

Report an error

Privacy regime coverage

Show reasoning
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

The In-House Counsel

GDPR is implemented with its own registers, industry templates and documentation duties, and the pages name a long list of security regimes (ISO 27001, BSI IT-Grundschutz, NIS-2, KRITIS, TISAX, DORA) on the same platform. Beyond GDPR itself no national privacy law — BDSG, Swiss nDSG, UK GDPR — and no AI Act or ePrivacy duty is named; there is only a general claim of EU-wide compliant documentation, which is one privacy regime, maintained as far as the pages show. 2 5 3 1

Report an error

The Drafted Generalist

GDPR is implemented properly with its own registers, templates and evidence duties in the dedicated privacy module, and the wider suite handles ISO 27001, BSI IT-Grundschutz, NIS-2 and TISAX on a shared data basis. Beyond a claim of EU-wide legally compliant documentation I found no public information on national privacy law variants such as BDSG, Swiss nDSG or UK GDPR, or on AI Act duties. 1 1 2 8

Report an error

The Lead Auditor

GDPR is implemented as a product with its registers, templates, DPIAs and evidence duties, and the suite runs it on one shared data basis alongside ISO 27001, BSI IT-Grundschutz and NIS-2. No national privacy law — BDSG, nDSG or UK GDPR — is named in the captured pages, and I found no public information on ePrivacy/TTDSG or AI Act duties, so the multi-regime breadth is on the security side. 2 1 1

Report an error

The IT Integrator

GDPR is implemented in depth — records, templates, DPIA, rights, incident duties, "EU-weit rechtskonforme Dokumentation" — and it runs on one shared data basis alongside ISO 27001, NIS-2, KRITIS, TISAX and BSI IT-Grundschutz content. But for privacy regimes specifically only the GDPR appears: I found no public information on national variants (BDSG, Swiss nDSG, UK GDPR) or on ePrivacy and AI Act duties, and no update cadence is documented. 2 1 3 5

Report an error

The Skeptic

GDPR with its registers and templates sits on one shared data basis alongside ISO 27001, BSI IT-Grundschutz, NIS-2, TISAX, KRITIS and DORA, which is more regime plumbing than a single-island tool. But the privacy regimes themselves stop at GDPR: no BDSG, Swiss nDSG, UK GDPR, TTDSG or AI Act duty appears on any captured page, no legal-update cadence is published, and the "EU-wide legally compliant documentation" slogan carries no per-country content behind it. 1 3 1 2

Report an error

Audit readiness & evidence

Show reasoning
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

The In-House Counsel

Documentation is versioned revision-safe with changes and statuses traceable and usable as audit evidence; audits are planned, executed and reported centrally with automatic, standardised audit reports and audit PDFs by location, user or cost centre, and exports are prepared for auditors, management or specialist departments. Read-only auditor access and reproduction of a record as it stood on a given date are not documented — I would want both before relying on it in an authority audit. 9 10 8 7 1

Report an error

The Drafted Generalist

This is where it feels solid for someone like me: revision-safe document versioning, changes documented in a way that holds up in audits, audit reports generated automatically as PDF, and a guided path through the audit from document review to implementation review. Reports export out for auditors and management and GDPR evidence tracking is an explicit function. I found no public information on read-only auditor access or reproducing a record as it stood on a given date. 9 10 2 8 2

Report an error

The Lead Auditor

Documents are managed revision-safe with versioning, changes are documented in an audit-capable manner, audit reports and audit PDFs generate automatically by location, user or cost centre, and a Report Manager with custom filters exports reports for auditors, management or specialist departments. I found no public information on read-only auditor access, point-in-time reproduction of a record, or evidence packs as a distinct artefact, which is what I would want before calling the documentation standing audit-ready. 2 8 9

Report an error

The IT Integrator

Audit proof is engineered in: changes are versioned and documented audit-capably, documents are managed revision-safe with templates, audit PDFs and reports are generated automatically and exported for auditors, management or specialist departments, and a full audit management module covers planning, scheduling, implementation checks with task and role assignment. I found no public information on read-only auditor access or on reproducing a record as it stood on a given date. 9 8 10 2

Report an error

The Skeptic

Audit management is a whole use case here: planning, scheduling and implementation checks run in the tool, audit reports generate automatically, changes are versioned and documented in audit-capable form, and reports export for auditors, management and departments. What no captured page shows is read-only auditor access or reproducing a record as it stood on a given date — the final mile of proof rests on the vendor's own "audit-proof" wording. 10 9 2 8

Report an error

Integrations & automation

Show reasoning
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

The In-House Counsel

A documented JSON-RPC API reads and writes all data including custom categories under the role model, with regular, event-based or manually triggered synchronisation; directory services (LDAP, Active Directory), ticketing (Zammad, KIX, OTRS), inventory (JDisc, OCS) and imports from Excel, ServiceNow, Matrix42 and others, plus no-code scheduled Flows, CMDB-event automation and AI add-ons. Single sign-on with SCIM provisioning and named webhooks are not documented, which is what holds it below the top level. 11 12 1 1 3 10

Report an error

The Drafted Generalist

The real IT estate feeds in: Active Directory and LDAP for people and rights, JDisc and OCS discovery, ticketing like Zammad, monitoring like Nagios or Checkmk, plus importers for Excel, ServiceNow and more. A documented JSON-RPC interface reads and writes all data with permissions respected, synchronisation runs on schedule or on events, and the Flows and Events add-ons automate without programming — AI add-ons are advertised too. I found no public information on single sign-on with automatic user provisioning. 11 12 1 1 10

Report an error

The Lead Auditor

The platform feeds from a real estate: a JSON RPC API reading, writing and updating all data with permissions enforced, custom categories exposed and event-based, scheduled or manual transfer; LDAP and Active Directory import; named connectors for ticketing (Zammad, OTRS, KIX), discovery (JDisc, OCS), monitoring (Nagios, Checkmk) and importers from Excel to ServiceNow; plus no-code Flows automation, events and AI add-ons. The documented interface is JSON RPC rather than REST, and I found no public information on single sign-on with provisioning or webhooks, so I stop short of infrastructure-grade. 11 12 1

Report an error

The IT Integrator

This is the anti-island: a documented JSON RPC API that reads and writes all data in real time, respects permissions, exposes custom categories, and syncs with third-party systems on a regular or event-based basis; Active Directory and LDAP for users and rights including personnel import; ticketing connectors (Zammad, KIX, OTRS, n8n, ServiceNow and Matrix42 importers); discovery via JDisc and OCS; plus Events, Flows and AI add-ons for automation. What keeps it off the top bench for me is that I found no public information on single sign-on with SCIM provisioning or on webhooks as such, though event-based forwarding is documented. 11 12 2 3 1

Report an error

The Skeptic

This is the strongest suit: a JSON RPC interface that reads and writes all data under the on-screen permission model, event- or time-triggered synchronisation, and named connectors across directories (Active Directory, LDAP), ticketing (Zammad, OTRS, KIX), discovery (JDisc, OCS) and importers (ServiceNow, Matrix42, GLPI), plus a no-code Flows add-on. We found no public information on single sign-on with SCIM provisioning or webhooks, and the AI add-ons are pure slogan — an "AI Bundle" promising 10x time savings with no named function behind it; the captured pages also give different figures for the add-on count, over 40 on one and over 50 on another. 11 12 1 1 4 1

Report an error

European sovereignty panel opinion

Show reasoning
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

The In-House Counsel

The contracting entity is proven German — i-doit GmbH, register court Düsseldorf, German VAT ID — with European majority ownership (Main Capital Partners, Netherlands) since 2022 and an on-premises deployment option marketed alongside a cloud variant. Hosting location, a subprocessor list and a data processing agreement are not stated on the captured pages; until that chain is documented, where my compliance record would actually live remains unknown. 5 1 11

Report an error

The Drafted Generalist

The contracting side is proven: i-doit GmbH registered in Düsseldorf with a German VAT ID, and on-premises operation is offered alongside a cloud option, which matters when the compliance record itself is sensitive. I found no public information on where cloud hosting runs, on a data processing agreement, or on subprocessors, so the residency question stays open. 5 1 11 5

Report an error

The Lead Auditor

The contracting entity is proven German — i-doit GmbH, register court Düsseldorf, VAT prefix DE — the group is majority-held by a Dutch investor, and on-premises deployment is offered alongside cloud. Beyond that I found no public information on hosting location, subprocessors, or a data processing agreement, so the chain above the entity is unproven rather than clean. 12 5 11

Report an error

The IT Integrator

A German contracting entity is proven — register court Düsseldorf with a German VAT ID, founded in Düsseldorf in 1996, majority-owned by the Dutch investor Main Capital Partners — and an on-premises deployment option is advertised alongside a cloud variant. I found no public information on the hosting location of the cloud offering, a data processing agreement, or a subprocessor list, so the chain beyond the entity itself is unproven. 5 1 4

Report an error

The Skeptic

The contracting entity is German to the letter — Düsseldorf register court, German VAT ID — and on-premises deployment is offered alongside a cloud variant, which lets a buyer keep the compliance record on its own infrastructure. Beyond that the trail goes cold: we found no public information on where the cloud variant is hosted, on subprocessors, or on a data processing agreement, and the self-hosting claim appears in homepage marketing copy without deployment details. 5 12 1 11 1

Report an error

Pricing transparency

Show reasoning
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

The In-House Counsel

One public from-price exists for the data protection module — "ab 599€/ Jahr" — plus a free 30-day trial and the API add-on at no charge. The other editions and modules carry no public prices, and no user counts, entity boundaries, setup fees or VAT treatment are given, so the real invoice is not computable from public pages alone — the market norm, but worth stating. 2 11 6

Report an error

The Drafted Generalist

One public figure exists — INPRIVE from 599€ per year as stated on the product page — plus a free 30-day trial and the API add-on listed as free. The other editions such as the GRC Suite and the individual Suite+ modules carry no public prices, so the full invoice for a company our size remains a sales conversation. 2 6 11

Report an error

The Lead Auditor

One public figure exists — INPRIVE "ab 599€/ Jahr" — alongside a free API add-on, a 30-day trial without payment details, and a Smart Bundle of "4 add-ons for the price of 2". Module and edition prices, user or entity boundaries, setup fees and VAT treatment are not public in the captured pages, so the invoice is not computable before a sales conversation. 2 11 6

Report an error

The IT Integrator

One public from-price exists — "I-DOIT INPRIVE ab 599€/ Jahr" — plus a free API add-on, a "4 add-ons for the price of 2" bundle claim without absolute figures, and a 30-day trial. The Suite+ modules and the GRC Suite, user or entity boundaries, setup fees and VAT treatment are not public, so the real invoice remains a sales conversation. 2 11 6

Report an error

The Skeptic

One public "from" price exists — INPRIVE "ab 599€/ Jahr" — alongside a free 30-day trial and a free API add-on, with licence terms published as general terms for rental and purchase licences; the add-on bundle is priced only relatively ("4 add-ons for the price of 2"). We found no public information on GRC Suite and Suite+ edition prices, add-on prices, user or entity boundaries, or setup fees, so computing the real invoice remains a sales conversation. 2 11 5 6

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 →