Trust, data boundaries, and conservative scan intelligence.
Vizuem separates operational scan data from anonymized platform intelligence. Evidence and exports stay access-controlled. Benchmarks are threshold-gated and presented as directional scan context only.
- Operational scan dataWorkspace-scoped
- Customer data saleNo
- BenchmarksAnonymized aggregation
- AI training on customer OCDNo
- Default retention18mo / 5yr / 90d
Formal terms depend on your agreement. This page summarizes the product trust posture.
Evidence, exports, and reports require authenticated access and plan authorization.
Operational scan data and anonymized platform intelligence are treated as separate classes.
Exports are gated, usage-tracked, and designed for customer-controlled workflows.
Reports provide informational scan context while final decisions remain with your team and advisors.
Operational scan data is separate from anonymized platform intelligence.
Workspace Operational Data stays workspace-scoped. Platform Intelligence Data is anonymized and aggregated before it can support benchmark context.
Operational scan data and platform intelligence stay separate.
Vizuem separates customer workspace data from anonymized aggregate intelligence. Full evidence, exports, and reports remain access-controlled; benchmark context is threshold-gated and non-attributable.
Operational Scan Data
Customer-scoped data generated to run scans, review evidence, and produce reports.
- Includes scan targets, configured scope, evidence, telemetry, Digital Risk signals, assets, and exports.
- Access-controlled within the customer workspace.
- Used to provide the requested scan, workspace, and reporting functionality.
- Retention-limited according to product defaults or written agreement.
Platform Intelligence Data
Aggregated signal data used to support scoring calibration and benchmark context when thresholds are met.
- Excludes URLs, domains, page paths, query strings, HTML, scan IDs, user IDs, and workspace identifiers.
- Used only in aggregate and designed to be non-attributable.
- Benchmark displays should remain hidden or directional until comparable sample size is sufficient.
- Presented as directional benchmark context only; final decisions remain with your team and advisors.
Workspace Operational Data
Data required to scan, review evidence, generate reports, and support customer-controlled audit workflows.
- • Scan targets and configured scope
- • Evidence, severity, and implementation context
- • Scan telemetry, Digital Risk, assets, reports, and exports
- • Workspace configuration and access-controlled activity
Platform Intelligence Data
Aggregated, anonymized signal data used to support scoring calibration and benchmark context when sample thresholds are met.
- • Aggregated rule trigger rates
- • Severity distributions and score bands
- • Segment-level benchmark snapshots when eligible
- • No URLs, page paths, HTML, scan IDs, or workspace identifiers
Benchmarks are context only when sample size supports them.
Benchmarks should remain hidden or directional until enough comparable data exists. They provide directional scan context only.
Public Benchmark Display
Benchmark values are displayed only after enough anonymized aggregate scoring data exists. This protects privacy, reduces small-sample noise, and avoids unsupported comparison claims.
Current sample size is below the minimum publication threshold. Public benchmark values will appear automatically once enough anonymized, eligible data is available.
From scan to report to anonymized aggregation.
Customer-facing scan output stays in the workspace. Any platform-level benchmark signal must be aggregated and anonymized.
Public previews are intentionally scope-limited and evidence-hidden. Evidence access and exports require authenticated access.
Retention defaults balance auditability with data minimization.
Defaults are designed for operational usefulness without keeping sensitive scan data indefinitely.
Customer operational scan data is not used to train public or general-purpose AI models.
AI-assisted features, if used, should remain bounded by product controls and customer-safe data handling.
Vizuem does not use customer URLs, page content, evidence, reports, or exports to train public or general-purpose AI models.
Customers control scan scope, access, and exports.
Trust posture is not only legal text. It has to show up in product behavior.
- Scope: Customers define which URLs are scanned and how deep crawling goes.
- Standards: Scan settings can align the run with WCAG-informed options and related readiness signals.
- Isolation: Operational data remains access-controlled within the customer workspace.
- Exports: Reports and logs are gated, usage-tracked, and customer-initiated.
Fast answers for security review and procurement.
Use this as the short version before reviewing formal terms.
Do you sell customer scan data?
No. Customer operational scan data is not sold and is not shared across customer accounts.
What is included in platform intelligence data?
Anonymized, aggregated metrics such as rule frequency, severity distributions, score bands, and eligible benchmark snapshots. It excludes URLs, HTML, page paths, identifiers, and customer-unique content.
Do you train AI on customer operational scan data?
Vizuem does not train public or general-purpose AI models on customer operational scan data.
Can retention be customized?
Defaults are designed for auditability and data minimization. Enterprise retention may vary by written agreement.
What does a report provide?
Reports provide WCAG-informed scan intelligence, evidence summaries, and informational scan context. Final decisions remain with your team and advisors.
Run a public preview first. Evidence and exports remain gated behind access.