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 iubenda S.r.l. · www.iubenda.com

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

Link to this page

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

iubenda at a glance

Vendor
iubenda S.r.l.
Headquarters
Incorporated in Italy source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 22 Sep 2026
Panel verdict
The AI panel rates iubenda 2/5, the mean of 6 judges. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

iubenda alternatives, European ones first →

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

No written verdict for this product

The panel scored iubenda, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.

Know this product well? Tell us what the verdict should say

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 2 of 5
Data subject rights & incidents 2 of 5
Privacy regime coverage 3.5 of 5
Audit readiness & evidence 2.5 of 5
Integrations & automation 3 of 5
European sovereignty 1 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 register of processing activities is genuinely structured: services carry legal bases, retention periods, transfer bases and selectable security measures, organised into areas with controller and processor member roles. But we found no public information on data protection impact assessments or on recording processor agreements, which caps it well below what a full mandate needs. 3 4 4 3

Report an error

The In-House Counsel

The register of processing activities is genuinely structured: services carry legal bases, transfer bases outside the EU, retention periods and a picklist of security measures, organised into areas with member roles including processors. But we found no public information on impact assessments or on recording processors with their data processing agreements, so I cannot defend this as a complete records programme. 3 4 3 4

Report an error

The Drafted Generalist

The register of processing activities is genuinely guided — I organise work into areas like website or employees, and each service carries legal basis, retention, security measures and a transfer basis picked from dropdowns, which beats a folder of templates. But we found no public information on an impact assessment module or on recording processor agreements, so I can only credit the register itself, not the deeper legal artefacts. 3 3 4

Report an error

The Lead Auditor

The register of processing activities is genuinely structured — services carry legal basis, transfer basis outside the EU, retention and a security-measures picklist, organised into areas with controller and processor member roles. We found no public information on a DPIA module or on processors and their DPAs as managed records, which is the backbone of a defensible DSMS. The link where register services feed the privacy policy is real but does not add the missing assessment layer. 3 4 3 4

Report an error

The IT Integrator

The register of processing activities is genuinely structured: areas, services carrying legal bases, non-EU transfer bases, retention defaults and selectable security measures, with services feeding the generated privacy policy. We found no public information on a DPIA workflow or on recording processors' data processing agreements, so the record sits mid-level. 3 4 4

Report an error

The Skeptic

The register of processing activities is real and more than a form: services carry legal bases (including special categories and criminal data), transfer bases, retention choices and security measures, organised into areas with controller and processor members, and the services feed the generated privacy policy. We found no public information on a DPIA module or on processor DPA management in the captured pages, so the model stops well short of a connected DSMS. 3 4 4 3

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

Data subject requests are handled end to end: an embeddable intake form on the client's site, guided workflows from submission to completion, a dashboard, instant notifications and detailed action logs, covering access through objection. We found no public information on a one-month deadline clock, a breach register or 72-hour notification workflows. 6 5 5

Report an error

The In-House Counsel

The rights tool documents an embeddable intake form, a central dashboard, guided workflows from submission to completion, notifications, action logs and detailed per-request records across the full set of request types. We found no public information on a tracked one-month deadline with escalation, on identity verification of the requester, or on any breach register with a 72-hour notification path — without that breach workflow I would not rely on this suite in an incident. 5 6 5 6

Report an error

The Drafted Generalist

There is a real request machine: an embeddable form for my site, instant notifications on submission, a dashboard, and a guided workflow from receipt to fulfilment with detailed logs of every action. We found no public information on a breach register with the 72-hour clock, and the one-month response deadline is not shown as tracked with reminders, so the incident half of my job would stay on paper. 5 6 6

Report an error

The Lead Auditor

The data subject rights tool shows an embeddable intake form, guided workflows from submission to completion, instant notifications, per-request detail records and action logs — an intake-to-case flow I could walk through. We found no public information on the one-month deadline being tracked, on any breach register with the 72-hour clock, or on deletion execution; only retention periods per processing activity are recorded. Without the deadline and breach halves this stays a request tracker rather than rights and incidents as operations. 5 5 6 4

Report an error

The IT Integrator

Requests are handled end to end — embeddable intake form, guided workflows from submission to completion, notifications, a dashboard, access controls and detailed reports. We found no public information on deadline tracking with reminders, escalation or any breach register with the 72-hour clock; retention periods appear only as a per-activity field. 5 6 5 3

