Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by caralegal GmbH · caralegal.eu

Compare with preeco | datenschutz → Compare with Akarion GRC Cloud → Report an error on this page Is this your product? →

Link to this page

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

caralegal at a glance

Vendor
caralegal GmbH
Headquarters
Incorporated in Germany source, captured 26 Oct 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 caralegal 3.5/5, the mean of 6 judges. caralegal, a data protection management platform from caralegal GmbH in Berlin, scores highest where its record of processing is the spine: privacy management runs 8–9, with records synchronising automatically into impact assessments, measures and vendor management, the deletion concept generated from the register, and processor agreements through to the register dispatched to the authority at a button press. how scores are made
As of
Vendor pages captured 23 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

caralegal alternatives, European ones first →

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

The panel's verdict

caralegal, a data protection management platform from caralegal GmbH in Berlin, scores highest where its record of processing is the spine: privacy management runs 8–9, with records synchronising automatically into impact assessments, measures and vendor management, the deletion concept generated from the register, and processor agreements through to the register dispatched to the authority at a button press. The weakest criterion is audit readiness, and it is where the bench genuinely splits, 4 to 7. The rationales describe the same one-click audit and vendor reports with a management summary; the divide is revision safety: two judges score 4 because we found no public information on versioned records, change history or read-only auditor access, while the external data protection officer's 7 weighs client-ready output first. Sovereignty spreads 4–6: a German contracting entity and hosting in an ISO/IEC 27001-certified Deutsche Telekom data centre in Frankfurt are stated on the vendor's own pages, but we found no public information on a processing agreement or subprocessor list for the platform itself. Pricing transparency scores 6.

Report an error

Speaks for it

  • The record of processing synchronises automatically with impact assessments, TOMs and vendor management, and the deletion concept is generated from the register itself.
  • Everything from processor agreements to the register can be sent to the supervisory authority at a button press.
  • More than 200 legally reviewed processing-activity templates and 150 vendor templates are included, and Art. 30(2) processor records run in the same workflow.
  • The German Standard Data Protection Model 3.1 is embedded with seven guarantee goals preloaded, alongside assessment templates for NIS2, DORA and AI compliance in every plan.
  • Three of four tiers carry public monthly prices — Essential ab 79€ pro Monat, Professional 349 €, Corporate 749 € — with unlimited users and documents in every plan and a 50% nonprofit discount.

Report an error

Held against it

  • We found no public information on revision-safe change history, versioned records or read-only auditor access — the gap behind the two audit-readiness scores of 4.
  • We found no public information on a data processing agreement or subprocessor list for the platform itself; the published processor agreements cover the vendor's website tooling.
  • Add-on prices are not shown, Enterprise is auf Anfrage, and we found no public information on setup fees or VAT treatment.
  • The public API, MCP connection, IAM integration and Lightway's more-than-2,000 standard integrations sit in the Enterprise tier only.
  • We found no public information on a 72-hour clock for breaches, identity verification at intake, or evidence that deletions were actually executed.

Report an error

Best for

  • Your German-market organisation wants departments to document processing activities themselves in a guided workflow, with one- or multi-stage approval configurable per legal entity.
  • You manage several legal entities — tiers include 1, 3 or 8, Enterprise unlimited — and want one connected register feeding DPIAs, vendor checks, TOMs and the deletion concept instead of parallel documentation.
  • You want one documentation basis that also serves the EU AI Act, NIS2, DORA and ISO assessments, with those assessment templates included in every plan.
  • You prefer per-organisation costs to per-seat licensing, since users and documents are unlimited in every plan.

Report an error

Avoid if

  • You face audits in which the auditor will ask to reproduce a record as it stood on a given date — we found no public information on versioning, change history or read-only auditor access.
  • You need the public API, MCP connection or IAM integration on any tier below Enterprise; on the captured pricing pages those are Enterprise-only.
  • You must review a platform data processing agreement and subprocessor list before signing; the published processor information covers the vendor's website tooling.
  • You must rely on the tool in a live Article 33 breach response — the rationales report no public information on a 72-hour clock or identity verification at intake.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Records & DPIA depth 4.5 of 5
