whats-best.ai
Search Sign in

Data Protection

Dastra

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

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

by Dastra SAS · www.dastra.eu

Report an error on this page Is this your product? →

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

The Drafted Generalist

Weighted verdict

Office manager at an 80-employee firm who got compliance added to her job title, not her calendar. Optimizes for guided workflows in plain language and software that knows the law so she does not have to. Rejects consultant-shaped platforms that assume a compliance department.

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

Scored by The Drafted Generalist

Records & DPIA depth

How this is scored

The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.

0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.

3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.

5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.

8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.

10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client/mandate capability included, and the documentation is audit-ready without manual assembly.

Report an error

The Drafted Generalist

The register is clearly a real module — the Article 30 record can be built from templates, questionnaires or an AI wizard, with a dedicated DPIA module, third-party contract analysis, and a questionnaire library running from legitimate-interest assessments to transfer and retention analyses. What I cannot see is the connective tissue a non-lawyer relies on: we found no public information on whether a risky register entry triggers a DPIA, how legal bases and security measures are modeled as linked objects, or reusable group templates for multi-entity reuse. 6 10 1 2

Report an error

Data subject rights & incidents

How this is scored

The operational half of the DSMS: data subject request handling with statutory clocks, breach register and authority notification, deletion concepts that actually delete.

0 — Requests arrive by email and live there; breaches are a phone call and a memo.

3 — A request log and a breach list exist, but deadlines are manual, intake is unstructured, and deletion rules are documentation rather than workflow.

5 — DSR workflows with the Art. 12 clock tracked, structured breach register with the 72-hour clock, deletion concepts assignable to records; automation is reminders.

8 — Intake channels for requests (portal/form), identity-check support, deadline automation with escalation, breach severity assessment and authority-report output, deletion rules tied to the RoPA with execution tracking.

10 — Rights and incidents as operations: end-to-end request handling an authority audit walks through, breach workflows that produce the Art. 33 notification, and deletion automation with evidence that the deletion happened.

Report an error

The Drafted Generalist

This is the half I care about most and it looks genuinely operational: requests flow in from email, website forms and APIs into a secure portal where I can chat with the requester and watch dashboards for overdue and average response times, and the breach module tracks the 72-hour duty with assignable tasks, an exportable register and notification to affected people. We found no public information on identity verification of requesters, escalation when a deadline slips, or deletion rules wired to the register with proof the deletion actually ran. 9 8 12

Report an error

Privacy regime coverage

How this is scored

Which privacy regimes the product actually operationalizes — GDPR, BDSG, Swiss nDSG, UK GDPR, ePrivacy, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.

0 — One regime, hard-coded; anything else is "on the roadmap".

3 — GDPR plus one national law as separate checklists; the same processing activity is documented once per regime.

5 — The major regimes for its market with partial cross-mapping; newer duties (AI Act, ePrivacy changes) present as content packs of varying depth.

8 — Broad current coverage with one-record-many-regimes mapping and visible maintenance as regimes evolve.

10 — Regime coverage as a living product: multiple privacy regimes on one data basis, per-country variants, and documented update cadence when the law moves.

Report an error

The Drafted Generalist

GDPR is home base and the breadth goes beyond it — UK GDPR, Europrivacy and ISO 27001 appear as framework choices, cookie consent is a module, and the questionnaire set even covers French Sapin 2. But the framework picker sits in the top tier, and we found no public information on Swiss law, EU AI Act duties, per-country variants, or any documented cadence for updates when the law moves. 2 10 11 6

Report an error

Audit readiness & evidence

How this is scored

Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.

0 — Exports are screenshots; history is overwritten in place.

3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.

5 — Versioned records, standard report generators for the core registers, evidence attachments per activity; assembling a full audit file still takes days.

8 — Revision-safe change history, audit-scoped evidence packs on demand, management and authority reports current at a click, auditor access roles.

10 — Audit readiness as a standing state: continuous documentation status per regime and scope, exportable proof packs an auditor accepts as-is, and a defensible answer to "show me the state on date X".

Report an error

The Drafted Generalist

