preeco | datenschutz

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

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

by preeco GmbH & Co. KG · www.preeco.de

Compare with caralegal → Compare with audatis MANAGER → Report an error on this page Is this your product? →

Link to this page

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

preeco | datenschutz at a glance

Vendor
preeco GmbH & Co. KG
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 preeco | datenschutz 3.5/5, the mean of 6 judges. preeco | datenschutz, data protection management software for the GDPR from preeco GmbH & Co. how scores are made
As of
Vendor pages captured 23 Aug 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

preeco | datenschutz alternatives, European ones first →

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

The External DPO

Weighted verdict

Carries thirty client mandates and bills by the hour they save. Optimizes for multi-client capability, reusable templates, a RoPA that drives the rest, and client-ready reports. Rejects single-tenant tools that treat the consultancy as thirty separate customers.

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

Scored by The External DPO

Panel median The External DPO 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 External DPO
Records & DPIA depth 4.5 of 5 4.5 of 5
Data subject rights & incidents 4 of 5 4 of 5
Privacy regime coverage 3.5 of 5 4 of 5
Audit readiness & evidence 4 of 5 4 of 5
Integrations & automation 3 of 5 3 of 5
European sovereignty 4 of 5 4.5 of 5
Pricing transparency 1 of 5 1 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 External DPO

This is the working model I want: the record of processing drives everything, with systems, TOMs, processors and legal bases linked per activity in a graphical relationship view, the DPIA necessity assessment derived from the record itself, and data processing agreements matched to data recipients automatically by name. Multi-client operation is explicit — new clients in under three minutes, per-client module activation, one login — with legally reviewed templates reusable across mandates and authority-facing outputs like the BayLDA questionnaire at the push of a button. 16 16 2 17 11 1 23

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 External DPO

Rights handling reads as end-to-end operations: web-form intake, identity verification documented with the time of the request, rejection reasons recorded, the one-month deadline under Art. 12(3) automatically monitored, and replies sent from the system via one-time links to an encrypted page. Breaches carry the 72-hour clock, severity classification and a risk matrix, with nine ready templates covering authority, controller and data subject notifications; deletion concepts derive rules tied to processing activities, but I found no public information on automated deletion execution beyond task attachments such as erasure logs. 18 19 18 18 21

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 External DPO

GDPR plus the German market specifics run deep — BDSG in the DPO self-check, a dedicated German authority variant, the BayLDA questionnaire and BSI reporting duties — and the EU AI Act is live content with its own system register rather than a promise. UK entities sit side by side in one system and roughly monthly updates ship regime changes automatically; I found no public information on ePrivacy/TTDSG or Swiss nDSG coverage. 18 3 2 20 15 1

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 External DPO

Every approval freezes an immutable revision with SHA-256 checksums and a colour-coded comparison, the activity log captures document and user-administration actions with timestamps, and status reports, procedure files and the BayLDA questionnaire generate at a click — branded per client, schedulable, with cross-tenant DPO reports. That is client-ready evidence work; I found no public information on dedicated read-only access for auditors. 2 23 23 15

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 External DPO

The estate feed is thin by design: several captured pages describe a closed system without a public REST interface, while one product page shows interactive OpenAPI documentation with personal API tokens — the captured pages give different statements here, and single sign-on arrives only on Private Cloud and On-Premises; I found no public information on webhooks, SCIM or directory and ticketing connectors for the privacy product. What is documented earns credit: DOCX and XLSX record import with AI field mapping, an MCP server exposing processing activities and revision exports with application-level access rights, embeddable web forms, automatic contract-to-recipient matching and schedulable reports. 2 15 24 2 16 17 23

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 External DPO

The whole chain sits in Germany and on paper: a German entity in Ulm, hosting exclusively in named Hetzner data centres in Nürnberg and Falkenstein, subprocessors Hetzner and UpCloud (Finland) both inside the EU, no third-country transfers, and the data processing agreement with TOMs published and signable online. An on-premises option exists, though the pages state it is generally reserved for the public sector or enterprise customers, and the optional AI feature — off by default — can send document data to a provider of the customer's choosing. 9 15 6 10 15 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 External DPO

