DataGuard
EU-Made Report an errorPanel 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 DataCo GmbH · www.dataguard.de
Compare with OneTrust → Report an error on this page Is this your product? →
Link to this page
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.
DataGuard at a glance
- Vendor
- DataCo GmbH
- Headquarters
- Incorporated in Germany source, captured 19 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates DataGuard 3/5, the mean of 6 judges. DataGuard, a data protection platform from DataCo GmbH of Munich, draws weighted verdicts from 5.7 to 6.3. how scores are made
- As of
- Vendor pages captured 15 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
DataGuard, a data protection platform from DataCo GmbH of Munich, draws weighted verdicts from 5.7 to 6.3. Its best marks come on rights and incidents, where scores sit at 7 with no spread: requests run as workflows with a website intake form, automatic routing, deadline tracking and audit-capable records, and breaches get an automatic 72-hour countdown, escalation workflows and prepared reporting forms. Sovereignty is weakest at 2-3: the pages prove a German contracting entity and standard contractual clauses for third-country recipients, but judges found no public information on hosting location, a subprocessor list or a data processing agreement. Other criteria spread at most one point — privacy management 6-7, framework coverage 7-8, audit readiness 6-7, integrations and automation 6-7 — with higher scores crediting the connected central inventory and cross-framework evidence reuse, lower ones wanting legal bases wired into records, national variants beyond UK GDPR and revision-safe history; headline percentages — a 100% first-attempt audit pass, up to 100 hours saved — carry no shown basis. No price figures appear on the captured pages; pricing transparency is not counted in the verdicts.
Speaks for it
- Data subject requests run as operational workflows — a secure website intake form, automatic routing with notifications, deadline tracking, a task per request, and complete audit-capable records for authority inspections
- Breach handling includes an automatic 72-hour countdown, escalation workflows, an assessment of whether and to whom notification is due, and prepared reporting forms to the supervisory authority
- A central data inventory carries the full record of processing activities with updates propagating system-wide, alongside guided DPIAs including AI-system evaluation, vendor data processing agreement management, and TOMs documented and periodically reviewed
- DSGVO, UK GDPR and the EU AI Act ship as ready-made frameworks alongside ISO 27001, TISAX and NIS2, with evidence reused across frameworks and country-specific requirements tracked per company group
- Named connectors for Asana, Jira, Azure asset updates and CRM consent data synchronise continuously, project-management tools connect in under 15 minutes, and APIs with documentation are included from the Base plan
Held against it
- Sovereignty scores sit between 2 and 3, with no public information found on hosting location, a subprocessor list or a data processing agreement, and every pricing plan labelled SaaS
- The privacy policy relies on standard contractual clauses wherever recipients sit outside the EU or EEA, leaving third-country recipients possible and unnamed
- The captured pages do not show legal bases wired into the record of processing activities, measures assigned to processing activities, or DPIA need derived from the record
- Judges found no public information on revision-safe change history, read-only auditor access, or records reproducible as they stood on a given date
- The API evidence reads as navigation labels and a documentation link rather than a documented REST surface for core objects, with no public information on webhooks or SCIM provisioning
Best for
- You need operational data subject request and breach handling, with deadline tracking, automatic routing and records expressly kept for authority inspections
- Your team runs several regimes at once — DSGVO, UK GDPR, the EU AI Act, ISO 27001, TISAX, NIS2 — and wants evidence reused across frameworks
- You want a central processing register with guided DPIAs including AI-system evaluation and vendor agreements managed on one platform
- Your company group spans departments, locations or subsidiaries managed under role-based permissions in one platform
Avoid if
- Your procurement must see hosting location, a subprocessor list and a data processing agreement before signature; the judges scoring sovereignty 2-3 treat this silence as the first thing to resolve
- Your audits require standing proof — revision-safe change history, records reproducible as of a given date, read-only auditor access — the gaps that withheld the audit readiness top band
- You are an external data protection officer with many separate client mandates; the multi-entity support described covers departments, locations and subsidiaries, not separate clients
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 3.5 of 5 |
| Data subject rights & incidents | 3.5 of 5 |
| Privacy regime coverage | 3.5 of 5 |
| Audit readiness & evidence | 3 of 5 |
| Integrations & automation | 3 of 5 |
| European sovereignty | 1.5 of 5 |
Records & DPIA depth
Show reasoningHide 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.
The External DPO
The records model is genuinely connected: a central data inventory carrying the full register of processing activities whose updates propagate system-wide, guided DPIAs with a growing template set including AI-system evaluation, processor contracts managed on the platform, and TOMs such as access controls, encryption and backups documented and reviewed. What I cannot see is legal bases woven into that model, and the multi-entity support speaks of departments, locations and subsidiaries — intra-group, not thirty separate client mandates, which is the distinction that decides my tooling. 9 10 14
The In-House Counsel
The four artefacts I audit against are all modelled — the register of processing activities records data, purposes and the systems involved, processor contracts are managed on the platform, TOMs are documented with periodic review, and DPIAs run on guided templates including AI-system assessment — and the central inventory propagates updates across the whole system, which is more than isolated modules. The captured pages do not show the legal basis wired into the record or DPIA need derived from it, so I stop short of calling the data model fully connected. 9 10 14
The Drafted Generalist
This is what I actually need on my desk: a guided workflow for the processing register, a central inventory where updates carry through the whole system, DPIA templates that already cover AI-system checks, vendor processing agreements managed on the platform, and TOMs documented and reviewed. I found no public information on legal bases being wired into the record or a finished Article 30 register output for the authority, so it lands solidly above the basics but short of the fully connected data model. 9 10 14
The Lead Auditor
The record of processing activities is a guided module backed by a central inventory of data subjects, assets and business processes whose updates propagate system-wide, with systems named per activity and risk-relevant processing flagged on a dashboard. DPIAs run as guided assessments with a growing template set including AI system evaluation, technical and organisational measures are documented and periodically reviewed, and data processing agreements are managed alongside third-party risk. What the pages do not show is measures assigned to processing activities or legal bases held in the linked model, so I place this between the structured-module and connected-data-model levels. 3 9 10 14
The IT Integrator
The record of processing is a real central object: all data subject categories, assets, business processes and the full VVT sit in one inventory with updates propagating system-wide, and a risk dashboard flags high-risk processing activities. DPIAs run as guided, customisable templates including AI-system evaluations, processors' data processing agreements are managed on the platform, and TOMs are documented and periodically reviewed. What the captured pages do not show is TOMs, legal bases and processors linked onto each processing record as one connected model. 9 10 14
The Skeptic
The dedicated pages do show the four core artefacts: a central VVT covering data subject categories, assets, business processes and involved systems, guided DPIAs with a growing template set including AI-system evaluation, AVV management with vendors, and documented TOMs under review. Updates are said to propagate system-wide and requests link back to the inventory, which reaches toward a connected model. I found no public information on legal bases recorded per activity, DPIA need derived from the record, or multi-client use for external data protection officers, and I count the 'everything in one place' prose as claims rather than architecture. 14 10 9
Data subject rights & incidents
Show reasoningHide 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.
The External DPO
Rights handling looks operational rather than logged: a secure intake form for the client's own website, central request tracking with deadline monitoring, a task per request for gapless processing, and complete audit-capable records of request handling for authority inspection; on the breach side there is an automatic 72-hour countdown, escalation workflows, an assessment of whether and to whom notification is owed, and prepared reporting forms. I found no public information on identity verification at intake or on deletion rules tied to the register with tracked execution — the two things that separate a smooth operation from one an authority can walk through. 11 12 14
The In-House Counsel
The clocks I insist on are in the product: a 72-hour countdown with escalation workflows and prepared notification forms, an assessment of whether a report is required and to whom, notifications to supervisory authorities, and request workflows with the one-month deadline, reminders, a website intake form and audit-capable records expressly for authority inspections. Identity verification of the requester and deletion rules tied to the register with tracked execution are not documented on the pages I read, which caps this below the top band. 11 12 14
The Drafted Generalist
Requests look genuinely operational rather than a folder of templates: a form I can embed on our website, automatic routing with notifications, deadlines and responsible teams in one view, a task per request, and audit-capable records of every request for the authorities. Breaches get a 72-hour countdown, escalation workflows, prepared notification forms and a determination of whether and to whom a report is due; I found no public information on identity verification at intake or deletion execution tracked against the register. 11 12 14
The Lead Auditor
Requests run as workflows with a secure intake form for the company website, automatic routing and notifications, a task per request, deadline and ownership tracking, and complete audit-capable records of request handling for authority review; breaches carry an automatic 72-hour countdown, escalation workflows, a notification-decision step naming internal teams and supervisory authorities, and prepared reporting forms. I found no public information on deletion periods recorded per processing activity or on deletion execution being tracked, which is the missing piece of the operational picture. 11 12 14
The IT Integrator
Requests run as operations, not a log: a secure intake form for the company website, assignment to responsible teams, deadline tracking with reminders, a task per request, and complete audit-capable records for authority inspections linked to the data inventory. Breaches get an automatic 72-hour countdown, escalation workflows, prepared notification forms, and an assessment of whether and to whom notification must go. Deletion periods per processing activity with tracked execution is the gap — I found no public information on that. 11 12 13 14
The Skeptic
Request handling is documented in real depth: a website intake form, automatic routing with notifications, a task per request, deadline and responsible-team tracking, and records written explicitly for authority checks. Breach handling shows an automatic 72-hour countdown, escalation workflows, an assessment of whether and to whom notification is due, and prepared reporting forms to the supervisory authority. I found no public information on identity verification for requesters or on deletion rules tied to the record of processing with tracked execution. 12 11 14
Privacy regime coverage
Show reasoningHide 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.
The External DPO
GDPR, UK GDPR and the EU AI Act are named as ready-made frameworks, country-specific requirements are tracked per company group, and evidence is reusable across frameworks with overlapping requirements managed on one record — that is the cross-regime posture I want for a portfolio of clients. I found no public information on BDSG, nDSG or TTDSG/ePrivacy as maintained content, and the template updates are described only as regular, without a published cadence when the law moves. 9 11 15 16
The In-House Counsel
GDPR and UK GDPR ship as ready-made frameworks alongside the EU AI Act with maintained assessment templates, evidence is reused across frameworks so one record serves several regimes, country-specific requirements are tracked per company group, and template content is stated to be regularly updated — the maintenance question I always ask is at least addressed. The published list leans security-side (ISO 27001, TISAX, NIS2); BDSG, Swiss nDSG and ePrivacy/TTDSG are not named as supported frameworks on the pages I read. 9 11 16 18
The Drafted Generalist
GDPR, UK GDPR, the EU AI Act, ISO 27001, TISAX and NIS2 are supported on one basis — evidence is reused across frameworks, overlapping requirements are managed together, country-specific requirements can be tracked per company group, and template content is updated regularly. Only UK GDPR appears as a named national variant, and I found no public information on a published update cadence when a law moves, so it stops short of the living-regime product. 11 15 16 18
The Lead Auditor
DSGVO and UK GDPR appear as ready-made frameworks alongside the EU AI Act, with AI system evaluation templates, requirements tracked across frameworks and per company group down to country-specific variants, and evidence reused across frameworks rather than re-collected per regime. Template content is stated to be updated regularly, which approaches but does not document a published update cadence when the law moves. 9 11 15 16 18
The IT Integrator
DSGVO, UK GDPR and the EU AI Act ship as ready-made frameworks alongside ISO 27001, TISAX and NIS2, with overlapping requirements managed on one record, evidence reused across frameworks, cookie management as an operational module, and country-specific requirements tracked per company group. Template content is described as regularly updated. BDSG and the Swiss nDSG are not named in the captured pages. 9 11 15 16 18
The Skeptic
Beyond DSGVO the pages name UK GDPR and the EU AI Act as ready-made frameworks alongside ISO 27001, TISAX and NIS2, with evidence and requirements reused across frameworks and country-specific requirements tracked per company group. Template content is described as regularly updated. I found no public information on BDSG, TTDSG or the Swiss nDSG, and no documented update cadence published when a regime changes. 11 12 15 16 9
Audit readiness & evidence
Show reasoningHide 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.
The External DPO
Evidence collection is product-grade: uploads land in a controls app and are automatically assigned to matching controls, reusable across frameworks, and dashboards plus automated individually tailored reports in minutes give shareable audit-ready results for internal and external parties. What I found no public information on is revision-safe change history, read-only auditor access, or reproducing a record as it stood on a given date — for my money the difference between attractive reports and defensible proof. 10 15 16
The In-House Counsel
Evidence is captured and stored automatically, assigned to matching controls, reusable across frameworks with gaps flagged early, request handling keeps records expressly for authority inspections, and dashboards claim continuous audit readiness with reports generated in minutes. A revision-safe version history of records and read-only auditor access are not documented, so I cannot treat audit readiness as a standing state. 12 15 16 17
The Drafted Generalist
Measures and documentation are captured and stored automatically, evidence is assigned to the matching controls and reused across frameworks, tailored reports come out in minutes, and dashboards promise audit readiness at any time. I found no public information on revision-safe version history, read-only auditor access, or reproducing a record as it stood on a given date, so the standing proof state an auditor would walk through is not demonstrated. 10 12 15 16 17
The Lead Auditor
The captures show continuous audit posture — dashboards for the privacy programme with real-time status, instant gap identification, automated tailored reports generated in minutes and shared with internal and external teams, and evidence automatically assigned to matching controls with unassigned items flagged for linking. What decides my score is what I cannot see: no revision-safe change history, no evidence packs generated on demand, no read-only auditor access, and nothing that would reproduce a record as it stood on a given date — the audit trail here is assembled as you work, not kept as standing proof. 10 11 12 15 16
The IT Integrator
Audit-ready reports come with a few clicks and are shareable with internal and external teams, compliance measures and documentation are captured and stored automatically, evidence is auto-assigned to matching measures and reused across frameworks with gap detection, and request handling keeps full records for authority inspections. A revision-safe change history, on-demand evidence packs and read-only auditor access are not shown in the captured pages, which caps this below the top band. 10 12 15 16
The Skeptic
Compliance measures and documents are captured and stored automatically, uploads are auto-assigned to controls and reusable across frameworks with gap detection, and dashboards and tailored reports are generated in minutes with selective export. I found no public information on revision-safe change history, records reproducible as they stood on a given date, or read-only auditor access. The '100% first-attempt audit pass' and 'up to 100 hours saved' figures are headline percentages whose basis the captured pages do not show, and I score the artefacts, not the slogans. 17 16 15 12 4
Integrations & automation
Show reasoningHide 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.
The External DPO
There are named connectors — Azure for asset updates, CRM for consent data, Asana and Jira connectable in under fifteen minutes — with continuously synchronized data flows, single sign-on with granular roles, interfaces and APIs, and AI assistance including suggested answers for vendor security questionnaires. The API evidence reads as a menu heading rather than a documented REST surface for the core objects, and I found no public information on webhooks, SCIM provisioning, or directory and ticketing sources — the estate my clients actually run on. 7 14 17 18
The In-House Counsel
A documented API sits in the Base plan, single sign-on with granular roles is listed, Azure, CRM, Asana and Jira connectors keep data continuously synchronised, and the workflow engine assigns tasks, monitors deadlines and escalates breaches, with AI drafting questionnaire answers and risk analyses. I found no public information on webhooks, SCIM provisioning or directory import, and the API's object coverage beyond "interfaces exist" is not specified. 7 14 17 18
The Drafted Generalist
There is real plumbing here: documented APIs included from the Base plan, single sign-on with granular roles, named connectors for Azure asset updates, CRM consent data, Asana and Jira with continuous synchronisation, and automated workflows with deadline monitoring, reminders and escalation. I found no public information on webhooks, SCIM provisioning, or how much of the data model the API actually covers. 7 14 17 18
The Lead Auditor
Single sign-on with granular role management is listed, named connectors exist for Asana, Jira, Azure asset updates and CRM consent data with continuous synchronisation, and APIs and documentation are offered alongside interfaces that feed processing documentation. Workflow automation covers task assignment, deadline monitoring and reminders with escalation in the breach context, and AI assistance includes answer suggestions for vendor security questionnaires; I found no public information on webhooks or SCIM provisioning, so this sits between the connector-set and infrastructure levels. 7 14 17 18
The IT Integrator
This is the part I can actually feed from the estate: Jira and Asana project management tools connect in under 15 minutes, Azure automates asset updates, CRM integrations carry consent data, and data flows are continuously synchronised so compliance data stays current across integrated tools. APIs with documentation, SSO with granular role and rights management, automated workflows with assignment, deadline monitoring and escalation, and AI-assisted automation are all named publicly. I found no public information on webhooks, SCIM provisioning or user-directory import, which keeps this off the top band. 7 10 17 18
The Skeptic
Named connectors exist — Asana, Jira, Azure asset updates, CRM consent management — with setup in under fifteen minutes, continuous synchronisation, SSO with granular roles, CSV migration, and workflow automation with task assignment, deadline monitoring and reminders. APIs appear in navigation labels and a 'Documentation APIs' link, but I found no public information on a documented REST API for core objects, webhooks or SCIM provisioning. The automation claims ('40% of tasks', 'up to 75% of ISO documentation') are headline percentages whose calculation the captured pages do not show. 17 7 10 14 1 18
European sovereignty
panel opinion
Show reasoningHide 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.
The External DPO
The contracting entity is DataCo GmbH of Munich with commercial register and VAT details, a published privacy policy, and standard contractual clauses per Article 46 where recipients sit outside the EEA — but hosting location, a data processing agreement and any subprocessor list are not stated on the captured pages, and the offering is SaaS only. For the platform that would hold my clients' most concentrated processing, that silence is the first thing I would have to resolve before signing a mandate. 1 8 19 8
The In-House Counsel
The contracting entity is proven German — DataCo GmbH, Munich, with a Munich commercial register number — and a privacy policy is published, but that policy's own text relies on standard contractual clauses whenever recipients sit outside the EU, which tells me non-EU processors are possible and unnamed. Hosting location, a subprocessor list and a data processing agreement are not stated on the captured pages, every plan is labelled SaaS, and a UK company has been acquired into the group, so I cannot say where the compliance record would actually live. 1 7 8 5 19
The Drafted Generalist
The contracting entity is a Munich GmbH with a commercial register entry, and the privacy policy commits to standard contractual clauses where recipients sit outside the EU — but that is where the public trail ends. I found no public information on where the platform is hosted, which subprocessors touch customer content, or a data processing agreement for the product itself, and for a tool that would hold our entire compliance record that is the gap I would push on first. 6 8 19 8
The Lead Auditor
What is proven is a German contracting entity at a Munich address with a commercial register entry, a privacy policy stating deletion once the storage purpose is fulfilled, and standard contractual clauses per Art. 46 GDPR concluded where recipients sit outside the EU. I found no public information on hosting location, on a published subprocessor list, or on a customer data processing agreement, and the SCC clause itself acknowledges third-country recipients — for a platform that concentrates a company's entire processing map, that is thin documentation of the chain. 8 19 8
The IT Integrator
The contracting entity is proven as a German GmbH — Munich address, commercial register number and VAT ID — named as controller in the privacy policy, with standard contractual clauses per Art. 46 for third-country recipients. Hosting location, a data processing agreement and a subprocessor list are not stated in the captured pages, so most of the sovereignty chain remains undocumented rather than proven. 8 19 8
The Skeptic
A German GmbH in Munich is named as controller in the imprint and privacy policy, and the policy promises standard contractual clauses for recipients outside the EEA. Hosting location, a subprocessor list and a data processing agreement are not stated on the captured pages, and the imprint discloses no group structure behind a VC-backed company with US and UK investors and a UK acquisition. A trust centre is linked but its contents were not captured. 6 19 8 8 5
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide 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.
The External DPO
The captured pricing page names a Base and a Pro plan with their inclusions — onboarding support, tech support, expert help, data migration, plus external DPO and CISO add-ons — but no figures, and the software page states costs depend on company size, functionality and number of users, so every configuration is a sales conversation. For a thirty-client practice there is nothing here to compute an invoice from, and software is not separated from the consulting services in any published price. 4 7 14
The In-House Counsel
The plans are named with their inclusions — Base, Pro, and add-ons for whistleblowing and an external data protection officer — but no monetary figure appears anywhere I read; the captured text says costs depend on company size, functionality and number of users, and the only number published is a claim of being up to 50% cheaper than external consultants. The real invoice is therefore a sales conversation, which I note as the market norm rather than condemn. 4 7 13 14
The Drafted Generalist
Plan names and inclusions are public — Base with onboarding, tech support, integrations and APIs and single sign-on; Pro adding experts, programme build-up, data migration and an external security officer; plus bookable external DPO and whistleblowing add-ons — but no price figure appears anywhere: the captured pages state that costs depend on company size, functionality and number of users, and the only number published is "Bis zu 50 % günstiger als externe Berater". I could not get anywhere near computing our real invoice from public pages. 4 7 14
The Lead Auditor
The captured pages give no concrete prices at all; the stated model is a SaaS subscription whose costs depend on company size, functionality and number of users, so every real invoice is a sales conversation. Plan structure is visible — the Base plan lists onboarding, tech support, integrations and APIs, the Pro plan adds expert support, ISMS build-out, data migration and an external security officer, with external DPO and whistleblowing as add-ons — and marketing claims up to 50 % cheaper than external consultants, but no figure a buyer could compute from. 4 7 14
The IT Integrator
The pricing page publishes the plan structure — Base and Pro with their inclusions, plus named add-ons such as external DPO, external ISB and whistleblowing management — but no price figures, and the DSGVO software page describes only a recurring SaaS subscription without numbers. The only pricing-adjacent claim captured is "Bis zu 50 % günstiger als externe Berater". I found no public prices per edition, module or entity count. 4 7 14
The Skeptic
The pricing page names a Base and a Pro plan with their inclusions and add-ons, but the captured pages state no price figure anywhere; the software page says costs depend on company size, functionality and number of users, and the path to an invoice is a demo booking. Expert support, an external data protection officer and an external information security officer sit inside the Pro plan and add-ons, so software and consulting are presented together rather than separated. No captured page states a billing period or VAT treatment, and '50% cheaper than external consultants' is a comparison, not a price. 7 14 4
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in DE
unverified
Why unverified?The imprint names only DataCo GmbH, not the brand DataGuard, and no excerpt states the group structure or a parent company's seat, so the link between this entity and the product rests solely on the imprint. |
2/2 pts | 6 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Cloud service only
unverified
Why unverified?The sentence sits in the TISAX® disclaimer and scopes DataGuard's TISAX-related offering rather than explicitly ruling out self-hosting, though every pricing plan in S4 is likewise labelled 'SAAS PLATTFORM'. |
0/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 DataGuard
Is DataGuard European?
Yes. whats-best.ai classifies DataGuard as EU-Made. Its vendor, DataCo GmbH, is incorporated in Germany, per the vendor’s page captured 19 Oct 2026.
Where does DataGuard store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does DataGuard have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to DataGuard?
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: DataGuard alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The imprint names only DataCo GmbH, not the brand DataGuard, and no excerpt states the group structure or a parent company's seat, so the link between this entity and the product rests solely on the imprint.
- Weak sourcing — Hosting options. The sentence sits in the TISAX® disclaimer and scopes DataGuard's TISAX-related offering rather than explicitly ruling out self-hosting, though every pricing plan in S4 is likewise labelled 'SAAS PLATTFORM'.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 41 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (19)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage (DE) www.dataguard.de Checked 16 Nov 2026 Details →
- 2 Platform/product page www.dataguard.de Checked 16 Nov 2026 Details →
- 3 GDPR framework page www.dataguard.de Checked 16 Nov 2026 Details →
- 4 ISO 27001 framework page www.dataguard.de Checked 16 Nov 2026 Details →
- 5 About page www.dataguard.de Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 6 Imprint www.dataguard.de Checked 19 Oct 2026 Details →
- 7 Vendor pricing page www.dataguard.de Checked 16 Nov 2026 Details →
- 8 Privacy policy www.dataguard.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 9 Records & DPIA depth — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 10 Records & DPIA depth — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 11 Data subject rights & incidents — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 12 Data subject rights & incidents — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 13 Privacy regime coverage — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 14 Privacy regime coverage — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 15 Audit readiness & evidence — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 16 Audit readiness & evidence — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 17 Integrations & automation — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 18 Integrations & automation — found from sitemap www.dataguard.de Checked 16 Nov 2026 Details →
- 19 Imprint www.dataguard.de Checked 16 Nov 2026 Details →