Report an error

The Skeptic

Request handling is genuinely operational: an embeddable intake form, a guided workflow from submission to completion, instant notifications, a dashboard, per-request detail and action logs covering access through objection. We found no public information on a breach register, the 72-hour clock or Art. 12 deadline tracking in the captured pages, and retention periods are recorded per service but with no execution evidence. 6 5 5 3

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

Several regimes are named and maintained: EU GDPR, the ePrivacy Directive, UK GDPR with current Data (Use and Access) Act 2025 content, Swiss FADP, LGPD and US state laws, with a legal team updating the tools automatically as the law moves. We found no public information on EU AI Act or German TTDSG duties, and the register itself is GDPR-framed rather than visibly mapping one record across regimes. 1 7 8 2

Report an error

The In-House Counsel

The pages name EU GDPR, the ePrivacy Directive, UK GDPR, US privacy laws, Swiss FADP and Brazilian LGPD, and the legal content is demonstrably maintained: the UK Data (Use and Access) Act 2025 changes — analytics-cookie exemptions, electronic complaint forms with 30-day acknowledgements, whitelisted legitimate interests — are worked into current product pages by an in-house legal team. We found no evidence that one record maps requirements across regimes, and no AI Act duties appear. 2 1 2 7 8

Report an error

The Drafted Generalist

GDPR, ePrivacy, UK GDPR, Swiss FADP, LGPD and US privacy laws are all named, and the in-house legal team updates the tools automatically — they already cover the 2025 UK changes like the analytics cookie exemption and complaint deadlines, which is exactly the hand-holding I want. We found no public information on the EU AI Act, and the pages do not evidence one record with requirements mapped across all these regimes. 1 7 8

Report an error

The Lead Auditor

Six regimes are named as supported — EU GDPR, ePrivacy, UK GDPR, US state laws, Swiss FADP and Brazil's LGPD — with geo-aware banners adapting per region and the UK GDPR product tracking the Data (Use and Access) Act 2025 changes as maintained content. A legal team updates the tools automatically when the law moves, which I count as a real update practice. We found no public information on requirements being mapped across regimes on one record, or on EU AI Act duties. 2 1 2 7 8

Report an error

The IT Integrator

The pages name EU GDPR, ePrivacy, UK GDPR, Swiss FADP, US privacy laws and LGPD, backed by a dedicated UK product tracking the Data (Use and Access) Act 2025 changes and a legal team that updates the tools as law shifts. We found no public information on one record with requirements mapped across regimes, or on AI Act duties. 1 7 8

Report an error

The Skeptic

GDPR and ePrivacy are covered alongside UK GDPR, Swiss FADP, LGPD and US laws, with the UK Data (Use and Access) Act 2025 changes carried as maintained content — that earns the mid band. The standing-update promise rests on an unnamed in-house legal team, and the captured pages give different figures for the TCF version (2.2 and 2.4) and the client count (100,000+ versus 150,000+), so I discount the trust signals; no AI Act duties and no single record mapped across regimes appear in the captures. 1 8 7 2 1 6

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

Consent evidence is the strong side: verifiable logs with banner versions, timestamps, identifiers, proof documents, and versioned legal notices with retrievable history per version. For the registers I hand to clients and auditors, we found no public information on change history or report generators for the register of processing activities, impact assessments or technical and organisational measures. 2 2 10 10 6

Report an error

The In-House Counsel

Consent evidence is the strong suit: logs of what users consented to, when and under which banner version, retrievable proof documents per consent, legal notices retrievable by identifier and version so a document can be reproduced as it stood, and action logs in the rights tool. We found no public information on report generators for the core registers, read-only auditor access, or on-demand evidence packs covering the whole programme. 6 10 2 2 10

Report an error

The Drafted Generalist

Consent proof is the strength: verifiable logs of what a user agreed to and under which banner version, proofs retrievable through the API, and legal notices kept in versions. We found no public information on generated reports for the processing register, audit evidence packs, or read-only access for an auditor, so a supervisory authority visit would still mean assembling proof myself. 2 2 10

Report an error

The Lead Auditor

The consent domain carries a proper evidence trail: timestamped records with proofs and proof documents, banner versions, checksums, and legal notices retrievable per version, so what a user consented to and under which notice version is reproducible. Beyond consent the trail thins — action logs cover the rights tool, but we found no public information on a revision-safe history for register entries, evidence packs generated on demand, or auditor access. The register record as it stood on a given date is not something these pages let me reconstruct. 6 10 2 2 10

