Trust & Security

Security, and what we’re honest about.

Event Horizon Data runs many of your end-clients in one platform, each seeing only their own data. This is how that isolation is enforced and tested, and a plain account of the controls we don’t yet have. We’d rather you read the limits here than discover them later.

Tenant isolation

One enforced boundary, tested from the outside.

Every read of your data passes through a single, fail-closed checkpoint that refuses any query reaching outside the authenticated client. Beneath it, the database engine applies a per-tenant policy as a second layer, and data is physically ordered by tenant, so one client’s query only ever touches its own storage, rather than filtering others’ out after the fact.

  • Adversarially red-teamed against the live system, probing for a cross-tenant read from every angle. None was achievable.
  • Covered by tests that assert refusal, not just that the happy path works.
  • The natural-language assistant was held to the same bar, red-teamed with a second tenant holding values the first could never see. No cross-tenant match was achievable, and any column can be excluded from matching, which erases what was already indexed.

Least privilege

A small blast radius, verified.

The application reaches the warehouse through narrowly-scoped database identities (read-only, ingest-only, and owner), each stripped of the ability to read external sources, reach the engine’s internal tables, or run destructive statements. We confirmed those denials live: every such attempt is refused by the engine.

Data handling & privacy

Encryption, backups, and your data on your terms.

  • All traffic over HTTPS/TLS; off-site backups encrypted at rest, with backup freshness monitored, a missing backup raises an alert, not a silent gap.
  • Your analytics data is exportable on request and on exit; an acceptable-use policy keeps payment-card and special-category data off the platform.
  • A Data Processing Agreement (GDPR Art. 28) is published; a current sub-processor list is available on request. Hosted in the United States.

Availability

Monitored, with the status public.

Every service is monitored by an independent uptime console with a public status page, and failures raise alerts rather than being discovered after the fact. Deploys are gated on a health check that round-trips the whole stack before traffic is switched.

Verified, not asserted, last tested 2026-09-12

0
cross-tenant reads achievable under adversarial test
Denied
every external-source, system, and destructive attempt, live
Fail-closed
a missing tenant context errors the query, never returns all rows
Closed
every database and infrastructure port to the public internet; only HTTP/HTTPS answer

What we’re honest about

The controls we don’t have yet.

No SOC 2 / ISO
Evaluated and deferred until demand justifies the cost. In its place: an interim assurance package: this posture, the DPA, the adversarial-test report, a scale report, and a pre-filled security questionnaire.
Small team
Operated by a small team today, a continuity risk any buyer should weigh. Mitigated by automated backups, export-on-exit, and a written continuity plan.
Boundary is code
The effective tenant boundary is enforced in the application layer; the database policy strengthens it but is a dependent second layer, not an independent engine-level guarantee. Stated plainly because a serious reviewer will find it anyway.

For your security review

Request the full package.

The adversarial security-test report, the one-page scale report, the pre-filled CAIQ questionnaire, and the signed DPA, shared for your due diligence.

Security posture reviewed 2026-09-12 · support@eventhorizondata.com