ECOMPLY
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 ECOMPLY GmbH · www.ecomply.io
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.
ECOMPLY at a glance
- Vendor
- ECOMPLY GmbH
- Headquarters
- Incorporated in Germany source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates ECOMPLY 2.5/5, the mean of 6 judges. ECOMPLY, a web-based GDPR compliance tool from ECOMPLY GmbH of Munich, earned persona-weighted totals of 4.1 to 4.8. how scores are made
- As of
- Vendor pages captured 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
ECOMPLY, a web-based GDPR compliance tool from ECOMPLY GmbH of Munich, earned persona-weighted totals of 4.1 to 4.8. Its strongest area is privacy management, a flat 6: a records-of-processing register with guided forms, automatic risk assessment and per-entry change tracking, plus a DPIA assistant, TOMs, processor management and multi-client capability — though linkage into one connected system of record is undocumented. Audit readiness ranged 5 to 7: higher scores credit conditionally linked audits with automatic gap-analysis reports reproducible across clients and an exportable logbook, while the lower mark notes no public information on read-only auditor access or point-in-time record reproduction. Weakest is sovereignty at a flat 3 — the German entity is proven, but hosting location and subprocessors for standard tiers are not stated on the captured pages, and on-premise hosting is Enterprise-on-request. Framework coverage sits at 3 to 4 (GDPR content), rights and incidents at a flat 4 with no public information on the one-month or 72-hour clocks, integrations and automation at a flat 4. Pricing transparency split 2 to 4; no price figures appear despite itemised tier limits.
Speaks for it
- Records of processing run on a guided form with automatic risk assessment and per-entry change tracking
- Audit assistant uses conditionally linked questions and generates automatic gap-analysis reports reusable across clients
- An automatic logbook records every change and exports for clients and authority enquiries
- Contracting entity is ECOMPLY GmbH, Munich, registered at Amtsgericht München under HRB 237932
- Multi-client capability with per-client dashboards supports external DPOs managing many controllers
Held against it
- We found no public information on hosting location or subprocessors for the standard tiers
- We found no public information on a one-month request deadline clock or a 72-hour breach notification workflow
- Framework coverage stopped at GDPR; LGPD consultants appear as a target sector, not a supported regime
- LDAP, SAML and SCIM and system interfaces sit behind the Enterprise plan, with no public information on a documented API or named connectors
- No price figures appear on the captured pages despite itemised tier limits
Best for
- You are an external DPO or German-speaking advisory firm maintaining GDPR documentation across many clients
- You want a guided records-of-processing register with automatic risk scoring instead of static templates
- You need audit gap-analysis reports and an exportable change log for accountability toward clients and authorities
Avoid if
- You need maintained content for a second legal regime such as BDSG, nDSG, UK GDPR or LGPD
- Your team needs single sign-on or system interfaces without buying the Enterprise plan
- You depend on system-enforced deadline clocks for one-month responses and 72-hour breach notification
- You want on-premise or customer-operated cloud hosting outside the Enterprise-on-request option
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 3 of 5 |
| Data subject rights & incidents | 2 of 5 |
| Privacy regime coverage | 1.5 of 5 |
| Audit readiness & evidence | 3 of 5 |
| Integrations & automation | 2 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 module set covers a consultancy practice — records of processing with a guided form and automatic risk assessment, a DPIA assistant, processors, TOMs, a document generator, plus client management with per-client dashboards; unlimited controller entities are claimed on the homepage and listed under the Enterprise plan, so the captured pages give different scopes for it. We found no public information on processors' DPAs, legal bases, or TOMs linked to processing activities as one connected data model, nor on DPIA need derived from the record, so this sits above module depth but short of the connected system of record. 1 2 3 6 11
The In-House Counsel
The register of processing activities is a real module with a guided form, automatic risk assessment with colour-coded weaknesses, and change tracking, and the module list names the DPIA assistant, processors, TOMs, document generator and multi-client capability for external data protection officers. We found no public information on processors' data processing agreements being recorded or on TOMs assigned to specific processing activities, so the connected data model beyond the risk assessment is undocumented. 1 2 3 6 7
The Drafted Generalist
Everything the German DSMS expects is there as a named module — processing register with a guided form and automatic risk scoring, a DPIA assistant, processors, and TOMs — and the guided form with autosave and tracked changes is exactly the hand-holding I want. I just can't see proof the pieces talk to each other enough to hand an authority a finished register without assembly work, and the DPIA assistant is gated to the Medium Business plan. 1 2 3 6 7
The Lead Auditor
Records of processing, a DPIA assistant, TOMs and processor identification are all modules, with a guided form, automatic risk assessment and per-entry change tracking on the record of processing and multi-client capability for external DPOs. The connected data model I audit for — legal bases tied to activities, processor agreements linked into the record, an authority-ready register output — is not documented, so this sits above templates but below a system of record. 1 2 3 6 7 11
The IT Integrator
The legal artefacts are real modules — a records-of-processing register with guided forms and automatic risk assessment, processors, TOMs and a DPIA assistant — and multi-client capability with holdings and group structures fits the external-DPO world. The captured pages show no connected spine though: I found no public information on processing activities linked to systems, processors, legal bases and measures, or DPIA need derived from the record, even if the auto-generated data map hints at linkage. 1 2 3 6 7
The Skeptic
The module list names processing activities, DPIA, TOMs and processors, and the records page describes a guided form with automatic risk assessment and change tracking — a structured DSMS, not a template pack. But we found no public information showing the record linked to legal bases, systems or TOM assignments, or an authority-ready Article 30 output, so I stop just above the module level. 1 2 3 6 7
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
Requests are tracked with status, categorised through a guided process, answered from templates and archived, and incidents get severity assessment, measures, documentation, team collaboration and an archive framed for management and authorities; delegation of requests comes only with the Enterprise plan. We found no public information on one-month or 72-hour deadline clocks, deadline reminders, or deletion periods tied to a processing activity. 1 2 8 9
The In-House Counsel
Data subject requests are tracked with categorisation, guided process, response templates and an archive, and the incident tracker assesses severity, assigns measures and keeps an archive for management and authorities, with a delegation assistant on the top plan. We found no public information on a one-month deadline clock with reminders, a 72-hour notification workflow producing the Art. 33 notification, or deletion rules tied to the register with tracked execution — the clocks a breach defence stands on. 1 2 8 9
The Drafted Generalist
Request handling is genuinely guided — categorise, work through it with templates, archive past cases, and on Enterprise a delegation assistant — and the incident tracker does severity assessment, measures and documentation for management and authorities. We found no public information on a one-month deadline clock, a 72-hour notification timer, or deletion concepts, which is the part that actually gets a company fined. 1 2 3 8 9
The Lead Auditor
Requests get a guided tracker with categorisation, templates, a status archive and an Enterprise delegation assistant; incidents get severity assessment, measures, team involvement and an archive framed for management and authorities. The pages do not show the one-month deadline clock with escalation, a 72-hour notification clock, or deletion periods per processing activity, so the operational spine is visible but the statutory timers are not. 1 2 3 8 9
The IT Integrator
Requests get categorisation, guided handling, templates, status tracking and an archive, and incidents get severity assessment, measures and an archive for management and authorities — clearly more than a simple log. I found no public information on the one-month deadline clock, a 72-hour notification path, or deletion rules per processing activity, so this half runs on team discipline rather than the machine. 1 8 9
The Skeptic
A request tracker with categorisation, guided handling, response templates and an archive is documented, alongside an incident tracker that assesses severity, assigns measures and keeps an archive for management and authorities. We found no public information on the one-month deadline clock, a 72-hour notification workflow, identity verification or deletion periods, so severity assessment and templates carry it only to the middle. 1 2 8 9
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
Everything captured is GDPR vocabulary — VVT, DSFA, AVV, TOM — sold to German firms, external data protection officers and DSGVO advisers, which fully meets the single-regime level. The pages name LGPD consultants as a target sector and offer a Portuguese demo, but we found no public information on LGPD, BDSG, nDSG or UK GDPR registers or templates of their own. 1 9 11
The In-House Counsel
GDPR is clearly operationalised with German-language registers, templates, audits and DSFA content, and whistleblower case management adds an adjacent regime on the Enterprise plan. We found no public information on BDSG, nDSG or UK GDPR templates, on LGPD content beyond marketing to LGPD consultants and a Portuguese demo button, or on a published update cadence when a regime changes. 1 2 7 9
The Drafted Generalist
This is clearly a GDPR product — VVT, DSFA, TOM, Betroffenenanfragen, Auftragsverarbeiter — and the whistleblower case management on Enterprise reaches a bit beyond pure GDPR. We found no public information on BDSG, TTDSG, nDSG or UK GDPR support; the LGPD mention shows up as a target sector, not as a supported regime. 1 2 9
The Lead Auditor
Everything captured is GDPR — registers, templates, audits and DPIA in the German tradition. LGPD consultants are named as a target sector, but we found no public information on BDSG, nDSG, UK GDPR, TTDSG or AI Act content, nor any documented update cadence when law changes. 1 7 9 11
The IT Integrator
GDPR is genuinely implemented — records of processing, DPIA, TOMs, processor management and audits with reusable templates. The target-customer lists mention LGPD consultants, but I found no public information on any second regime supported with its own templates or on per-country variants. 1 7 9
The Skeptic
Every capability captured is GDPR — records of processing, DPIA, TOMs, data subject requests, processors — aimed at German-speaking law firms and external DPOs. The pages court LGPD consultants and even book demos in Portuguese, yet we found no public information naming a second legal regime with its own maintained content; marketing reach is not regime coverage. 1 7 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
The audit assistant is built for a consultancy: pre-built and own audit templates reproducible across all clients, conditional question logic, saved progress, automatic gap-analysis reports as professional documents, and branding on software and reports. An automatic log of all system events, exportable for authority queries, plus change tracking on the record of processing gives accountability; we found no public information on read-only auditor access or on reproducing a record as it stood on a given date. 1 3 6 10 11
The In-House Counsel
All changes in the system are logged automatically and exportable for accountability toward clients and authorities, records track changes over time, and the audit assistant runs prebuilt or custom audits reproducible across clients and generates gap-analysis reports as documents. We found no public information on revision-safe storage guarantees, on-demand evidence packs, or read-only auditor access, which keeps this short of authority-grade. 1 3 6 10 11
The Drafted Generalist
The logbook automatically records every change and can be exported for authority queries, and the audit assistant runs conditionally-linked questionnaires that produce automatic gap analysis reports, reusable across every client. We found no public information on read-only auditor access or on-demand evidence packs, so some assembly is still on me. 1 3 6 10 11
The Lead Auditor
An automatic logbook of all system changes, exportable for clients and authority inquiries, plus a guided audit assistant generating automatic gap-analysis reports reproducible across clients — the two things I look for first. Evidence packs generated on demand, read-only auditor access and reproduction of any record as it stood on a given date are not documented, so this is good history and good reports, not yet a standing audit state. 1 3 6 10 11
The IT Integrator
Automatic logging of every change, exportable for authority questions, plus guided audits with conditional questions that generate gap-analysis reports reproducible across clients — a decent evidence story, backed by change tracking on the processing records. I found no public information on read-only auditor access, evidence attached per measure, or reproducing a record as it stood on a given date. 1 3 6 10 11
The Skeptic
A guided audit assistant generating automatic gap-analysis reports, a logbook that records every change and can be exported for authority enquiries, and change tracking per processing activity are all documented. We found no public information on read-only auditor access, evidence packs per measure, or reproducing a record as it stood on a given date. 1 3 6 10 11
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
Standard plans offer exports to pdf, xlsx and docx and collaboration with task assignment and reminders — useful, but data still gets typed in. LDAP, SAML and SCIM, system interfaces and a data migration are gated to the Enterprise plan on request, and we found no public information on a documented API, webhooks or named connectors to the real IT estate. 1 2 3
The In-House Counsel
Export to pdf, xlsx and docx plus task assignment, comments and reminders are in the standard product, while LDAP, SAML and SCIM provisioning, interfaces to other systems and legacy data migration are listed only as Enterprise features obtained on request. We found no public information on a documented API, webhooks, or named connectors to directory, ticketing or HR sources, so the platform cannot feed from the real IT estate without re-typing. 1 2 3
The Drafted Generalist
Export to pdf, xlsx and docx, task assignment with reminders, and automatic risk scoring and gap reports do save re-typing the core work. The connections to the real IT estate — LDAP, SAML, SCIM and system interfaces — sit on the Enterprise plan only, and we found no public information on a documented API or webhooks for the standard tiers. 1 2 3 6
The Lead Auditor
The standard tiers offer export to pdf, xlsx and docx plus task assignment with discussions, comments and reminders; single sign-on via LDAP, SAML and SCIM, system interfaces and stock-data migration appear only as Enterprise-plan features obtained on request. We found no public information on a documented API or directory import for the regular plans, so automation rests on reminders rather than feeds from the real estate. 1 2 3 6
The IT Integrator
This is the criterion that hurts: the only estate hooks anywhere are LDAP, SAML and SCIM plus a bare 'interfaces to other systems' line, and every one of them sits behind the Enterprise plan on request. I found no public information on a documented API, webhooks, named connectors, or import of any kind below enterprise data migration — so compliance data here stays current because someone retypes it, exactly the data island I reject. 1 2 3
The Skeptic
Exports in pdf, xlsx and docx, reminders, task assignment and collaboration are documented, and single sign-on via LDAP, SAML and SCIM is real — but it sits behind the Enterprise plan, and 'Schnittstellen zu anderen Systemen' names no actual system. We found no public information on a documented API or any named connector, which is exactly the kind of unbacked integration claim I discount. 1 2 3
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 proven German — ECOMPLY GmbH, Munich, commercial register HRB 237932 — and on-premise or customer-operated cloud hosting and a custom data processing agreement exist, but only as Enterprise options on request. We found no public information on hosting location for the standard tiers, a standard data processing agreement, or subprocessors, so the chain beyond the German entity is unknown. 2 4 5
The In-House Counsel
The contracting entity is proven German — ECOMPLY GmbH, Leopoldstraße 31, München, registered at Amtsgericht München HRB 237932 — and on-premise or customer-operated cloud hosting exists, though only as Enterprise features on request. We found no public information on where standard tiers are hosted, on subprocessors, or on a standard data processing agreement; a custom data processing agreement appears only as an Enterprise option. 2 4
The Drafted Generalist
The company behind it is plainly German — ECOMPLY GmbH in Munich, registered at Amtsgericht München — and Enterprise can run on-premise or in your own cloud, on request. We found no public information on where the standard tiers host, on subprocessors, or on a standard data processing agreement for regular customers; only a custom DPA on Enterprise appears. 2 4 5
The Lead Auditor
The contracting entity is the German ECOMPLY GmbH in Munich with a published imprint and a captured privacy policy, but hosting location and subprocessors are not stated on the pages we read, and a data processing agreement is not confirmed on the vendor's own pages — a custom one is listed only as an Enterprise feature. On-premise and customer-operated cloud hosting exist, but as top-tier options on request. 2 4 5
The IT Integrator
A Munich-registered German GmbH is proven down to the commercial register entry, and on-premise or customer-operated cloud hosting plus a custom DPA exist — but only as Enterprise-on-request features. Hosting location and the subprocessor chain for the standard tiers are unknown on the captured pages, so the chain is only half documented. 2 4
The Skeptic
The contracting entity is proven German — ECOMPLY GmbH, Munich, commercial register HRB 237932, VAT ID DE316542294 — and on-premise or customer-operated cloud hosting is offered, but only as an Enterprise plan item on request. We found no public information on the default hosting location, a subprocessor list, or a standard data processing agreement on the vendor's own captured pages; a custom processor contract appears only as another Enterprise line item. 2 4 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 pricing page publishes the tier architecture in detail — employee, user, department, location, processing-activity and audit-count limits per edition, included onboarding hours, a free trial, and the VAT note 'Alle Preise zzgl. Mehrwertsteuer.' — with Enterprise extras on request. We found no public price figures for any edition and no billing period, so a buyer cannot compute the real invoice from the pages read. 2
The In-House Counsel
The pricing page publishes tier boundaries in unusual detail — user, employee, processing-activity, department, location and audit-per-year limits, onboarding hours, a free trial and VAT treatment quoted as "Alle Preise zzgl. Mehrwertsteuer." — but we found no price figures on the captured pages, so a buyer cannot compute the invoice, and Enterprise features are on request. 2
The Drafted Generalist
The pricing page shows real structure: two named tiers with employee, register, user, department and location limits, included onboarding hours, a free trial, and VAT treatment stated exactly as 'Alle Preise zzgl. Mehrwertsteuer.' We found no public information on an actual price figure for any tier, so I still cannot estimate an invoice for my 80 people without talking to sales. 2
The Lead Auditor
The pricing page is unusually explicit about boundaries — Small Business caps at 99 employees, 60 processing activities, 2 users and 25 audits a year, Medium Business at 400, 150, 10 and 300, with onboarding hours itemised and VAT treatment stated as "Alle Preise zzgl. Mehrwertsteuer." — but no euro figure for any edition appears on the captured pages, and Enterprise is by request. The buyer knows the shape of the invoice, not its amount. 2
The IT Integrator
The pricing page does publish sharp tier boundaries — employees, processing activities, users, locations, audits per year, included onboarding hours and VAT treatment. But no monetary figure appears anywhere I read, so a buyer still cannot compute an invoice without a sales conversation. 2
The Skeptic
The pricing page is unusually concrete about boundaries — employee, user, department, location and processing-activity limits per tier, audits per year, included onboarding hours, a free trial, and 'Alle Preise zzgl. Mehrwertsteuer'. Yet we found no public price figures or billing period in the captured facts, and the Enterprise plan is request-based, so a buyer still cannot compute the real invoice from what was captured. 2
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 | 4 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?On-premise and customer-operated cloud hosting are listed only as features of the Enterprise plan, obtained on request, not offered in the standard self-serve tiers. |
1/1 pts | 2 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about ECOMPLY
Is ECOMPLY European?
Yes. whats-best.ai classifies ECOMPLY as EU-Made. Its vendor, ECOMPLY GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does ECOMPLY store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does ECOMPLY have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to ECOMPLY?
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: ECOMPLY alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting options. On-premise and customer-operated cloud hosting are listed only as features of the Enterprise plan, obtained on request, not offered in the standard self-serve tiers.
- 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.
- We found no public information on compliance on the pages we read (ecomply.io, ecomply.io/de/preise, ecomply.io/de/product, ecomply.io/de/impressum, ecomply.io/de/datenschutzerklarung, ecomply.io/en/features/records-of-processing-activities and 5 more). If the vendor publishes it somewhere else, send us the page. 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.ecomply.io Checked 16 Nov 2026 Details →
- 2 Vendor pricing page www.ecomply.io Checked 16 Nov 2026 Details →
- 3 Product page www.ecomply.io Checked 16 Nov 2026 Details →
- 4 Imprint www.ecomply.io Checked 16 Nov 2026 Details →
- 5 Privacy policy www.ecomply.io Checked 16 Nov 2026 Details →
- 6 Records & DPIA depth — found from sitemap www.ecomply.io Checked 16 Nov 2026 Details →
- 7 Records & DPIA depth — found from sitemap www.ecomply.io Checked 16 Nov 2026 Details →
- 8 Data subject rights & incidents — found from sitemap www.ecomply.io Checked 16 Nov 2026 Details →
- 9 Data subject rights & incidents — found from sitemap www.ecomply.io Checked 16 Nov 2026 Details →
- 10 Audit readiness & evidence — found from sitemap www.ecomply.io Checked 16 Nov 2026 Details →
- 11 Audit readiness & evidence — found from sitemap www.ecomply.io Checked 16 Nov 2026 Details →