Report an error

The IT Integrator

Consent proof is the strong part: timestamped logs with banner versions, proofs and documents retrievable over the API, versioned legal notices, and proof kept ready for audits, plus detailed action logs and per-request reports in the rights tool. We found no public information on audit evidence packs, read-only auditor access, or report generators for the core registers. 2 10 10 6

Report an error

The Skeptic

Consent evidence is the strong suit: timestamped logs with banner versions, proofs retrievable per consent through the API, versioned legal notices, and detailed action logs on each data subject request. We found no public information on register exports for a supervisory authority, auditor access or generated evidence packs, and "aligned with standards like ISO 27001" is alignment claimed, not a certificate. 2 10 10 6 1

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 JSON API with public and private keys covers consents, subjects, legal notices, documents and privacy policy creation, with rate limits and pagination, plus Zapier actions, CMS integrations and an MCP connector that registers sites, runs scans and generates documents from an editor. We found no public information on API access to the register of processing activities, single sign-on, SCIM provisioning, directory or ticketing connectors, or webhooks. 10 10 11 12 1

Report an error

The In-House Counsel

A documented JSON API with public and private keys covers consents, subjects, documents and legal notices, with rate limits, pagination and versioning, and the platform connects through Zapier with named actions, major CMSs such as WordPress and Shopify, Contact Form 7 and even MCP for AI tooling. We found no public information on single sign-on, SCIM provisioning, webhooks, or recurring review tasks with reminders. 10 1 10 11 12

Report an error

The Drafted Generalist

A documented JSON API for consents and subjects with rate limits, Zapier actions that create consents straight from a form entry, WordPress and Shopify plugins, and even a connector that runs scans from an AI assistant. We found no public information on single sign-on, webhooks, or directory and ticketing connections, so the register itself would still be typed by hand. 10 12 1

Report an error

The Lead Auditor

The consent API is documented to a depth I rarely see — create, read, update and list on consents, subjects, legal notices and documents, cursor pagination, rate limits, public and private keys — plus a Zapier connector with named actions, CMS integrations for WordPress and Shopify, and an MCP path into Claude and ChatGPT. Automation is present where consent work recurs: automatic site scanning and legal updates. We found no public information on single sign-on, directory or HR sources, webhooks, or recurring review reminders. 12 2 10 11

Report an error

The IT Integrator

The consent database has a real documented HTTP API — JSON, public and private keys, consent and subject CRUD, versioned legal notices, cursor pagination, rate limits, a beta channel — alongside Zapier actions, a policy-generation API, CMS plugins and even MCP for Claude and ChatGPT. We found no public information on directory, ticketing or HR connectors, SSO, SCIM or webhooks, and the documented API covers consent objects rather than the register or request objects, so the compliance core does not sync from the estate. 10 10 11 12 12

Report an error

The Skeptic

The consent side is well wired: a documented JSON API over consents, subjects, documents and legal notices with rate limits and key types, Zapier actions, WordPress, Shopify and Contact Form 7 plugins, and even an MCP connector for editors. We found no public information on SSO, SCIM, webhooks or directory and ticketing connectors in the captured pages, and the documented API covers consent objects rather than the privacy register itself. 10 12 11 2 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 proven Italian — iubenda S.r.l. of Milan, with registered share capital and an EU VAT number — operating under the direction and coordination of team.blue NV, whose seat the captured pages do not state. Hosting location, subprocessors and a data processing agreement are unstated on the captured pages, which is unknown rather than non-European, but leaves nothing to diligence before onboarding the vendor as a processor for clients. 13 6 1

Report an error

The In-House Counsel

The contracting entity is proven Italian with an EU VAT number, but the same footer states it stands under the direction and coordination of team.blue NV, whose own seat is not stated in any capture. We found no public information on hosting location, subprocessors, or a data processing agreement — for a platform that maps my processing, that is the gap I would close before signing. 6 13 6

Report an error

The Drafted Generalist

The contracting entity is Italian — iubenda S.r.l. in Milan with an EU VAT number — which is proven, but we found no public information on where data is hosted, which subprocessors touch it, or a data processing agreement. The pages name the group parent, team.blue NV, but give no statement of its seat, so the ultimate jurisdiction stays unknown rather than non-European. 13 6 6

