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 Dastra SAS · www.dastra.eu

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

Link to this page

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

Dastra at a glance

Vendor
Dastra SAS
Headquarters
Incorporated in France source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Dastra 3.5/5, the mean of 6 judges. Dastra is a GDPR platform from Dastra SAS of Saint-Mandé, France, covering the Article 30 record of processing, DPIAs, data subject requests, breaches and audits. how scores are made
As of
Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

Dastra alternatives, European ones first →

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

The panel's verdict

Dastra is a GDPR platform from Dastra SAS of Saint-Mandé, France, covering the Article 30 record of processing, DPIAs, data subject requests, breaches and audits. Its strongest area is integrations and automation at 8: a REST API documented to the OpenAPI 3.x standard, SSO with SCIM, webhooks and 18 named integrations including Jira, ServiceNow and SAP LeanIX. Privacy management and rights and incidents hold at 7, with a multi-client view for external data protection officers and a breach register built around the 72-hour clock. Framework coverage sits at 6 — GDPR, UK GDPR, Europrivacy, ISO 27001 — with no public information on AI Act content or update cadence. Audit readiness scores 6 to 7, with read-only auditor access and point-in-time record reproduction not documented. Sovereignty shows the widest spread, 4 to 6, higher scores crediting European development and ISO certifications, lower ones weighing the US subprocessor names; hosting is stated as Microsoft Azure in the European Union with data stored mainly in France, and we found no public information on a data processing agreement. No price figure appears on any page.

Report an error

Speaks for it

  • A REST API documented to the OpenAPI 3.x standard, with SSO via SAML and OpenID, SCIM provisioning, IP filtering, webhooks and 18 named integrations including Jira, ServiceNow, SAP LeanIX and Zapier.
  • A dedicated data subject rights module with intake from email, forms and APIs, a no-code intake widget, a secure portal and dashboards tracking open and overdue requests.
  • A breach register built around the 72-hour clock of Article 33(1) and the documentation duty of Article 33(5), with per-task deadlines and an exportable activity feed.
  • A multi-client role that lets an external data protection officer steer all clients as if there were one.
  • Sixteen audit templates filterable by tag, with questionnaire reports exportable as risk matrices or spider charts and audit logs streamed to a SIEM in real time.

Report an error

Held against it

  • Framework coverage stops at 6, with no public information on AI Act or ePrivacy duties as maintained content or on any update cadence when a regime changes.
  • The published subprocessor list names US providers such as Google Ads, Hubspot, Cloudflare and Google Analytics under SCC/DPF safeguards, and we found no public information on a platform data processing agreement.
  • Evidence automation, custom reporting and the framework of choice sit on the Enterprise tier, and read-only auditor access is not documented on the captured pages.
  • No public information on DPIA need derived from the record itself, or on deletion execution tied to the record with tracked completion.
  • Three tiers are named with public caps of 150 users and 50 legal entities, but no price figure appears on any captured page — the call to action is 'Ask for a demo'.

Report an error

Best for

  • You want one European platform for the record of processing, DPIAs, rights requests and breaches that syncs with Jira, ServiceNow or SAP LeanIX instead of retyping data.
  • You are an external data protection officer steering multiple clients and need the multi-client view the platform explicitly sells.
  • Your security team wants compliance evidence piped out of the tool — audit logs stream to a SIEM in real time and questionnaire reports export as risk matrices and spider charts.

Report an error

Avoid if

  • You need a published price to compare vendors before a sales call — every figure sits behind 'Ask for a demo' and 'Request a quote from our teams', though a free trial exists.
  • Your compliance scope extends beyond GDPR, UK GDPR, Europrivacy and ISO 27001, the frameworks the Enterprise plan names.
  • You require a processing chain free of US subprocessors — the published list names US providers for advertising, CRM, statistics and website security under SCC/DPF safeguards.
  • You rely on the record of processing to drive deletions end-to-end — the captured pages document a retention questionnaire type and a Filerskeepers connector, not tracked deletion execution.

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 3.5 of 5
Data subject rights & incidents 3.5 of 5
Privacy regime coverage 3 of 5
Audit readiness & evidence 3.5 of 5
Integrations & automation 4 of 5
European sovereignty 2.5 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

