Data Protection
iubenda
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
iubenda, from an Italian S.r.l., is website-compliance tooling: cookie and consent banners, generated privacy and cookie policies, terms, and accessibility. The bench scores it strongest on framework coverage, 4-5, where six regimes are named — EU GDPR, ePrivacy, UK GDPR, US privacy laws, Swiss FADP, LGPD — with an in-house legal team monitoring changes and 27 languages without AI translations. Integrations and automation follow at 3-4: CMS integrations, prior cookie blocking, recording of every choice, and Google Consent Mode sync on an IAB-validated TCF 2.2, Google-certified CMP. Weakest are rights and incidents, 0-1, with no public information on data subject requests, statutory clocks, breach registers or deletion, and privacy management, 1-2, document generation with no public information on records of processing, DPIAs or processor management. Sovereignty scores sit at 2: a European vendor, hosting described only as secure, no hosting location, DPA or subprocessor list in public information. The splits are single-point — whether consent recording counts as rights-adjacent, and whether missing API and directory connections cap integrations. A free plan with no credit card needed is public; paid prices are not.
Speaks for it
- Six regimes — EU GDPR, ePrivacy, UK GDPR, US privacy laws, Swiss FADP, LGPD — named as covered, with an in-house legal team monitoring regulatory changes.
- Live consent automation: prior cookie blocking, recording of every choice, and Google Consent Mode sync on an IAB-validated TCF 2.2, Google-certified CMP.
- Integrations for all major CMSs connect directly to the website estate.
- Free plan available with no credit card needed, plus a free scan of privacy, cookie and accessibility posture.
- 27 languages with no AI translations, cited by judges as a maintenance signal.
Held against it
- No public information on data subject request workflows, statutory clocks, breach registers or deletion execution.
- No public information on records of processing, DPIA workflows, or processor and technical-measures management.
- Audit proof stops at consent logs, with no public information on revision-safe history, evidence packs or auditor reports.
- Automation ends at the website estate, with no public information on a documented API, directory import, ticketing or SSO.
- No public information on hosting location, a published DPA or a subprocessor list.
Best for
- You need consent banners and generated privacy and cookie policies spanning EU GDPR, UK GDPR, Swiss FADP, LGPD and US privacy laws across your websites.
- You want Google Consent Mode sync and TCF 2.2 signaling live inside a major CMS.
- You want to start on a free plan with a free site scan before committing budget.
Avoid if
- You need to run data subject requests, deletion workflows and breach notification through a system.
- You need a records backbone — records of processing, DPIAs, processor and TOM management — rather than generated documents.
- You must hand an auditor revision-safe history and evidence packs beyond consent logs.
- Your compliance work reaches past websites into directories, ticketing and SSO-connected systems.
The scores
Records & DPIA depth
Show reasoningHide reasoning
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.
The External DPO
The register of processing activities is genuinely structured — legal bases, transfer bases, security measure pick-lists, retention and controller/processor roles all live on the service record, with "areas" for website, employees, recruiting and more. But we found no public information on data protection impact assessments, on processor contract or DPA management, or on group template reuse across mandates, which is what I would need to run thirty RoPAs from one seat. 3 4 5
The In-House Counsel
The register of processing activities is properly structured — every service carries legal basis, transfer legal basis, security measures, retention and controller/processor roles, organized by areas such as website, employees and recruiting. But we found no public information on a DPIA module, and processor management appears as a role label rather than DPA management, so the deeper artifacts a DSMS owes me are not evidenced. 3 4
The Drafted Generalist
The processing register is genuinely structured: each service carries legal basis, transfer basis, security measures, retention and role assignments inside the tool, with scopes for website, app, stores and employees. But we found no public information on data protection impact assessments or on managing processor agreements, so the deeper legal artifacts are not in view. 3 4
The Lead Auditor
The register of processing activities is a genuinely structured module: legal bases, transfer bases, retention, security-measure options and controller/processor roles sit on each service record, scoped by area. But we found no public information on impact assessment functionality at all, and processor management appears only as a role label with no evidenced DPA handling, so the register is a solid single artifact rather than a connected legal model. 3 4
The IT Integrator
The register of processing activities is a real structured model — services carry legal basis, transfer basis, retention, security measures and controller/processor roles, with areas like employees and recruiting as separate perimeters. But we found no public information on a DPIA module or processor/DPA management, so the legal artifacts beyond the record itself are unevidenced. 3 4
The Skeptic
The register of processing activities is genuinely modeled: services carry legal basis, transfer legal basis, retention policy, security-measure options and roles, with scopes created per perimeter and defaults reused across services. We found no public information on a DPIA function, on processor/DPA management beyond role labels, or on outputs a supervisory authority would accept, so this sits between a structured register and a connected data model. 3 4
Data subject rights & incidents
Show reasoningHide reasoning
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.
The External DPO
The rights tool has real intake — an embeddable request form, a dashboard, instant notifications and guided workflows covering access through objection. But we found no public information on statutory deadline tracking or escalation, on a breach register with the 72-hour clock, or on deletion execution tied to the record; erasure appears as a request type, not a workflow I could walk an authority through. 5 6
The In-House Counsel
The intake side is presentable — an embeddable request form, six request types, guided workflows, instant notifications and action logs. But we found no public information on the statutory one-month clock being tracked or escalated, on a breach register with the 72-hour clock, or on any output that would serve as an authority notification, so my breach workflow would have to live outside this tool. 5 6
The Drafted Generalist
Request handling looks like what I'd want on my desk: an embeddable form on our site, six request types, a guided workflow with notifications, controlled access and action logs, all on one dashboard. We found no public information on statutory deadline clocks, escalation, or any breach register with authority notification, so the incident half of the job is unevidenced. 5 6
The Lead Auditor
Request handling is operationalized rather than an inbox — an embeddable intake form, guided submission-to-completion workflow, instant notifications, detailed action logs and controlled access — covering access, rectification, erasure, portability, restriction and objection. We found no public information on statutory deadline tracking, identity verification, or a breach register with the 72-hour clock, and deletion appears as a request type with no evidenced execution trail. 5 6
The IT Integrator
Request handling has the right intake shape — an embeddable form, a dashboard, guided workflows and instant notifications across the standard request types. We found no public information on statutory deadline tracking, a breach register or authority notification, and erasure appears only as a request type with no deletion execution evidence. 5 6
The Skeptic
Request handling shows an embeddable intake form, a central dashboard, instant notifications and guided workflows covering access, rectification, erasure and portability. We found no public information on statutory deadline tracking or escalation, and no public information on a breach register or authority-notification workflow; deletion appears as a request type rather than a documented execution. 5 6
Privacy regime coverage
Show reasoningHide reasoning
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.
The External DPO
GDPR, ePrivacy, UK GDPR, US privacy laws, Swiss FADP and LGPD are all named as covered, geo-aware banners adapt per region, and a legal team updating the tools automatically when the law moves is an unusually explicit maintenance claim. But we found no public information showing a single processing activity documented once across regimes rather than per tool, and no public information on AI Act privacy duties. 1 2 7 8
The In-House Counsel
The regime list is broad and visibly maintained — EU GDPR and ePrivacy, UK GDPR with the 2025 Data (Use and Access) Act tracked, Swiss FADP, LGPD and US laws, updated by an in-house legal team as the law moves, which I credit. The mapping story is the gap: the register is described as usable for processing generally rather than linking one record across regimes, and we found no public information on EU AI Act privacy duties. 1 2 7 8
The Drafted Generalist
They name the regimes I'd get asked about — EU GDPR, ePrivacy, UK GDPR, US privacy laws, Swiss FADP, Brazilian LGPD — with geo-aware banners and a legal team that updates the tools automatically, including visible tracking of the UK Data (Use and Access) Act 2025. Cross-regime mapping shows up as one general-purpose register rather than proven one-record-many-regimes, and we found no public information on EU AI Act duties. 1 2 8
The Lead Auditor
Documented coverage is broad for the market: EU GDPR, ePrivacy, UK GDPR including Data (Use and Access) Act 2025 tracking, US privacy laws, Swiss FADP and LGPD, with the vendor stating tools are updated automatically when the law changes. We found no public information on one-record-many-regimes mapping or AI Act privacy duties, so each regime reads as its own configuration rather than a shared data basis. 1 2 7 8
The IT Integrator
Six regimes are named from EU GDPR through FADP and LGPD, geo-aware banners adapt per region, and a legal team updates the tools when the law moves — the UK pages even track the Data (Use and Access) Act 2025. We found no public information on EU AI Act privacy duties or on a single record mapping across regimes instead of per-regime content packs. 1 2 7 8
The Skeptic
GDPR, ePrivacy, UK GDPR, US laws, Swiss FADP and Brazilian LGPD are named as covered, with an in-house legal team claimed to update tools automatically and UK Data (Use and Access) Act 2025 changes tracked. The cross-regime mapping evidence is banner-level (geo-aware banners per region), and we found no public information on EU AI Act duties or on one processing record serving several regimes without re-entry. 1 2 7 8
Audit readiness & evidence
Show reasoningHide reasoning
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".
The External DPO
Consent evidence is the strong point — timestamped consent logs with proofs, IP and banner versions, legal notices retrievable per version through the API, plus claimed detailed action logs. But we found no public information on revision-safe history for the register itself, auditor access roles, or report generators that would let me hand a client a finished audit file without days of assembly. 2 6 9 10
The In-House Counsel
Consent evidence is the strong suit — versioned legal notices, stored proofs and proof documents, timestamped consent logs with banner versions — a defensible record for a consent audit. For the registers I see only the claim of detailed action logs and request reports; we found no public information on revision-safe change history, auditor-ready evidence packs, or reconstructing the state of a record on a given date. 2 6 10
The Drafted Generalist
Consent evidence is the strong part: timestamped logs with proofs and banner versions kept ready for audits, legal notices versioned and retrievable per version, plus action logs on rights requests. We found no public information on revision-safe history for the processing register, auditor access roles, or on-demand evidence packs, so a state-of-the-world on a given date is not in view. 2 5 10
The Lead Auditor
Consent evidence is the strong part: stored proofs with timestamps, identifiers and banner versions, plus versioned legal notices retrievable per version through the API — that answers 'which notice was live on date X' for consent. But we found no public information on revision-safe change history for the registers themselves, auditor access roles, or evidence packs assembled on demand; the audit trail on the records side is limited to action logs on rights requests. 2 6 10
The IT Integrator
Consent evidence is genuinely solid — timestamped logs with proofs and proof documents retrievable by API, versioned legal notices, and action logs plus detailed reports on the rights tool. For the wider compliance record we found no public information on revision-safe change history, evidence packs or auditor access roles, so a full audit file still gets assembled by hand. 2 6 10
The Skeptic
Consent evidence is the real thing — timestamped proofs and versioned legal notices retrievable per consent event — while the register side rests on a marketing bullet about "detailed logs of all actions". We found no public information on revision-safe change history for the register, auditor reports or reconstructing the state on a past date; the captured pages also give different figures for the customer count, which weighs on how much the unverifiable numbers can carry. 6 10
Integrations & automation
Show reasoningHide reasoning
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.
The External DPO
The consent API is properly engineered — documented REST with subjects, consents and legal notices, cursor pagination, honest rate limits — and Zapier plus an MCP connector that registers a site, runs a scan and generates documents is real automation I could use for batch client setup. But we found no public information on directory import, SSO or SCIM, ticketing or HR connectors, webhooks, or API access to the register and rights modules — the estate feeds a DSMS lives on. 10 11 12
The In-House Counsel
There is a real, documented REST API for consent objects — keys, rate limits, filtering, pagination — plus Zapier actions, CMS plugins, and an MCP connector that can register a site, run a scan and generate documents from an editor. We found no public information on directory import, SSO/SCIM or ticketing connectors, and the workflow automation shown is guidance and notification rather than delegation and escalation. 1 10 11 12
The Drafted Generalist
There's a real, well-documented API for consents, subjects, legal notices and policy creation, plus Zapier templates, CMS plugins for WordPress and Shopify, and MCP connections so I could register a site or run a scan from an AI editor. We found no public information on directory import, single sign-on, or connectors for ticketing and HR, so estate sync is not in view. 10 11 12
The Lead Auditor
The consent side is well wired: a documented HTTP API with subjects, consents, filtering, pagination and rate limits, a JavaScript library, CMS plugins, Zapier actions and even MCP connectors for scans and document generation. We found no public information on directory import, SSO/SCIM, webhooks or ticketing and HR connectors, and the processing register itself has no documented API — the automation reaches the website estate, not the internal one. 9 10 11 12
The IT Integrator
There is a real documented REST API — auth keys, cursor pagination, rate limits, a beta channel — for consent subjects, consents and legal notices, plus a Zapier bridge and MCP operations to register a site, run a scan and generate documents. But the API story stops at documents and consent: we found no public information on directory import, SSO, webhooks, ticketing connectors, or any API surface for the register and rights modules, so the compliance data does not feed from the existing IT estate. 10 11 12
The Skeptic
A documented HTTP/JSON API with public and private keys, stated rate limits and full CRUD for consents, subjects and legal notices — plus Zapier actions, CMS plugins and MCP operations — is substance rather than integration logos. It is consent-centric, though: we found no public information on directory import, SSO/SCIM, ticketing connectors or webhooks, nor an API for the processing register itself. 10 11 12
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the compliance record of the whole company actually lives and under whose law — 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.
The External DPO
The legal entity is Italian — iubenda S.r.l. of Milan under EU jurisdiction, directed and coordinated by team.blue NV — which is where I want a client's compliance record to live. But we found no public information on hosting location, data residency, subprocessors or a published DPA in the captured pages, so the chain below the entity is undocumented. 6 7
The In-House Counsel
The registered seat is confirmed in Milan with an Italian VAT number, and the parent, team.blue NV, is named — that is where the confirmed chain ends. We found no public information on hosting location, a published DPA, or a subprocessor list, and I will not put a client's register of processing into a chain I cannot document. 6 7
The Drafted Generalist
The company is European at the root: Milan registration, Italian VAT, and coordination through the team.blue group that also owns consentmanager, CookieFirst and Complianz. But we found no public information on hosting location, data residency, subprocessor exposure, or a published DPA, and security is described only as aligned with ISO 27001 rather than certified. 6 7
The Lead Auditor
The legal entity is confirmed European — a Milan-registered company with Chamber of Commerce entry, coordinated by a parent NV — which is the right starting point for a system holding the compliance record. But we found no public information on hosting location, data residency, subprocessor exposure or a published DPA, so the chain below the entity cannot be assessed from public evidence. 6 7
The IT Integrator
The entity is European — iubenda S.r.l. registered in Milan with an Italian VAT number — under the direction and coordination of team.blue NV. We found no public information on hosting location, a published DPA, or a subprocessor list for the platform holding consent and rights data. 1 6 7
The Skeptic
The registered entity is iubenda S.r.l. in Milan under a parent listed as team.blue NV, and that is where the confirmed facts end. We found no public information on hosting location or data residency, and no published DPA or subprocessor list — for the system that would hold a customer's full compliance record, that undocumented chain is the deciding fact. 6 7
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
0 — No public prices at all; every configuration is a sales conversation.
3 — 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.
The External DPO
The only public pricing facts are a free plan with no credit card and a named Ultimate plan whose perks are listed without figures; we found no public prices for any edition, module, billing period or scale step. Multi-licenses mechanics appear only as API behavior for creating policies per destination user, unpriced, so neither a 100-employee company nor my ten-client practice can compute a real invoice. 1 6 11
The In-House Counsel
A free plan with no credit card and a free scan are the only figures I can see; the named Ultimate plan lists features, we found no public information on any price for it, and the captured pages point to booking a demo. The real invoice for a mid-sized group is not computable from public pages. 1 6 7
The Drafted Generalist
The only price visible is free: a free plan with no credit card, a free scan, and a named Ultimate plan with no figure attached, plus a demo button. There's a promise of no add-ons and no hidden costs, but we found no public prices for any paid edition, so I can't begin to compute what an 80-employee firm would actually pay. 1 6 7
The Lead Auditor
A free plan without credit card and a named Ultimate tier with feature descriptions are public, and the vendor claims no hidden costs, but no monetary figure appears on any captured page, so the real invoice stays a sales conversation and a demo is the stated path. We found no public information on per-module prices, entity or user boundaries, billing periods or setup fees. 1 6 7
The IT Integrator
A free plan with no credit card and support included on paid plans are the only public pricing signals, and plan names like Ultimate and multi-licenses appear without figures. We found no public prices for any paid edition or module, so computing the real invoice is a sales conversation. 1 6
The Skeptic
A free plan is publicly stated with no credit card required and an Ultimate plan is named with its features, but not one paid figure appears in the captured pages — no edition prices, module prices, billing periods or setup fees. Beyond the free tier a buyer cannot compute any total; the offered path is a demo booking. 1 6 7
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in IT ⚠ unverified | 3/3 pts | 2 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. A UK VAT number is also listed for sales purposes, but the registered seat and Chamber of Commerce entry place the legal entity in Milan, Italy.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 9 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.iubenda.com Checked 22 Sep 2026 Details →
- 2 Privacy policy — found from the homepage www.iubenda.com Checked 30 Sep 2026 Details →
- 3 Records & DPIA depth — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 4 Records & DPIA depth — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 5 Data subject rights & incidents — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 6 Data subject rights & incidents — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 7 Privacy regime coverage — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 8 Privacy regime coverage — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 9 Audit readiness & evidence — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 10 Audit readiness & evidence — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 11 Integrations & automation — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →
- 12 Integrations & automation — found from sitemap www.iubenda.com Checked 1 Oct 2026 Details →