Trust & Security
Your customers’ data should not depend on someone remembering to add a WHERE clause.
Event Horizon is multi-tenant by design. That means tenant isolation is part of the system’s execution path, and we test it as an adversary would.
The problem
Multi-tenant analytics creates a dangerous failure mode.
When one platform serves many customers, a mistake in a query can become a data isolation problem.
We don’t treat tenant isolation as a documentation rule. We enforce it before data is returned.
The boundary
Every read must have a tenant.
Every warehouse read passes through a fail-closed tenant checkpoint. A query without valid tenant context does not run.
The database adds a second policy layer, and data is physically ordered by tenant to reduce unnecessary reads.
We attack our own boundary
Security claims are easy. Tests are harder.
We red-team the live system for cross-tenant access. The security posture currently reports:
Least privilege
Keep the blast radius small.
Warehouse access uses narrowly scoped database identities. Different identities handle different responsibilities, and permissions are explicitly restricted.
Privacy & data handling
Know what happens to your data.
- HTTPS/TLS for traffic
- Encrypted off-site backups
- Backup freshness monitoring
- Data export on request and on exit
- Published DPA
- Subprocessor information on request
What we don’t have
We’d rather tell you now.
Due diligence
Want to review the evidence?
Request the security package:
- Adversarial security-test report
- Scale report
- CAIQ questionnaire
- DPA
Security posture reviewed 2026-09-12 · support@eventhorizondata.com