Pageguard vs iubenda
Lawyer-crafted modular policies with a service-clause library
Free scan · No account required
iubenda is the right pick if you need teams that want a structured library of pre-vetted legal clauses and prefer selecting from a catalogue of 2,400+ service integrations rather than writing policies from scratch. Pageguard is the right pick if you want documents grounded in what your site actually runs — not what you remember it runs. The free scan takes 60 seconds and needs no account.
Our honest take
The core tension here is epistemological: how do you know what's actually running on your site? iubenda bets you know your own stack and just need a professional way to document it. Pageguard bets you don't, and it's right more often than you'd think. iubenda's clause library is genuinely impressive. Two thousand four hundred pre-vetted service integrations, drafted by lawyers, assembled like a modular policy kit. If you're a compliance-minded team with a stable, well-documented tech stack and someone whose job includes keeping that list current, iubenda is a serious tool. The Essentials plan at $5.99/mo is a reasonable starting point, though you'll quickly discover that 20 clauses covers almost nothing real-world. We built Pageguard for a different kind of team: the solo founder who installed Hotjar six months ago and forgot, the two-person SaaS whose designer dropped in a Intercom widget last sprint, the developer who needs accurate docs for an iOS app submission by Friday. Pageguard scans what's actually there, generates documents grounded in that reality, and covers the app store privacy forms that iubenda doesn't touch at all. These are genuinely different philosophies, not just feature gaps.
The real differences
Detection vs. declaration
iubenda's model requires you to declare what you use by selecting from their 2,400+ service catalogue. That works when your stack is stable and your team is disciplined about updating the policy every time a new tool gets added. In practice, third-party scripts accumulate quietly. Pageguard scans your live site against 437+ technology signatures and surfaces what's actually loading, including the A/B testing SDK that started firing last week or the analytics pixel your ad agency added without telling you. The gap report assigns severity ratings (critical, high, medium, low) so you know what to fix first, not just that something is missing.
Clause depth at each price tier
This is where iubenda's pricing structure creates real friction. The Essentials plan at $5.99/mo per site caps you at 20 service clauses. A solo founder running a typical SaaS stack with Stripe, PostHog, Intercom, Google Analytics, and a CDN will blow past that limit before they've documented half their integrations. Moving to Advanced at $24.99/mo unlocks more clauses but still scales per site, so a founder running three small products pays $74.97/mo before they've generated a single terms of service. Pageguard charges per document generated with no subscription and no pageview caps.
App store privacy forms
iubenda is a web compliance tool. It generates privacy policies, cookie policies, and terms of service for websites, and its Ultimate plan at $99.99/mo per site adds a mobile consent SDK. But it does not generate Apple App Store privacy nutrition labels or Google Play Data Safety forms. For a 5-person SaaS shipping their first iOS app, that's a hard stop: iubenda gets you the website docs, then you're on your own for the App Store submission. Pageguard covers both.
Consent management
This is where Pageguard genuinely trails iubenda. iubenda includes a consent banner and CMP (consent management platform) across its paid plans. Pageguard does not currently offer a consent banner. If you need a compliant cookie consent UI as part of the same tool and workflow, iubenda has that and Pageguard does not. That's worth naming plainly.
Feature comparison
Pricing
Essentials $5.99/mo · Advanced $24.99/mo · Ultimate $99.99/mo (per site)
Free scan (no account) · Pay per document generated. No subscription required, no pageview caps.
Migration considerations
Switching from iubenda to Pageguard is not a complex data migration. iubenda doesn't hold your policy data hostage, and Pageguard doesn't need it. The process looks like this: run a free Pageguard scan on your live site (no account required), review the gap report to see what your actual stack contains, then pay per document to generate the privacy policy, cookie policy, or terms of service you need. The scan takes minutes.
What you gain: documents grounded in your detected stack rather than your remembered stack, app store privacy form generation if you have a mobile product, and no ongoing subscription cost tied to traffic volume.
What you give up is real and worth being honest about. iubenda's clause library is genuinely lawyer-vetted at a granular service level, which matters if you want a human-legible audit trail showing exactly which services are covered and why. You also lose the consent banner and CMP that iubenda includes. If your current iubenda setup includes the cookie consent widget embedded on your site, you'll need a separate CMP solution after switching. Factor that into the decision. For teams where the consent banner is the core value they're getting from iubenda, switching today may not make sense.
When to pick which
Teams that want a structured library of pre-vetted legal clauses and prefer selecting from a catalogue of 2,400+ service integrations rather than writing policies from scratch.
Things to know first
- —Essentials plan limits you to only 20 of 2,400+ available service clauses — very restrictive for any real-world stack
- —Pricing scales steeply per site; managing multiple domains gets expensive quickly
- —Still form-fill at its core — you pick services from a list rather than having your stack detected automatically
- —Branding removal requires the Ultimate plan at $99.99/mo per site
iubenda's model is clever — a library of pre-drafted clauses you assemble like LEGO. But it still requires you to know what you're using and pick the right services from their catalogue. Pageguard detects your actual stack automatically, so you don't miss the Intercom widget your designer added or the A/B testing SDK that started loading last week. And Pageguard covers app store privacy forms that iubenda doesn't touch.
Scenarios: who fits where
A solo founder running a Shopify store with PostHog, Stripe, and a recently added affiliate tracking pixel they half-remember installing: Pick Pageguard. The free scan will surface everything loading on the site, including that affiliate script. Generating a privacy policy and cookie policy per-document costs less than one month of iubenda Advanced, and there's no subscription renewing while the store is quiet.
A 5-person SaaS team shipping their first iOS app and a companion web dashboard: Pick Pageguard. iubenda will get you the web docs but cannot generate the Apple App Store privacy nutrition label required at submission. Pageguard covers both the web policy and the app store form in one workflow.
An agency managing compliance for 15 client websites across different industries: Look closely at iubenda's per-site pricing before committing. At $24.99/mo per site on the Advanced plan, 15 sites runs $374.85/mo. iubenda's clause library is well-suited to varied client stacks, but the cost stacks fast. Pageguard's per-document model may be cheaper depending on how often docs need to be regenerated.
A compliance-focused B2B SaaS with a dedicated legal ops person, a stable known stack, and a need for a consent banner: iubenda is a reasonable fit here. The clause library gives legal ops a structured, auditable record of exactly which services are covered. The built-in CMP handles consent. Pageguard doesn't offer the consent banner, and a team with a dedicated legal person who maintains the stack list won't get as much value from automated detection.
Common questions
How does iubenda's clause library differ from Pageguard's approach?
iubenda gives you a catalogue of pre-drafted legal clauses for 2,400+ services — you pick the ones that apply to you. It's accurate if you choose correctly. Pageguard detects your actual stack by scanning your live site, so you don't need to know in advance what you're using.
Why does iubenda's pricing scale by pageviews?
iubenda charges per site and imposes pageview caps at each tier, with overage fees. This means a growing site can see costs jump unexpectedly. Pageguard charges per document generated, not by traffic volume.
Does iubenda support App Store privacy forms?
iubenda focuses on web compliance documents and consent management. It does not generate Apple App Store privacy nutrition labels or Google Play Data Safety forms. Pageguard handles both.
Can I use iubenda for a mobile app?
Browsing alternatives instead of comparing directly?
Best iubenda alternatives →Don't ship without Bandit.
Run the scan. See what your stack actually contains.
Free scan · No account required