Report an error

The Lead Auditor

The contracting entity is proven Italian — iubenda S.r.l. of Milan, with EU VAT number and chamber of commerce registration — though the footer places it under the direction and coordination of team.blue NV, whose own seat the captured pages do not state. Hosting is described as secure and ISO 27001-aligned without a location, and we found no public information on a published data processing agreement or a subprocessor list. For a platform that maps your processing, that silence is the finding. 6 13 6 1

Report an error

The IT Integrator

The contracting entity is proven Italian — iubenda S.r.l. of Milan with an EU VAT number and fully paid-up capital at the Milan Chamber of Commerce — while standing under the direction and coordination of team.blue NV, whose own seat the captured pages do not state. Hosting location, subprocessors and a data processing agreement are unknown on the evidence we hold. 13 6 6

Report an error

The Skeptic

An Italian contracting entity is proven down to the paid-up share capital and the EU and UK VAT numbers, though the group parent team.blue NV is only described as directing the company, with its own seat not stated in the excerpts. We found no public information on hosting location, a subprocessor list or a data processing agreement in the captured pages — thin for a vendor whose product is itself a record of your processing. 13 6 6 1

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 captured pages name a free plan requiring no credit card and an Ultimate plan whose inclusions are listed, with plans said to scale from startups to enterprises and support included on every paid plan. We found no public price figures for any paid edition, billing period or module, so the real invoice for a client remains a demo conversation. 1 1 6

Report an error

The In-House Counsel

The captured pages contain no monetary figure for any paid edition: a free plan without credit card is public, the Ultimate tier is described by its inclusions, support is said to sit on every paid plan with no add-ons, and the documented path beyond the free tier is a demo booking. A buyer cannot compute an invoice from what is public here. 6 1 2 1

Report an error

The Drafted Generalist

A free plan with no credit card is public and the Ultimate plan's inclusions are listed, but no paid price, billing period, or per-site and per-entity boundaries appear on the captured pages, so the real invoice needs a sales conversation. Unpublished pricing is normal in this market, and this sits at the thinner end of it — though I do credit the plain statement that support is on every paid plan with no add-ons. 1 6 1

Report an error

The Lead Auditor

A free plan with no credit card and a named Ultimate edition with its inclusions are public, and support is stated as included on every paid plan with no add-ons. No figure for any paid edition, billing period, or scale boundary appears on the captured pages, so the real invoice is not computable from them. We found no public information on per-module or entity-based prices. 6 1 2 1

Report an error

The IT Integrator

Public pages state a free plan with no credit card needed and name an Ultimate plan with its inclusions (unlimited third-party services, unbranded banner, consent analytics), with support included on every paid plan. We found no price figure for any paid edition, and no billing period, seat or entity boundaries are published. 1 6 1 2

Report an error

The Skeptic

A free plan with no credit card and a named Ultimate edition with its inclusions listed are public, alongside the claim of no add-ons and no hidden costs. The captured pages show no figures for any paid edition, and the enterprise path is a demo booking, so a buyer cannot compute an invoice from these pages. 1 1 6 7

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

Is iubenda European?

Not determined: the vendor’s pages as captured do not say where iubenda is based. Its vendor, iubenda S.r.l., is incorporated in Italy, per the vendor’s page captured 16 Nov 2026.

Where does iubenda store data?

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

Does iubenda have a free plan?

Yes. iubenda has a free plan, per the vendor’s page captured 22 Sep 2026.

What are the best alternatives to iubenda?

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

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

  1. 1 Vendor page www.iubenda.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 22 Sep 2026 Details →
  2. 2 Privacy policy — found from the homepage www.iubenda.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 30 Sep 2026 Details →
  3. 3 Records & DPIA depth — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 Records & DPIA depth — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 Data subject rights & incidents — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  6. 6 Data subject rights & incidents — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  7. 7 Privacy regime coverage — found from sitemap www.iubenda.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
  8. 8 Privacy regime coverage — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  9. 9 Audit readiness & evidence — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  10. 10 Audit readiness & evidence — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  11. 11 Integrations & automation — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  12. 12 Integrations & automation — found from sitemap www.iubenda.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  13. 13 Legal notice — found from the homepage www.iubenda.com Checked 16 Nov 2026 Details →