Data subject rights & incidents 3.5 of 5
Privacy regime coverage 3.5 of 5
Audit readiness & evidence 3 of 5
Integrations & automation 3.5 of 5
European sovereignty 2.5 of 5
Pricing transparency 3 of 5

Records & DPIA depth

Show 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.

Report an error

The External DPO

This is the connected model I bill hours out of: the record of processing activities synchronises automatically with the impact assessment, the measures and the vendor register, impact-assessment need is derived by automated threshold analysis, and the deletion concept is generated from the record itself. Processor records under Article 30(2) sit beside controller records, more than 200 legally reviewed processing-activity templates and 150 vendor templates carry across companies and locations with configurable approval per company, and everything from the processor agreements to the record goes to the supervisory authority at a click. Only a continuously maintained, standing audit-ready state keeps it from the top mark. 7 8 9 7

Report an error

The In-House Counsel

The register of processing activities is the backbone: an automated Schwellwertanalyse derives DPIA need from the record, vendors link automatically to the register, and TOMs — including process-specific measures — are connectable to the SDM guarantee goals, with legal bases under Art. 6 and 9 pre-built and legally reviewed. Registers for Art. 30(2) processors run in the same workflow across companies and locations with configurable approval, and at a button press the whole file from processor agreements to the register goes to the supervisory authority. That is a connected data model I can defend to an authority. 7 8 9 7

Report an error

The Drafted Generalist

This is the deep end of privacy records and it is built for people like me: processing activities captured in a guided workflow across all companies and locations, the DPIA threshold analysis runs automatically against risky activities, and TOMs and vendor checks link into the register automatically. The register even generates the deletion concept, and everything from processor agreements to the register goes to the authority at a button press. The one step toward a full system of record I cannot see evidenced is a dedicated multi-client mode for external data protection officers. 7 8 9 7

Report an error

The Lead Auditor

The records of processing sit in one connected model: they synchronise automatically with DPIAs, TOMs and vendor management, the deletion concept is generated from the record, and the whole pack from processor agreements to the register goes to the authority at a button press, maintained across several companies with approval configurable per entity and a threshold analysis linking risky activities to DPIAs. That is a genuine system of record in the making; I found no public information on an external data protection officer's multi-client mode, which is what separates this bench from the top one. 8 7 9 4

Report an error

The IT Integrator

The record of processing is the spine: DPIAs carry an automated need assessment linked to risky processing activities, vendor management is automatically linked to the register, TOMs are managed across modules, and the deletion concept is generated from the register itself. With capture across multiple companies and locations, configurable per-company approval workflows, and authority-ready output from processor agreements to the register at a button press, this is a connected model close to system-of-record depth. 7 8 9 7

Report an error

The Skeptic

The record of processing activities demonstrably drives the rest: DPIA need is derived automatically and tied to risky processing activities, vendor management links into the record, the deletion concept is generated from it, and records synchronise with DPIAs, TOMs and vendors. Records are captured per company with a configurable one- or multi-stage approval, processor records under Art. 30(2) are supported with over 200 legally reviewed templates, and everything from the processor agreements to the register goes to the authority at a button press. I found no public information on a multi-client mode for external data protection officers, which is the one gap here. 8 7 9

Report an error

Data subject rights & incidents

Show 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.

Report an error

The External DPO

Requests land in one place with automatic data-location lookup and the response deadline shown, an intake web form arrives from the Corporate plan upward and a customisable request workflow from Enterprise, and responses go out through a secure data room. Breaches get a central register with a guided decision process, and the deletion concept is built from the record of processing activities with more than 100 statutory retention periods preconfigured. The captured pages give no information on a 72-hour clock, on identity verification at intake, or on evidence that a deletion was actually executed. 8 9 4

Report an error

The In-House Counsel

Requests arrive centrally with the response deadline shown automatically, relevant data locations identified, an intake webform from the Corporate plan and delivery through a protected data room, and the deletion concept is generated from the register itself. On breaches, the product documents incidents centrally and guides the notification decision. We found no public information on a 72-hour clock, identity verification at intake, or an authority notification produced from the register, which I need before relying on it in a live Art. 33 situation. 8 9 4 4