The Article 30 register is a structured module fed by templates, questionnaires or an AI wizard, DPIAs, LIAs and TIAs run through the same questionnaire engine with validatable, exportable reports, and processors with their DPAs are handled through contracts with AI analytics — plus an external-DPO role to steer all clients as if there were only one, which is precisely my practice. We found no public information showing DPIA need derived from the register itself or legal bases modelled inside that connected record, so it stops just short of the register driving the rest. 1 2 6 10

Report an error

The In-House Counsel

The Article 30 register, a dedicated impact-assessment module, and processor contracts with AI analytics are all documented, alongside LIA and TIA questionnaires and a multi-client view for external data protection officers. I found no public information on the DPIA trigger being derived from the record itself or on a register output formatted for a supervisory authority, which is what I would need before relying on it in an inspection. 2 6 10

Report an error

The Drafted Generalist

The record of processing is built around Article 30 and can be filled via templates, questionnaires or an AI wizard, with asset, stakeholder and data-mapping records already on the lowest tier; DPIAs, transfer impact assessments and retention analyses run as questionnaire modules, contracts including DPAs get AI analysis on the Pro tier, and there is a role for external data protection officers managing all their clients as if they were one. I found no public information on the record itself flagging when a DPIA becomes mandatory, so I stayed just under the top band. 6 10 2 1

Report an error

The Lead Auditor

The record of processing is built around Article 30 and kept current via templates, questionnaires or AI, impact assessments run as their own module, questionnaires cover LIA, DPIA, TIA and retention analyses, and contracts and policies including data processing agreements come with AI analytics; an external data protection officer role steers all clients as if there were only one, and security measures, actors and processing appear as objects of one model. We found no public information on impact-assessment need being derived from the record or on reusable templates across companies, so I stop short of the connected top level. 2 6 10 12

Report an error

The IT Integrator

The Article 30 register, DPIA/LIA/TIA questionnaires, asset-and-stakeholder records and security measures all exist as modules, with DPA and transfer analytics in the Pro plan and data mapping in Starter. The external-DPO pitch — steer all your clients as if they were one — plus ServiceNow and LeanIX applications feeding the record points at a genuinely connected model. I found no public information showing DPIA need derived from the record or authority-ready register outputs, so I stop below the top benches. 6 10 2 12 1

Report an error

The Skeptic

The Article 30 record of processing is a real module with templates, questionnaires and an AI wizard, DPIAs run in their own module, and processor contracts with AI analytics are named in the Pro plan; multi-client steering for external data protection officers is explicitly sold. What holds this below the connected-model band is that the captured pages never show security measures assigned to processing activities or a DPIA need derived from the record. 2 6 10

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 arrive from email parsing, website forms and APIs into a no-code widget with automatic email validation, a secure portal and a chat with the requester, with dashboards for open, overdue and average response times; breaches live in an exportable register with the 72-hour clock, Article 33(5) documentation, data subject notification and configurable deadlines per task. We found no public information on authority notification documents generated from the breach workflow, or deletion rules tied to the register with tracked execution — the two things a client audit always probes. 8 9 12

Report an error

The In-House Counsel

The breach module is built around the 72-hour clock of Article 33(1) and the documentation duty of Article 33(5), with per-task regulatory deadlines and an exportable register, and the rights side has intake forms, a secure portal carrying identification information, and an overdue-status dashboard. I found no public information on a breach severity assessment feeding the authority notification, explicit deadline escalation, or deletion rules tied to the register with execution tracked. 8 9

Report an error

The Drafted Generalist

Requests arrive from email (with an automated parser), website forms and APIs, get qualified and answered through a chat interface and a secure portal, and a dashboard shows requests by status including overdue ones plus average response times — the deadline pressure is visible at a glance. The breach side has an exportable register that spells out the 72-hour rule and the Article 33(5) documentation duty, task deadlines you can configure, and notification of affected people. I found no public information on deletion rules tied to the record with tracked execution, which keeps it below the very top. 9 8 12

Report an error

The Lead Auditor

Requests are collected from emails, website forms and APIs into a dedicated module with a no-code intake widget carrying email validation, a secure portal for identification information, chat with the requester and dashboards counting open and overdue requests; breaches sit in an exportable register with the 72-hour rule spelled out, configurable per-task deadlines, notification of affected data subjects and an exportable activity feed. Severity assessment producing the authority notification and deletion execution evidence are not shown on the captured pages. 8 9

Report an error

The IT Integrator

Requests arrive from email, forms and APIs into a no-code widget with email validation, a secure portal and a requester chat, while a dashboard tracks overdue status and average response times; the breach register carries the 72-hour clock, custom workflows, configurable task deadlines, subject notifications and an exportable activity feed. Deletion tied to the register appears only as a retention questionnaire type and a Filerskeepers connector — I found no public information on tracked deletion execution. 9 8 12 10

Report an error

The Skeptic

A dedicated data subject rights module with intake from email, forms and APIs, a no-code widget with automatic email validation, a secure portal, chat with the requester and overdue-tracking dashboards; on the breach side, an exportable register built around Articles 33(1) and 33(5), data-subject notification, custom workflows, per-task deadlines and an exportable activity feed. Identity verification beyond email validation, deadline escalation and deletion execution tied to the record of processing are not documented on the captured pages. 2 8 9

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, UK GDPR, Europrivacy, ISO 27001 and even SAPIN 2 are supported with multi-compliance questionnaires, which is broader regime exposure than most DSMS vendors publish. We found no public information on AI Act or ePrivacy duties as maintained content, per-country variants on one record, or a published update cadence when a regime changes. 2 10

Report an error

The In-House Counsel

GDPR, UK GDPR, Europrivacy and ISO 27001 are named as supported frameworks, backed by sixteen audit referentials and multi-compliance questionnaires including SAPIN 2. We found no public information on per-country variants such as BDSG or the Swiss nDSG, on requirements mapped across regimes from one record, or on a published update cadence — and for legal content, unmaintained is a liability. 2 10 11

Report an error

The Drafted Generalist

GDPR is the core, and the Enterprise tier adds a choice of frameworks including UK GDPR, Europrivacy and ISO 27001, with multi-compliance questionnaires — even SAPIN 2 — run on the same platform plus a cookie-consent module. I found no public information on German, Swiss or other national variants, on AI Act duties, or on a published cadence for updating content when a law changes. 2 6 10

Report an error

The Lead Auditor

GDPR, UK GDPR, Europrivacy and ISO 27001 are offered as frameworks of choice on one platform, questionnaires extend to SAPIN 2 and multi-compliance checks, cookie consent is a module, and the audit template library counts sixteen templates filterable by tag. We found no public information on AI Act duties or a published update cadence when a regime changes. 2 6 10 11

Report an error

The IT Integrator

GDPR, UK GDPR, Europrivacy and ISO 27001 are named as selectable compliance frameworks on the Enterprise plan, cookie consent is its own module, and the questionnaire engine handles multi-compliance checks including SAPIN 2. That puts several regimes on one platform rather than separate islands. I found no public information on maintained content for newer duties such as the AI Act, or on a published update cadence when a regime changes. 2 10 6

Report an error

The Skeptic

GDPR, UK GDPR, Europrivacy and ISO 27001 are named as selectable frameworks on the Enterprise plan, and the questionnaire library spans LIA, DPIA, TIA, retention, security, third-party and SAPIN 2 checks, with a cookie-consent module alongside. We found no public information on AI Act or ePrivacy duties as maintained content, nor on any update cadence when a regime changes. 2 6 10 11

Report an error

Audit readiness & evidence

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

Audit logs stream to a SIEM in real time, files attach to actors, security measures, processing activities, tasks and incidents, a sixteen-template audit referential filters by tag, questionnaire reports move through validation, publication, export and archiving with spider charts and risk matrices, and evidence automation plus custom reporting are named at the Enterprise tier. We found no public information on read-only auditor access or on reproducing any record exactly as it stood on a given date. 2 10 11 11 12

Report an error

The In-House Counsel

Audit logs stream to a SIEM in real time, incident reports carry an exportable activity feed, questionnaire reports move through a validate, publish and archive lifecycle, and evidence automation with custom reporting is listed at the Enterprise tier. Those plan bullets are not documented behaviour, and we found no public information on read-only auditor access or on reproducing a record as it stood on a given date. 2 8 10 12

Report an error

The Drafted Generalist

There is a library of sixteen audit templates you can filter by tag, questionnaire reports that go through validate, review, export and archive with risk matrices, an exportable activity feed on each incident, audit logs streamed to a SIEM in real time, and evidence automation plus custom reporting named on the Enterprise tier. I found no public information on read-only access for auditors or on reproducing a record exactly as it stood on a given date. 10 11 2 12

Report an error

The Lead Auditor

Evidence automation and custom reporting are named Enterprise features, audit logs stream to a SIEM in real time, incident reports carry an exportable activity feed, and questionnaire reports move through validate, publish, export and archive with spider-chart and risk-matrix views. We found no public information on read-only auditor access or on reproducing a record as it stood on a given date, which is what I require before calling audit readiness a standing state. 2 8 10 11 11 12

Report an error

The IT Integrator

Sixteen audit templates in a tag-filterable library, questionnaire reports that can be validated, exported and archived as spider charts or risk matrices, file attachments across actors, measures and processing activities, custom reporting and a named evidence-automation feature on Enterprise. Audit logs stream to a SIEM in real time, which is exactly the evidence trail I want piped out of a compliance tool. I found no public information on read-only auditor access or reproducing a record as it stood on a given date. 11 11 10 12 2 8

Report an error

The Skeptic

Sixteen audit templates filterable by tag, questionnaire reports that can be validated, published, exported and archived as risk matrices or spider charts, an exportable activity feed on incidents, real-time audit-log streaming to SIEM, and 'Evidence automation' and 'Custom Reporting' named on the Enterprise plan. Evidence automation sits behind the top tier, and read-only auditor access and revision-safe change history are not documented on the captured pages. 2 8 10 11 12

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

A documented OpenAPI 3 REST API, eighteen connectors including Jira, ServiceNow assets, SAP LeanIX and Docusign, Zapier bridging over three thousand apps, SSO with SCIM, webhooks, HTTP calls from workflow rules, an email parser for intake and a bring-your-own OpenAI-compatible AI provider — this is the estate-connected automation that saves billable hours across mandates. We found no public information on escalation paths inside the workflow automation or on human review of AI-generated records. 1 3 12 13

Report an error

The In-House Counsel

A REST API documented to the OpenAPI 3.x standard, eighteen integrations including Jira, ServiceNow and SAP LeanIX, webhooks, single sign-on with SCIM provisioning, an email parser feeding requests into workflows, and an AI agent with a custom provider — this is the estate-connected profile I want before signing. We found no public information on human review of AI output or on escalation rules within the workflow engine. 1 12 13

Report an error

The Drafted Generalist

This is the strongest area: a REST API documented to the OpenApi 3.x standard, eighteen named connectors (Jira, Trello, ServiceNow, SAP LeanIX, Teams, Slack, Docusign, the Insee Sirene lookup), Zapier access to over 3000 apps, webhooks, single sign-on with SCIM provisioning, workflow rules that can call any external API, an email parser that collects requests automatically, and an AI wizard that can point at any OpenAI-compatible provider. Recurring review cycles and documented human review of the AI output are the pieces I found no public information on. 12 13 1 3

Report an error

The Lead Auditor

A well-documented REST API built to OpenApi 3.x, eighteen named integrations including Jira, ServiceNow, SAP LeanIX, Docusign and Zapier with three thousand apps, single sign-on over SAML and OpenID with SCIM provisioning and IP filtering, webhooks, custom HTTP calls from workflow rules, and an automated email parser feeding tasks and requests — the platform genuinely feeds from the estate. Escalation chains and automated recurring reviews are only partially evidenced, so I hold below the top. 1 3 12 13

Report an error

The IT Integrator

This is the wiring I look for: a documented REST API built to OpenAPI 3.x, webhooks, SSO SAML/OpenID with SCIM provisioning and IP filtering, and Jira kept in sync with requests and tasks. ServiceNow assets and SAP LeanIX applications feed the registry, an automated email parser collects requests and processing projects, workflow rules can call any external API via custom HTTP, and eighteen native connectors plus Zapier cover the rest — compliance data that syncs instead of being retyped. I found no public information on a named directory-import connector, which alone keeps it off the infrastructure grade. 13 13 12 1 3 9

Report an error

The Skeptic

The strongest-documented area: a REST API documented to the OpenAPI 3.x standard, SSO with SAML/OpenID plus SCIM provisioning and IP filtering, webhooks, eighteen named integrations including Jira sync for requests and tasks, ServiceNow assets, SAP LeanIX, Docusign and Zapier, an email parser feeding requests automatically, and custom HTTP calls from workflow rules. Escalation rules and human review of the AI wizard's output are not documented on the captured pages. 1 13 12 13

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

A French SAS in Saint-Mandé hosts on Microsoft Azure in the European Union, with data 'mainly stored on servers located in the European Union (particularly in France)' and no transfer outside the EEA for hosting, ISO 27001 and 27701 certification, and a published subprocessor list whose non-EU names are advertising, CRM and statistics tools under SCC or DPF safeguards. We found no public information on a customer data processing agreement, published technical and organisational measures, or hosting options beyond the EU cloud. 3 4 5

Report an error

The In-House Counsel

A French company registered in Créteil states hosting on Microsoft Azure in the European Union with data stored particularly in France, and publishes a subprocessor list with SCC and Data Privacy Framework safeguards for the US processors among them. We found no public information on a data processing agreement or a sovereign-cloud option, which leaves the chain short of a clean bill for the platform that will hold the company's entire processing map. 4 5 6

Report an error

The Drafted Generalist

The company is a French SAS registered near Paris, hosting runs on Microsoft Azure in the European Union with 'Data hosted in Europe' stated, the software is designed and developed in Europe, and ISO 27001 and 27701 certifications are claimed. A subprocessor list is published with safeguards, but it names US providers such as Google Ads, Microsoft Clarity, HubSpot and Cloudflare, and I found no public information on a data processing agreement — so the picture is a European one with some US names on the published list. 5 4 3

Report an error

The Lead Auditor

The contracting entity is a French company registered in Créteil, hosting is Microsoft Azure in the European Union with data stated as hosted in Europe and stored mainly in France, and a subprocessor list is published with locations and safeguards, though it names US providers for advertising, analytics and CRM under SCC and Data Privacy Framework. We found no public information on a data processing agreement or named data centres, and the word mainly is doing quiet work in the residency sentence. 4 5 6

Report an error

The IT Integrator

A French SAS registered in Saint-Mandé, hosting stated as Microsoft Azure in the European Union with data mainly in France and no transfer outside the EEA claimed, backed by ISO 27001 and 27701 certificates and development in Europe. The published subprocessor list is detailed but names US processors — Google Ads, Hubspot, Cloudflare, Google Analytics — for the vendor's own website and marketing under SCC/DPF safeguards. We found no public information on a data processing agreement for the platform or on the parent-company chain, so this settles mid-table. 4 5 6

Report an error

The Skeptic

Dastra SAS is registered in Saint-Mandé under French law, hosting is stated as Microsoft Azure in the European Union with data stored mainly in France, and a published subprocessor list nonetheless names US processors (Google Ads, Hubspot, Cloudflare) under SCC/DPF safeguards. We found no public information on a data processing agreement or on named data centres in the captured pages. 3 4 5

Report an error

Pricing transparency not rated — the vendor publishes no price

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

The tiers are named — Starter, Pro, Enterprise — with feature lists and public caps of fifty legal entities and one hundred fifty users, and the product is free to try, but we found no public prices on any captured page; the path to an invoice runs through 'Request a quote from our teams' and 'Ask for a demo'. For a multi-client practice, nothing here lets me compute one client's licence before the sales call. 2

Report an error

The In-House Counsel

Three named editions with their inclusions, user and legal-entity limits and a free trial are public, which lets a buyer scope the tier. Every price sits behind 'Ask for a demo' and 'Request a quote from our teams', so no invoice can be computed from public pages. 2 12

Report an error

The Drafted Generalist

The pricing page names three tiers — Starter, Pro, Enterprise — and is refreshingly specific about boundaries: 50 legal entities and 150 users on every tier, with feature lists per tier and a free trial to start. But there is not a single price figure on the page; the Enterprise tier says 'Request a quote from our teams' and the call to action is 'Ask for a demo', so the real invoice stays a sales conversation. 2 12

Report an error

The Lead Auditor

Three editions are named with their feature inclusions, limits of one hundred fifty users and fifty legal entities, and a free trial, but no price figure appears anywhere — the call to action is to ask for a demo and the Enterprise tier directs buyers to request a quote from the teams. A buyer cannot compute an invoice from these pages. 2 12

Report an error

The IT Integrator

Three editions are named with their feature lists, the boundaries are public at 150 users and 50 legal entities per tier, and a free trial exists. But every figure sits behind 'Ask for a demo' and 'Request a quote from our teams' — no public price appears on any edition, so a buyer cannot compute the invoice from these pages. 2 12

Report an error

The Skeptic

The pricing page publishes three plan names with their inclusions, a free trial, and limits of 150 users and 50 legal entities shown identically on every tier — but no monetary figure appears on any page we read; Enterprise is 'Request a quote from our teams' and the call to action is 'Ask for a demo'. 2 12

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 unverified
Why unverified?

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

— 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 Dastra

Is Dastra European?

Yes. whats-best.ai classifies Dastra as EU-Made. Its vendor, Dastra SAS, is incorporated in France, per the vendor’s page captured 16 Nov 2026.

Where does Dastra store data?

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

Does Dastra have a free plan?

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

What are the best alternatives to Dastra?

As of 19 Nov 2026, the panel rates preeco | datenschutz (3.5/5), caralegal (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: Dastra 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 (14)

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 16 Nov 2026 Details →
  2. 2 Vendor pricing page www.dastra.eu Checked 16 Nov 2026 Details →
  3. 3 Features overview www.dastra.eu Checked 16 Nov 2026 Details →
  4. 4 Legal notice/imprint www.dastra.eu Checked 16 Nov 2026 Details →
  5. 5 Privacy policy www.dastra.eu Checked 16 Nov 2026 Details →
  6. 6 Security / trust page www.dastra.eu Checked 16 Nov 2026 Details →
  7. 7 Records & DPIA depth — found from sitemap learn.dastra.eu Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  8. 8 Data subject rights & incidents — found from sitemap www.dastra.eu Checked 16 Nov 2026 Details →
  9. 9 Data subject rights & incidents — found from sitemap www.dastra.eu Checked 16 Nov 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap www.dastra.eu Checked 16 Nov 2026 Details →
  11. 11 Audit readiness & evidence — found from sitemap www.dastra.eu Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  12. 12 Integrations & automation — found from sitemap www.dastra.eu Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  13. 13 Integrations & automation — found from sitemap www.dastra.eu Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  14. 14 Structured-data backfill: markup only, no text or screenshot www.dastra.eu Checked 8 Nov 2026 Details →