No figures anywhere: the pages point pricing questions to a personal demo, so the invoice remains a sales conversation. Credit for structure — the license is public as employees, modules and hosting variant, explicitly not per client organization, which matters enormously to a multi-mandate practice — with no setup fees, an annual subscription including updates and support, and the paid add-ons named (audit catalogues, DeepL translation, premium support, migration, training). 16 2 3 3 15

Report an error

European sovereignty — proven facts

4 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?

Die Zusicherung gilt für Cloud und Private Cloud; On-Premises läuft im eigenen Rechenzentrum des Kunden, und die optionale, standardmäßig deaktivierte KI-Integration kann Dokumentdaten an einen vom Kunden gewählten Anbieter senden.

4/4 pts 9 Report an error
Hosting options Self-hostable unverified
Why unverified?

Die Seite schränkt ein, dass On-Premises mit erheblichem Aufwand verbunden ist und in der Regel nur im öffentlichen Bereich oder im Enterprise-Segment zur Verfügung steht.

1/1 pts 9 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 needed, no transfer outside the EU/EEA unverified
Why unverified?

Die Aussage bezieht sich auf das preeco-Hosting; die optionale, standardmäßig deaktivierte KI-Integration kann Dokumentdaten an einen vom Kunden gewählten Anbieter senden, und die TIA-Funktion des Produkts ist ein Kundenfeature, nicht die eigene Bewertung des Anbieters.

1/1 pts 9 Report an error

Questions about preeco | datenschutz

Is preeco | datenschutz European?

Yes. whats-best.ai classifies preeco | datenschutz as EU-Made. Its vendor, preeco GmbH & Co. KG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does preeco | datenschutz store data?

preeco | datenschutz 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 preeco | datenschutz have a free plan?

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

What are the best alternatives to preeco | datenschutz?

As of 19 Nov 2026, the panel rates caralegal (3.5/5), Dastra (3.5/5) and Data Legal Drive (3/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 caralegal (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: preeco | datenschutz 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 (25)

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

  1. 1 Vendor homepage www.preeco.de Checked 16 Nov 2026 +6 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026, 15 Sep 2026, 31 Aug 2026, 24 Aug 2026 Details →
  2. 2 Data protection product page www.preeco.de Checked 16 Nov 2026 +5 earlier captures: 19 Oct 2026, 5 Oct 2026, 16 Sep 2026, 15 Sep 2026, 31 Aug 2026 Details →
  3. 3 Information security product page www.preeco.de Checked 16 Nov 2026 +6 earlier captures: 19 Oct 2026, 5 Oct 2026, 16 Sep 2026, 31 Aug 2026, 24 Aug 2026, 23 Aug 2026 Details →
  4. 4 About page www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 Imprint www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  6. 6 Privacy policy www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  7. 7 GDPR software page www.preeco.de Checked 16 Nov 2026 +7 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026, 16 Sep 2026, 11 Sep 2026, 31 Aug 2026, 24 Aug 2026 Details →
  8. 8 Product documentation library www.preeco.de Checked 16 Nov 2026 +4 earlier captures: 2 Nov 2026, 5 Oct 2026, 31 Aug 2026, 24 Aug 2026 Details →
  9. 9 Hosting variants page www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 16 Sep 2026 Details →
  10. 10 Published DPA (AVV) for cloud customers www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  11. 11 Multi-entity use case page www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  12. 12 AI-assisted GDPR use case page www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  13. 13 MFA documentation www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  14. 14 Access rights system documentation www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  15. 15 Full product specification (Leistungsbeschreibung) www.preeco.de Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026 Details →
  16. 16 Records & DPIA depth — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  17. 17 Records & DPIA depth — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  18. 18 Data subject rights & incidents — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  19. 19 Data subject rights & incidents — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  20. 20 Privacy regime coverage — found from sitemap www.preeco.de Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026 Details →
  21. 21 Privacy regime coverage — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
  22. 22 Audit readiness & evidence — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  23. 23 Audit readiness & evidence — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
  24. 24 Integrations & automation — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  25. 25 Integrations & automation — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →