preeco | datenschutz
EU-Made Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
preeco | datenschutz, data protection management software for the GDPR from preeco GmbH & Co. KG in Ulm, scores strongest on privacy management at 8 to 9: an Art. 30 record model with graphical relationship views, automatic contract-to-recipient matching and multi-client setups in under three minutes. Rights and incidents score 8 throughout on automatic one-month and 72-hour clocks, nine notification templates. Sovereignty scores 8 to 9 on hosting exclusively in Hetzner data centres in Nuremberg and Falkenstein with subprocessors Hetzner of Germany and UpCloud of Finland; audit readiness 8 to 9 on immutable, checksum-verified revisions. Framework coverage splits at 7 to 8: judges at 8 credit the German layer — BDSG, BayLDA, BSI reports — and a maintained AI Act module; judges at 7 hold back over no public information on ePrivacy/TTDSG or Swiss nDSG. Weak points recur: pricing transparency scores 2 — no public price figures, pricing deferred to the 30-minute demo — and integrations and automation score 6, with different captured figures for the public API, single sign-on only on Private Cloud and On-Premises, and no public information on webhooks or SCIM.
Speaks for it
- The Article 30 register links systems, safeguards and data processing agreements to each processing activity in a graphical relationship view
- The one-month rights deadline and the 72-hour breach clock are monitored automatically, with nine ready notification templates covering Article 33, Article 34 and BSI reports
- Every approval freezes an immutable revision with SHA-256 checksums and colour-coded comparison, alongside a filterable activity log
- External data protection officers run hundreds of clients with new tenants set up in under three minutes and per-client module activation
- A documented European chain: German vendor in Ulm, hosting exclusively in Hetzner data centres in Nuremberg and Falkenstein, subprocessors Hetzner of Germany and UpCloud of Finland, and a published Article 28 data processing agreement that can be concluded online
Held against it
- No public price figures on the pages — pricing transparency scores 2, with the invoice left to a 30-minute demo conversation
- The captured pages give different figures for the public API, and single sign-on over SAML2 is confined to Private Cloud and On-Premises
- No public information on webhooks, SCIM provisioning, or directory and ticketing connectors for this product
- No public information on Swiss nDSG or ePrivacy/TTDSG coverage, and no public information on a dedicated read-only auditor access role
- The pages state preeco itself holds no ISO 27001 certification, and the optional AI, off by default, can send document data to a customer-chosen provider
Best for
- You are an external data protection officer managing many client organisations and need strict tenant separation, one login and per-client module activation
- You work under GDPR and German national duties and need authority-facing outputs — status reports, procedure files, the BayLDA questionnaire — at the push of a button
- You need a change history you can defend to supervisory authorities, with immutable revisions, SHA-256 checksums and a filterable activity log
- You are migrating an existing Word or Excel register and want AI-assisted import into structured fields
Avoid if
- You need to know the price before talking to sales — the pages publish the license structure but no price figures
- You depend on single sign-on in the standard cloud tier — the hosting comparison marks it unavailable for the standard Cloud variant
- You are a smaller organisation counting on the on-premises variant — the pages state it generally serves only the public sector or enterprise segment
- You require the vendor itself to hold ISO 27001 certification — the pages state the certification covers the Hetzner data centres, not preeco
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 4.5 of 5 |
| Data subject rights & incidents | 4 of 5 |
| Privacy regime coverage | 3.5 of 5 |
| Audit readiness & evidence | 4 of 5 |
| Integrations & automation | 3 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 1 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
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
The In-House Counsel
The record model is genuinely connected: each processing activity carries its systems, safeguards and data processing agreements as a graphical relationship view, legal bases sit in the same structured form, and a threshold analysis derives the Article 35 need from the record itself, which an external data protection officer can run across hundreds of clients. Deletion classes hang off the processing activities, and status reports, procedure files and the Bavarian supervisory-authority questionnaire come out at a button push. That approaches a system of record; I hold a point back because the DPA-to-record linkage rests on name matching with a manual step for everything that does not match. 16 21 11 16
The Drafted Generalist
External data protection officers can run hundreds of clients with new tenants set up in under three minutes, and every approval freezes an immutable revision. I found no public information on a report proving TOM coverage across the whole register, which is the only thing keeping it off the very top. 12 2 2 16 7 16
The Lead Auditor
The Art. 30 register is a structured form covering purpose, data categories, data subjects, legal bases, recipients, third-country transfers and retention periods, with DOCX/XLSX import and AI-supported drafting; DSFA carries a threshold analysis and an Art. 35 necessity assessment, AVV management runs with an online signature workflow and automatic name matching to data recipients, and TOMs are versioned and linked to processing activities in a graphical relationship view. Multi-tenant operation for external data protection officers with new tenants in under three minutes and authority outputs (status reports, procedure files, BayLDA questionnaire) at the push of a button sits right below the top anchor: the pages themselves state that missing contract connections are established by hand, so the record does not fully drive processor management. 16 2 16 17 11 15
The IT Integrator
The record model is genuinely connected: each processing activity shows its systems, safeguards and data processing agreements in a graphical relationship view, contracts are matched to data recipients automatically, and a built-in screening analysis on the record drives the Art. 35 DPIA necessity assessment. Multi-client capability for external data protection officers is real — new tenants in under three minutes with strict separation — and status reports, procedure files and the BayLDA questionnaire come out at the push of a button. Where names do not match, missing contract links are still closed by hand, which keeps this just short of a fully self-driving system of record. 16 2 11 16 17 12
The Skeptic
The Art. 30 register enforces every mandatory field including legal bases, and each processing activity carries a graphical view of its systems, safeguards and data processing agreements, with automatic name matching linking contracts to data recipients and every link and unlink recorded. DPIA necessity is assessed inside the record with an optional pre-assessment (Schwellwert-Analyse), deletion classes derive rules from the linked activities, and external data protection officers run hundreds of clients with per-client module activation and client setup in under three minutes. It sits just short of the top because I found no public information showing the register flagging TOM coverage gaps on its own. 16 2 17 16
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
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
The In-House Counsel
This is the operational half done properly: the one-month Article 12 clock and the 72-hour Article 33 clock are both monitored automatically, with a clear deadline status per report and a documented justification when a clock is missed. Nine templates cover the initial, follow-up and final report to the authority, the Article 33(2) processor notice, the Article 34 notification of data subjects and the German BSI reports — exactly the workflow a breach has to produce — and requests arrive through embeddable web forms with identity verification documented and replies sent from the system via a one-time encrypted link. Deletion rules are tied to the register, though the documentation of execution itself is thinner. 18 18 15 2
The Drafted Generalist
Requests arrive through embeddable website forms, identity verification is documented with the request time, the one-month Article 12 clock and the 72-hour breach clock are monitored automatically, and nine ready templates cover the authority and data subject notifications plus the BSI reports. Replies go out from the system via a one-time link to an encrypted page, rejection reasons are recorded, and deletion rules derive from the linked processing activities with deadlines tracked. I found no public information showing automatic proof that an executed deletion actually happened, which keeps it a step below the top. 15 2 18 19 18
The Lead Auditor
Requests run as operations: embeddable web forms with identity verification documented including time of receipt, automatic monitoring of the one-month Art. 12(3) deadline, response by email from the system via a one-time link to an encrypted page, rejection reasons recorded, and requests linked to the affected processing activities. Breaches carry automatic 72-hour monitoring, a graphical risk matrix and nine templates covering Art. 33 and Art. 34 as well as BSI notifications, each with an explicit deadline status and documented justification if missed; deletion concepts derive rules with deadlines, procedures and responsibilities from linked processing activities, though we found only thin evidence on proof of executed deletion. 18 18 19 18 2
The IT Integrator
Requests arrive through embeddable web forms, identity verification and rejection reasons are documented with timestamps, the one-month Art. 12(3) deadline is monitored automatically, and replies leave the system by a one-time link to an encrypted page rather than by plain email. Breaches carry the 72-hour Art. 33 clock, a graphical risk matrix and nine ready notification templates covering Art. 33, Art. 34 and the German BSI reports, while deletion classes are tied to processing activities with deadlines, procedures and responsibilities. We found no public information on automated proof that a deletion was executed — the closest is erasure logs that can be attached to tasks. 18 18 19 15 2 21
The Skeptic
Requests arrive through embeddable web forms, identity verification is documented with the time of the request, the one-month Art. 12(3) deadline is monitored automatically with proactive overdue warnings, and replies go out as a one-time link to an encrypted page rather than as the message itself by email. Breaches get the 72-hour clock, a likelihood-by-severity risk matrix and nine ready templates covering Art. 33, Art. 34 and BSI reports, each with its own deadline status and a documented justification when missed. Deletion rules are derived from linked processing activities and their deadlines tracked, but I found no public information on automated deletion execution with proof it happened — erasure logs surface only as task attachments. 2 18 19 21 23 18
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 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
The In-House Counsel
GDPR is fully built out and the German layer is real rather than cosmetic: BDSG in the data protection officer self-check, the Bavarian authority questionnaire, BSI reporting duties inside the breach templates, and a maintained AI Act module with an AI system register, compliance checks and AI-specific measures. UK entities can be kept side by side in one system. I found no public information on Swiss nDSG or ePrivacy/TTDSG handling, and updates are promised as timely without a published cadence tied to legal changes, so I stop short of the top band. 15 2 20 18 1
The Drafted Generalist
GDPR is covered end to end and the German market is properly served: a BDSG self-check with legal references, the BayLDA questionnaire, BSIG breach report templates, a German variant for public authorities, an AI Act module with its own AI-system register, and Schrems II transfer assessments. EU and UK entities sit side by side in one system, and the pages promise prompt implementation of NIS2, DORA and GDPR updates as part of the subscription. I found no public information on ePrivacy/TTDSG duties or the Swiss nDSG, so it is not a full multi-regime map. 2 15 2 18 1 20
The Lead Auditor
GDPR is operationalised end to end and the German national layer is present — the data protection officer self-check names duties under the German BDSG, breach templates cover reporting under the BSIG, and EU and UK entities can be kept side by side in one system. The EU AI Act is covered as maintained content (risk classification, own AI system register, TOMs for AI applications) and the vendor commits to prompt updates for NIS2, DORA and GDPR changes on an approximately monthly release cadence; we found no public information on ePrivacy/TTDSG or the Swiss nDSG. 20 2 18 1 3 1
The IT Integrator
GDPR is fully operationalised with Art. 30, 35, 33/34, 15-22, 26 and 28 modules, joined by German national duties — a BDSG-based data protection officer self-check, BSI breach reports under Sections 25 and 32 BSIG, the BayLDA questionnaire — plus an EU AI Act module with its own AI system register, Schrems II transfer impact assessments, and EU and UK entities held side by side in one system. Updates land roughly monthly, with NIS2, DORA and GDPR changes promised promptly. We found no public information on ePrivacy/TTDSG or Swiss nDSG coverage. 20 15 18 2 3 1
The Skeptic
GDPR is the backbone and the German layer is real: a BDSG officer self-check with a legal reference per point, the BayLDA questionnaire, a public-administration language variant, BSI reporting duties and an EU AI Act module with its own system register, risk classes and compliance checks, on one platform updated roughly monthly. Beyond that I found no public information on Swiss nDSG, ePrivacy/TTDSG, or UK-specific templates beyond keeping EU and UK entities side by side in one system. The "rechtlich geprüfte" templates and text modules name no lawyer or firm, and GDPR updates being "zeitnah umgesetzt" is a promise without a stated legal-content cadence — the kind of claim I want a name behind. 1 18 23 7 20
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
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
The In-House Counsel
Immutable revisions with SHA-256 checksums on every approval, colour-coded version comparison and an automatic activity log of document changes and account administration give me a change history I can defend, and the integrity checks catch later tampering. Status reports, procedure files and the authority questionnaire are generated at the push of a button, with dedicated data protection officer reports across all clients and compliance KPIs on approved, in-progress and overdue documents. The audit module runs on catalogs including BSI IT-Grundschutz, CISIS12 and VdA ISA as paid options; I found no public information on dedicated read-only auditor access. 15 16 23 22
The Drafted Generalist
Every approval freezes an immutable revision with SHA-256 checksums and colour-coded comparison, and the automatic log captures document and user-account actions with timestamps, filterable by document, period and person. Status reports, procedure files and data protection officer reports with compliance metrics are produced at a click and described as directly usable as evidence for authorities and management. I found no public information on a dedicated read-only auditor login, which is what keeps it from the top step. 23 23 15 16
The Lead Auditor
This is the strongest part of the system: every approval produces an immutable revision as PDF/ZIP or HTML with a stored SHA-256 checksum, colour-coded comparison of two states, and an automatic activity log of document and user-account actions filterable by document, time period and user. Status reports, procedure files and the BayLDA questionnaire are generated at the push of a button and described as directly usable as evidence for supervisory authorities and management, with data protection officer reports across tenants and schedulable recurring reports; we found no public information on a dedicated read-only auditor access role. 2 23 23 16 22
The IT Integrator
Every approval freezes an immutable revision as PDF/ZIP or HTML with a SHA-256 checksum and a colour-coded diff, and an automatic activity log records document and user-account actions, filterable by document, period and user. Status reports, procedure files and the BayLDA questionnaire generate at the push of a button, data protection officer reports run cross-tenant, and recurring reports are schedulable with email notification. We found no public information on dedicated read-only auditor access. 15 23 15 16
The Skeptic
Every approval freezes an immutable revision as PDF/ZIP or HTML with stored SHA-256 checksums and color-coded comparison, and the automatic log captures document actions and user-account administration with timestamp, user and action — including every link and unlink. Status reports, procedure files and the BayLDA questionnaire generate at the push of a button, data protection officer reports run across tenants, recurring reports ship by email, and audits produce reports with all questions, answers and comments in a professional layout. I found no public information on read-only auditor access, and the dashboards count documents by status rather than showing a continuous per-regime compliance state, which keeps it off the top step. 22 23 17 23 16
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
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
The In-House Counsel
Import of existing records as Word or Excel with AI mapping into the structured fields, embeddable web forms, recurring review reminders and an MCP server that lets an AI assistant query processing activities under the application's own access rights are all documented. The captured pages give different pictures of the API: some state that no public REST interface is available, with customer-specific endpoints only on Private Cloud and On-Premises, while later pages document an interactive API with OpenAPI file, personal tokens and a rate limit. Single sign-on via SAML2 exists only on Private Cloud and On-Premises, and I found no public information on webhooks or SCIM provisioning. 16 2 2 24 15
The Drafted Generalist
My daily reality is covered: existing Word and Excel registers import with the AI mapping the content into the structured fields, reminders arrive by email and as dashboard tasks, web forms for requests, breaches, consents and data processing agreement signing embed with an HTML snippet, and an MCP server lets an AI assistant query the records under the same access rights. The captured pages give different figures for the public API — some state that a public REST API is currently unavailable, while the newest product page shows interactive OpenAPI documentation with personal API tokens. Single sign-on appears only for Private Cloud and On-Premises, and I found no public information on webhooks or SCIM provisioning. 2 24 2 15 2
The Lead Auditor
The captured pages give different figures on a public REST API: earlier captures describe a closed system without one for the data protection product, a later capture shows interactive API documentation with an OpenAPI file, personal tokens and rate limits, and custom endpoints are offered on Private Cloud and On-Premises. Single sign-on over SAML2 is available only on Private Cloud and On-Premises, while AI assistance with mandatory human review, an MCP server connection for AI assistants, DOCX/XLSX import with AI mapping of existing records, embeddable web forms, automatic reminders per processing activity and scheduled reports are documented; we found no public information on webhooks, SCIM provisioning or directory and ticketing connectors for this product. 2 2 3 24 15 16
The IT Integrator
From my seat this is the weak flank: the documented import is a DOCX or XLSX upload of an existing register that the AI maps to structured fields, single sign-on via SAML2 is confined to Private Cloud and On-Premises while the comparison table marks it unavailable in the standard cloud, and we found no public information on directory synchronisation, SCIM provisioning or webhooks. The captured pages give different figures for the API — one set describes a closed system with no public REST API and customer-specific endpoints only on Private Cloud and On-Premises, a later capture shows interactive OpenAPI documentation, personal API tokens with a 60-request-per-minute limit, and an MCP server letting AI assistants query processing activities and export revisions. Reminders, task assignment and approval workflows with human review of AI suggestions are solidly documented, so the automation is real even where the estate feed is a file drawbridge rather than a sync. 2 2 3 15 24 16
The Skeptic
The captured pages give different figures for API access: several captures describe a closed system with no public REST API currently, while a later capture of the same product documents personal API tokens at up to 60 requests per minute with an OpenAPI file and interactive documentation, and the named connectors (CMDB, ticketing, monitoring) appear only on the information security product's page. What is solid: DOCX/XLSX import with AI mapping into structured fields, automatic contract-to-recipient matching, embeddable web-form widgets, and an MCP server letting external AI assistants query processing activities under the application's own access rights. But the hosting comparison marks SAML2 single sign-on "Nein" for the standard cloud tier, and I found no public information on SCIM provisioning, webhooks, or directory and HR connectors for this product. 2 15 2 3 24
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 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
The In-House Counsel
The chain is documented end to end: a German company registered in Ulm, hosting on the vendor's cluster in ISO 27001-certified Hetzner data centres in Nuremberg and Falkenstein, no third-country transfers, and a published Article 28 data processing agreement with downloadable technical and organisational measures, a two-week subprocessor change notice and deletion with certificate on termination. An On-Premises option exists, though the pages themselves say it involves significant effort and normally serves the public sector or enterprise segment. Two points for contract review: the company itself is not ISO 27001 certified — only the data centres are — and the optional AI, off by default, sends document data to a provider the customer chooses. 9 10 15 5
The Drafted Generalist
The chain is European and named: a German company in Ulm, hosting exclusively in ISO-27001-certified Hetzner data centres in Nuremberg and Falkenstein with daily encrypted off-site backups, a published data processing agreement with a subprocessor list and a downloadable TOMs annex that can be signed online, and the stated position that no third-country transfers occur. The named subprocessors — Hetzner in Germany and UpCloud in Finland — both sit in the EU. An on-premises option exists, but the captured pages describe it as usually reserved for the public sector or the Enterprise segment, which an 80-person private firm like mine cannot count on. 15 9 10 5 6
The Lead Auditor
The chain is provably European: a German entity registered at the district court in Ulm, development, operation and support exclusively in Germany, hosting on named ISO 27001 data centres of Hetzner in Nuremberg and Falkenstein with EU-only processing, and named subprocessors Hetzner (Germany) and UpCloud (Finland), both in the EU. The Art. 28 data processing agreement is published with online conclusion and the TOMs downloadable, and an on-premises option exists — the pages state it is generally available only to the public sector or enterprise segment; the optional AI integration, off by default, can send document data to a provider chosen by the customer. 5 6 15 9 10 10
The IT Integrator
The chain is European end to end as documented: a German vendor in Ulm, hosting exclusively in Hetzner data centres in Nuremberg and Falkenstein, and subprocessors Hetzner (Germany) and UpCloud (Finland) with two weeks' written notice of changes. The Art. 28 data processing agreement is published and can be concluded electronically, the technical and organisational measures are downloadable, and an on-premises variant exists — though the vendor itself states it is costly and in general available only to the public sector or enterprise customers. The optional AI features, off by default and run with the customer's own key, can send document data to a provider of the customer's choosing. 15 6 10 15 9
The Skeptic
A German entity in Ulm — the imprint registers preeco GmbH at Amtsgericht Ulm while the vendor summary styles it a GmbH & Co. KG — hosts exclusively in named Hetzner data centres in Nürnberg and Falkenstein on 100 percent green power, with a published, online-signable Art. 28 DPA, downloadable TOMs, a two-week subprocessor change notice and a subprocessor list naming only Hetzner and UpCloud of Finland, all within the EU. An on-premises variant keeps data in the customer's own data centre, though the pages state it is usually reserved for the public sector or enterprise segment. Two caveats a buyer should weigh: preeco itself holds no ISO 27001 — only its data centres do, stated openly — and the optional AI features, off by default, can route document data to a customer-chosen provider such as OpenAI. 9 9 10 5 6
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
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
The In-House Counsel
No euro figure appears on the captured pages; pricing is handled in the 30-minute demo conversation. What is public is the structure — the license runs per employees, modules and hosting variant rather than per organisation, an annual subscription with updates and support included, no setup fees and no cancellation periods — and the optional paid extras are named (BSI, CISIS12 and VdA ISA audit catalogs, DeepL, premium support, migration). That lets a buyer frame the questions, but not compute the invoice. 16 2 3 15
The Drafted Generalist
I found no public price figures, so the real invoice stays a sales conversation: the license is said to depend on employees, modules and hosting variant rather than the number of organizations, there are no setup fees, and updates, maintenance and support are included in an annual subscription. That structure information is genuinely helpful, but the optional paid pieces — the BSI audit catalogs, DeepL translation, data migration, premium support — also carry no public prices, and I cannot compute an invoice from what is published. 3 2 3 16
The Lead Auditor
We found no price figures on any captured page — pricing is positioned as a topic for the 30-minute demo with sales — so no invoice can be computed from public information alone. What is public is the structure: the license depends on employees, modules and hosting variant and not on the number of organisations, with no setup fees and no cancellation periods, updates, maintenance and support included in a yearly subscription, and named optional paid add-ons such as premium support, data migration, trainings, the BSI IT-Grundschutz, CISIS12 and VdA ISA audit catalogs and DeepL translation. 16 2 3 3 3
The IT Integrator
We found no public prices at all — the captured page defers figures to a 30-minute demo promising "honest answers from data protection experts on hosting, AI, migration and pricing". The pages do publish the invoice structure: the licence follows employees, modules and hosting variant rather than the number of organisations, with no setup fees and no cancellation periods, and the optional paid items — BSI IT-Grundschutz, CISIS12 and VdA ISA audit catalogs, DeepL translation, premium support, migration and trainings — are at least named. A buyer still cannot compute a single euro of the actual invoice from public pages. 16 2 3 2 3
The Skeptic
The captured pages state no prices at all; the buyer is offered a 30-minute demo promising "Honest answers from data protection experts on hosting, AI, migration and pricing", and the support FAQ even poses the premium-support cost question with no figure on the page. Public pages do name the variables — license by employees, modules and hosting variant, not by the number of organisations, with no setup fees or cancellation periods, an annual subscription including updates, maintenance and support, and named optional extras such as audit catalogs, DeepL, migration and training. That tells you what the invoice depends on but not what it will be, so this sits just above the fully opaque end. 3 8 16 2
European sovereignty — proven facts
4 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
unverified
Why unverified?Das Impressum nennt das Registergericht, aber nicht wörtlich das Wort „Deutschland“; das Land wird aus dem Registergericht Ulm abgeleitet (die Datenschutzerklärung [S13] nennt „89077 Ulm Deutschland“ als Anschrift). |
2/2 pts | 5 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 23 Aug 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 — Transfer impact assessment. 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.
- Weak sourcing — Legal entity. Das Impressum nennt das Registergericht, aber nicht wörtlich das Wort „Deutschland“; das Land wird aus dem Registergericht Ulm abgeleitet (die Datenschutzerklärung [S13] nennt „89077 Ulm Deutschland“ als Anschrift).
- Weak sourcing — Hosting location. 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.
- Weak sourcing — Hosting options. 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.
- 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.
- 271 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
- 48 hosting 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
- 36 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
- 26 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
- 12 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
- 12 legal 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
- 10 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
- 3 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The oldest source behind this page was captured 90 days ago, past our 90-day ceiling. It is re-checked on a schedule; until then every claim carries the date it was read. 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 (25)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 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 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 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 About page www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Imprint www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 6 Privacy policy www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 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 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 Hosting variants page www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 16 Sep 2026 Details →
- 10 Published DPA (AVV) for cloud customers www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 11 Multi-entity use case page www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 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 MFA documentation www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 14 Access rights system documentation www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 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 Records & DPIA depth — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 17 Records & DPIA depth — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 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 Data subject rights & incidents — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 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 Privacy regime coverage — found from sitemap www.preeco.de Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 22 Audit readiness & evidence — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 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 Integrations & automation — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 25 Integrations & automation — found from sitemap www.preeco.de Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →