heyData
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 heyData GmbH · heydata.eu
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.
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
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. Audit readiness, integrations and automation, and pricing transparency showed no spread — 7, 6 and 4. Pricing transparency, flat at 4, reflects a single public from-price — Professional at "ab 99 € /Monat*" — with the final price following company size through a quote; the captured pages give different figures, 99 € on German pages and 99 £ on the UK page. Rights and incidents drew the widest spread, 4 to 6: judges weighed documented 72-hour breach workflows against the absence of public information on identity-verified intake, per-breach severity assessment and deletion rules tied to the record.
Speaks for it
- Article 30 record of processing activities with guided fields, templates, versioning and an export for supervisory authorities, linked to asset and vendor data.
- DPIAs under Article 35 with a risk matrix, central TOMs, and Article 28 processor management against a database of 4,000+ vendors.
- GDPR, UK GDPR, the revised Swiss FADP and the EU AI Act as maintained modules steered from one shared evidence base with proofs reused rather than rebuilt.
- Assembled audit-ready package of evidence, risk reports and policies, with versioning, an audit trail and a real-time compliance score.
- Request and breach workflows with owners, deadlines, logs, the 72-hour Article 33 clock and 24h/72h escalation paths under NIS2.
Held against it
- A single public from-price with the final invoice set by company size through a quote, and no public prices shown for other editions, modules, size steps or setup fees.
- We found no public information on identity-verified request intake, a per-breach severity assessment feeding the authority notification, or deletion rules tied to the record with tracked execution.
- We found no public information on a documented API, webhooks, single sign-on or SCIM provisioning behind the claimed over fifty integrations.
- We found no public information on read-only auditor access or on reproducing any record as it stood on a given date.
- Sovereignty stated at company and country level, with the privacy policy naming US providers such as Webflow and AWS CloudFront for the vendor's own website and no public information on a platform-side subprocessor list or named data centres.
Best for
- You are a small or medium-sized business that wants GDPR, UK GDPR and the revised Swiss FADP steered from one shared evidence base instead of separate tools.
- You need a guided Article 30 record with an authority export, DPIAs on a risk matrix and Article 28 processor management in one workspace.
- You want an external DPO service bundled with the platform, published at "from €99 /month*" with the Article 37 GDPR appointment, trainings on demand and an annual DPIA included.
- You are gathering evidence for internal or external audits and want an assembled package with versioning, an audit trail and a real-time compliance score.
Avoid if
- You must compute your invoice for a given headcount in advance — only one from-price is public and the final price follows company size through a quote.
- Your review requires the platform's own hosting and subprocessor chain in writing — the published disclosures cover the vendor's website, naming US providers such as Webflow and AWS CloudFront, rather than the platform that would hold your compliance data.
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 3.5 of 5 |
| Data subject rights & incidents | 2.5 of 5 |
| Privacy regime coverage | 4 of 5 |
| Audit readiness & evidence | 3.5 of 5 |
| Integrations & automation | 3 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 2 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 record of processing activities is a real module with guided fields, templates, versioning and an export for authorities, kept current through links to asset and vendor data; DPIAs run as a structured module with a risk matrix, TOMs are held centrally, and processor agreements are managed against a database of 4,000+ vendors. For a practice like mine two things hold it back: I found no public information on DPIA need being derived from the record or on legal bases as linked data, and the reuse heyData markets is across frameworks rather than across client mandates. 9 13 9 13 12
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
The Drafted Generalist
The records side is genuinely built out: a guided record of processing with templates, versioning and an export for the supervisory authority, a DPIA module with a risk matrix, TOMs held centrally with gaps flagged, and processor contracts with deadlines and evidence — and the record is linked to asset and vendor data, so I am not re-typing into separate tools. I found no public information on TOMs being assigned to individual processing activities or DPIA need being derived automatically from the record, so it sits just below the connected top level. 10 12 3 9 13
The Lead Auditor
The record of processing activities is maintained with templates, guided fields, ownership and versioning, includes an export for supervisory authorities, and is linked to asset and vendor data; DPIAs run as a structured module with a risk matrix, and TOMs and Art. 28 processor agreements sit centrally on the same platform with a 4,000+ vendor database. I found no public information showing DPIA need derived from the record, legal bases modelled into it, or multi-client reuse, so this is a well-connected module set rather than one data model driving everything. 12 13 3 9 13
The IT Integrator
The register of processing activities is a real module with guided fields, ownership, versioning and an authority export, DPIAs run per Article 35 with a risk matrix, and processor data processing agreements and TOMs sit on the same platform — the register even links to asset and vendor records to stay current. We found no public information on DPIA need being derived from the register itself or on reusable templates across multiple client companies, so this lands just short of the fully connected data model. 12 3 9 13
The Skeptic
The record of processing activities is a real module — Article 30, guided fields, templates, versioning, exportable documentation and an authority export — and it is linked to asset and vendor data, alongside DPIAs under Article 35 with a risk matrix, centrally documented TOMs, and Article 28 processor management over a database of 4,000-plus vendors. We found no public information on legal bases modelled inside the record, DPIA need derived from it, or template reuse across client companies, which keeps this below the fully connected data-model level. 13 9 3 12 4
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
Data subject requests run in fixed workflows with owners, deadlines and logs, and breaches are documented with the 72-hour Art. 33 clock, reminders and prepared reporting steps, plus 24h/72h escalation paths for security incidents. I found no public information on an intake portal with identity verification, a per-breach risk assessment, or deletion periods tied to the record of processing with execution tracked; the deletion timelines published are heyData's own website practices. 13 12 3 8
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
The Drafted Generalist
Requests run in fixed workflows with owners, deadlines and logs, and breaches get a structured register with the 72-hour clock, reminders and prepared reporting steps — the operational half, done in language I can follow. I found no public information on deletion periods recorded per processing activity or a risk assessment per breach, which the deadline-and-deletion level expects, so it lands below that. 8 13 12 3 13
The Lead Auditor
Data subject requests run through workflows with owners, deadlines and logs, and breaches are documented with the 72-hour clock, reminders and prepared reporting steps under Art. 33 GDPR. I found no public information on identity-verified intake, per-breach severity assessment producing the authority notification, or deletion periods recorded per processing activity, so rights and incidents are handled but not closed-loop. 12 12 3 13
The IT Integrator
Data subject requests run as workflows with owners, deadlines and logs, and breaches are documented with the 72-hour clock, reminders and prepared reporting steps per Article 33. We found no public information on an intake portal with identity verification, a per-breach risk assessment feeding the authority notification, or deletion rules tied to the register with tracked execution — solid workflow territory, not yet end-to-end operations. 12 3 13
The Skeptic
Data subject requests run in workflows with owners, deadlines and logs, and breaches are documented in structured workflows with the 72-hour Article 33 reporting deadline in view, reminders and prepared reporting steps, plus 24h/72h escalation paths under NIS2. We found no public information on a request intake portal with identity verification, a per-breach severity assessment producing the authority notification, or deletion rules tied to the record of processing with tracked execution. 12 13 3 8
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 revised Swiss FADP ship as modules steered from one common evidence basis, with evidence reused rather than rebuilt, multi-framework mapping across ISO 27001, NIS2 and GDPR, an EU AI Act module, and a team that monitors legal developments and flows changes into templates, workflows and content. Short of the top: we found no public information on a published update cadence, and cookie-law duties appear only as heyData's own consent basis rather than as maintained product content. 12 12 16 8 2
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
The Drafted Generalist
GDPR, UK GDPR, the Swiss revFADP and the EU AI Act all appear as maintained modules, with the pages saying requirements are steered from one common evidence base and reused instead of rebuilt, and that regulatory changes flow continuously into templates, workflows and content. 8 12 12 14 16
The Lead Auditor
GDPR, UK GDPR and the Swiss revDSG are offered as modules alongside the EU AI Act, with the vendor stating UK and EU requirements are steered from one common evidence base that is reused rather than rebuilt, and regulatory changes flowing continuously into templates, workflows and status. We found no public information on ePrivacy or cookie-regime duties as maintained product content or on a published update cadence, so coverage is broad and shared but not a documented living programme. 12 12 16 2
The IT Integrator
GDPR, UK GDPR, the Swiss revDSG and the EU AI Act run on one platform where evidence is reused across frameworks instead of rebuilt, with multi-framework mapping for ISO 27001, NIS2 and GDPR and a stated process that regulatory changes flow into templates and workflows. TDDDG appears only as the basis of their own cookie banner, not as maintained product content, which keeps this just below the top band. 8 12 14 2
The Skeptic
GDPR, UK GDPR and the Swiss revFADP each appear as named modules with dedicated pages and experts holding nFADP and UK GDPR credentials, the EU AI Act is a module, and the vendor states UK and EU requirements are steered from one shared evidence base with proofs reused rather than rebuilt, while regulatory changes are said to flow into templates and workflows. We found no public information on ePrivacy/TTDSG duties as product content — the TDDDG reference we saw concerns the vendor's own cookie banner. 12 12 13 14 8 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
Relevant evidence, risk reports, policies and ISMS documentation are assembled into an audit-ready package, all results and evidence remain structured and retrievable at any time, the policy centre carries versioning and an audit trail, and status is monitored continuously with regulatory changes feeding into it and a compliance score in real time. We found no public information on read-only auditor access, management or DPO reports at a click, or reproducing any record as it stood on a given date. 14 4 8 12
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
The Drafted Generalist
Evidence is assembled into an audit-ready package — records, risk reports, policies and ISMS documentation — with central evidence for internal and external audits, versioning and an audit trail in the policy centre, plus a real-time compliance score and continuous status monitoring. I found no public information on read-only auditor access or management and DPO reports at a click, which is what the next level up adds. 4 14 8 14 4
The Lead Auditor
Evidence is a first-class output: an automated preparation checklist assembles evidence, risk reports and policies into a package the vendor calls fit for audit, results and evidence stay structured and retrievable at any time, records carry versioning and an audit trail, and a real-time compliance score shows standing status across frameworks. We found no public information on read-only auditor access or on reproducing any record as it stood on a given date — the exact question an authority asks — which is why this stops below the top band. 4 8 9 12 4
The IT Integrator
Versioned records with an audit trail, a central evidence hub for internal and external audits, and an assembled audit-ready package of evidence, risk reports, policies and ISMS documentation are all documented, alongside continuous status monitoring and a real-time compliance score. We found no public information on read-only auditor access or on reproducing a record as it stood on a given date. 8 9 14 4
The Skeptic
Policies and documentation carry templates, versioning and an audit trail, the risk register sits in a single auditable dataset, evidence is centralised for internal and external audits and exportable, and an automated checklist assembles a certification-ready package including the statement of applicability and internal audits, with continuous status monitoring and a real-time compliance score. We found no public information on read-only auditor access or on reproducing any record as it stood on a given date. 8 4 12 4 14 9
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
Over fifty integrations are claimed, with Microsoft 365, Jira and Slack named, automatic employee synchronisation from HR systems, cloud and repository connectors, and an automatic infrastructure scan, on a foundation said to keep expanding. That is well past a few named connectors; we found no public information on a documented API, single sign-on or SCIM provisioning, or webhooks, so I see no developer surface to script across client estates. 17 4 17 17 4
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
The Drafted Generalist
Over 50 integrations are claimed for HR, cloud and repository systems with named tools like Microsoft 365, Jira and Slack, plus automatic employee synchronisation from HR systems, an automatic infrastructure scan, and recurring work with reminders, assignment and escalation logic. I found no public information on a documented API, single sign-on or webhooks, so it is connector-rich but not at the infrastructure level. 4 8 16 17 17
The Lead Auditor
Over fifty integrations are claimed across HR, cloud and repository systems with named connectors such as Microsoft 365, Jira and Slack, plus automatic employee synchronisation from HR systems, an automatic infrastructure scan, and workflows carrying responsibilities, deadlines, escalation logic and automated reminders. We found no public information on a documented API, single sign-on, SCIM or webhooks, so the feed from the real estate is plausible but not demonstrable from public pages. 16 17 4 17
The IT Integrator
This is the part I came for: over fifty integrations across HR, cloud and repository systems with Microsoft 365, Jira and Slack named, automatic employee synchronization from HR systems, a continuously expanded integration landscape, and exportable register data. But we found no public information on a documented API, webhooks, or single sign-on with SCIM provisioning — until that appears it is a connector catalogue rather than infrastructure, and my directory and CMDB estate has no documented way in. 10 16 4 17
The Skeptic
Over fifty integrations are claimed — displayed as an animated counter whose exact figure is not extractable from the page text — with Microsoft 365, Jira and Slack named, HR, cloud and repository systems as categories, automatic employee synchronisation, automatic updates to the record, and recurring workflows with responsibilities and deadlines. We found no public information on a documented API, webhooks, single sign-on or SCIM provisioning, so the automation story rests on marketing counters plus a handful of named tools. 17 17 16 17 8
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
A Berlin GmbH under German law, hosting in Germany at an ISO 27001-certified hoster, a customer data processing agreement in place, and a published subprocessor disclosure — though the US processors named there (Webflow, AWS CloudFront, Google, Taboola) serve the website and marketing. We found no public information on the platform's own data centres, further hosting options, or a platform-side subprocessor list, so the European posture is proven at the company and country level while the product-side chain stays unknown. 6 11 13 6
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
The Drafted Generalist
A German GmbH in Berlin with a commercial register number, hosting stated as Germany with an ISO 27001-certified hoster, a customer data processing agreement named in the privacy policy, and the claim of no access by non-EU authorities. The privacy policy does list non-EU processors such as Webflow and AWS, though for the vendor's own website rather than the hosted platform's customer data, and named data centres and platform subprocessors are not detailed, so it stays short of the clean end-to-end level. 3 6 5 6 17
The Lead Auditor
A German GmbH registered in Berlin hosts in Germany with an ISO 27001-certified hoster, concludes a data processing agreement with its customers, and states that no non-EU authority has access. The published processor disclosures name non-EU providers such as Webflow and AWS CloudFront for the vendor's website, the hosting facilities are not named, and we found no public information on the platform's own subprocessor chain, so the European posture is stated but not documented end to end. 3 6 11 6
The IT Integrator
The contracting entity is a German GmbH in Berlin with hosting stated in Germany at an ISO 27001-certified hoster, a claim of no access by non-EU authorities, and a data processing agreement concluded with customers. The published subprocessor disclosures relate to the website and include US processors such as Webflow and AWS CloudFront, and we found no public information on named data centres or a platform-side subprocessor list, so this sits in the middle band. 3 6 5 6
The Skeptic
The contracting entity is the Berlin heyData GmbH with a commercial register number, hosting is stated as Germany under an ISO 27001-certified hoster, and the privacy policy says customer platform data is processed under a concluded data processing agreement. The hoster and its data centres are never named, the page at the data-processing-agreement address advertises expert help with customers' own processor contracts rather than publishing the vendor's own agreement text, and the privacy policy itself discloses US processing by Webflow and AWS CloudFront for the website while footers promise no non-EU authority access — we found no public information on published TOMs, a platform subprocessor list, or an on-premises option. 5 6 3 6 7
Pricing transparency
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
One public from-price exists — Professional at "ab 99 € /Monat*" and the external DPO at "from €99 /month*" — with monthly billing, "Jährlich -10%", bundle savings of "bis zu 30%" and inclusions listed. The final price is stated to depend on company size, custom packages are quote-based, and we found no public prices for further editions or the size steps; the captured pages also give different figures for the Professional plan (99 € monthly on German pages, 99 £ on the UK page). A single SMB can budget from this; a consultancy pricing thirty mandates cannot compute its real invoice. 3 2 2 13 12
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
The Drafted Generalist
One edition is priced publicly — Professional from €99 per month, where the captured pages give different figures (another shows the same plan from £99), with an asterisk whose footnote is not shown — and the inclusions are listed clearly: the Art. 37 DPO appointment, the platform, trainings, an annual DPIA, monthly or annual billing with 10% off annual, plus a freemium registration. But the end price is set by company size through a quote, and the other editions, modules and size steps are not public, so I cannot compute my real invoice from the pages alone. 2 3 12 2 3
The Lead Auditor
One professional plan is public at a from-price of 99 per month — the captured pages show 99 € on the German GDPR pages and 99 £ on the UK GDPR page — with monthly billing, an annual option shown at ten percent off, no commitment, and the main service inclusions listed. The final price follows company size and arrives by quote, and no module, scale-step or setup prices are public, so the real invoice cannot be computed in advance. 2 3 2 13
The IT Integrator
One plan is priced publicly — the external DPO service and Professional plan from €99 per month with its main inclusions listed, an annual option at ten percent off, and the final price stated to scale with company size with no commitment. Everything else is quote-based and the pricing page itself carries no figures, so the real invoice for a given headcount is not computable from public pages. 2 3 1 2
The Skeptic
One from-price is public — the Professional plan at "ab 99 € /Monat*" with monthly billing, annual billing at −10%, and the main inclusions listed — but final prices depend on company size, a custom quote is offered, and the asterisk's footnote is not shown on the page. Other editions, module prices, setup fees and VAT treatment are not public; the captured pages also give different currencies for the same from-price (euros on German pages, pounds on the UK page), and an earlier capture of the pricing page showed no prices at all. 3 2 13 12 2 1
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 | 2/2 pts | 6 Report an error |
|---|---|---|---|
| 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
- 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 — Hosting location. 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.
- 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.
- 49 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
- 15 integrations 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
- 11 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
- 6 support 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 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
- 3 pricing 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 legal 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (17)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage heydata.eu Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
- 2 Vendor pricing page heydata.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 3 GDPR product page heydata.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 4 ISO 27001 product page heydata.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Imprint heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 6 Privacy policy heydata.eu Checked 16 Nov 2026 +2 earlier captures: 5 Oct 2026, 15 Sep 2026 Details →
- 7 Data processing agreement (dpa) heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 8 Security / trust page — found from the homepage heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 9 Records & DPIA depth — found from sitemap heydata.eu Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
- 10 Records & DPIA depth — found from sitemap heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 11 Data subject rights & incidents — found from sitemap heydata.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 12 Privacy regime coverage — found from sitemap heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 13 Privacy regime coverage — found from sitemap heydata.eu Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
- 14 Audit readiness & evidence — found from sitemap heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 15 Audit readiness & evidence — found from sitemap heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 16 Integrations & automation — found from sitemap heydata.eu Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 17 Integrations & automation — found from sitemap heydata.eu Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →