Security at Arbor

Every record is scoped to your organization. Access is enforced in the database with PostgreSQL Row-Level Security, not just in application code, and the organization id is carried in a signed session token. A query can only ever return rows belonging to the caller's organization — cross-tenant reads return nothing.

All traffic is encrypted in transit over TLS. Data at rest — including your database and backups — is encrypted by our infrastructure provider. Secrets and tokens are compared in constant time to resist timing attacks.

Every privileged action is written to an append-only audit log that administrators can review and export. Application errors and performance are tracked with request-correlated, structured logs and error monitoring. Live service health is published on our status page.

The ingestion pipeline is idempotent and fault-tolerant — retries with backoff, a circuit breaker, and a dead-letter queue keep a single bad source from affecting the rest. The platform is load-tested and uses keyset pagination so it stays responsive as your tracked universe grows.

You can export or permanently delete your data at any time from Settings. We act as a processor for the data you put into Arbor; how we handle it is detailed in our Privacy Policy.

Arbor is built to SOC 2 control objectives — encryption, access control, audit logging, change management, and monitoring are all in place. A formal SOC 2 Type II examination and independent penetration test are on our roadmap; enterprise customers can request our current security documentation and questionnaire responses.

We welcome reports from security researchers. If you believe you have found a vulnerability, email privacy@arbor.example with the details and steps to reproduce. Please give us a reasonable window to remediate before any public disclosure.