Data & isolation
How LocusVia separates tenant data, environment state, operational caches, and high-volume telemetry.
Isolation model#
Tenant scoped
Authoritative records are accessed only within the authenticated tenant.
Environment scoped
Development, staging, and production state remain independently addressable.
Fail closed
Missing or mismatched scope prevents reads, writes, and public resolution.
Least data
Edge resolution uses only the fields required to make a routing decision.
Storage responsibilities#
Authoritative configuration and audit records use durable transactional storage. Derived association artifacts and short-lived lookup results use caches. High-volume product telemetry uses an append-oriented analytics plane.
Cached data never replaces the authoritative tenant and environment checks required for a routing decision.
Retention and deletion#
Retention depends on data purpose and product contract. Expired operational and journey data is removed on a bounded schedule; customer configuration remains until changed or deleted by an authorized administrator.
Note
Contact support for a tenant-specific retention or deletion request.