Skip to content
INSIGHTSbyPROVENANCE
Book a demo

Website privacy & cookies

No optional analytics or advertising is configured in this website application. There is no optional tracking preference to save. Dismissing the notice only hides it until this page reloads; closing this panel does not give consent to anything.

Our source and public-response check is limited. Hosting logs, security challenges, enquiry handling and retention still need confirmation. The information pages are review-needed, not a complete approved privacy or cookie policy.

You can browse without an enquiry. The demo form explains whether it opens a mail draft or submits to a configured endpoint, and includes a clear-fields control. These website choices do not change consent on customer websites using INSIGHTS.

Website privacy informationCookies and choices
Pricing

Priced on traffic measured, not on people identified.

Plans scale with the requests you measure and the evidence your reviewers need. Every plan includes the three-lane model and the audit evidence; the difference is depth of reporting, jurisdiction handling and how much of your DPIA we help you carry.

Standard

See how your whole audience uses your site, without a consent fight.

Tailored

Single product · standard traffic profile

  • Anonymous statistics and consent-accepted lanes with one tag
  • Aggregate dashboard: page groups, country, device, network
  • 1, 7 or 14-day privacy windows, within the property profile cap
  • Bot classification and abuse-rate summary
  • Window reach estimates with 90% intervals
  • Standard suppression threshold
Scope a pilot
Most common

Regulated

For teams whose DPO needs the evidence, not just the dashboard.

Tailored

Regulated product · enhanced evidence

  • Everything in Standard
  • Monthly modelled reach with confidence bands, once calibrated
  • Jurisdiction profiles, including conservative EU defaults
  • 30-day windows within profile cap and current approval
  • The evidence pack: test results, attestations, destruction records
  • Signed, hash-chained deletion records for your regulator
  • Configurable suppression threshold
Scope a pilot

Enterprise

Discuss multi-brand requirements and future deployment options.

Talk to us

Multi-brand requirements · individually scoped

  • Everything in Regulated
  • Multiple tenants with isolated keys and row policies
  • Jurisdiction and approval-workflow requirements review
  • Private edge deployment: future option, outside this beta
  • Discuss support for your DPIA review
  • Contract terms subject to agreement
Contact sales

Pilot and production terms are confirmed after a traffic, jurisdiction and evidence review. We do not publish placeholder prices as if they were agreed commercials.

Questions

The ones that come up first.

Why is pricing based on requests rather than visitors?
The proposed operational reporting unit is measured requests rather than a billable visitor identity. Operational output is aggregate; separate security processing has its own data and retention rules. Pilot commercial terms still require agreement.
Does this replace our existing analytics?
It replaces the part that stopped working. Conventional analytics only sees visitors who accept the banner. INSIGHTS measures those visitors and, on the anonymous statistics lane, the ones who never answered, as aggregates with no cookie or identifier. If you need individual-level behaviour, funnels tied to a person or ad attribution, keep a consented tool for the consenting minority and use INSIGHTS for the whole audience.
Do we still need a consent banner?
The current operational beta requires an analytics consent signal from your consent-management integration. Rejected or unknown consent is security-only. The absence of operational SDK cookies does not itself establish a consent exemption or legal basis. Review your notice and obligations with your advisers; this website is not legal advice.
What happens to the data if we leave?
The applicable terms and processing lane determine retention and deletion. Operational reports use aggregates, but the separate security lane can retain raw signals under its own short limit. Review closure, key-destruction and purge evidence for the relevant records. A signed evidence pack alone does not prove independent physical absence or that a deadline was met.
Can we self-host or run it in our own cloud?
Private deployment and customer-account edge hosting are future requirements to discuss, not available options in the Closed Operational Beta.