CONTROLLED TRANSPARENCY

Website analytics and diagnostic workflow boundaries.

VXS separates website measurement from diagnostic-content review. Traffic analytics, page interactions, and diagnostic submissions do not share the same consent basis or retention scope.

Website analytics

Google Analytics 4 is loaded only after explicit consent. If you choose Essential Only, analytics remains disabled and no GA4 tag is loaded from this site.

What analytics is for

Analytics is used only to understand aggregate website performance, such as page visits, navigation flow, and general content engagement. It is not used to profile diagnostic submissions.

Diagnostic workflow boundary

The Formula Diagnostic Engine uses separate submission-level consents for manual review, anonymized aggregate pattern retention, and optional public case reference. Those choices are handled inside the FDE workflow.

Cross-entity boundary

Raw diagnostic submissions are not routed into any other entity's sales or client-service workflows. VXS maintains its own protocol, identity, and data-handling boundary.

Operational principles

Minimal collection

VXS is designed to avoid unnecessary collection. Early-stage diagnostic workflows ask for ranges, categories, and process context rather than exact proprietary formulations wherever possible.

Delayed public use

Any public reference to pattern-level learnings requires anonymization, aggregation, and delay. Identifying details require a separate preview or approval path.