whats-best.ai
Search Sign in

Data Protection

heyData

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by heyData GmbH · heydata.eu

Report an error on this page Is this your product? →

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

The In-House Counsel

Weighted verdict

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

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

Scored by The In-House Counsel

Records & DPIA depth

How this is scored

The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.

0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.

3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.

5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.

8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.

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

Report an error

The In-House Counsel

All four core artifacts are in the platform — an Art. 30 Verarbeitungsverzeichnis with templates and export, an Art. 35 DSFA that derives measures, Art. 28 AVV/vendor management with deadlines and Nachweise, and central TOM documentation. But nothing evidences a connected data model: no legal-basis modeling, no DPIA triggers derived from the register, no group templates or multi-client capability — each is sold as its own module. Linked modules with shallow connection, not a system of record. 1 3

Report an error

Data subject rights & incidents

How this is scored

The operational half of the DSMS: data subject request handling with statutory clocks, breach register and authority notification, deletion concepts that actually delete.

0 — Requests arrive by email and live there; breaches are a phone call and a memo.

3 — A request log and a breach list exist, but deadlines are manual, intake is unstructured, and deletion rules are documentation rather than workflow.

5 — DSR workflows with the Art. 12 clock tracked, structured breach register with the 72-hour clock, deletion concepts assignable to records; automation is reminders.

8 — Intake channels for requests (portal/form), identity-check support, deadline automation with escalation, breach severity assessment and authority-report output, deletion rules tied to the RoPA with execution tracking.

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

Report an error

The In-House Counsel

The breach side is real — structured incident documentation, the 72-hour Meldefrist tracked, workflows, reminders and 'vorbereitete Meldeschritte' — though prepared steps is short of actually producing the Art. 33 notification, which is what I would need to see. The evidence is silent on data subject request intake, the Art. 12 clock, identity checks and any deletion-concept workflow, and silence is information: one solid pillar out of three. 3

Report an error

Privacy regime coverage

How this is scored

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

0 — One regime, hard-coded; anything else is "on the roadmap".

3 — GDPR plus one national law as separate checklists; the same processing activity is documented once per regime.

5 — The major regimes for its market with partial cross-mapping; newer duties (AI Act, ePrivacy changes) present as content packs of varying depth.

8 — Broad current coverage with one-record-many-regimes mapping and visible maintenance as regimes evolve.

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

Report an error

The In-House Counsel

The catalogue names DSGVO, UK GDPR, revDSG and an EU AI Act module — usefully, exactly the regimes my companies operate under — plus NIS2 and ISO 27001. But the regimes appear as parallel modules with no evidence that one processing record maps across them, no per-country variants, and no documented update cadence for the legal content, which for me is the disqualifier for anything higher. 1 4

Report an error

Audit readiness & evidence

How this is scored

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

0 — Exports are screenshots; history is overwritten in place.

3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.

5 — Versioned records, standard report generators for the core registers, evidence attachments per activity; assembling a full audit file still takes days.

8 — Revision-safe change history, audit-scoped evidence packs on demand, management and authority reports current at a click, auditor access roles.

10 — Audit readiness as a standing state: continuous documentation status per regime and scope, exportable proof packs an auditor accepts as-is, and a defensible answer to "show me the state on date X".

Report an error

The In-House Counsel

There is an audit-prep offering ('prüffähiges Paket' of Nachweise, Risikoberichte, Policies, ISMS-Dokumentation), exportable Art. 30 documentation, training certificates and vendor evidence tracking. But I see no revision-safe change history, no auditor access roles, no on-demand evidence packs — and the package reads as something heyData assembles for you, a service step, not a standing state I can defend to an authority. 3 4

Report an error

Integrations & automation

How this is scored

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

0 — A closed island: manual entry in, PDF out, no API.

3 — CSV/Excel import and export; no live connections, no API worth the name.

5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing or SSO); automation is reminders and recurrence.

8 — Real connector set (ticketing, HR or asset sources), webhooks, SSO/SCIM, workflow automation with delegation and escalation, useful AI assistance with human review.

10 — The platform behaves like infrastructure: API parity for the data model, event streams, bidirectional sync with the estate, and automation that measurably removes the recurring toil (reviews, attestations, evidence pulls) rather than renaming it.

Report an error

The In-House Counsel

Named integrations with Microsoft 365, Jira and Slack plus genuine recurrence automation — automatic training assignment, reminders, documented completions — put this above CSV in/out. But the evidence evidences no API, no directory import, no SSO/SCIM, no webhooks; 'Integrationen mit bestehenden Tools' is breadth without demonstrated depth, and I cannot assume infrastructure the vendor does not document. 3 4

Report an error

European sovereignty

How this is scored

Where the compliance record of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. A platform that maps your processing is itself your most concentrated processing.

0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your RoPA.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.

5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.

8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.

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

Report an error

The In-House Counsel

A German GmbH at a Berlin address claiming Germany hosting on an ISO 27001-certified hoster with 'kein Zugriff durch Nicht-EU-Behörden' is the right posture for the record itself. EU entity and German hosting, but the publication duty is unmet and US exposure in the chain is documented by the vendor itself. 3 5 6 6

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.

0 — No public prices at all; every configuration is a sales conversation.

3 — An entry price exists, but module add-ons, entity counts or bundled consulting make the real total incomputable.

5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; only genuine corporate-group contracts are custom.

10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a 10-client consultancy is a two-minute exercise.

Report an error

The In-House Counsel

From €99/month with monthly/annual terms and a stated -10% annual discount is a start, but the asterisk's footnote isn't shown, the 'Endpreis nach Unternehmensgröße' scale isn't published, and the default path is a custom Angebot. Worse for computability, the Professional price bundles an official external DSB appointment under Art. 37 and an annual DSFA — software and a regulated legal service fused into one number I cannot decompose. 2 3

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about heyData? Tell us Report an error on this page

Sources (17)

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

  1. 1 Vendor homepage heydata.eu Checked 5 Oct 2026 +1 earlier capture: 16 Sep 2026 Details →
  2. 2 Vendor pricing page heydata.eu Checked 5 Oct 2026 Details →
  3. 3 GDPR product page heydata.eu Checked 5 Oct 2026 Details →
  4. 4 ISO 27001 product page heydata.eu Checked 5 Oct 2026 Details →
  5. 5 Imprint heydata.eu Checked 5 Oct 2026 Details →
  6. 6 Privacy policy heydata.eu Checked 5 Oct 2026 +1 earlier capture: 15 Sep 2026 Details →
  7. 7 Data processing agreement (dpa) heydata.eu Checked 5 Oct 2026 Details →
  8. 8 Security / trust page — found from the homepage heydata.eu Checked 5 Oct 2026 Details →
  9. 9 Records & DPIA depth — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  10. 10 Records & DPIA depth — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  11. 11 Data subject rights & incidents — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  12. 12 Privacy regime coverage — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  13. 13 Privacy regime coverage — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  14. 14 Audit readiness & evidence — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  15. 15 Audit readiness & evidence — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  16. 16 Integrations & automation — found from sitemap heydata.eu Checked 5 Oct 2026 Details →
  17. 17 Integrations & automation — found from sitemap heydata.eu Checked 5 Oct 2026 Details →