How we keep your unannounced title unannounced

Every game studio has the same first question about AI tooling, and it is the right question: this thing hears our meetings and reads our design docs, so where does that data go?

Having spent two decades shipping under NDA at Sony Santa Monica, I know what a leaked codename costs. Marketing beats planned around a reveal. Platform deals with confidentiality clauses. The morale hit when a surprise gets spoiled. So when we built Aligned, the data model was designed like every customer is working on an unannounced title, because many of them are.

What follows is exactly how we handle it, in the same plain English we use on our security page.

Your data never trains anything

Your meetings, docs, and roadmaps are never used to train AI models. Not ours, and by contract, not our AI providers' either. We use business-tier APIs where the provider is contractually prohibited from training on submitted data. Model training is the fear we hear most, so it is the commitment we make first.

There is also a structural reason to believe it, beyond the promise: we make money one way, subscriptions. Your data is not our product. There is no version of our business where leaking or mining it helps us.

Walls between every team

Every workspace is isolated with Row-Level Security at the database layer. That is not an application-level filter that a bug can slip past; the database itself refuses to return another tenant's rows. Your codename cannot appear in someone else's account because the query that would fetch it is impossible to execute.

Around that core: OAuth tokens are wrapped in dual-layer AES-256-GCM encryption, production access is MFA-gated, and every privileged action lands in an append-only audit log with hash-chain integrity verification, which means tampering with history is detectable. If your security reviewer wants the full list, from our SOC 2 audit status to the subprocessor table with DPA links, it is all public on the security page.

Delete means delete

Self-service account deletion removes your content from our systems. No support ticket, no exit interview, no retention games. If you leave, your unannounced title leaves with you.

And if it can never leave your walls

Some studios have platform agreements or publisher requirements that mean no third-party cloud, period. For those teams, Enterprise includes dedicated deployment: Aligned running in your own cloud, on your infrastructure, with your keys. Talk to us if that is your situation.

Why we publish this

The honest answer: because a studio once walked away from a deployment conversation over data concerns, and they were right to ask. Security you cannot inspect is just vibes. So the commitments are public, the subprocessors are listed, the DPA is available, and the architecture is explained. Trust the incentives, verify the controls.

Your reveal should come from your trailer, not from your tooling.