There is a whole audit product here: a library of sixteen templates filterable by tag, spider charts, tables and risk matrices, reports that can be validated, published and exported, "Evidence automation" named as a feature, and audit logs streaming in real time to a SIEM. What I would need before an inspector visits is not shown — we found no public information on revision-safe version history or a way to answer "show me the state on a given date." 10 11 2 12

Report an error

Integrations & automation

How this is scored

Whether the platform feeds from the real IT estate — directory import, ticketing, API — and automates the recurring privacy work instead of re-typing it.

0 — A closed island: manual entry in, PDF out, no API.

3 — CSV/Excel import and export; no live connections, no API worth the name.

5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing or SSO); automation is reminders and recurrence.

8 — Real connector set (ticketing, HR or asset sources), webhooks, SSO/SCIM, workflow automation with delegation and escalation, useful AI assistance with human review.

10 — The platform behaves like infrastructure: API parity for the data model, event streams, bidirectional sync with the estate, and automation that measurably removes the recurring toil (reviews, attestations, evidence pulls) rather than renaming it.

Report an error

The Drafted Generalist

Strongest area for someone like me: a documented REST API on the OpenAPI 3.x standard, webhooks, single sign-on with SCIM and IP filtering, and seventeen connectors including Jira for automatic request tracking, ServiceNow and LeanIX for assets, Zapier for three thousand more apps, plus an email parser that files incoming requests automatically. AI can draft the processing activities and I can connect my own AI provider. We found no public information on bidirectional sync across the full data model, so I stop short of the top. 12 13 1 3

Report an error

European sovereignty

How this is scored

Where the compliance record of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. A platform that maps your processing is itself your most concentrated processing.

0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your RoPA.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.

5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.

8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.

10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.

Report an error

The Drafted Generalist

The vendor is a French company registered in Créteil, my data would sit on Azure in France, and there is a published subprocessor list naming safeguards provider by provider, with ISO 27001 and 27701 certifications on top. But the hosting rests on US-headquartered Microsoft within CLOUD Act reach, several listed subprocessors are US firms, ownership is stated nowhere I can find, and we found no public information on a customer data processing agreement or published technical security measures. 5 4 6

Report an error

Pricing transparency not rated — the vendor publishes no price

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 — An entry price exists, but module add-ons, entity counts or bundled consulting make the real total incomputable.

5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; 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 Drafted Generalist

Three tiers are named with published limits of 150 users and 50 legal entities, and there is a free trial — but every tier ends in "Request a quote from our teams" or "Ask for a demo", and we found no public prices anywhere. As the person who has to budget this, I can name the plans but cannot compute a single invoice figure from the public pages. 2 8

Report an error

European sovereignty — proven facts

2 of 4 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.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors US CLOUD Act reach ⚠ unverified 0/2 pts 5 Report an error

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.

Do you know more about Dastra? Tell us Report an error on this page

Sources (13)

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

  1. 1 Vendor homepage (EN) www.dastra.eu Checked 17 Sep 2026 Details →
  2. 2 Vendor pricing page www.dastra.eu Checked 17 Sep 2026 Details →
  3. 3 Features overview www.dastra.eu Checked 17 Sep 2026 Details →
  4. 4 Legal notice/imprint www.dastra.eu Checked 17 Sep 2026 Details →
  5. 5 Privacy policy www.dastra.eu Checked 17 Sep 2026 Details →
  6. 6 Security / trust page www.dastra.eu Checked 30 Sep 2026 Details →
  7. 7 Records & DPIA depth — found from sitemap learn.dastra.eu Checked 1 Oct 2026 Details →
  8. 8 Data subject rights & incidents — found from sitemap www.dastra.eu Checked 1 Oct 2026 Details →
  9. 9 Data subject rights & incidents — found from sitemap www.dastra.eu Checked 1 Oct 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap www.dastra.eu Checked 1 Oct 2026 Details →
  11. 11 Audit readiness & evidence — found from sitemap www.dastra.eu Checked 1 Oct 2026 Details →
  12. 12 Integrations & automation — found from sitemap www.dastra.eu Checked 1 Oct 2026 Details →
  13. 13 Integrations & automation — found from sitemap www.dastra.eu Checked 1 Oct 2026 Details →