CASCADE DYNAMICS
Request documents
ALL SYSTEMS OPERATIONAL · BETA

Security and privacy, in plain view.

Everything your security team needs to review us, in one place, without a call: what we protect, what we never collect, and what is not in place yet. Where a control is missing we say so and show when it is planned — an honest gap is easier to review than a vague claim.

FOR REVIEWERS · START HERE
THE ARCHITECTURE ARGUMENT

The safest data is the data we never hold.

Most vendors answer a security review by describing how well they guard your data. We would rather reduce what there is to guard. Three properties do most of the work.

CONTROLS
Items marked PLANNED have a committed date and are not in place today. We would rather you find them here than in a questionnaire.
All systems operational
public status page ships at GA · hosted off our own infrastructure
INCIDENT HISTORY
No customer-impacting incidents to report during the beta. When one occurs, the post-mortem — including what kept working — is published here. Public status history begins at general availability.
SUBPROCESSORS
Air-gapped deployments use none of these. Nothing leaves your perimeter, so there is nothing to subprocess.
DISCLOSURE & CONTACT

We operate a safe-harbour policy. Report a vulnerability in good faith and we will not pursue legal action, will respond within one business day, and will credit you unless you would rather we did not.

PGP key and security.txt published at /.well-known/security.txt

THE UNUSUAL PART

You do not have to trust this page.

Every claim on it about coordination — no double-booking, a signed history that hasn’t been edited — is checkable by you, on your own machine, against a key we published before the run existed. A trust centre that asks for trust is a weaker document than one that hands you the evidence.

Verify a real run yourself → Read the verification spec Reference verifier & spec