Clerk.io
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 Clerk.io ApS · www.clerk.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.
Clerk.io at a glance
- Vendor
- Clerk.io ApS
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- In the EU source, captured 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Clerk.io 2/5, the mean of 6 judges. Clerk.io is a personalisation engine for e-commerce search, recommendations and email content, and the bench scored it highest as a privacy product and lowest as a testing product. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Clerk.io is a personalisation engine for e-commerce search, recommendations and email content, and the bench scored it highest as a privacy product and lowest as a testing product. Consent and tracking is the strongest criterion at 6-7: cookieless tracking is the default, sessions are hashed from IP address, user agent and a per-store salt rotated every 30 days, and four privacy modes, retention of one to twelve months and deletion via API and interface are all published. Statistical rigour is the weakest at 1-2: variants are compared by label in the analytics page, and we found no public information on the statistical method, significance figures or sample-size guidance behind those comparisons. Experimentation scope scores 3-4 because testing covers the vendor's own content blocks, not arbitrary page changes or server-side experiments. Data and integrations is uniform at 4 — a versioned REST-like API, with no public information on analytics, tag-manager or warehouse integrations. Sovereignty scores 5-6: servers in Germany with backup in Ireland, but optional AI features send text to OpenAI in the US.
Speaks for it
- Cookieless tracking is the default and stores nothing on the visitor's device
- Four privacy modes, including a persistent identifier for visitors who consent and a private mode that collects nothing
- Visitor data retention stated at one to twelve months, with deletion via the Forget API and the interface
- Servers in Germany with backup in Ireland, plus a published subprocessor list, a standard data processing agreement and third-party GDPR certification
- A versioned REST-like API with a published reference and documented click and sale logging
Held against it
- We found no public information on the statistical method, significance figures or sample-size guidance behind split-test comparisons
- Split tests compare the vendor's own content blocks, configured through an attribute in the embed code
- Optional AI features send text to OpenAI in the US unless disabled
- The captured pages give different figures for the company name — the copyright notice names Clerk.io, Inc. while the vendor presents itself as a Danish ApS
- We found no public information on script weight, its effect on Core Web Vitals, or pricing
Best for
- You run an e-commerce store and want personalised search and recommendations with cookieless tracking on by default
- Your data protection review depends on documented retention windows, a deletion API and storage of visitor data within the EU
- Your developers are ready to build a custom export pipeline on a documented REST-like API
Avoid if
- You need a full client-side testing programme — arbitrary page changes, split-URL tests, multivariate designs, audience targeting or server-side experiments
- You must defend a declared winner statistically to a client or finance team, with significance figures and sample-size guidance
- Your marketers must configure and read tests without developer help
- You need customer data to stay within the EU and plan to enable the optional AI features, which send text to OpenAI in the US
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 2 of 5 |
| Statistical method & guardrails | 1 of 5 |
| Consent & visitor tracking | 3.5 of 5 |
| Analytics, data export & integrations | 2 of 5 |
| European sovereignty | 3 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
Split testing is documented and real: Clerk.js divides visitors evenly across any number of variants of the store's own content blocks and you compare them by label in the Analytics page, next to a well-documented personalisation engine for search, recommendations and email. But tests are configured through a data attribute in the embed code rather than a visual editor my marketers could drive alone, and we found no public information on targeting by URL, device or audience for tests, on multivariate testing, or on server-side experiments. For my programme this is a specialist's personalisation tool, not a team-wide testing platform. 5 7
The E-Commerce Manager
Split testing is built in and automatic: Clerk.js splits visitors evenly across any number of variants, supports several test groups per page, and results are compared per content block in the analytics pages. But the tests compare which Clerk logic runs — we found no public information on a visual editor, targeting by URL, device or audience, split-URL tests, multivariate tests or server-side experiments. The personalisation engine itself, recommendations driven by click and purchase history, is well evidenced and is what the variants manipulate. 5 3 7
The Product Engineer
Split testing is documented, but only for this vendor's own content blocks: variants are declared in the embed code with a data-split-test attribute, the client script splits visitors evenly across any number of variants, and results are compared by label in the analytics page. That is a client-side A/B mechanism attached to a personalisation engine — we found no public information on multivariate tests, holdouts, mutually exclusive experiment groups, or allocating experiments from a server-side SDK. If I can only test which of the vendor's own recommendation logics wins, I still need a real experimentation platform next to it. 5 7
The CRO Consultant
Split testing here means comparing the vendor's own content blocks: variants are declared in the embed code, Clerk.js renders them client-side with an even split, any number of variants and multiple groups per page are supported, and performance is compared by label in the analytics page. We found no public information on testing arbitrary page changes, split-URL tests, targeting by URL or device, or server-side experiments, so this covers testing a recommendations programme rather than a full client-side CRO programme. 5
The Data Protection Officer
The split-testing documentation shows client-side A/B tests of the vendor's own content blocks, configured through an embed attribute, with an automatic even traffic split, any number of variants, and results read by comparing labelled blocks in the analytics page; behaviour-driven recommendations and search personalisation through the Knowledge Graph are core to the platform. We found no public information on server-side experiments, split-URL or multivariate designs, audience targeting, or holdouts, so testing stays within the client-side split of the vendor's own content. 5 7
The Skeptic
Split testing is documented, but only inside Clerk's own product: an embed-code attribute splits traffic evenly across any number of variants of Clerk banners, several groups can run on one page, and results are compared by label in the analytics page, while the broader platform is a personalisation engine for search, recommendations and email content. We found no public information on testing arbitrary page changes, split-URL or multivariate designs, server-side experiments, feature flags or holdouts. 5 7
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
The split-testing documentation says to compare each variant's performance in the Analytics page, but none of the captured pages name a statistical method, show a significance or confidence figure, or mention sample-size guidance, peeking protection, multiple-comparison correction or sample ratio checks. I could not defend a declared winner to my finance team on the strength of what is published here. 5
The E-Commerce Manager
The only documented evaluation is comparing each variant's content block by tracking label on the analytics page. We found no public information on the statistical method, significance or probability figures, sample-size or duration guidance, or any protection against peeking, multiple comparisons or unbalanced splits — as a shop owner I would be reading raw dashboard differences and deciding myself. 5 9
The Product Engineer
The documentation says variants are compared by performance in the analytics page, with sales attribution fed by click and order logging, but no statistical method is named in any of the captured pages. We found no public information on significance or probability figures, confidence intervals, sample-size guidance, peeking, multiple-comparison correction or sample ratio mismatch detection. For a team that re-runs the numbers in its own warehouse, nothing here tells me how a winner is decided. 5 6
The CRO Consultant
The testing pages describe comparing variant content blocks in the analytics page and dashboards that attribute sessions to the vendor's widgets, but we found no public information naming a statistical method, a significance or probability figure, sample-size guidance, or protections such as sample ratio mismatch detection. Without a documented method, a client of mine could not defend a winner from these reports alone. 5 6
The Data Protection Officer
The only documented readout is a performance comparison between labelled content blocks in the analytics page. We found no public information on the statistical method, significance or probability figures, intervals, sample-size guidance, protection against peeking, correction for multiple comparisons, or sample ratio mismatch detection, so the decision is documented without a named method. 5
The Skeptic
The documentation promises an even split and a performance comparison in the analytics page, then stops: no method is named anywhere we read, no significance or probability figure, no intervals, and nothing on peeking, multiple comparisons, sample-ratio checks or stopping rules. A comparison page without a stated method is a scoreboard, not a finding. 5 6
Consent & visitor tracking
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
Strong: cookieless anonymous sessions are the default and store nothing on the device, there are four privacy modes including a consent-gated persistent identifier in localStorage and a private mode collecting nothing, and the identifier name, its lifetime, the one-to-twelve-month visitor-data retention and deletion via API and UI are all published. We found no public information on integration with consent management platforms or on written guidance for the German TDDDG legal basis for testing, which is exactly what our legal review would ask me for. 7 3 6
The E-Commerce Manager
Cookieless tracking is on by default, the anonymous session identifier stores nothing on the device and blocks tracking beyond 30 days, and there are four privacy modes including a persistent mode explicitly for consented visitors and a private mode that collects nothing. Visitor data retention is stated at one to twelve months, deletion runs through a forget API and the dashboard, and a data processing agreement is offered. We found no public information on integration with consent management platforms or written guidance on testing under §25 TDDDG. 7 3 2
The Product Engineer
This is the strongest part: cookieless tracking is activated by default, sessions are hashed from IP address, user agent and a per-store salt rotated every 30 days, and the session identifier stores nothing on the device. Four privacy modes are documented — the anonymous default, a persistent localStorage identifier explicitly for visitors who give consent, a private mode collecting nothing, and self-generated IDs — alongside visitor-data retention of one to twelve months and deletion via the Forget API. We found no public information on consent-management-platform integration, a consent-pending mode, or written guidance on the legal basis for testing under §25 TDDDG. 7 3 6
The CRO Consultant
Cookieless is the default mode: a session hash over IP address, user agent and a per-store salt rotated every 30 days, nothing stored on the device, long-term tracking beyond 30 days prevented, and a persistent local-storage identifier offered for visitors who consent. Default data collection, one-to-twelve-month retention, deletion via the API and interface, a data processing agreement and a per-account GDPR dashboard are all documented. We found no public information on consent management platform integrations or a consent-pending mode, so the DPO sign-off conversation still has open questions. 7 3 2
The Data Protection Officer
Better documented than most: cookieless tracking is the default and stores nothing on the device, four privacy modes are explained, the persistent mode's single storage key (a long-term visitor identifier in localStorage) is named with its lifetime, visitor data retention of one to twelve months is stated, and a Forget API plus a GDPR dashboard support per-visitor deletion. But the pages never answer whether the script may run before the consent banner is answered, and we found no public information on a consent-pending mode, on integration with consent management platforms, or on guidance for the legal basis of testing in the EU under §25 TDDDG; the default mode also computes a session hash from the IP address and user agent without the vendor stating when that processing may begin. 7 6 3
The Skeptic
Cookieless is the documented default: sessions identified by a hash of IP address, user agent and a per-store salt rotated every 30 days, storing nothing on the device, with four privacy modes including a persistent identifier tied to consenting visitors and a private mode that collects no visitor data; retention of one to twelve months and deletion by API and interface are stated. We found no public information on a consent-pending hold that keeps serving variants, integration with consent management platforms, or guidance on the legal basis for testing under §25 TDDDG. 7 3
Snippet performance & flicker
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead not rated — no public information
We found no public information on snippet performance or flicker: the pages that describe Clerk.js cover setup and cookieless tracking but publish nothing on script weight, loading behaviour, anti-flicker handling or Core Web Vitals impact. 6 7
The E-Commerce Manager not rated — no public information
We found no public information on the snippet's loading behaviour, script weight, flicker handling or impact on Core Web Vitals in the captured pages, including those describing Clerk.js setup and split rendering. On a product page where a tenth of a second shows in conversion, that is the first thing I would demand before installing. 1 5 6
The Product Engineer not rated — no public information
We found no public information on the client script's weight, loading behaviour, flicker handling or effect on Core Web Vitals. The pages we read covering the script's setup and split rendering say nothing about what it costs the page, so this stays unevidenced rather than judged. 1 6 5
The CRO Consultant not rated — no public information
We found no public information on the Clerk.js snippet's size, loading behaviour, flicker handling, a self-hosting option, or any measured effect on Core Web Vitals. The pages we read on the homepage, split testing, visitor tracking, the API and the analytics page describe what the script does but publish no performance figures. 1 5 6 8 9
The Data Protection Officer not rated — no public information
We found no public information on the snippet's weight, loading behaviour, flicker handling, self-hosting options, or any measured effect on Core Web Vitals on any of the captured pages, including the split-testing, visitor-tracking, and cookieless documentation where the script is installed. 1 5 6 7
The Skeptic not rated — no public information
We found no public information on the script's weight, loading behaviour, flicker handling, or impact on Core Web Vitals; the captured documentation describes Clerk.js for tracking and rendering variants but publishes no measurement of what it costs the page. 5 6 7 8
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
There is a documented, versioned REST-like API with a published API reference returning JSON, and the privacy policy states you can access any data you send, processed and unprocessed, with a valid API key. We found no public information on integrations with Google Analytics, Adobe or tag managers, on CSV or warehouse export of results, or on webhooks, so checking a result against our own data would rest entirely on what that API exposes. 8 2 3
The E-Commerce Manager
A versioned REST-like API with a published reference and JSON responses is documented, customers can request any data through it processed or unprocessed, and dashboards attribute sales per location via tracking labels. We found no public information on integrations with analytics or tag-management tools, CSV export of results, webhooks or warehouse delivery, so checking a result against my own order data means building on the API myself. 8 2 6
The Product Engineer
There is a real, versioned REST-like API with a published reference — GET, POST, PATCH and DELETE, JSON responses, and documented click, sale and visitor endpoints — and the privacy policy commits to access to processed and unprocessed data with a valid API key. Beyond that the story stops: we found no public information on analytics or tag-manager integrations, visitor-level export to a data warehouse, or webhooks. I could build against this API, but I would be building my own export pipeline from scratch. 8 2 6
The CRO Consultant
A documented, versioned REST-like API with GET, POST, PATCH and DELETE, JSON responses and a published reference, plus the privacy policy's statement that any data can be accessed through the API processed and unprocessed with a valid key, means results can at least be pulled out of the platform. We found no public information on integrations with analytics or tag management tools, CSV or report export, webhooks, or streaming to a data warehouse, so checking a result in the client's own data would mean building that yourself. 8 2 6 5
The Data Protection Officer
A REST-like API at version 2 is documented with a public reference, including click and sale logging endpoints, and the privacy policy states that data provided through the API, processed and unprocessed, can be accessed with a valid API key, with dashboards attributing sessions. We found no public information on integrations with common analytics or tag managers, warehouse-native or streaming export, or stated API limits. 8 6 2
The Skeptic
What stands on the page is a documented REST-like JSON API, versioned and with a full reference, plus the privacy policy's offer to access any data the API provides, processed and unprocessed, with a valid key, and a Privacy Information API for pulling data into existing setups. We found no public information on exporting results as files, integrations with analytics or tag-management tools, or visitor-level raw data flowing to a warehouse. 8 2 3
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
Servers are stated to be in Germany with backup in Ireland, all personal data stored and processed there, service providers are required to keep personal data within the EU, a data processing agreement and third-party GDPR certification are offered, and a trust centre publishes the subprocessor list. The contracting entity's jurisdiction is not confirmed on the captured pages — the copyright notice names Clerk.io, Inc. — and the optional AI features send text to OpenAI in the US, so enabling them moves some data outside the EU. 3 2
The E-Commerce Manager
Hosting is stated as standard with servers in Germany and backup in Ireland where all personal data is stored and processed, subprocessors are kept within the EU and listed at the trust centre, and a data processing agreement plus third-party GDPR certification are published. The contracting entity is not confirmed — the captured pages give different figures for the company name — and optional AI features send text to OpenAI in the US, so data is not European end to end; we found no public information on where the delivered script itself is hosted. 3 2
The Product Engineer
The trust documentation states all personal data is stored and processed on servers in Germany with a backup in Ireland, that service providers must keep personal data within the EU, and a subprocessor list sits at the trust center with a standard data processing agreement offered. The contracting entity's jurisdiction is not confirmed on the captured pages, snippet-delivery location is not stated, and the privacy policy discloses optional AI features that send message content to OpenAI in the US — so this reaches solid EU-standard processing but not sovereign end to end. 3 2
The CRO Consultant
Servers are stated to be in Germany with a backup in Ireland, where all personal data is stored and processed, service providers are pledged to keep personal data within the EU, and a subprocessor list, data processing agreement and third-party GDPR certification are published at the trust centre. The contracting entity's jurisdiction is not confirmed — the privacy policy's copyright names 'Clerk.io, Inc.' — and optional AI features send message content to OpenAI in the US unless disabled, so this sits at solid mid-level rather than higher. 3 2
The Data Protection Officer
Visitor data is stated to be stored and processed in Germany with a backup in Ireland, service providers are stated to keep personal data within the EU, a subprocessor list is published at the trust centre, and a standard data processing agreement is offered with third-party GDPR certification. The contracting entity is not pinned down — the copyright names "Clerk.io, Inc." while the company presents itself as a Danish ApS — the snippet delivery location is not stated, and the privacy policy states that US transfers go only to processors on the EU–US Privacy Shield list while separately disclosing that optional AI features send content to OpenAI, L.L.C. for language-model processing. 3 2
The Skeptic
Servers in Germany with backup in Ireland, a statement that all personal data is stored and processed there, service providers required to keep data within the EU, a published subprocessor listing through the trust centre, a standard data processing agreement and third-party GDPR certification. Against that, the contracting entity's jurisdiction is not confirmed on the captured pages, subprocessor locations are not shown, and optional AI features send provided text to OpenAI, L.L.C., so some customer data can leave the EU when those features are enabled. 3 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead not rated — no public information
We found no public information on pricing: none of the captured pages state tiers, a traffic metric such as tracked users or impressions, or any starting price, so an annual cost cannot be estimated from the public pages I read. 1
The E-Commerce Manager not rated — no public information
We found no public information on pricing in any captured page — no tiers, no traffic metric such as monthly visitors or impressions, not even a "from" price. A traffic-based price I cannot see at all is worse than one I have to estimate before the December peak. 1 3 8
The Product Engineer not rated — no public information
We found no public information on pricing — no tiers, no traffic metric such as tracked users or impressions, no seats — in the captured pages. A buyer cannot compute any annual cost from what is published, so this is reported as unevidenced rather than scored as a limitation. 1 5 8
The CRO Consultant not rated — no public information
We found no public information on prices, tiers, the traffic metric behind them, seat counts or trial terms on any page we read, including the homepage, the security and trust pages, the API documentation and the analytics page. A client could not estimate an annual cost from what is published, which means every quote is a sales conversation. 1 3 8 9
The Data Protection Officer not rated — no public information
We found no public information on pricing — no tiers, no traffic metric, and no "from" price appears on any captured page, so a buyer cannot begin to compute an annual cost. 1 5 8
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
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The privacy policy (S1) discloses optional AI features that send message content to OpenAI, L.L.C., so some customer data can leave the EU when those features are enabled. |
4/4 pts | 3 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 Clerk.io
Is Clerk.io European?
Not determined: the vendor’s pages as captured do not say where Clerk.io is based.
Where does Clerk.io store data?
Clerk.io stores customer data in the EU, per the vendor’s page captured 17 Nov 2026.
Does Clerk.io have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Clerk.io?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 Conversion Optimization 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 Varify.io (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: Clerk.io 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.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting location. The privacy policy (S1) discloses optional AI features that send message content to OpenAI, L.L.C., so some customer data can leave the EU when those features are enabled.
- 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 could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 16 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
- 13 integrations 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
- 3 support 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
- 2 legal 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.clerk.io Checked 17 Nov 2026 Details →
- 2 Privacy policy — found from the homepage trust.clerk.io Checked 17 Nov 2026 Details →
- 3 Security / trust page — found from the homepage help.clerk.io Checked 17 Nov 2026 Details →
- 4 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap docs.clerk.io Checked 17 Nov 2026 Details →
- 6 Consent & visitor tracking — found from sitemap docs.clerk.io Checked 17 Nov 2026 Details →
- 7 Consent & visitor tracking — found from sitemap help.clerk.io Checked 17 Nov 2026 Details →
- 8 Analytics, data export & integrations — found from sitemap docs.clerk.io Checked 17 Nov 2026 Details →
- 9 Analytics, data export & integrations — found from sitemap www.clerk.io Checked 17 Nov 2026 Details →