Report an error

The Drafted Generalist

Requests arrive in the system with the data locations found automatically and the response deadline shown, plus an intake webform from the Corporate plan, and incidents are documented centrally through a guided decision process — exactly the hand-holding I need. The deletion concept is created straight from the register of processing activities. I found no public information on identity verification for requesters, an explicit 72-hour clock, or proof that deletions were actually executed. 8 9 4 4

Report an error

The Lead Auditor

Requests arrive in the tool with automatic data-location lookup and a visible response deadline, are answered through a protected data room, and get a webform for intake from the Corporate plan; incidents receive central documentation with a guided decision process, and the deletion concept is derived from the records with over a hundred retention periods pre-configured. The captured pages do not show a 72-hour clock on breaches, identity verification at intake, or tracked evidence that a deletion was executed, so the operational half stops short of a walkthrough an authority can follow end to end. 8 9 7 4

Report an error

The IT Integrator

Requests arrive in one place with automatic data-location lookup, tracked deadlines, and answers delivered through a protected data room, with a webform intake and adjustable workflow in the upper tiers; incidents are documented centrally with a guided decision process, and the deletion concept is derived from the register. We found no public information on identity verification at intake, the 72-hour notification clock, or tracked execution of deletions. 8 9 4 4

Report an error

The Skeptic

Requests land in the system with the deadline and data location shown automatically, answers go out via a secure data room, an intake webform for data subject requests arrives from the Corporate plan and an adjustable request workflow at Enterprise; breaches get central documentation with a guided decision process, and the deletion concept is built from the record of processing. I found no public information on identity verification at intake, deadline escalation, a 72-hour clock on breaches, or tracked execution of deletions. 8 9 4 4

Report an error

Privacy regime coverage

Show 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.

Report an error

The External DPO

GDPR is the backbone, but Privacy Flow and AI Flow build on the same documentation basis, and Swiss nDSG, the EU AI Act, ISO 27001, ISO 27701, NIS2, DORA and TISAX appear as assessment use cases with templates in every plan. The Standard Data Protection Model 3.1 is embedded as maintained content: seven guarantee goals pre-stored, linkable to measures, described as continuously updated. We found no public information on per-country variants or a published update cadence beyond that SDM content. 1 9 1 10

Report an error

The In-House Counsel

GDPR is implemented in depth and the home market is served properly: the Standard-Datenschutzmodell 3.1 with its seven guarantee goals and always-updated building blocks, plus Swiss nDSG, the EU AI Act, NIS2, DORA and ISO as named use cases with assessment templates in every plan. Privacy Flow and AI Flow build on the same documentation, so regimes are not separate islands. We found no public information on a published update cadence when a regime changes, and no ePrivacy/TTDSG content is named. 9 1 10 4

Report an error

The Drafted Generalist

The named regimes go well past GDPR: Swiss nDSG, EU AI Act, NIS2, DORA, ISO 27001 and 27701, TISAX and the Standard Data Protection Model 3.1 with its seven guarantee goals built in and described as continuously updated. Privacy Flow and AI Flow are stated to build on the same documentation, so one record serves several regimes rather than starting fresh. I found no published update cadence for when a law changes. 10 9 4 1

Report an error

The Lead Auditor

GDPR with Art. 6 and 9 legal bases sits alongside the Swiss nDSG, the EU AI Act, NIS2, DORA and the German Standard Data Protection Model 3.1, whose guarantee goals and always-updated building blocks are built into the product, and the Privacy and AI modules build on the same documentation. I found no public information on per-country variants or a published update cadence when a regime changes, which is what the top bench demands. 10 9 1 8

Report an error

The IT Integrator

GDPR is the core, with Swiss nDSG, the EU AI Act, NIS2, DORA, ISO 27001 and 27701, TISAX and the German Standard Data Protection Model 3.1 named as use cases; AI governance is described as sitting on the same documentation as privacy, and the SDM building blocks are described as continuously updated. That is several regimes on one record with maintained content for the newer duties. 1 9 1 10 4

Report an error

The Skeptic

GDPR runs deep with German-market SDM 3.1 content — seven guarantee goals preloaded, SDM modules described as always updated — and the AI Act has a dedicated product building on the same documentation; assessment templates for NIS2, DORA and AI compliance are included in every plan and Swiss nDSG appears in the use-case list. I found no public information on per-country variants mapped onto one record, ePrivacy/TTDSG content, or a published update cadence when a regime changes. 9 1 10 4

Report an error

Audit readiness & evidence

panel disagrees Show 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.

Report an error

The External DPO

Client-ready output is there: the audit report with answers, notes and a management summary is created at a click, vendor compliance reports likewise, findings are documented with measures and responsibilities assigned in the tool, and the whole package from processor agreements to the record of processing goes to the authority by button. Records export to PDF, Word and Excel, and audits can be sent to external parties from the Enterprise plan. The captured pages give no information on revision-safe change history, read-only auditor access, or reproducing a record as it stood on a given date. 9 10 7 4

Report an error

The In-House Counsel

Audit and vendor compliance reports with answers, notes and a management summary are produced at a click, the register exports to PDF, Word or Excel, and the file goes to the authority at a button press. What defensibility actually rests on is revision safety, and we found no public information on versioned records, a change history, evidence attached per measure, or read-only auditor access. 8 10 4 7

Report an error

The Drafted Generalist

Audit and vendor reports are generated at a click with answers, notes and a management summary, findings turn into measures with named responsibilities, and audits can be sent to external parties from the Enterprise plan. Register exports in PDF, Word and Excel plus the one-click authority submission help too. I found no public information on a revision-safe change history or evidence attached per measure, which is what an auditor would ask me for. 10 8 4 7

Report an error

The Lead Auditor

Reports are generated at a click — an audit report with management summary, a vendor compliance report, and a button-press submission of everything from processor agreements to the register to the authority — and audit findings carry measures with assigned responsibility. But the captured pages give no information on change history, versioning, or reproducing a record as it stood on a given date, and an audit trail that only exists when the report is pressed is exactly what I refuse to sign off. 10 9 7

Report an error

The IT Integrator

Audit and vendor reports are generated at a button press with answers, notes and a management summary, findings carry derived measures with assigned responsibility, audits can be dispatched to external parties, and authority submissions run from processor agreements to the register. We found no public information on a versioned change history or read-only auditor access. 8 10 4 4

Report an error

The Skeptic

Audit and vendor compliance reports generate at a click with answers, notes and a management summary, findings carry measures and named responsibilities, audits can be sent to third parties at Enterprise, and the register exports to PDF, Word or Excel with authority dispatch at a button press. I found no public information on change history or versioned records, evidence attached per processing activity or measure, or read-only auditor access — the spine of defensible proof. 10 7 9 4

Report an error

Integrations & automation

Show 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.

Report an error

The External DPO

The Enterprise tier is where the estate connects: a public API, an MCP interface, identity-management hookup, single sign-on from Corporate upward, and 2,000-plus standard integrations through the workflow module, with AI agents taking over recurring steps and existing documentation migrated automatically. The AI assistant drafts processing activities, risks and measures, and follow-up reminders come in from the Professional plan. The captured pages give no information on webhooks, SCIM provisioning or the API's reach into the data model — and a consultancy my size has to buy the top tier to get any API at all. 4 1 4

Report an error

The In-House Counsel

Single sign-on arrives from the Corporate plan and resubmission reminders for recurring work from Professional, while the public API, an MCP interface, IAM connection, AI agents and Lightway with webform intake and 2.000+ standard integrations arrive only with Enterprise. That is a genuine connection to the real IT estate for the top tier. We found no public information on the API's object coverage, webhooks or SCIM provisioning. 4 4 4

Report an error

The Drafted Generalist

Single sign-on starts at Corporate, and the Enterprise tier adds a public API, a caralegal MCP connection, IAM hookup and a Lightway module with webform intake and more than 2,000 standard integrations, plus AI agents for recurring steps and an AI assistant add-on. The reminder function and the free automatic migration of existing documentation sit in the lower tiers where a company like mine would live. I found no public information on webhooks or SCIM provisioning, and the API-based pieces are gated to the top plan. 4 4 4

