/00 Security
Your architecture is sensitive. Arq treats it that way.
What follows describes how the product works today. Controls that are planned are marked as such.
/01 Controls in the product
Tenant isolation
Every read and write goes through one authorization gate scoped to your organization and workspace. Anything outside your scope is answered as not found, and cross-tenant access is covered by negative tests.
Changes on the record
Model content changes only through validated changesets, each with an author, an origin (person, agent, import) and a revision. Sign-ins, billing, sharing, tokens and hub imports are written to an audit log that organization owners and admins can filter and export.
Keys and tokens
Your own AI provider keys are encrypted with AES-256-GCM before they are stored. MCP tokens and share-link tokens are shown once and stored only as SHA-256 hashes, so they can be revoked but never read back.
Sign-in
Passwords of at least 12 characters, verified email before first sign-in, rate-limited sign-in and reset, and HTTP-only session cookies. Social sign-in is offered only where configured.
AI requests
Arq does not train models on your data. A hosted drafting request sends the brief and the relevant part of the model to the configured provider for that request only. Hosted AI is metered and stops at your credit.
Coding agents
Agents connected over MCP can read and propose. Proposals wait in the model's inbox until a person accepts them; agents cannot change a model on their own.
Web hardening
A strict, per-request nonce content security policy, no third-party scripts or trackers, frame embedding refused, same-origin checks on every change, and an XML importer that refuses DTDs and entities and enforces size and depth limits.
Dependencies
Every direct dependency is registered with its licence and origin, checked in CI against a licence allowlist and a provenance policy that excludes software maintained in sanctioned or adversary jurisdictions. Secrets scanning runs on every change.
/02 Where your data lives
Models, views and accounts are stored in Postgres hosted by Neon, which encrypts data at rest, and served over TLS. Arq keeps no copy of your data outside these services. The demo runs entirely in your browser and stores nothing on our servers except anonymous usage counters.
| Subprocessor | Purpose | Location |
|---|---|---|
| Vercel | Application hosting and delivery | United States |
| Neon | Postgres database | United States |
| Stripe | Payments and billing | United States |
| AI model provider (Anthropic or OpenAI) | Hosted drafting requests, only when you use the hosted credit | United States |
| Email delivery provider | Account and invitation email | United States |
On the roadmap A choice of US or EU data residency for organizations, single sign-on and SCIM, pushing the audit log to your SIEM, and SOC 2 (Type I, then Type II).
/03 Reporting a vulnerability
Contact Lattix through lattix.io with the details and steps to reproduce. Please give us a reasonable time to fix the issue before disclosing it. We do not pursue good-faith research that avoids privacy violations, data destruction and service disruption.
Legal terms, privacy and data processing are in Legal.