Pandectes GDPR Compliance
Provenance unknown 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 Pandectes · pandectes.io
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.
Pandectes GDPR Compliance at a glance
- Vendor
- Pandectes
- Headquarters
- Incorporated in Estonia source, captured 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates Pandectes GDPR Compliance 3/5, the mean of 6 judges. Pandectes GDPR Compliance is a consent management app built for Shopify. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Pandectes GDPR Compliance alternatives, European ones first →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Pandectes GDPR Compliance is a consent management app built for Shopify. Its strongest scoring is banner and choice at 7-8: accept and decline are documented as equal side-by-side choices, geolocation shows each visitor the banner their own law requires across 35 covered privacy laws, available in 130+ languages, and externally audited against WCAG 2.2 Level AA. Scanning and classification is the only criterion with a single score, 7: cookies, HTML storage and pixels are matched to a vendor database, with scheduled rescans and automatic follow-up actions. Sovereignty is the weakest at 2-3: Pandectes OÜ is an Estonian entity and consent records are stated to sit in the app's cloud database, but we found no public information on hosting location, subprocessors, a data processing agreement or security certifications. Scores stayed within one point on every criterion, with no substantive disagreement recorded. Prior blocking, consent records, standards and platforms, and pricing transparency sit at 6-7, held back by Shopify-only reach, no public information tying records to the banner version shown, and unstated multistore discounts, minimum term and VAT treatment.
Speaks for it
- Banner and choice scored highest at 7-8, with accept and decline documented as equal side-by-side choices, per-country geolocation across 35 covered privacy laws and an external audit against WCAG 2.2 Level AA.
- Scanning and classification took a single score of 7, covering cookies, HTML storage and pixels with scheduled rescans and automatic follow-up actions that add, update or remove records.
- The signal stack is deep for an ad-driven store: registered IAB CMP ID 445, Google Consent Mode v2 from the Plus plan, Microsoft consent mode and Global Privacy Control on the free Basic plan.
- Every consent is logged server-side with a unique ID, timestamp, preferences, visitor country and truncated IP, and visitors can verify their own record with a consent key.
- All four tiers are public — Basic free forever, Plus $9, Premium $29 and Enterprise $49 per month with yearly figures listed — and paid plans are stated as not limited by page views.
Held against it
- Sovereignty scored lowest at 2-3, with no public information found on hosting location, subprocessors, a data processing agreement or security certifications.
- The documented platform is Shopify only, and we found no public information on plugins for other content management systems or on iOS and Android SDKs.
- We found no public information tying consent records to the banner version and texts the visitor saw, and the documented export covers the current page of records in CSV.
- The integration runs in advanced mode by default, where tags are activated before the visitor interacts with the banner.
- We found no public information on multistore volume discounts, the pricing of Request Quote custom plans, minimum term or VAT treatment.
Best for
- You run a Shopify store and want an equal-choice banner that adapts per country across 35 covered privacy laws, in 130+ languages, with an external accessibility audit behind it.
- Your store's ad revenue depends on consent signals — Google Consent Mode v2 is available from the Plus plan and IAB TCF from the Enterprise plan, with a registered IAB CMP ID of 445.
- You want to price a single store precisely from public figures, with paid plans stated as not limited by page views.
- You need server-side proof of each consent with configurable retention and a key visitors can present to verify their own record.
Avoid if
- Your storefront runs on a platform other than Shopify — the documented platform is Shopify only, with headless support through a Storefront API.
- Your procurement cannot sign off without a documented hosting region, subprocessor list, data processing agreement or security certifications — sovereignty scored 2-3, the lowest criterion.
- You need blocking to hold all tags until the visitor interacts with the banner — the integration runs in advanced mode by default.
- You need dispute-grade exports of the consent log — the documented export covers the current page of records in CSV.
The scores
| Criterion | Panel median |
|---|---|
| Banner & choice architecture | 4 of 5 |
| Prior blocking & script control | 3.5 of 5 |
| Scanning & cookie classification | 3.5 of 5 |
| Consent records & proof | 3.5 of 5 |
| Frameworks, signals & platforms | 3.5 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 3.5 of 5 |
Prior blocking & script control
Show reasoningHide reasoning
How this is scored
What happens before the visitor decides: automatic blocking of scripts, pixels, cookies and embedded content until consent is given, content blockers with placeholders for videos, maps and social embeds, integration with tag managers (Google Tag Manager, Matomo Tag Manager) and server-side tagging, consent passed to forms and plugins, and a documented way for the site owner to check that nothing loads too early.
0 — No blocking of any kind; the product only shows a banner and leaves every script running.
3 — Blocking by hand: the site owner changes script tags or tag-manager triggers using the consent state; automatic blocking, embeds and testing are basic or not described.
5 — Automatic blocking of known scripts and cookies before consent, placeholders for embedded videos and maps, a Google Tag Manager template or integration, and the blocking method documented in the help centre.
8 — Blocking described in depth: an auto-blocking mode and a manual mode with their limits explained, content blockers for named services that the vendor maintains, consent passed to forms, CAPTCHAs and plugins through a JavaScript API or events, server-side tagging supported, and instructions to test in the browser or a tag-manager preview that nothing loads before consent.
10 — Prior blocking the site owner can verify: an automated check or monitor that reports scripts and cookies set before consent on the live site, alerts when a new tracker bypasses the banner, blocking covering local storage, fingerprinting and pixels as well as cookies, and the method published so an auditor can follow it.
The Data Protection Officer
Three blocking routes are documented in depth — an auto-blocker through the Shopify app embed covering every app embed and app pixel, one-click rules for 17 named services, custom URL or domain rules, inline markup and a Google Tag Manager template — with the basic and advanced modes and their limits explained. Two things hold it back for me: the integration is advanced mode by default, where tags are activated before the visitor interacts with the banner (denied defaults, cookieless pings), and I found no documented way to verify on the live site that nothing loads before consent, nor server-side tagging or consent passed to forms and CAPTCHAs. 5 6 2 12 1
The Agency Developer
The auto-blocker runs through the Shopify app embed so themes stay untouched, manual setup and its limits are documented (app embeds and app pixels by default, an inline blocker for page-level scripts on the top plan), and seventeen named services including YouTube and Vimeo have vendor-maintained one-click rules, plus a Google Tag Manager template with a setup guide. The JavaScript API sits on the top plan, and we found no public information on server-side tagging or a documented browser check that nothing fires before consent. 1 2 5 6
The Publisher Marketing Lead
The auto-blocker holds third-party trackers until consent, working by default through the app embed with its scope limits stated, and a manual setup injects the rules script at the top of the theme; 17 named services have one-click blocking rules including Google Tag Manager through a template, plus custom domain rules and manual markup, and the opt-out behaviour is explained (scripts run from the start and are blocked from the next page load after a decline). I found no public information on content-blocker placeholders for videos and maps, server-side tagging, or a documented way to verify nothing loads before consent. 1 2 5 6
The In-House Lawyer
The auto-blocker holds third-party trackers through the app embed, a manual mode injects a rules script at the top of the theme, and one-click rules exist for seventeen named services alongside custom URL rules and category-based script markup, with a Google Tag Manager template passing the choice to tags. The help pages are candid about what each mode covers and what Shopify's native banner would not block. I found no public information on placeholders for embedded videos or maps, server-side tagging, or documented steps to verify on the live site that nothing loads before consent. 2 5 6
The WordPress Webmaster
The auto-blocker holds third-party trackers through the Shopify app embed with no coding, a manual mode injects a rules script at the top of the theme, and seventeen named services including Google Analytics, YouTube, Google Tag Manager and the Facebook Pixel have vendor-maintained one-click rules, alongside a Google Tag Manager template and a JavaScript API on the top plan. I found no public information on placeholder blockers for embedded videos and maps, server-side tagging, or instructions to verify in the browser that nothing loads before consent. Every blocking mechanism is documented around Shopify's app embeds and pixels, and there is no WordPress plugin for my Maps embed and reCAPTCHA form. 1 2 5 6
The Skeptic
The auto-blocker's default scope through the Shopify app embed is documented with its limits stated rather than glossed, plus 17 named services blocked with one click, custom URL and domain rules, manual markup and an inline blocker at Enterprise. We found no public information on placeholders for embedded videos or maps, server-side tagging, or instructions to verify in a browser that nothing fires before consent — the check I would run first. 1 2 5 6
Scanning & cookie classification
Show reasoningHide reasoning
How this is scored
How the product knows what the site sets: a scanner that crawls the site for cookies, local storage, pixels and third-party requests, scheduled rescans, a maintained database that classifies cookies and services by purpose, provider and lifetime, alerts on new or changed trackers, and a cookie declaration or policy section that updates itself from the scan.
0 — No scanning and no cookie list; every service is entered and described by the site owner from scratch.
3 — A one-off scan or a list of services the site owner fills in, with some predefined templates; scheduled scans, classification and the declaration are basic or not described.
5 — A scanner that finds cookies and third-party services on the site, regular rescans, automatic classification into categories from a vendor database, and a cookie declaration generated from the result and kept on the site.
8 — Scanning described in depth: scheduled scans with a stated depth or page count, scanning behind logins or in different regions, local storage and pixels as well as cookies, a large maintained database of services with purposes, providers and lifetimes, email alerts on new or changed trackers, and the declaration updated automatically in several languages.
10 — The cookie list stays true without manual work: continuous monitoring of the live site with a change history, unknown trackers flagged for review rather than silently classified, the classification sources and update process published, and scan reports exportable for an audit.
The Data Protection Officer
The scanner covers cookies, local storage, pixels and HTML storage, runs an automatic first scan with weekly or monthly schedules (Enterprise plan) and can scan behind a store password (Enterprise plan), classifying everything against the vendor's multilingual cookie database and feeding an automated cookie policy. Follow-up actions after each scan update, add, classify and prune records automatically, with manually created records never touched and AI never applied automatically, so the list largely maintains itself. I found no stated scan depth or page count and no alerts on new or changed trackers. 8 6 7 2 1
The Agency Developer
An automatic scan runs on install, weekly or monthly schedules and scan-behind-password exist on the top plan, and the scanner covers cookies, HTML storage and pixels, classifies them from a maintained database, rescans with a difference check and then automatically adds, updates or removes records — which is close to the Friday-tracker workflow I need. We found no public information on email alerts for new trackers, on stated scan depth, or on exportable scan reports for an audit. 1 2 6 7 8
The Publisher Marketing Lead
The initial scan runs on install, cookies, HTML storage and pixels are matched to a vendor database and categorised automatically, and weekly or monthly schedules come with a five-scan daily limit, scanning behind a password, and documented follow-up rules after each scan: group, update, add, classify from the catalogue, and remove entries unseen for 14 days, with manually created records never changed automatically. The cookie policy can update itself from the scan and curated cookie texts exist in multiple languages. I found no public information on email alerts when new or changed trackers appear. 2 7 8
The In-House Lawyer
Cookies, local storage and pixels are scanned on install, on demand, or on weekly and monthly schedules (up to five scans a day), with behind-password scans and scan-location choice on the Enterprise plan, and every find is matched to the vendor's database and categorised. Rescans show differences and trigger ordered follow-up actions, records the owner edited are never changed automatically, and unrecognized records drop out after fourteen days unseen; the cookie policy regenerates itself and curated descriptions are multilingual. I found no public information on email alerts when new or changed trackers appear, or on a stated scan depth. 1 2 7 8
The WordPress Webmaster
An install-time scan matches cookies, local storage and pixels against a vendor database and categorises them, rescans can be scheduled weekly or monthly (on the top plan, up to five a day), diff rescans feed automatic follow-up actions that add, update or remove records while hand-edited ones are protected, and a cookie policy keeps itself in step with what the store loads. I found no public information on scan depth or page count, cookie lifetimes in the database, or email alerts when a new tracker appears, which keeps this below the top level. 2 6 7 8
The Skeptic
The scanner covers cookies, HTML storage and pixels, classifies them against a multilingual vendor database, with scheduled scans and scan-behind-password at Enterprise, rescan diffs, and follow-up rules that group, update, add and remove records after each scan with manual records protected. Scan depth or page count, email alerts on new trackers, and exportable scan reports are areas where we found no public information. 1 2 6 7 8
Consent records & proof
Show reasoningHide reasoning
How this is scored
What the site owner can show afterwards: a record per consent with time, pseudonymous ID, the choices made and the banner version shown, how long records are kept and where, export of the consent log, re-consent when the services or texts change, consent expiry, records available to the visitor (a consent ID), and proof that withdrawal took effect.
0 — No record of consent is kept anywhere; the choice lives only in the visitor's browser.
3 — Consent stored in a cookie with a simple log or counter; per-visitor records, retention, export and banner versions are basic or not described.
5 — A consent log with a record per consent (time, pseudonymous ID, choices), a retention period stated, export of the log as a file, and the banner asking again when the configuration changes.
8 — Proof described in depth: each record tied to the banner version and texts shown, a consent ID the visitor can look up, retention and storage location stated, consent expiry configurable, withdrawal recorded as its own event, cross-domain or cross-device consent recorded consistently, and the log searchable and exportable through an API.
10 — Records built for a dispute: a tamper-evident or audit-proof log, every record reproducible with the exact banner and texts the visitor saw, documentation on how to answer a supervisory authority's request, and the full log exportable in an open format when the customer leaves.
The Data Protection Officer
Every consent is logged server-side as well as in the browser with a unique ID, timestamp, status, exact preferences, visitor country and truncated IP, account-configurable retention with automatic anonymisation or deletion, encryption, restricted access, dashboard CSV export, and a unique consent key the visitor can present to verify. The gap for an authority request: the record shows no banner version or texts the visitor saw, and I found no API access to the log, with the documented CSV export covering the current page of records at a time. Cross-domain consent covers the main domain and subdomains, and withdrawal runs through a two-step form with confirmation emails and a requests dashboard. 9 10 1 2 3
The Agency Developer
Every consent is logged server-side with a unique ID, timestamp, choices, visitor country and truncated IP, retention is configurable per account with automatic anonymisation or deletion, CSV export comes from the dashboard, and a visitor-facing consent key plus a data-request page let people verify their own record. We found no public information tying each record to the exact banner version shown, or on exporting the log through an API. 1 3 9 10
The Publisher Marketing Lead
Every consent is logged server-side as well as in the browser, with a unique ID, timestamp, status, exact preferences, visitor country and truncated IP, a configurable retention policy with automatic anonymisation or deletion, dashboard CSV export, and a unique consent key the visitor can present to verify — a downloadable record pitched as ready if a regulator asks. Consent can be set to expire and be asked again after a set number of days. I found no public information on records being tied to the banner version shown, or on withdrawal being logged as its own event. 1 3 9 10
The In-House Lawyer
Each consent is stored in the browser and server-side with a unique ID, date and time, status, exact category preferences, visitor country and truncated IP, held under a per-account retention policy with automatic anonymisation or deletion afterwards, exportable as CSV, and the visitor can verify their own entry by consent key; withdrawal runs through a two-step form with confirmation emails and a requests dashboard. Access is restricted to authorised persons and data is encrypted in transit and at rest. I found no public information tying each record to the exact banner version and texts the visitor saw — what I would need to reconstruct the choice in a German proceeding — nor any tamper-evident log or documentation for answering a supervisory authority. 1 2 9 10
The WordPress Webmaster
Every consent is recorded server-side as well as in a first-party cookie, with a unique ID, timestamp, status, exact preferences, visitor country and truncated IP; retention is configurable per account with automatic anonymisation or deletion afterwards, access is restricted to authorised staff, records are pseudonymised and exportable as CSV, and a visitor can verify their own entry with a unique consent key, with a withdrawal form and its own request dashboard documented. I found no public information tying each record to the exact banner version and texts shown, and export runs through the dashboard for the current page rather than an API, so the proof is strong but not built for a dispute. 1 2 9 10
The Skeptic
Each consent is recorded on the server as well as in the browser, with a unique ID, timestamp, status, preferences, country and truncated IP, under a configurable retention policy with automatic anonymisation or deletion, a CSV export, and a consent key the visitor can present to verify. The documented export covers the current page in CSV; we found no public information tying records to the banner version and texts shown, nor an API for the log — the parts that decide a dispute. 1 3 9 10
Frameworks, signals & platforms
Show reasoningHide reasoning
How this is scored
Where the consent goes and where the product runs: the IAB Transparency and Consent Framework (TCF, current version) with a registered CMP ID, Google Consent Mode v2 and Google's CMP certification, Microsoft UET consent mode and other ad-platform signals, the Global Privacy Platform and Global Privacy Control for US laws, plugins and apps for WordPress, Shopify, TYPO3 and other systems, iOS and Android SDKs, connected TV, multi-domain and agency accounts, and an API.
0 — No consent signal is passed on; other tools cannot read the visitor's choice.
3 — Consent readable through a cookie or a JavaScript variable, perhaps one CMS plugin; TCF, Consent Mode, app SDKs and multi-site management are basic or not described.
5 — Google Consent Mode v2 supported with the vendor named as a Google-certified CMP, IAB TCF supported, plugins or integrations for several named CMS and shop systems, a JavaScript API, and several domains manageable from one account.
8 — Signals and platforms described in depth: a registered IAB Europe CMP ID and the current TCF version, Google Consent Mode v2 in basic and advanced mode, Microsoft UET consent mode and other named ad signals, GPP and GPC for US states, iOS and Android SDKs documented, agency or partner accounts managing many client sites, and a REST API for configuration.
10 — One consent across every channel: web, apps and connected TV under one configuration, consent shared across domains and logged-in devices, every signal (TCF, Consent Mode, GPP, ad platforms) documented with its mapping to the banner choices, and configuration exportable or managed as code.
The Data Protection Officer
The signals are strong: a registered IAB Europe CMP (ID 445) on TCF v2.3 and v2.4 including Google's Additional Consent Mode, Google Consent Mode v2 in basic and advanced mode as a Google-certified CMP, Microsoft Consent Mode and Clarity, the Amazon consent signal, Rakuten, Klaviyo and Global Privacy Control even on the free plan, plus a JavaScript API, headless storefront support and multistore management. But the product runs on Shopify only — no WordPress or other CMS plugins, no iOS or Android SDKs — and I found no Global Privacy Platform signal or REST configuration API, with the IAB TCF banner itself behind the Enterprise plan. 11 12 1 2
The Agency Developer
The signal stack is genuinely deep: a registered IAB CMP ID, TCF (the captured pages give different figures for the version), Google Consent Mode v2 in basic and advanced mode with the defaults explained, Microsoft Consent Mode, Amazon and Rakuten signals and Global Privacy Control on the free plan, plus a JavaScript API, Shopify's Customer Privacy API and a storefront API for headless builds. Platform reach is Shopify only — we found no public information on a WordPress or TYPO3 plugin, on app SDKs or on a REST API for configuration — so the multistore account with volume discounts covers Shopify stores alone, which matters when I run sites on three systems. 1 2 3 11 12
The Publisher Marketing Lead
The IAB registration with CMP ID 445 and Google Consent Mode v2 integrated by default in advanced mode, with cookieless pings and automatic ad user data and ad personalization signals, is exactly the signal stack our ad revenue runs on; the captured pages give different figures for the current TCF version, 2.3 and 2.4. Microsoft certification and consent mode, Global Privacy Control on the free plan, Amazon and Rakuten signals and a Google Tag Manager template round out the ad side. It runs on Shopify only, with multistore support, a headless StoreFront API and a JavaScript API, and I found no public information on iOS or Android SDKs, GPP, or a REST configuration API, so consent shared with an app is not evidenced. 1 2 7 11 12
The In-House Lawyer
The vendor is registered with IAB Europe as CMP 445 (the captured pages give different figures for the TCF version, v2.3 and v2.4), is a Google-certified CMP with Consent Mode v2 in basic and advanced mode, is a Microsoft-certified CMP, and supports Google's Additional Consent Mode, the Amazon and Rakuten signals and Global Privacy Control on the free plan. A JavaScript API and a Storefront API for headless storefronts are Enterprise-plan features and a Google Tag Manager template passes choices to tags. I found no public information on iOS or Android SDKs, on GPP, or on a REST API for configuration, and the product runs on Shopify only. 1 2 11 12
The WordPress Webmaster
The signal side is documented in depth: a registered IAB CMP ID with a TCF banner on the top plan (the captured pages give different figures for the TCF version), Google Consent Mode v2 in basic and advanced mode as a Google- and Microsoft-certified CMP, Additional Consent Mode, Global Privacy Control on the free plan, and Google Tag Manager via a vendor template. But the product runs on Shopify only — themes, headless storefronts through a storefront API, several stores from one account — and I found no public information on iOS or Android SDKs, GPP for US states, agency accounts or a REST API for configuration. As the WordPress webmaster, there is nothing here for me to install. 1 2 11 12
The Skeptic
Signals run deep: IAB TCF under registered CMP ID 445 at v2.4 (Enterprise) with Google Additional Consent Mode, Google Consent Mode v2 in basic and advanced mode with advanced as the default, Microsoft consent mode plus Facebook, Amazon, Rakuten, Klaviyo and Clarity signals, and Global Privacy Control on the free plan. The documented platform is Shopify only; we found no public information on plugins for other CMS systems, iOS or Android SDKs, connected TV, GPP, or a REST configuration API. 1 2 7 11 12
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where the banner script is served from, where consent logs and scan results are stored, and who the subprocessors are (hosting, CDN, geolocation, scanner infrastructure, app SDK telemetry, email and support). Independently sourced by the sovereignty pipeline; a CMP runs on every page of the customer's site and sees every visitor, so the whole chain counts, not only the database. For a plugin that runs on the customer's own server, the vendor's licence, update and scanner services are the chain.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (CDN for the banner script, geolocation, scanner, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, banner script and consent logs served and stored in the EU, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, CDN and every subprocessor, or a self-hosted option that keeps the banner and the logs on the customer's own server; data export and deletion documented, and certifications published with their scope rather than implied.
The Data Protection Officer
The contracting entity is Pandectes OÜ in Estonia, which is a start. Beyond that the chain goes dark: consent records are stored in the app's cloud database with no country named, and I found no public information on hosting or CDN location, on subprocessors and their locations, or on a published data processing agreement. For a banner that runs on every page and sees every visitor, I could not put an unnamed chain in front of my boards. 7 10 9
The Agency Developer
The contracting entity is Pandectes OÜ in Estonia with an EU-registered trademark, and consent data is described as encrypted in transit and at rest and stored in an app database in the cloud. We found no public information on where the hosting or that cloud database sit, on subprocessors anywhere in the chain, or on a data processing agreement, so the chain beyond the Estonian entity is unproven. 7 9 10
The Publisher Marketing Lead
Pandectes OÜ is an Estonian contracting entity with an EU registered trademark, and consent data is stated to be encrypted in transit and at rest and stored in a cloud app database. Beyond that I found no public information on where hosting sits, on any subprocessor, on a data processing agreement, or on security certifications — for a script that runs on every page and sees every visitor, too much of the chain is unknown to me. 7 9 10
The In-House Lawyer
The contracting entity is Pandectes OÜ in Estonia with an EU-registered trademark, so the contract sits under EU law, and consent data is stated to be encrypted in transit and at rest with access limited to authorised persons. Beyond that the chain is dark: consent records are said to sit in an app database in the cloud with no region named, and I found no public information on hosting or banner-script infrastructure, on subprocessors, on a published data processing agreement, or on ISO 27001 or SOC 2 certifications. For a script that sees every visitor on every page, I would not sign until those points are documented. 1 7 9 10
The WordPress Webmaster
The contracting entity is Pandectes OÜ at an address in Estonia with an EU-registered trademark, consent data is encrypted in transit and at rest, and records sit in the app database in the cloud. The hosting country for the banner script and the consent logs is not stated on the pages I read, no subprocessors are listed, and I found no public information on a data processing agreement or security certifications. For code that loads on every pageview of a customer's site, that chain stays unproven. 7 9 10
The Skeptic
Pandectes OÜ is an Estonian entity with an Estonian address, and consent records are stated to sit in the app's database in the cloud. We found no public information on where the banner script or the logs are actually hosted, on any subprocessor, on a data processing agreement, or on security certifications — 'secure environments that meet international standards' is as specific as the captured pages get. 7 9 10
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per domain or site licence, the page-view, session or consent limits of each tier and what happens above them, the free tier's limits, which features (TCF, app SDKs, A/B testing, multi-domain, white label) cost extra, agency or reseller terms, minimum term, and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with domains, traffic or features is unclear.
5 — Tiers are public with their price per domain or licence and their main inclusions, but at least one commonly needed piece (traffic overage, extra domains, TCF, app SDKs, agency use) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (per domain, per page view or session band, per site licence), overage and extra domains priced, add-ons listed with prices, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of domains, traffic and apps, with every add-on, setup, support, overage and agency fee and the cancellation and data-return terms published.
The Data Protection Officer
All four tiers are public — Basic free forever, Plus $9 per month, Premium $29 per month, Enterprise $49 per month, with yearly prices listed as $108/$90, $348/$290 and $588/$490 — paid plans are stated to carry no page-view limits, a 7-day free trial applies to paid plans, and the documentation consistently maps features to plans (auto-blocker from Premium, scheduled scans and IAB TCF from Enterprise). Still not computable from public pages: multistore volume discounts and custom plans for large stores are quote-only, and VAT treatment and minimum term are not stated anywhere I read. 7 1 2 3
The Agency Developer
All four tiers carry public figures — Basic free forever, Plus at $9 a month, Premium at $29 a month, Enterprise at $49 a month, with yearly prices published too — paid plans are stated as not limited by page views, there is a seven-day trial, and the plan gating of each feature is listed clearly enough to price a single store's year. What I cannot compute is the agency picture: multistore comes with volume discounts and custom plans on request, and minimum term and VAT treatment are not stated. 1 2 3 7
The Publisher Marketing Lead
All four tiers are public — Basic free forever, Plus $9, Premium $29 and Enterprise $49 per month, with yearly figures listed and a 7-day free trial — paid plans are stated to carry no page view limits, and nearly every feature's plan is named so I can price our stack precisely. The multistore volume discounts are mentioned without amounts, custom plans are "Request Quote", and I found no public information on minimum term or VAT treatment. 1 2 3 7
The In-House Lawyer
All four tiers are public with monthly and yearly figures — Basic "Free Forever", Plus "$9 Per month" with "$108 $90 Per year", Premium "$29 Per month" with "$348 $290 Per year", Enterprise "$49.00" monthly and "$588 $490 Per year" — paid plans are stated to carry no page-view limits, and the feature gates per plan are spelled out on the public pages. What I cannot compute for a retailer with several stores: the volume discounts for multiple stores are unnamed, large stores are directed to "Request Quote", and minimum term and VAT treatment are not stated. 1 2 3 7
The WordPress Webmaster
Every tier is public: Basic free forever, Plus at $9 per month or $108/$90 per year (list and discounted), Premium at $29 per month or $348/$290 per year, Enterprise at $49 per month or $588/$490 per year, paid plans are not limited by page views, a 7-day free trial applies to paid plans, and which feature sits behind which plan is documented across the captured pages. Custom plans for large stores go through Request Quote, multistore volume discounts are unpriced, and minimum term and VAT treatment are not stated. And the whole list prices a Shopify store, so there is no WordPress licence to buy at any of these figures. 1 2 3 7
The Skeptic
All four tiers are public with monthly and yearly figures as shown — Basic free forever, Plus $9 Per month ($108 $90 Per year), Premium $29 ($348 $290), Enterprise $49 ($588 $490) — paid plans stated as not limited by page views, with a 7-day free trial and the per-plan feature gates (Consent Mode from Plus, TCF and scheduled scans from Enterprise) laid out publicly. What a buyer cannot compute: the multistore 'volume discounts', the 'Request Quote' custom plans, VAT treatment and the minimum term. 1 2 3 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 | Incorporated in EE | 2/2 pts | 1 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 | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Pandectes GDPR Compliance
Is Pandectes GDPR Compliance European?
Not determined: the vendor’s pages as captured do not say where Pandectes GDPR Compliance is based. Its vendor, Pandectes, is incorporated in Estonia, per the vendor’s page captured 17 Nov 2026.
Where does Pandectes GDPR Compliance store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Pandectes GDPR Compliance have a free plan?
Yes. Pandectes GDPR Compliance has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to Pandectes GDPR Compliance?
As of 19 Nov 2026, the panel rates Uniconsent (3.5/5), Usercentrics CMP (3.5/5) and Didomi (3.5/5) highest among the other 25 Consent Management (CMP) 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 Usercentrics CMP (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: Pandectes GDPR Compliance alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- 13 pricing 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
- 6 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 compliance 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 pandectes.io Checked 17 Nov 2026 Details →
- 2 Privacy policy — found from the homepage pandectes.io Checked 17 Nov 2026 Details →
- 3 Banner & choice architecture — found from sitemap pandectes.io Checked 17 Nov 2026 Details →
- 4 Banner & choice architecture — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →
- 5 Prior blocking & script control — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →
- 6 Prior blocking & script control — found from sitemap pandectes.io Checked 17 Nov 2026 Details →
- 7 Scanning & cookie classification — found from sitemap pandectes.io Checked 17 Nov 2026 Details →
- 8 Scanning & cookie classification — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →
- 9 Consent records & proof — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →
- 10 Consent records & proof — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →
- 11 Frameworks, signals & platforms — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →
- 12 Frameworks, signals & platforms — found from sitemap help.pandectes.io Checked 17 Nov 2026 Details →