Report an error

The Lead Auditor

There is a public API, an MCP connection and an IAM tie-in at Enterprise, single sign-on from Corporate, over two thousand standard integrations feeding intake, AI assistance creating processing activities, risks and measures, and orchestration that routes each case from central intake through assignment to documented completion, plus automatic migration of existing documentation. The API and the connector set are gated to the top tier, and the pages say nothing about webhooks or provisioning standards for the directory connection. 4 4 4

Report an error

The IT Integrator

There is a public API, an identity-and-access-management connection, SSO from the Corporate tier, case intake via webform with 2000+ standard integrations in Lightway, AI agents for recurring steps, an MCP interface, and automatic migration of existing documentation. What tempers it from my bench: the API, IAM connection and MCP are Enterprise-only, and we found no public information on webhooks or SCIM provisioning. 2 4 4

Report an error

The Skeptic

Single sign-on from the Corporate plan, a public API, an MCP connection, IAM integration, a workflow layer with webform intake and assignment, an AI Assistant that drafts processing activities, risks and measures, plus automatic migration of existing documentation. Everything beyond single sign-on sits in the Enterprise tier, and the 2.000+ standard integrations figure is a count on a pricing page rather than a named connector set; I found no public information on webhooks, SCIM provisioning, or human review of the AI output. 4 4 4 1

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The External DPO

The contracting entity is a Berlin company and the software runs in an ISO 27001-certified Deutsche Telekom data centre in Frankfurt, with hosting in a private cloud included in every plan — that part is clean and German. The captured pages give no information on a data processing agreement for the product or a subprocessor list for the platform itself; the published privacy policy covers the vendor's website, where transfers to the US run on standard contractual clauses and the Data Privacy Framework for Google and Microsoft. 3 4 4 5

Report an error

The In-House Counsel

The contracting entity is caralegal GmbH, Berlin, and the software runs in an ISO 27001-certified Deutsche Telekom data centre in Frankfurt, with hosting in a private cloud included in every plan — the jurisdictional core is where I want it. The two documents I must review before signing — the platform's own processing agreement and its subprocessor list for the service — are what we found no public information on; the published processor agreements cover the vendor's website tooling such as HubSpot, Cloudflare and Livestorm, not the platform itself. 3 4 4 3 4

Report an error

The Drafted Generalist

The vendor is a German GmbH seated in Berlin and the platform is hosted in an ISO/IEC 27001-certified Deutsche Telekom datacentre in Frankfurt, with private-cloud hosting included in every plan. The privacy policy publishes subprocessors with concluded Art. 28 agreements and names US transfers via Google LLC and Microsoft under the Data Privacy Framework, though those disclosures cover the vendor's website. I found no public information on a data processing agreement for the platform itself or its full subprocessor chain. 1 4 5 5

Report an error

The Lead Auditor

The contracting entity is a German GmbH seated in Berlin and the software runs in an ISO/IEC 27001-certified Deutsche Telekom data centre in Frankfurt — that much is proven on the captured pages. I found no public information on a customer data processing agreement, a subprocessor list for the platform itself, or published TOMs, and the vendor's own website stack names US-certified processors under the Data Privacy Framework, so the chain is documented only halfway. 3 4 4 5

Report an error

The IT Integrator

A German GmbH hosts the software by default in an ISO 27001-certified Deutsche Telekom data centre in Frankfurt, so entity and hosting are proven European. We found no public information on a customer data processing agreement or a platform subprocessor list on the captured pages; the published processor agreements cover the vendor's own website tooling, not the product. 3 4 4 4

Report an error

The Skeptic

The contracting entity is caralegal GmbH in Berlin, and the vendor's own pages state hosting in a named, ISO/IEC 27001-certified Deutsche Telekom data centre in Frankfurt. I found no public information on a customer data processing agreement for the platform, its subprocessor list beyond hosting, or any parent company; the published processor information covers the vendor's website tooling, which includes US recipients (Google LLC and Microsoft Corporation, certified under the EU-US Data Privacy Framework). 4 1 4 5

