Trust Center

How we operate, in writing.

Cap tables, SAFEs, partner notes, financial models — the data inside Arx is among the most sensitive a company will ever own. Below are our published policies on how we protect it, how we operate the platform, and what we expect of you in return. Each document is current, dated, and reachable from one place.

I. Security & engineering practice
II. Platform & supply chain
III. Use of the service
The short version

One stack. Documented.

If you want the long answers, every policy above is read in detail. If you want the short version, here it is.

  • Encrypted in transit and at rest.TLS 1.3 on every connection. Database and object storage encryption provided by Supabase. OAuth tokens encrypted with a separate AES-256-GCM key.
  • Row-level isolation.Every database query is gated by workspace membership. No cross-tenant reads possible at the data layer.
  • No training on your data.Your workspace is read at runtime by the AI; never used to update foundation models.
  • Audit log on every mutation.Founder activity log + admin platform audit log. Every write is recorded with actor and time.
  • Two-factor authentication.TOTP MFA available on every account; enforceable for the whole workspace.
  • Subprocessor change notice.30-day advance notice before adding or replacing a subprocessor that processes customer data.
  • Daily backups, 30-day retention.Point-in-time recovery on the primary database; object storage versioned for 30 days.
  • Public incident history.Every customer-facing incident is recorded on status.arx.so with a written post-mortem.