OneTrust

OneTrust is an enterprise consent management and privacy governance platform, sold as one quote-priced suite spanning cookie banners, DSARs and AI risk.

OneTrust is a consent management and privacy governance platform that compliance, legal and marketing teams use to collect consent, prove it later, and control how personal data and AI systems are used. It is built and sold by OneTrust, LLC, an independent company founded in 2016 and based in Atlanta, Georgia. The product and the company share a name, a website and a single login, so a privacy programme, a cookie banner and an AI risk review all live in the same place. Work that otherwise sits in spreadsheets, ticket queues and hand-edited tag rules becomes one record. Consent and Preferences is the part a website visitor meets. Cookie Consent scans a site on a schedule, sorts what it finds into purpose categories against OneTrust's pre-categorised cookie database, and holds trackers through no-code blocking, tag manager integrations or script re-writing until someone opts in. Geolocation rules change the banner, the default consent state and the legal wording by region, country or state. Mobile and OTT/CTV SDKs carry the same categories into iOS, Android, Roku, Apple TV and Amazon Fire apps, and Universal Consent and Preference Management gives people a portal to revisit their choices. Privacy Automation, Data Use Governance, AI Governance, Tech Risk and Compliance and Third-Party Management sit alongside it. The platform suits organisations large enough to have a named privacy owner: enterprises with several brands and domains, publishers and advertisers that must pass consent into the advertising ecosystem through the IAB Transparency and Consent Framework, and regulated firms already running vendor risk and control frameworks. Marketing teams come to it for a consented first-party dataset as much as for compliance. It is bought as a package through the OneTrust sales team, and the pricing page asks for contact details and returns a personalised quote based on team size and business goals. Day to day the work is a banner on a site, a preference link in an email footer and a consent record someone can produce when an auditor asks. Teams publish a cookie policy page from the latest scan, send consent signals to Google's analytics and advertising tags through Google Consent Mode, pass TCF strings to ad-tech vendors including through Prebid and header bidding, carry a visitor's choices across domains and devices, and export consent receipts through the API. A/B testing of banner templates turns the opt-in rate into something a team can tune rather than guess at. It sits beside tag managers, analytics and advertising stacks, cloud data warehouses, and the assessment work that runs before an AI system reaches production.