Report an error

Pricing transparency

Show 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.

Report an error

The External DPO

Three of four tiers carry public prices — Essential from 79 euros per month, Professional at 349 euros, Corporate at 749 euros — with included legal entities stated per tier at one, three, eight and unlimited, unlimited users and documents in every plan, main inclusions listed and a 50 percent nonprofit discount published. Enterprise is on request, tolerable for a top corporate tier. The add-ons such as the AI assistant, the retention library and the workflow module carry no prices in the captured pages, and we found no public information on setup fees or VAT treatment. 4 4 4

Report an error

The In-House Counsel

Three of four tiers carry public prices — Essential ab 79€ pro Monat, Professional 349 EUR, Corporate 749 EUR — with included legal entities (1, 3, 8), unlimited users on all plans and the main inclusions listed per tier, while Enterprise is auf Anfrage. We found no public information on add-on prices, set-up fees or VAT treatment, so the real invoice still requires a conversation. 4 4 4

Report an error

The Drafted Generalist

The three lower editions are public — Essential ab 79€ pro Monat, Professional 349 €, Corporate 749 € — with the included legal-entity counts of 1, 3 and 8, unlimited users and the main feature lists published, plus a 50% nonprofit discount. Enterprise is auf Anfrage, the add-on prices are not shown, and VAT treatment and setup fees are not stated. Good enough to budget from, not enough to compute the exact invoice. 4 4 4

Report an error

The Lead Auditor

Three tiers carry public monthly prices — Essential ab 79€ pro Monat, Professional 349 €, Corporate 749 € — with included legal-entity counts of one, three and eight, unlimited users on every plan, and detailed inclusion tables, so most buyers can compute the invoice in minutes. Enterprise is auf Anfrage and the add-ons are listed without prices, and VAT treatment and setup fees are not stated, which keeps the real invoice short of fully computable. 4 4 4 4

Report an error

The IT Integrator

Three of four editions carry public prices with legal-entity counts of one, three, eight and unlimited, unlimited users and documents in all plans, and inclusions listed per tier; Enterprise is on request and a 50 percent nonprofit discount is stated. Add-on pricing, setup fees and VAT treatment are not shown, so the full invoice is not computable from the public pages. 4 4 4 4

Report an error

The Skeptic

Three of four tiers carry public euro prices — Essential "ab 79€ pro Monat", Professional 349, Corporate 749 — with monthly billing stated, unlimited users and documents, and legal-entity counts plus main inclusions listed per plan; the 50% nonprofit discount is public and Enterprise is "auf Anfrage". The add-ons (AI Assistant, Otto Schmidt legal database, retention library, translation tool) carry no public prices, and I found no public information on setup fees, VAT treatment, or how consulting is separated from software. 4 4 4 4

Report an error

European sovereignty — proven facts

1 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 Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about caralegal

Is caralegal European?

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

Where does caralegal store data?

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

Does caralegal have a free plan?

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

What are the best alternatives to caralegal?

As of 19 Nov 2026, the panel rates preeco | datenschutz (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 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: caralegal 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 (10)

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

  1. 1 Vendor homepage caralegal.eu Checked 26 Oct 2026 +3 earlier captures: 15 Sep 2026, 24 Aug 2026, 23 Aug 2026 Details →
  2. 2 Product page (EN) caralegal.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  3. 3 Imprint caralegal.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 Vendor pricing page caralegal.eu Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 26 Oct 2026, 5 Oct 2026 Details →
  5. 5 Privacy policy caralegal.eu Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  6. 6 Security / trust page caralegal.eu Checked 2 Nov 2026 Details →
  7. 7 Records & DPIA depth — found from sitemap caralegal.eu Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  8. 8 Records & DPIA depth — found from sitemap caralegal.eu Checked 16 Nov 2026 Details →
  9. 9 Privacy regime coverage — found from sitemap caralegal.eu Checked 16 Nov 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap caralegal.eu Checked 26 Oct 2026 Details →