Conversion Optimization
Instapage
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Instapage, Inc. · instapage.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.
Instapage at a glance
- Vendor
- Instapage, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Instapage 1/5, the mean of 6 judges. Instapage, Inc. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Instapage, Inc. is a hosted drag-and-drop landing-page builder whose evidenced testing is client-side: A/B tests and AI-generated page variations inside the builder, AdMap ad-to-page alignment, and Collections that vary one page by audience, location and use case. It scores highest on data and integrations, 2 to 4, where a catalogue of 120+ integrations across email, CRMs, e-commerce, analytics and marketing automation is the standout fact, and on experimentation scope, 2 to 4 — though only within the vendor's own pages. Statistical rigour sits at 0 to 0, with no public information on the method behind a winner call, and consent and tracking sits at 0 to 1 because the GDPR pages set out the buyer's obligations rather than the test script's behaviour. Performance impact clusters at 1 to 2 on speed claims without measurements. Sovereignty holds at 1 to 1: Amazon and Google cloud hosting with servers across North America, Europe and Asia is disclosed, while data residency, subprocessors and the contracting entity's jurisdiction are unconfirmed on the captured pages. The only pricing fact is a 14-day free trial.
Speaks for it
- 120+ documented integrations across email platforms, CRMs, e-commerce, analytics and marketing automation
- A/B tests and AI-generated page variations are available inside a drag-and-drop builder that needs no tech expertise
- AdMap connects ads to relevant landing pages, and Collections turn one page into many for different audiences, locations and use cases
- Custom JavaScript, HTML/CSS and third-party scripts are supported in the builder
- A 14-day free trial is published — "No obligations. Cancel anytime."
Held against it
- Statistical rigour has the lowest range on the board, 0 to 0, with no public information on the method behind a winner call
- Everything evidenced sits client-side inside the vendor's own page builder, and we found no public information on server-side SDKs, feature flags or multivariate tests
- Consent and tracking scored 0 to 1, as the GDPR pages address the customer's obligations and we found no public information on the test script's behaviour before consent
- We found no public information on exporting results, visitor-level data or a documented API, so a test's verdict stays inside the vendor's reporting
- Performance rests on claims — pages that "load blazingly fast" via the Thor Render Engine — with no public information on script weight or measured Core Web Vitals impact
Best for
- You run paid campaigns and need ads matched to personalised landing pages built without developers
- You want client-side A/B tests on landing-page variations flowing into an existing analytics and CRM stack
- You need to scale one page across audiences, locations and use cases using manual or AI placeholders
Avoid if
- You must defend winner calls with a documented statistical method, sample-size or duration guidance
- You need experimentation beyond the vendor's own landing pages, such as server-side delivery, feature flags or multivariate tests
- Your data protection officer must sign off on visitor tracking before deployment — the captured pages address your obligations, not the script's behaviour
- You must confirm where visitor data is processed — hosting is disclosed across North America, Europe and Asia, with residency and subprocessors unconfirmed on the captured pages
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 1.5 of 5 |
| Statistical method & guardrails | 0 of 5 |
| Consent & visitor tracking | 0 of 5 |
| Snippet performance & flicker | 1 of 5 |
| Analytics, data export & integrations | 1 of 5 |
| European sovereignty | 0.5 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 — Simple A/B split of one page element through a visual editor; no server-side option, no targeting beyond URL.
3 — Client-side A/B and split-URL tests with basic audience targeting, and no SDK or server-side delivery.
5 — Client-side and server-side experiments through documented SDKs for common languages, multivariate and multi-page tests, audience targeting on behaviour and attributes, and rule-based personalisation.
8 — Feature-flag-based experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, edge or CDN delivery, 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
A drag-and-drop builder with A/B tests on pages created inside it is confirmed, and Collections can vary placeholders by audience, location or use case, which meets my no-developer requirement for landing pages. But we found no public information on server-side or SDK delivery, split-URL or multivariate tests, feature flags, or audience targeting beyond page-level placeholders — nothing captured shows a testing programme beyond the vendor's own landing pages. 1 4
The E-Commerce Manager
A/B tests and AI-generated page variations are documented, plus AdMap and Collections that swap content by audience or location — all of it client-side landing-page work. We found no public information on server-side or SDK delivery, multivariate or multi-page tests, or personalisation tested against a control, which is exactly the proof I need before serving targeted content to shoppers. 1 4
The Product Engineer
Client-side A/B tests and AI-generated variations live inside the vendor's own drag-and-drop page builder, with audience and location personalisation through Collections and ad-to-page matching. We found no public information on server-side SDKs, feature flags, edge delivery, multivariate tests or mutually exclusive groups, so testing anything outside the vendor's builder has no documented path. 1 4
The CRO Consultant
What's evidenced is A/B tests and AI-generated page variations inside a hosted landing page builder, plus ad-to-page personalisation through AdMap and Collections placeholders for different audiences and locations. We found no public information on server-side SDKs, feature flags, or multivariate and multi-page experiments, so from these pages I can only recommend it for client-side landing page testing, not a wider experimentation programme. 1 4
The Data Protection Officer
The captured pages show A/B testing and AI experiments on variations of the vendor's own hosted landing pages, with basic audience targeting through ad-to-page alignment and Collections for different audiences and locations. We found no public information on SDKs, server-side or edge delivery, feature flags, multivariate tests, or holdouts. 1 4
The Skeptic
Everything evidenced lives inside a hosted drag-and-drop landing-page builder: A/B tests, AI-generated page variations, Collections scaled to different audiences and locations, and ad-to-page personalisation. We found no public information on server-side SDKs, multivariate or multi-page tests, feature flags, mutually exclusive experiment groups or holdouts — the evidence stops at client-side page tests with basic audience targeting. 1 4
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 — A "winner" or "probability to beat" figure with no documented method, no stated sample-size guidance and no warning against stopping early.
3 — The method is named (frequentist or Bayesian) but its assumptions are not documented, and nothing prevents a test from being called while it is still underpowered.
5 — Documented method with confidence or credible intervals, a sample-size or test-duration calculator, and stated guidance on when a result may be read.
8 — Sequential testing or an equivalent documented protection against peeking, 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 captured pages say only that you run A/B tests or AI experiments to "quickly optimize and iterate"; we found no public information on which statistics decide a winner, sample-size or duration guidance, handling of repeated looks, or sample ratio checks. For figures I have to defend when finance asks where the revenue went, nothing here is presentable. 4
The E-Commerce Manager
The pages mention A/B tests and "AI experiments" but we found no public information on the statistical method, sample-size or duration guidance, protection against early stopping, or sample ratio mismatch detection. A winner call I cannot verify is a risk to my conversion numbers, and nothing documented here supports one. 1 4
The Product Engineer
The pages say to run A/B tests or AI experiments and leave it there; we found no public information on the statistical method, confidence or credible intervals, sample-size guidance, peeking, multiple-comparison handling or sample ratio mismatch detection. From the captured pages, a winning variant is a number with nothing behind it I could defend in a review. 4
The CRO Consultant
The pages invite you to "run A/B tests or AI experiments" but we found no public information on the statistical method, any sample-size or duration guidance, or any guardrail against calling a test while it is underpowered. Nothing here would let me defend a winner call to a client. 4 1
The Data Protection Officer
The pages say to run A/B tests and iterate toward the best-performing version, but we found no public information naming a statistical method, sample-size or duration guidance, or any protection against calling a result early. Nothing captured documents intervals, peeking safeguards, or sample ratio checks. 4 1
The Skeptic
The only methodology-adjacent sentence captured is "run A/B tests or AI experiments to quickly optimize and iterate for the best-performing version" — a best-performing verdict with no named method, and "quickly" reads as encouragement to stop early rather than a warning against it. We found no public information on the statistical method, sample-size or duration guidance, intervals, sequential testing, multiple-comparison corrections, sample ratio mismatch detection or guardrail metrics. 4
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 — Nothing on the vendor's pages says what the script stores on the device or whether it runs before consent; consent is described as the customer's problem.
3 — Cookies or local storage are listed, and a consent integration is mentioned, but the documentation does not say what the script does before consent is given.
5 — Documented behaviour before and after consent, integration with common consent management platforms, a published list of cookies and storage keys with their lifetime, and IP anonymisation described.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, retention of visitor data stated, and guidance on the legal basis for testing in the EU.
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
The GDPR pages describe general obligations plus infrastructure security — cloud servers, firewalls, SSL, SAML sign-in — but we found no public information on what the script stores on a visitor's device, when it runs relative to consent, or any consent-management platform integration. The GDPR page frames the obligations as applying to the customer "regardless of your physical operational location", which leaves the §25 TDDDG questions my legal team will ask unanswered. 2 3
The E-Commerce Manager
The GDPR page tells the operator "the GDPR will apply to you", and the compliance page covers cloud hosting, firewalls, SSL and SAML sign-in. We found no public information on what the script stores on the device, whether it runs before consent, or a cookieless mode — the consent question reads as mine to answer, not the vendor's. 2 3
The Product Engineer
The GDPR and compliance pages describe SSL, firewalls and SSO, and tell the customer that GDPR applies to them regardless of where they operate. We found no public information on what the tracking stores on the device, whether it runs before consent, a cookie or storage-key list, or any consent management platform integration — the compliance story is about the customer's obligations, not the script's behaviour. 2 3
The CRO Consultant
The GDPR pages are addressed to the customer's own obligations — "the GDPR will apply to you, regardless of your physical operational location" — and the compliance feature list covers SSL, firewalls and SAML sign-in rather than the test script's behaviour. We found no public information on what the script stores on a visitor's device, when it runs relative to consent, or a cookieless mode, so a DPO has nothing to sign off from these pages. 2 3
The Data Protection Officer
The GDPR page explains that the GDPR applies to the customer regardless of their location, and the GDPR-compliance page covers SSL, firewalls and single sign-on — security features, not consent behaviour. We found no public information on whether the test script may run before the consent banner is answered, on any list of cookies or storage keys, on a consent-pending or cookieless mode, or on how visitor identifiers and IP addresses are handled. 2 3
The Skeptic
The GDPR page addresses the buyer — the GDPR "will apply to you" — and the compliance-features page documents hosting, firewalls, SSL and single sign-on rather than anything about cookies or when the script runs. We found no public information on what the script stores on the device, its behaviour before consent, consent-management-platform integration, a cookieless mode, or how visitor identifiers and retention are handled. 2 3
Snippet performance & flicker
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 snippet with no stated size, no flicker handling and no mention of performance.
3 — An anti-flicker snippet that hides the page until the test loads, with a timeout, and no published figures for script size or load cost.
5 — Script size and loading behaviour documented, asynchronous loading option, flicker handling explained with its trade-off, and CDN delivery of the snippet.
8 — Published performance figures including 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
Performance appears only as marketing language — a "Thor Render Engine", pages that "load blazingly fast", dual redundancy on Amazon and Google servers across North America, Europe and Asia. We found no published figures for script weight, load cost or flicker handling, and no mention of Core Web Vitals, so I cannot quantify what a test configuration costs the page. 3 4
The E-Commerce Manager
Speed appears only as marketing language — pages that "load blazingly fast" through a Thor Render Engine on Amazon and Google servers across three continents. We found no public information on script size, asynchronous loading, flicker handling, or measured Core Web Vitals impact; a claim is not a figure, and my product pages cannot bet on one. 3 4
The Product Engineer
Speed is claimed in marketing language — a Thor Render Engine with servers across three continents and pages that load blazingly fast — but we found no published script weights, load-cost figures, Core Web Vitals impact, flicker handling or a self-hosting option. These are claims, not measurements a customer can act on. 3 4
The CRO Consultant
Speed is marketed — the Thor Render Engine with servers across North America, Europe, and Asia, and pages that "load blazingly fast" — but these are delivery claims about the vendor's own pages, not measurements of what testing costs. We found no public information on script weight, load cost, Core Web Vitals impact, flicker handling or a self-hosting option. 3 4
The Data Protection Officer
Speed appears only as a marketing claim — landing pages that load blazingly fast through the vendor's rendering engine on Amazon and Google servers. We found no public information on published script weight or load-cost figures, flicker handling with its trade-off, Core Web Vitals impact, or a self-hosting option. 3 4
The Skeptic
Performance appears only as adjectives — pages that "load blazingly fast" through a render engine on servers "across North America, Europe, and Asia" — with no measurement behind any of it. We found no public information on script size, load cost, effect on Core Web Vitals, asynchronous loading or flicker handling. 3 4
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 — Results visible in the vendor's dashboard only; no export, no analytics integration, no API.
3 — CSV export of aggregated results and one analytics integration, with no visitor-level data and no documented API.
5 — Integrations with common analytics and tag managers, export of results, and a documented API for managing experiments and reading results.
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 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
Integrations are the strongest card: 120+ apps by category including analytics, CRMs and marketing automation, which would connect to our existing stack. But we found no public information on a documented API, export of visitor-level results, or any data warehouse connection — so on what is captured, a result cannot be re-checked in our own data and remains a claim, not a finding. 1 4
The E-Commerce Manager
One solid fact: 120+ integrations covering email, CRM, e-commerce, analytics and marketing automation. We found no public information on exporting results, visitor-level data, or a documented API, so I see no way to check a winning page against my own numbers. 1
The Product Engineer
120-plus integrations including analytics, CRM and marketing automation are advertised, which is genuine breadth for page plumbing. But we found no public information on results export, visitor-level data, a documented API or any warehouse analysis — an experiment result I can only read in the vendor's dashboard is a claim I cannot check against my own data. 1 4
The CRO Consultant
A catalogue of 120+ integrations including analytics, CRM and marketing automation is published, which connects the platform to the marketing stack. We found no public information on export of results, visitor-level data or a documented API, so an experiment result cannot be checked against a client's own data from these pages. 1 4
The Data Protection Officer
The vendor advertises 120+ integrations including analytics and marketing automation tools, so results can flow into other platforms. We found no public information on exporting aggregated or visitor-level results, on a documented API with stated limits, or on warehouse-based analysis. 1 4
The Skeptic
A documented catalogue of 120+ integrations across analytics, CRMs, e-commerce and marketing automation is genuine plumbing for getting signals out. We found no public information on export of results or visitor-level data, a documented API, or warehouse-based analysis — so a test's verdict stays inside the vendor's own reporting as far as the captured pages show. 1 4
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 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and visitor data leaving the EU without a stated safeguard.
3 — EU data residency offered as an option or an enterprise add-on while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU processing of visitor data as standard and an EU contracting entity, but parts of the chain — CDN, support access, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure including the delivery of the snippet, EU contracting entity, subprocessor list published, and a DPA 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
Hosting is named as Amazon and Google clouds with servers across North America, Europe and Asia, which tells me visitor data can be processed outside the EU with no stated safeguard. The contracting entity's jurisdiction, ownership, data residency for visitor data and the subprocessor list are all reported as not confirmed on the vendor's own captured pages — for a script that records every visitor's behaviour, that is not something I can take to our data protection officer. 3
The E-Commerce Manager
Hosting is at least named — Amazon and Google cloud, dual redundancy, servers across North America, Europe and Asia — but we found no public information on the contracting entity's jurisdiction, an EU residency commitment, subprocessors, or a data processing agreement for visitor data. With regions outside Europe in the chain and no stated safeguard, I could not run this over my EU traffic with confidence. 3
The Product Engineer
Hosting is named as Amazon and Google cloud with dual redundancy across North America, Europe and Asia, but we found no public information on where visitor data is processed, the contracting entity's jurisdiction, a subprocessor list, or a data processing agreement covering the visitor data collected. Multi-continent redundancy with no stated EU residency commitment leaves the visitor-data path unaccounted for. 3
The CRO Consultant
Hosting is disclosed as Amazon and Google cloud in dual redundancy with servers across North America, Europe and Asia, but we found no public information on the contracting entity's jurisdiction, an EU processing commitment, a subprocessor list or a data processing agreement covering the visitor data. With North American regions in the disclosed list and no stated safeguard, there is nothing here showing visitor behaviour data stays in the EU. 3
The Data Protection Officer
Hosting is named — Amazon and Google clouds with servers across North America, Europe and Asia — with no stated EU residency for visitor data and no stated safeguard for data leaving the EU. We found no public information on a published subprocessor list including the content delivery layer, on the contracting entity's jurisdiction, or on a data processing agreement covering visitor data. 3 2
The Skeptic
The vendor names Amazon and Google cloud hosting with servers "across North America, Europe, and Asia", which describes a global footprint rather than an EU processing commitment, and no safeguard for data leaving the EU is stated. We found no public information on the contracting entity's jurisdiction, a subprocessor list, or a data-processing agreement covering the visitor data the platform collects. 3
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 starting price or a free tier exists, but the traffic metric, the limits and what happens above them are unstated — the invoice is unknowable.
5 — Tier prices public with the traffic metric and its limits defined, but at least one commonly needed piece (server-side SDKs, personalisation, overage) is unpriced or "contact sales".
8 — Every tier priced publicly with the traffic metric defined, limits, overage rates, module prices, 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
The only pricing-related fact published is a 14-day free trial with no obligations; we found no public prices, no traffic metric, and no statement of limits, overage or what happens above a limit. I cannot estimate even a rough annual cost for a given traffic volume from the captured pages. 1
The E-Commerce Manager
The only public pricing fact is a 14-day free trial with "no obligations". We found no public information on tier prices, the traffic metric, limits, overage or seat costs, so the annual invoice for my December traffic is not computable from these pages. 1
The Product Engineer
A 14-day free trial with no obligations is published, but we found no public prices, traffic metric, tier limits, overage terms or module pricing on the captured pages. A buyer cannot compute any annual cost from what is shown here. 1
The CRO Consultant
The only public pricing fact is a "14-day free trial. No obligations. Cancel anytime." — we found no public information on tier prices, the traffic metric, limits, overage or module terms. Since I have to estimate a client's traffic tier before recommending a contract, the annual invoice is unknowable from public pages. 1
The Data Protection Officer
The only pricing-related information on the captured pages is a 14-day free trial with no obligations. We found no public prices for any tier, no traffic metric or limits, and no statement of what happens above a limit — the invoice is not computable from public pages. 1
The Skeptic
A 14-day free trial is the only pricing fact on the captured pages; we found no public information on tier prices, the traffic metric a site is billed on, limits, overage treatment, or module and seat prices. Nothing public allows even a rough annual invoice to be worked out in advance. 1
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Instapage
Is Instapage European?
Not determined: the vendor’s pages as captured do not say where Instapage is based.
Where does Instapage store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Instapage have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Instapage?
As of 21 Oct 2026, the panel rates GrowthBook (3.5/5), Convert Experiences (3.5/5) and Webtrends Optimize (3/5) highest among the other 31 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 Webtrends Optimize (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Instapage alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 15 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
- 5 compliance 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
- 4 data 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 legal 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 support 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (4)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page instapage.com Checked 13 Oct 2026 Details →
- 2 Consent & visitor tracking — found from sitemap instapage.com Checked 13 Oct 2026 Details →
- 3 Consent & visitor tracking — found from sitemap instapage.com Checked 13 Oct 2026 Details →
- 4 Analytics, data export & integrations — found from sitemap instapage.com Checked 13 Oct 2026 Details →