OneTrust
Rest of world Report an errorPanel 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 OneTrust LLC · www.onetrust.com
Compare with DataGuard → Report an error on this page Is this your product? →
Link to this page
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.
OneTrust at a glance
- Vendor
- OneTrust LLC
- Headquarters
- Not stated on the vendor’s pages as of 1 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Oct 2026
- Panel verdict
- The AI panel rates OneTrust 3/5, the mean of 6 judges. The judges scored OneTrust, a data protection platform from OneTrust LLC, Atlanta, from one set of captured public pages. how scores are made
- As of
- Vendor pages captured 31 Aug 2026 to 1 Oct 2026; evaluated by the panel 27 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
The judges scored OneTrust, a data protection platform from OneTrust LLC, Atlanta, from one set of captured public pages. Its strongest area is integrations and automation, with scores at 8–9: a developer portal documents API families across assessments, data mapping, data subject requests, incident management and SCIM user provisioning, plus more than 500 pre-built plug-ins and named connectors such as MuleSoft, Apigee and Amazon API Gateway. Privacy management follows at 7–8, built on a live record of processing fed from assessments, system integrations and bulk imports, with automated DPIA and PIA workflows. Sovereignty is weakest at 3–4: the captured pages show an Atlanta headquarters, Data Privacy Framework certification under FTC enforcement, and SCCs plus the UK addendum as transfer mechanisms, while we found no public information on hosting location or where subprocessors sit. The judges split by a point on framework coverage, 5–6, crediting deep GDPR operationalization and Europrivacy preparation while we found no public information on country variants such as BDSG, UK GDPR or the Swiss nDSG. Pricing transparency scored 0; this vendor publishes no prices.
Speaks for it
- A developer portal documents API families across assessments, data mapping, data subject requests, incident management and SCIM user provisioning, with more than 500 pre-built plug-ins and connectors such as MuleSoft and Apigee
- A live record of processing builds from assessments, system integrations, questionnaire responses and bulk imports into one central inventory, with automated DPIA and PIA workflows
- Data subject request handling is documented end to end — automated identity verification, discovery, deletion and redaction, legal hold checks, timestamped logs — against a one-month deadline with a two-month extension
- Evidence is exportable: an audit log covering deleted assessments, assessment exports with respondents, approvers and risks, and bulk exports of data subjects, consent and cookie receipts
- Trust documentation is published: a DPA, standard contractual clauses, a Schrems II response and a subprocessor list
Held against it
- Sovereignty scores sit at 3–4 — an Atlanta-headquartered, FTC-enforced Data Privacy Framework chain — and we found no public information on hosting location or where subprocessors sit
- Incident handling is thin on the captured pages: we found no public information on a 72-hour clock, severity assessment or an authority-notification workflow
- Framework coverage reaches 5–6, with GDPR and CCPA shown, and we found no public information on BDSG, UK GDPR, the Swiss nDSG or AI Act duties as maintained content
- We found no public information on read-only auditor access, on-demand evidence packs, or management and data protection officer reports
- The vendor's developer documentation states the GDPR transfer impact assessment template is not directly addable and must be imported through an API as a stop-gap
Best for
- You need to run data subject requests at volume, with documented APIs, automated identity verification and timestamped logs
- You want a record of processing that builds itself from assessments and system integrations rather than re-typed spreadsheets
- You run a GDPR-first program and value Europrivacy certification preparation with built-in workflows
- Your stack depends on a broad integration fabric — more than 500 pre-built plug-ins and connectors such as MuleSoft, Apigee and Amazon API Gateway feeding request servicing
Avoid if
- You must establish a verifiably European contracting and hosting footing before signature — the captured pages show an Atlanta headquarters under FTC enforcement of the Data Privacy Framework, and sovereignty scores sit at 3–4
- You need a documented breach workflow with a 72-hour clock and an authority notification — the captured pages reach only streamlined incident management and maintained incident records
- Your compliance map runs through country variants like BDSG, UK GDPR or the Swiss nDSG — framework coverage scores sit at 5–6 and GDPR with CCPA is what the evidence shows
The scores
| 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 | 1.5 of 5 |
Records & DPIA depth
Show reasoningHide 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.
The External DPO
A live record of processing drawn from assessments, system integrations, questionnaire responses and bulk imports into one central inventory, automated DPIA and PIA workflows, and a centralized vendor record of DPAs, transfer mechanisms and security obligations — that is the connected model I bill clients for, and template import and export APIs make artefacts reusable. We found no public information on multi-client operation for an external data protection officer or on TOMs assigned per processing activity, so a thirty-mandate practice cannot confirm the reusability it lives on. 3 2 10
The In-House Counsel
The record of processing is presented as a live central inventory fed from assessments, system integrations, questionnaire responses and bulk imports, with automated DPIA and PIA workflows and vendor files holding the DPAs, transfer mechanisms and security obligations — that is the connected model I want standing in front of an auditor. Two reservations for the file: the captured pages give no view of how technical and organisational measures are modelled against individual processing activities, and the published GDPR transfer impact assessment template needs a documented import workaround because the vendor's own documentation states it is not supported natively. 3 2 10
The Drafted Generalist
The record of processing activities is genuinely alive — it builds itself from assessments, system integrations, questionnaire responses and bulk imports into one central inventory, with DPIA and PIA workflows automated and vendor DPAs, transfer mechanisms and remediation outcomes kept in the same record. I found no public information showing TOMs assigned to individual processing activities, which is exactly the thing my auditor asks for. 2 3 10
The Lead Auditor
The live register of processing activities — fed from assessments, system integrations, questionnaire responses and bulk imports into one central processing inventory — together with automated DPIA and PIA workflows, a versioned GDPR transfer impact assessment template, and vendor due diligence with a centralized record of processing agreements and transfer mechanisms, is a genuinely connected model. I found no public information on technical and organisational measures being modelled and assigned to processing activities, on legal bases linked to records, or on a register output stated as ready for a supervisory authority, which the top level demands. 2 3 10
The IT Integrator
The record of processing is generated live from assessments, system integrations, questionnaire responses and bulk imports into a central inventory — the connected model I want, with vendor records holding their DPAs and transfer mechanisms and change monitoring routing updates of systems and data flows for review. Automated DPIA and PIA workflows plus a published GDPR Transfer Impact Assessment template round it out; we found no public information on TOM modelling or DPIA need derived from the record, so it stops short of the fully connected top tier. 3 2 10
The Skeptic
The developer documentation backs the marketing: a live record of processing fed by assessments, system integrations, questionnaire responses and bulk imports; automated DPIA and PIA workflows; and a published, versioned GDPR transfer impact assessment template, with vendor due diligence and a centralized record of DPAs and transfer mechanisms. I found no public information on TOMs assigned to processing activities, legal bases on the record, or a register output ready for a supervisory authority, so I stop short of the fully connected data model. 2 3 10
Data subject rights & incidents
Show reasoningHide 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.
The External DPO
Request handling is documented end to end: intake through the integrated secure portal, automated identity verification, data discovery, redaction and deletion with legal hold checks, every action logged with a timestamp, six rights supported, and the one-month response deadline with the two-month extension named. Incident management and incident records are documented, with a dedicated incident management API family. We found no public information on a 72-hour clock, per-breach severity assessment or authority-notification drafting. 3 7 8
The In-House Counsel
Rights handling is documented the way I would defend it: intake through a secure customer portal, automated identity verification, data discovery, deletion and redaction, legal hold checks, every action timestamped, against the one-month response deadline with the two-month extension. On incidents the pages name incident management and the maintenance of incident records, but I found no public information on a 72-hour clock, a per-breach severity assessment, or a workflow that produces the authority notification — that is exactly what I would probe before relying on it in a breach. 3 7 8
The Drafted Generalist
Requests are handled end to end: a secure intake portal with identity verification, automated data discovery, redaction and deletion, legal hold checks, and every step logged with a timestamp against the one-month deadline with a two-month extension. The incident half only shows records kept alongside the registers — I found no public information on a 72-hour clock, severity assessment or a ready authority notification. 3 7 8
The Lead Auditor
The request side is documented end to end — portal and API intake, automated identity verification, personal data discovery, deletion and redaction, every action logged with timestamps, and the one-month deadline with a two-month extension tracked — which is walkable in an audit. On breaches I see only streamlined incident management and incident records kept with the other documentation; I found no public information on a 72-hour clock, a severity assessment, or a workflow that produces the authority notification, and none tying deletion execution back to the processing register. 3 7 8
The IT Integrator
Request handling is real operations: intake through a secure portal with automated identity verification, the one-month deadline with a two-month extension stated, automated discovery, redaction, deletion and legal hold checks, every action timestamped, and a documented API to submit a request on a data subject's behalf. Incidents appear only as maintained records and streamlined incident management — we found no public information on a 72-hour clock, per-breach severity assessment or the authority notification workflow. 3 7 8 2
The Skeptic
Request handling is documented in substance: an intake portal unified with the consent platform, automated identity verification, data discovery, deletion and redaction with legal hold checks, timestamped logging of every action, and a DSAR submission API with headers, response codes and rate limits. For incidents the captured pages reach only 'streamline incident management' and maintained incident records; I found no public information on a 72-hour clock, severity assessment, or the authority notification being produced. 3 7 8
Privacy regime coverage
Show reasoningHide 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.
The External DPO
GDPR is modelled deeply — readiness assessments aligned to the seven principles, an official Europrivacy partnership supplying certification workflows and templates, and a published GDPR transfer impact assessment template which the developer pages say must be imported through an API as a stop-gap rather than added directly. GDPR and CCPA are named as regimes serviced through the same portal. We found no public information on country variants such as BDSG, UK GDPR or the Swiss nDSG, or on requirements mapped across regimes on one record. 3 10 7
The In-House Counsel
GDPR is operationalised deeply — readiness assessments against the seven principles, automated DPIAs, a published transfer impact assessment template — with CCPA named in the request portal and Europrivacy certification preparation as a European extra. I found no public information on BDSG, Swiss nDSG, UK GDPR or ePrivacy/TTDSG as supported regimes, nor any documented update cadence when a law moves, so I cannot credit the broader mapping. 3 7 10
The Drafted Generalist
GDPR is built in as a continuous program with readiness assessments against the seven principles, and as an official Europrivacy technology partner they offer certification-prep workflows, templates and documentation; CCPA is named for request handling too. I found no public information on BDSG, the Swiss nDSG, UK GDPR or AI Act duties on the captured pages. 3 7 10
The Lead Auditor
GDPR is deeply operationalised — readiness assessments aligned to the seven principles, automated DPIA workflows, the GDPR transfer impact assessment template, and Europrivacy certification preparation as an official technology partner — with CCPA named alongside GDPR in the request portal and integration descriptions. I found no public information on BDSG, TTDSG, Swiss nDSG or UK GDPR support, on AI Act duties as maintained content, or on any published update cadence when a regime changes, so coverage does not reach the connected multi-regime level. 2 3 7 10
The IT Integrator
GDPR runs deep — principle-aligned readiness assessments, automated DPIA and PIA workflows, a published Transfer Impact Assessment template, and Europrivacy certification prep with built-in workflows — and CCPA is operational in the customer portal and connector descriptions rather than merely named. We found no public information on BDSG, Swiss nDSG, UK GDPR or AI Act privacy duties as maintained content, so cross-regime mapping on one record beyond GDPR and its companions is not shown. 3 7 10 14
The Skeptic
GDPR runs deep — readiness assessments aligned to the seven principles, automated DPIA and PIA workflows, a versioned transfer impact assessment template, and Europrivacy certification prep as an official technology partner — and CCPA is named with its own mechanics in a global opt-out API endpoint. Beyond those I found no public information on BDSG, Swiss nDSG or UK GDPR support or on a published update cadence when a regime changes, and the AI Governance module appears only as an API family without AI Act duties shown as maintained content. 3 8 10
Audit readiness & evidence
Show reasoningHide 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.
The External DPO
Every data subject request action is timestamped, decisions and approvals on changes are captured, per-individual consent history can be produced across channels, and an exportable audit log covers even deleted assessments — supervisory-authority material a client can walk through. Bulk exports of data subjects, consent receipts and cookie receipts are documented for compliance reporting. We found no public information on generated evidence packs, management or DPO reports, or read-only auditor access. 3 11 12
The In-House Counsel
Proof is producible on demand: an assessment export API returning questions, responses, respondents, approvers and risks, an export of the audit log for deleted assessments, bulk exports of data subject, consent and cookie receipts for compliance reporting, and consent history reproducible per individual across channels, with decisions and approvals captured for vendor remediation. Management and data protection officer reporting and read-only auditor access are not shown on the captured pages, which keeps this just short of the top band. 11 12 3
The Drafted Generalist
I could show an auditor things: consent history for any individual across any channel, timestamped request logs, decisions and approvals captured on changes, an export of the audit log for deleted assessments, and bulk exports of data subjects and consent receipts for compliance reporting. I found no public information on read-only auditor access or management and officer reports generated on demand. 3 11 12
The Lead Auditor
Real evidence trails exist: an exportable audit log of deleted assessments, change monitoring that captures decisions and approvals, per-individual consent history, timestamped request logs, and bulk exports of data subject, consent and cookie receipts for regulatory reporting. But my core asks are undocumented — I found no public information on evidence packs generated on demand, management or data protection officer reports, read-only auditor access, or reproducing any record as it stood on a given date. 3 11 12
The IT Integrator
Evidence collection is scriptable, which is how it should be: an assessment export API returns respondents, approvers, questions, responses and risks, an audit log covering even deleted assessments is exportable, bulk export jobs serve compliance reporting, and DSAR actions and per-individual consent history are timestamped. What is not documented is revision-safe history in the audit-grade sense, read-only auditor access or one-click officer reports, so this sits just below the revision-safe tier. 11 12 3 10
The Skeptic
The developer documentation carries this criterion: an exportable audit log of deleted assessments, assessment exports including respondents, approvers, questions, responses and risks, bulk exports of data subjects and consent receipts for compliance reporting, plus timestamped logging and captured decisions and approvals. I found no public information on read-only auditor access, on-demand evidence packs, or management and data protection officer reports. 3 11 12
Integrations & automation
Show reasoningHide 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.
The External DPO
The developer portal documents API families across nearly the whole platform — inventory, object manager, task management, SCIM user provisioning, assessments, DSR and incident management — alongside 500+ pre-built plug-ins, named connectors such as Apigee, Microsoft Azure App Gateway and a OneTrust-developed MuleSoft connector, and automation of identity verification, deletion, legal hold checks and redaction. The bridging documentation itself notes some native methods are not exposed without a request to a OneTrust representative. We found no public information on webhooks or event streams. 8 10 5 14 7
The In-House Counsel
The developer portal documents REST APIs across effectively the whole platform — privacy automation, assessments, data mapping, incident management, consent, inventory, object manager, SCIM provisioning, task management — alongside native Swift and Java SDKs, bridges to React Native, Flutter and Cordova/Ionic, documented rate limits, and more than 500 pre-built plug-ins with named connectors such as MuleSoft and Apigee. Event or webhook coverage and escalation rules are not separately documented; everything else behaves like infrastructure. 10 5 9 8
The Drafted Generalist
This is the part that would stop me re-typing: over 500 pre-built plug-ins, documented APIs across the whole platform including SCIM user provisioning, task management and an object manager, native mobile SDKs with bridging for React Native and Flutter, and named connectors like MuleSoft, Apigee and Azure. Identity verification, discovery, deletion, legal hold checks, redaction and vendor reassessments are all automated, though I found no public information on webhooks. 5 7 9 10 12 14
The Lead Auditor
The documented API families span assessments, data mapping, request automation, incident management, inventory, documents, task management and SCIM user provisioning, backed by more than 500 pre-built plug-ins and named connectors such as Amazon API Gateway, Apigee, Microsoft Azure App Gateway and MuleSoft, with recurring work — vendor reassessments, identity verification, deletion, redaction — automated rather than re-typed. Webhooks and AI assistance with human review are the only upper-level items for which I found no public information. 3 5 7 10 14
The IT Integrator
This is what I look for: a developer portal with documented API families for assessments, data mapping, DSR, incident management, inventory, task management, access management and SCIM user provisioning, 500+ pre-built plug-ins, and named connectors such as MuleSoft, Apigee, Amazon API Gateway and Azure App Gateway — some developed by OneTrust itself — feeding DSAR servicing. The record of processing draws from system integrations instead of retyping, and consent preferences are enforced in downstream systems automatically. We found no public information on webhooks as an event backbone or on delegation and escalation rules, which is what keeps a strong API platform from behaving like self-driving infrastructure. 10 8 12 5 14 3 7
The Skeptic
The most verifiable part of the product: the developer portal documents API families across the platform — assessment automation, DSR, incident management, data mapping, SCIM user provisioning, task management, and bulk export jobs that can be created, status-checked, downloaded and cancelled — with native Swift and Java SDKs bridged to React Native, Flutter and Cordova, documented rate-limit headers, and named connectors behind a claim of more than 500 pre-built plug-ins. Webhooks, SSO and AI assistance with human review are the unproven remainder, so the score sits at the documented-API-and-provisioning level rather than higher. 5 8 10 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: 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.
The External DPO
A privacy notice, data processing agreement, Standard Contractual Clauses, a Schrems II response and a subprocessor list are published, with the UK addendum named for transfers. The contracting side is US-headquartered in Atlanta and under Federal Trade Commission jurisdiction for Data Privacy Framework enforcement. We found no public information on hosting location or where the subprocessors sit, so the EU footing of a client's most concentrated processing cannot be established from the captured pages. 6 4 5
The In-House Counsel
What is proven is an American contracting posture: headquarters in Atlanta, Data Privacy Framework self-certification under Federal Trade Commission enforcement, transfers on standard contractual clauses and the UK addendum supplemented per the European Data Protection Board's recommendations, with a published DPA and a subprocessor list page. Hosting location and where the subprocessors sit are not stated on the captured pages — for the platform that would hold our entire compliance record, those are questions I would want answered in writing before signature. 6 4
The Drafted Generalist
My compliance record would sit with an Atlanta-headquartered US company under FTC enforcement of the Data Privacy Framework, with a published DPA, Standard Contractual Clauses, a subprocessor list and a Schrems II response available. I found no public information on hosting location or ownership on the captured pages. 6 4 8
The Lead Auditor
The privacy notice places the company in Atlanta with U.S. Federal Trade Commission jurisdiction under the Data Privacy Framework, and the trust page publishes a data processing agreement, standard contractual clauses, a Schrems II response and a subprocessor list. I found no public information on hosting location or on which subprocessors touch customer content, and ownership is unconfirmed, so a European buyer cannot verify where this platform's own processing of their data sits. 6 4
The IT Integrator
The captured pages put the contracting posture in the United States — Atlanta headquarters, a US LLC, and a DPF-certified entity under FTC enforcement, relying on SCCs and the UK IDTA with supplementary measures for transfers — while a DPA, an MSA and a viewable subprocessor list are published. We found no public information on hosting location or data residency options on these pages, so the residency dimension stays unknown rather than European. 6 4
The Skeptic
The privacy notice states the chain plainly: headquarters in Atlanta, Data Privacy Framework certification held by OT Technology Inc. under FTC enforcement, and SCCs plus the UK addendum as transfer mechanisms — a US-jurisdiction chain. The trust page does publish a DPA, SCCs and a subprocessor list, but I found no public information on hosting location or where any subprocessor sits, so European residency is unproven rather than stated. 6 4
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 — 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.
The External DPO not rated — no public information
We found no public information on pricing, editions, modules or billing terms on the product, GDPR solution and DSR automation pages I read. For my clients that means the real invoice cannot be computed from public pages; every configuration is a sales conversation. 2 3 7
The In-House Counsel not rated — no public information
We found no public information on prices, editions, module boundaries or billing periods on the homepage, product and company pages we reviewed. The invoice cannot be computed from public material, so this stays open for the procurement file. 1 2 5 7
The Drafted Generalist not rated — no public information
We found no public information on prices — no editions, modules, billing periods or setup fees on the homepage or the product pages we read. The only figures a buyer can see are efficiency claims like reducing cost to fulfill 'by up to 99%', not what the invoice would be. 1 2 3 7
The Lead Auditor not rated — no public information
We found no public information on pricing — no editions, prices, billing periods or terms appear on the homepage, product pages, developer documentation or company pages we read. 1 2 5 7
The IT Integrator not rated — no public information
We found no public information on pricing in the captured pages: no edition prices, tiers, billing periods, user boundaries or setup fees appear on the homepage, the privacy operations product page or the data subject request product page we read. 1 2 7
The Skeptic not rated — no public information
I found no public information on pricing in the captured pages — no editions, figures, billing periods or setup fees appear on the homepage, the privacy operations product page, the data subject request product page or the about page. Every price therefore starts as a sales conversation, which this market treats as normal and this criterion records as fact. 1 2 5 7
European sovereignty — proven facts
1 of 6 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| 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 |
Published, self-serve
unverified
Why unverified?The excerpt shows only a public Trust Center link to a legal documents area that lists the DPA; whether the agreement can actually be concluded online or sits behind a customer login is not stated. |
1/1 pts | 4 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about OneTrust
Is OneTrust European?
No. whats-best.ai classifies OneTrust as Rest of world.
Where does OneTrust store data?
Not stated on the vendor’s pages as of 1 Oct 2026.
Does OneTrust have a free plan?
Not stated on the vendor’s pages as of 1 Oct 2026.
What are the best alternatives to OneTrust?
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: OneTrust alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt shows only a public Trust Center link to a legal documents area that lists the DPA; whether the agreement can actually be concluded online or sits behind a customer login is not stated.
- 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.
- We found no public information on pricing on the pages we read (onetrust.com, onetrust.com/products/privacy-operations, onetrust.com/solutions/gdpr-compliance, onetrust.com/trust, onetrust.com/company/about-us, onetrust.com/privacy-notice and 8 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 61 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
- 19 compliance 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
- 18 integrations 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
- 4 legal 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 support 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.onetrust.com Checked 15 Sep 2026 Details →
- 2 Privacy operations product page www.onetrust.com Checked 15 Sep 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
- 3 GDPR solution page www.onetrust.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 4 Security/trust page www.onetrust.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 5 About page www.onetrust.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 6 Privacy policy www.onetrust.com Checked 15 Sep 2026 Details →
- 7 Data subject rights & incidents — found from sitemap www.onetrust.com Checked 1 Oct 2026 Details →
- 8 Data subject rights & incidents — found from sitemap developer.onetrust.com Checked 1 Oct 2026 Details →
- 9 Privacy regime coverage — found from sitemap developer.onetrust.com Checked 1 Oct 2026 Details →
- 10 Privacy regime coverage — found from sitemap developer.onetrust.com Checked 1 Oct 2026 Details →
- 11 Audit readiness & evidence — found from sitemap developer.onetrust.com Checked 1 Oct 2026 Details →
- 12 Audit readiness & evidence — found from sitemap developer.onetrust.com Checked 1 Oct 2026 Details →
- 13 Integrations & automation — found from sitemap www.onetrust.com Checked 1 Oct 2026 Details →
- 14 Integrations & automation — found from sitemap www.onetrust.com Checked 1 Oct 2026 Details →