Security
Boundaries that fail closed.
Evidence you can inspect.
What we protect, how every administrative change is recorded, why public resolution stays free of personal data, and an honest statement of where compliance evidence stands today.
What we protect
Customer configuration, journey data, and operational evidence live inside strict boundaries. Tenant and environment scope is enforced per request, for the control plane and for public link resolution alike.
- 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.
Cryptographic audit trail
Material administrative actions produce ordered, tamper-evident records in a cryptographic, append-only Merkle-ledger audit trail. Records are hash-chained, so altering history breaks chain verification instead of rewriting it quietly.
Control evidence is tied to a specific environment and observation time. A policy or test result is never presented as production runtime proof.
Zero-PII execution model
Public link resolution runs at the edge without collecting install-time personal data. The resolver sees only what a routing decision requires.
- No raw IP storage and no full user-agent fingerprint storage.
- Deterministic deferred matching by default; probabilistic matching requires explicit tenant opt-in.
- Click context is short-lived and expires aggressively.
- SDK responses expose no tenant identifiers.
Hashing is not a privacy escape hatch. Hashed identifiers can still be tracking identifiers when linkable.
Infrastructure posture
LocusVia runs on Cloudflare’s edge network. Public requests execute in isolated runtimes, and each customer’s published link estate can be served from its own dedicated Worker.
Invalid scope, disabled configuration, and unavailable destinations fail closed. Only public, immutable, and safely derived responses are cached; tenant-sensitive data is never shared across authorization boundaries.
Compliance status
LocusVia provides a scoped, evidence-backed customer security evidence pack covering authentication, tenant/environment isolation, SDK and Admin API security, webhook signature integrity, audit logging, backup/restore, dependency management, and retention.
LocusVia holds no SOC 2, ISO/IEC 27001, CSA STAR, or PCI DSS certificate or attestation report today. Design and operating evidence is documented in compliance registers; operating effectiveness across a dated period is not yet established, and no readiness work is presented as certified, audited, attested, or compliant.
Subprocessors
Available on request. The current subprocessor list is not published on this page; contact LocusVia for the current security package, subprocessors, and environment-specific evidence as part of procurement review.
Keep reading, or start shipping
The security model and system documentation cover the same controls in operational detail.