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 heyData GmbH · heydata.eu

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

Link to this page

heyData: AI-assisted analysis on whats-best.ai heyData: 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.

heyData at a glance

Vendor
heyData GmbH
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
In the EU; pages mention Germany source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates heyData 3/5, the mean of 6 judges. heyData, a Berlin compliance platform for small and medium-sized enterprises, scored strongest on framework coverage, 7 to 8, and privacy management, 6 to 7: GDPR, UK GDPR, the Swiss revFADP and the EU AI Act run as modules steered from one shared evidence base, and the Article 30 record of processing activities carries guided fields, templates, versioning and an authority export, linked to asset and vendor data, with DPIAs on a risk matrix and Article 28 processor management against a 4,000+ vendor database. 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

heyData alternatives, European ones first →

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

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

Records & DPIA depth

How this is scored

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

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

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

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

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

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

Report an error

The In-House Counsel

The record of processing activities is built to Article 30 with templates, versioning and an export for the supervisory authority, and it is linked to asset and vendor data; DPIAs run on a risk matrix and TOMs, processor agreements and a 4,000-entry vendor database sit in the same workspace. What I cannot see is the DPIA obligation being derived from the record itself or legal bases modelled as connected fields, so I stop short of the top band. 13 12 3 9

Report an error

Data subject rights & incidents

How this is scored

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

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

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

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

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

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

Report an error

The In-House Counsel

Data subject requests run in workflows with owners, deadlines and logs, and breaches are documented in a register with the 72-hour clock of Article 33, reminders and prepared reporting steps toward the authority. We found no public information on an intake portal with identity verification, a severity assessment that produces the notification itself, or deletion rules tied to the record with tracked execution — the parts an authority audit would walk through first. 13 12 3 13

Report an error

Privacy regime coverage

How this is scored

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

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

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

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

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

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

Report an error

The In-House Counsel

GDPR, UK GDPR and the revised Swiss FADP are steered from one common evidence base with proof objects re-used rather than rebuilt, the EU AI Act is a maintained module, and the vendor states that regulatory changes flow into templates and workflows so the content does not age after setup. Dedicated national German content beyond the GDPR is not shown as separate maintained material. 8 12 12 16

Report an error

Audit readiness & evidence

How this is scored

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

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

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

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

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

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

Report an error

The In-House Counsel

Records carry versioning and an audit trail, evidence is exportable for audits and customer requests, and the vendor assembles evidence, risk reports and policies into a package it calls fit for inspection, backed by a real-time compliance score. Read-only auditor access and reproduction of a record as it stood on a given date are not documented, and that is what I would insist on before an authority visit. 4 12 8 9

Report an error

Integrations & automation

How this is scored

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

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

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

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

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

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

Report an error

The In-House Counsel

More than fifty integrations including Microsoft 365, Jira and Slack, automatic employee synchronisation from HR systems and an automatic infrastructure scan feed the platform from the real IT estate, and the connector landscape is stated to be expanding. No documented API, webhooks or single sign-on with user provisioning appear on the captured pages, so the automation depth beyond the named connectors is unknown to me. 16 17 4 17

Report an error

European sovereignty

How this is scored

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

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

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

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

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

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

Report an error

The In-House Counsel

The contracting entity is a German GmbH and hosting in Germany with an ISO 27001-certified hoster and no non-EU authority access is claimed, and a data processing agreement with customers is referenced in the privacy policy. That claim is a footer line without detail on data centres, and the published processor list covers the website — including US processors such as Webflow and CloudFront — rather than the platform that would hold my compliance record; an on-premises or sovereign-cloud option is not documented. 3 6 5 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 — 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 In-House Counsel

A Professional plan is published from €99 per month with a 10% annual discount and its main inclusions listed, but the end price follows company size and custom packages are quoted, so a buyer cannot compute the invoice for a given headcount from public pages alone. The captured pages give different figures for what the pricing page shows: an earlier capture states no prices at all, while later captures show the from-price and the annual discount. 2 3 1 2

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 EU only unverified
Why unverified?

Footer marketing line with no detail; the privacy policy discloses US processing by Webflow and AWS CloudFront, but for the website itself rather than the hosted platform's customer data.

4/4 pts 1 Report an error
Hosting options Not determined — uncited 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 heyData

Is heyData European?

Yes. whats-best.ai classifies heyData as EU-Made. Its vendor, heyData GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does heyData store data?

heyData stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 2 Nov 2026.

Does heyData have a free plan?

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

What are the best alternatives to heyData?

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