Security & trust
How we build,
told straight.
CommandCenter holds your assessments, your evidence, and your program's history. This page says what actually protects it today, what we're still building, and what we will not say until it is true. No marketing language stands in for an audit.
What protects your data today
Built in, not bolted on
Every table is scoped to your organization. CommandCenter enforces tenant isolation at the database layer with row-level security — not just in application code. Your data is scoped to your organization by the database itself, on every read and every write.
You sign in with a one-time code, never a stored password. Sign-in codes are single-use and short-lived; we never hold a plaintext password to lose. Every request after sign-in is re-checked against a live session — there is no standing access that outlives your login.
Invitations are single-use and tokened, never a shared link. When your organization adds a director or department lead, they join through a one-time invite token tied to their own account — not a link anyone who finds it can use.
The evidence you upload sits behind the same access control as everything else. Documents, procedures, and proof files are stored in access-controlled storage, gated by the same per-tenant policies as the rest of the platform — never a public bucket.
Before launch, the site itself stays out of search entirely. While CommandCenter is in private launch, every page outside the small public set carries a no-index instruction — nothing here is meant to be discovered by a crawler before it is meant to be discovered by you.
Scheduled system jobs authenticate with a shared secret where that gate is wired. Background jobs that touch your data run behind a secret credential, not an open endpoint. We say “where wired” deliberately — see below.
What's still in progress
The honest list
We would rather tell you what is not finished than let a clean page imply it is.
- We are running a formal security program (SOC 2) across the platform. Several of its controls are already built and running; a number are still open work, in progress right now — not yet finished, and not yet claimed as finished.
- The shared secret that gates our background jobs is not yet on every endpoint the same way — we are standardizing it platform-wide rather than calling it done early.
- A couple of remaining checks in our security program need a person to sign in to a hosting dashboard directly and confirm a setting by hand — those have not happened yet.
- Formal data-processing agreements with our clients and the vendors we rely on are being finalized — a signature step, not an engineering one, and not yet executed.
What we do not claim
No certificate we don't hold
We do not claim SOC 2 certification, attestation, or compliance on this page, and we will not, until an independent report exists and our founder has signed off on saying so. Building the controls a security program requires is real, ongoing work — attesting to them is a separate, formal step that has not happened yet.
If you are evaluating CommandCenter for your own compliance program and need more than this page — the specific controls in place, our current gaps, or a signed agreement — request onboarding and ask; a person reads every request.