ConsentStack
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 ConsentStack · consentstack.com
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.
ConsentStack at a glance
- Vendor
- ConsentStack
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- In the EU source, captured 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates ConsentStack 1/5, the mean of 6 judges. ConsentStack is a privacy SaaS suite from Digital Data Solutions B.V., a Dutch company in Amsterdam (KvK 75762277), listing eight modules — among them a Cookie Consent manager, a Consent / PII API and third party consent sync — for GDPR, LGPD and CCPA, in an open beta. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ConsentStack is a privacy SaaS suite from Digital Data Solutions B.V., a Dutch company in Amsterdam (KvK 75762277), listing eight modules — among them a Cookie Consent manager, a Consent / PII API and third party consent sync — for GDPR, LGPD and CCPA, in an open beta. Sovereignty scored best, clustering at 4-5: judges credited a Dutch contracting entity, a named data protection officer, and subprocessors disclosed by name — OVH, Google, Sendgrid, Mailgun, Mailchimp — though that list covers the vendor's own website. Its weakest rows are prior blocking and scanning and classification, both scored 0: no public information on whether scripts are blocked before consent or how cookies are classified. Judges split on sovereignty, 5 versus 4 — the judges at 4 weighed the policy's "effective protection level" allowance for processing outside the EU and the absence of a published customer data processing agreement — and 3 versus 2 on standards and platforms, over what the named API proves without IAB TCF or Google Consent Mode. One judge scored 0 on every criterion, finding the pages too thin to credit.
Speaks for it
- Contracting entity is Digital Data Solutions B.V. of Amsterdam, KvK 75762277, with a data protection officer appointed.
- Sovereignty scores cluster at 4-5, the highest row this product received.
- Subprocessors are disclosed by name — OVH, Google, Sendgrid, Mailgun, Mailchimp — for hosting, web analytics and email.
- Eight modules stretch beyond consent into a DSAR inbox, DPIA management, policy and document management and a custom privacy portal.
- Documents can be distributed to websites, applications and mobile apps.
Held against it
- Prior blocking scored 0, with no public information on whether scripts, pixels or embeds are blocked before consent.
- Scanning and classification scored 0, with no public information on a site scanner, cookie database or generated declaration.
- Consent records scored 0-2, with no public detail on record contents, log retention, export or banner versions.
- Standards and platforms topped out at 3, with no public information on IAB TCF, Google Consent Mode or CMS plugins.
- The banner exists as a module name, with no public information on where reject sits, withdrawal, customisation or languages.
Best for
- You are a privacy-first organisation open to a pre-launch suite and can get banner, blocking and record detail from the vendor during the beta.
- You want one platform combining consent with a DSAR inbox, DPIA management and policy and document management.
- Your procurement requires a Dutch contracting entity with a KvK number and named subprocessors.
- You publish policies across a website, application and mobile apps and want one place to keep them current.
Avoid if
- You need a launched product with published prices today — ask the vendor: the public pages we read do not show it
- You require unconditional EU processing — the policy allows processing outside the European Union where a country has an "effective protection level".
- You must document the subprocessor chain for your own customers' data — the published list covers the vendor's own website hosting, web analytics and email.
- You need to see the banner's behaviour — where reject sits, how visitors withdraw — before committing; the pages name the Cookie Consent manager module and stop there.
The scores
Prior blocking & script control
n/r
n/r
n/r
n/r
n/r
n/r
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 not rated — no public information
We found no public information on automatic blocking of scripts, pixels or cookies before consent, on content blockers or tag-manager integration, or on any way to verify that nothing loads early; the captured homepage and privacy policy describe the module list and the vendor's own data handling only. 1 2
The Agency Developer not rated — no public information
I found no public information on automatic script or cookie blocking, placeholders for YouTube, Maps or social embeds, or tag-manager integration. The captured homepage and privacy policy name a cookie consent manager and a Consent API but say nothing about what loads before consent or how I would verify it. 1 2
The Publisher Marketing Lead not rated — no public information
We found no public information on prior blocking or script control. The two pages we captured name the product's modules but say nothing about blocking scripts, pixels or embedded content before consent, tag-manager integration, or how a site owner could verify that nothing fires before consent. 1 2
The In-House Lawyer not rated — no public information
We found no public information on blocking of scripts, pixels, cookies or embedded content before consent, tag-manager or server-side tagging integration, or any way for the site owner to test that nothing loads too early. The pages we read were the vendor homepage and the privacy policy, neither of which describes this. 1 2
The WordPress Webmaster not rated — no public information
We found no public information on prior blocking or script control. Nothing on the two captured pages we read — the homepage and the privacy policy — covers automatic blocking, placeholders for videos and maps, tag-manager integration, or a way to check that nothing loads before consent. 1 2
The Skeptic not rated — no public information
We found no public information on automatic blocking of scripts, pixels and cookies before consent, placeholders for embeds, tag-manager integration, or any documented way to test that nothing loads early. I read both the homepage and the privacy policy; neither addresses blocking in any form. 1 2
Scanning & cookie classification
n/r
n/r
n/r
n/r
n/r
n/r
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 not rated — no public information
We found no public information on a cookie scanner, scheduled rescans, a maintained classification database or a self-updating cookie declaration; the captured pages name a cookie consent manager module without describing how the site's cookie list is produced. 1 2
The Agency Developer not rated — no public information
I found no public information on a site scanner, a cookie classification database, scheduled rescans, or a generated cookie declaration. The module list covers DSAR, DPIA and document management, and neither captured page describes how services on a client site would be discovered or classified. 1 2
The Publisher Marketing Lead not rated — no public information
We found no public information on scanning or cookie classification: nothing on the captured pages describes a site scanner, a maintained database of services and purposes, rescans, alerts on new trackers, or a cookie declaration generated from a scan. 1 2
The In-House Lawyer not rated — no public information
We found no public information on a website scanner, a maintained database classifying cookies and services, scheduled rescans, alerts on new trackers, or a cookie declaration generated from the scan. The module list on the homepage and the privacy policy are silent on all of it. 1 2
The WordPress Webmaster not rated — no public information
We found no public information on scanning or cookie classification. Neither the homepage nor the privacy policy mentions a scanner, a maintained cookie or service database, or a cookie declaration, so how this suite would find our Analytics, Maps and reCAPTCHA scripts is unknown to us. 1 2
The Skeptic not rated — no public information
We found no public information on a site scanner, a maintained cookie and service database, scheduled rescans, alerts on new trackers, or a generated cookie declaration. Neither the homepage nor the privacy policy addresses scanning or classification. 1 2
Consent records & proof
n/r
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
A consent and personal-data API and third-party consent sync appear in the module list, and the vendor's own privacy policy names cookie preferences among the data it processes, but we found no public information on per-visitor consent records, the banner version shown, retention of the log, export or proof of withdrawal. In a supervisory-authority letter I need a log I can reconstruct, and nothing here shows one. 1 2
The Agency Developer not rated — no public information
I found no public information on a consent log, per-visitor records, retention of consent records, export, or re-consent on configuration change. The only related mention is that the vendor's privacy policy collects cookie preferences from its own site visitors, which says nothing about what a customer could show an auditor. 1 2
The Publisher Marketing Lead
Module names on the homepage — third-party consent sync, a consent/PII API and a DSAR inbox for handling customer data requests — suggest consent data is stored and passed on somewhere. But we found no public information on what a consent record contains, retention, banner versions, consent expiry, or export of the log, so nothing here yet proves a choice to an authority. 1
The In-House Lawyer
The homepage names third-party consent sync and a consent/PII API, and the vendor's own privacy policy records cookie preferences, so consent data is evidently held centrally rather than only in the browser. We found no public information on per-visitor records with time and pseudonymous ID, retention of the consent log, export for an audit, banner versions kept so the choice shown can be reconstructed, or proof of withdrawal — the evidence I would want in a dispute with a consumer group. 1 2
The WordPress Webmaster
The module list names a 'Consent / PII API' and 'Third party consent sync', and the privacy policy lists cookie preferences as stored data, which suggests consent gets recorded somewhere. But we found no public information on what a consent record contains, retention of consent logs, banner versions, export of the log, or proof that a withdrawal took effect — the things our DPO would ask me for. 1 2
The Skeptic
A "Consent / PII API" module and cookie preferences counted among stored data are the only things on these pages that touch records. We found no public information on what a consent record contains, how long consent logs are kept, export of the log, re-consent when services change, or any tie between a record and the banner version the visitor saw. 1 2
Frameworks, signals & platforms
panel disagrees
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
Consent is evidently readable and passed on through a consent and personal-data API and third-party consent sync. We found no public information on an IAB TCF registration, Google Consent Mode, Microsoft or US-state signals, CMS plugins, app SDKs or multi-domain management. 1
The Agency Developer
The homepage names a Consent / PII API and third-party consent sync, so there is a stated mechanism for other tools to read the choice, and documents can be distributed to websites, applications and mobile apps. But no captured page names IAB TCF, Google Consent Mode, Microsoft UET, GPP, or plugins for WordPress, Shopify or TYPO3, so the signal and platform story stays at naming level. 1
The Publisher Marketing Lead
This is the first page an ad-funded publisher reads, and it is empty where it matters: we found no public information on the IAB Transparency and Consent Framework, a registered CMP ID, Google Consent Mode, Microsoft or other ad-platform signals, GPP or GPC, app SDKs or CMS plugins. Only a third-party consent sync module and a consent/PII API are named, with GDPR, LGPD and CCPA listed as target laws. 1
The In-House Lawyer
The modules list documents third-party consent sync and a consent/PII API, so other tools can read the visitor's choice, and the vendor names GDPR, LGPD and CCPA as target laws. We found no public information on an IAB TCF registration, Google Consent Mode, Microsoft signals, plugins for named CMS or shop systems, app SDKs, or managing several domains from one account. 1
The WordPress Webmaster
The modules include a 'Consent / PII API' and 'Third party consent sync', so consent presumably reaches other tools, and policy documents are said to distribute across websites, applications and mobile apps. But we found no public information on IAB TCF, Google Consent Mode, or a plugin for WordPress or any other named system — exactly the integrations our site's tag setup depends on. 1
The Skeptic
"Third party consent sync" and a "Consent / PII API" are named modules, and the homepage names GDPR, LGPD and CCPA as laws the product helps with. We found no public information on IAB TCF, Google Consent Mode, Microsoft or US-state signals, CMS plugins, app SDKs, or managing several domains from one account. 1
European sovereignty
panel opinion
panel disagrees
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
There is a Dutch contracting entity with a KvK number, an Amsterdam address, and a policy statement that data is processed within the European Union, though the same passage also allows processing outside the EU where a country offers an effective protection level. Subprocessors are named for hosting, analytics and email — OVH alongside Google, Sendgrid, Mailgun and Mailchimp — without locations or safeguards. We found no public information on a customer data processing agreement, certifications, or where the banner script and consent logs are served and stored. 1 2
The Agency Developer
The contracting entity is a Dutch B.V. with a KvK number and Amsterdam address, a data protection officer is named, and the policy states processing within the European Union with a carve-out for countries with an effective protection level. Subprocessors are listed by name — OVH, Google, Sendgrid, Mailgun, Mailchimp — for hosting, web analytics and email, with only that general sentence as a safeguard, and I found no public information on where consent logs are stored, a customer data processing agreement, or certifications. 1 2
The Publisher Marketing Lead
The top of the chain looks European: a Dutch company in Amsterdam with a KvK number, EU processing stated as the default, security basics listed, and named subprocessors OVH, Google, Sendgrid, Mailgun and Mailchimp. But the EU-only claim bends to countries with an 'effective protection level', several of those processors are US providers with no stated safeguard, and we found no public information on a data processing agreement, certifications, or where the banner script and consent logs are actually served and stored. 1 2
The In-House Lawyer
The contracting entity is a Dutch company with a KvK number and an Amsterdam address, processing is stated to remain in the EU unless a country offers an effective protection level, and subprocessors are named, including OVH, Google, Sendgrid, Mailgun and Mailchimp. Where the banner script is served from and where consent logs and scan results are stored are not described, the subprocessors carry no locations, and we found no public information on a customer data processing agreement or security certifications, so only part of the chain is evidenced. 1 2
The WordPress Webmaster
The contracting entity is Dutch (Digital Data Solutions B.V., KvK 75762277, Amsterdam) with a data protection officer and a stated EU-first processing policy that allows non-EU processing where the country has an effective protection level, and subprocessors are named: OVH, Google, Sendgrid, Mailgun and Mailchimp. However that list covers the hosting, web analytics and email of their own website, and we found no public information on a data processing agreement for customers, security certifications, or where the banner script and consent logs are served and stored. 1 2
The Skeptic
The contracting entity is European — Digital Data Solutions B.V. at Plantage Middenlaan 42a, Amsterdam, KvK 75762277 — and the privacy policy states processing stays in the European Union, though the very next sentence allows processing outside it wherever a country has an "effective protection level". The named processors — OVH, Google, Sendgrid, Mailgun, Mailchimp — are disclosed for the vendor's own website hosting, analytics and email, several of them US-based with no safeguard named beyond that phrase. We found no public information on a published data processing agreement, security certifications, or where the banner script and consent logs are served and stored. 1 2
Pricing transparency
not rated — the vendor publishes no price
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
The captured homepage shows a pre-launch product reached by application — "Interested? Apply for the bèta!" — with no tiers, prices or limits on the page. We found no public information on per-domain pricing, traffic or consent limits, minimum terms or agency conditions, so no annual cost can be computed from the public pages. 1
The Agency Developer
The captured pages publish no prices, tiers, limits or terms; the homepage invites applications to an open beta and promises notification when the product goes live. As a buyer I cannot compute any cost for one client site, let alone a portfolio of forty. 1
The Publisher Marketing Lead
We found no public information on pricing: the captured pages show no tiers, prices, page-view or consent limits, add-ons, minimum terms or agency terms, and the homepage routes every interested buyer into an open-beta application, so no annual cost can be computed from what is published. 1
The In-House Lawyer
The captured pages show no prices, tiers, page-view or domain limits at all, and the product is in an open beta reached through an application form. A buyer cannot compute any annual cost from public information today. 1 2
The WordPress Webmaster
No price appears anywhere on the captured pages; the homepage only invites readers to apply for an open beta and get notified when the product goes live. As the one who has to defend a budget line, I cannot work out an annual cost per site from public information at all. 1
The Skeptic
No price, tier, limit or minimum term appears on either captured page; the only commercial signal is "Interested? Apply for the bèta! … and get notified when we go live". A buyer cannot compute any annual cost from what is public — unsurprising for a product still in open beta ahead of launch. 1
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 |
EU only
unverified
Why unverified?The immediately following sentence allows processing outside the EU if the country has an "effective protection level", so the exclusivity is conditional rather than absolute. |
4/4 pts | 2 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 ConsentStack
Is ConsentStack European?
Not determined: the vendor’s pages as captured do not say where ConsentStack is based.
Where does ConsentStack store data?
ConsentStack stores customer data in the EU, per the vendor’s page captured 10 Nov 2026.
Does ConsentStack have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to ConsentStack?
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: ConsentStack alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The immediately following sentence allows processing outside the EU if the country has an "effective protection level", so the exclusivity is conditional rather than absolute.
- 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 (consentstack.com, consentstack.com/privacy-policy). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
Sources (2)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page consentstack.com Checked 10 Nov 2026 Details →
- 2 Legal notice — found from the homepage consentstack.com Checked 10 Nov 2026 Details →