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 operational dataNo
- 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 for internal analytics, scoring calibration, and service improvement.
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; platform intelligence is aggregated, anonymized, and designed to be 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 internally for product analytics, scoring calibration, service improvement, and aggregate intelligence.
- 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.
- May support internal benchmark snapshots, percentile analysis, and segment-level intelligence.
- Designed for internal aggregate analysis rather than customer-specific comparison displays.
From scan to report to anonymized aggregation.
Customer-facing scan output stays in the workspace. Platform-level intelligence is aggregated and anonymized for internal analysis.
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.
Current product coverage is explicit.
This matrix distinguishes implemented scan context from future work so product and marketing language does not exceed current capability.
| Profile or context | Status | Current product scope |
|---|---|---|
| WCAG 2.0 / 2.1 / 2.2 | Implemented | Selectable WCAG version and conformance-level context for scan mapping, scoring, Evidence references, and reporting. |
| Section 508 Context | Implemented | Optional supporting standards context where mapped requirements apply. |
| ADA Context | Implemented | Optional web-context mapping used as informational scan and report context. |
| AODA Web Context | Implemented | Optional Ontario web context using the applicable WCAG 2.0 Level AA mapping, excluding WCAG 2.0 success criteria 1.2.4 and 1.2.5. |
| EU Accessibility / EN 301 549 Context | Implemented | Optional European accessibility context using EN 301 549 and EAA-related mappings where applicable. |
| Accessible Canada Act ICT Context | Planned | Future-effective Canadian federal ICT context. Registry foundation is prepared, but this context is not currently selectable, scored, or included in customer reports. |
Primary-source references are provided for context and independent review. External sources do not endorse Vizuem, and formal applicability depends on the customer's circumstances.
A limited set of providers supports core platform operations.
These disclosures identify current production providers, the functions they support, and the related data categories. Provider references are supplied for independent review and do not imply endorsement, partnership, or that provider certifications are held by Vizuem.
Cloudflare
- Operational purpose
- Application hosting, edge delivery, routing, scan queues, browser execution, and operational observability.
- Data categories
- Application requests, operational metadata, queued scan-work identifiers, and data required to execute requested platform functions.
Supabase
- Operational purpose
- Authentication, workspace database services, report storage, signed downloads, and retention deletion workflows.
- Data categories
- Account, workspace, scan, Evidence, settings, entitlement, and stored-report data required to provide the service.
Stripe
- Operational purpose
- Subscription checkout, one-time purchases, billing administration, and the customer billing portal.
- Data categories
- Customer and transaction information required to process and administer billing.
Postmark
- Operational purpose
- Transactional delivery for contact messages and organization invitations.
- Data categories
- Recipient address and message content required to deliver the requested transactional email.
Provider roles may change as the service evolves. Material updates are reflected in this disclosure. Questions about provider use or data handling can be directed to the privacy team.
Public vendor-review materials in one place.
Use these materials for initial security, privacy, accessibility, contracting, and procurement review. Controlled-request materials are confirmed separately when applicable.
Operational scan data, platform intelligence, sharing, and retention.
Service providers used for hosting, data, billing, email, and rate-limiting functions.
Contracting exhibit covering data classes, permitted use, retention, and access controls.
Sanitized example of the structure and customer-facing boundaries of an Executive Report.
Current accessibility approach, product preferences, scope boundaries, and feedback channel.
Standard service, subscription, acceptable-use, output-limitation, and contractual terms.
Subscription, add-on, duplicate-charge, billing-error, and service-failure review terms.
For questionnaires, contracting coordination, W-9 requests, insurance information when applicable, or other vendor-review materials, contact the sales team. Availability is confirmed during the request process.
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.