The OneTrust alternative with public prices and a self-serve checkout

You may not need a privacy platform. You need a banner.

OneTrust shines when a privacy team runs a programme across many jurisdictions: data mapping, assessments, subject requests, vendor risk and consent in one place. For a marketing site, a SaaS landing page or an online shop, most of that sits unused.

PrivacyPill does one job: show a clear, fair consent banner, block trackers until people agree, tell Google tags what was decided and keep a record. That focus is why the script is tiny and why setup takes minutes.

Performance is part of the user experience

A consent script runs before your analytics, before your ads and often before your content becomes interactive. PrivacyPill's runtime is around 5 kB gzipped, renders in an isolated Shadow DOM and ships its configuration in the same request.

When OneTrust is the right call

Stay with an enterprise platform if any of these apply:

• You sell programmatic ads and need IAB TCF with a Google-certified CMP.
• You must cover many non-EU privacy laws with region-, country- or state-specific banner logic.
• Your organisation wants subject-request handling, assessments or vendor risk in the same platform.
• You need banners in many more languages than the six PrivacyPill ships.

Moving from OneTrust

OneTrust uses five default categories, PrivacyPill uses four. Map them like this: Strictly necessary → necessary, Performance → analytics, Functional → functional, Targeting and Social media → marketing. Then replace the OneTrust script with the one-line embed.

OneTrust blocks scripts with type="text/plain" and a class such as optanon-category-C0004 (the default ID for Targeting — check the IDs in your own OneTrust setup). Change those to data-pp-category="marketing" (or analytics / functional) and keep type="text/plain". Afterwards, check in Google Tag Assistant that consent defaults and updates arrive as expected.