[ security ]

Security posture, posted publicly.

We document what we do for security in the open so your team can assess us without a meeting. This page is the canonical reference — if it contradicts something a salesperson says, this page wins.

[ what we do today ]

Defaults that shouldn't need to be defaults.

Encryption at rest and in transit

TLS 1.2+ for every request to quilldocs.ai and our API. AES-256 for stored data. Customer-managed KMS keys are an enterprise option for workspaces that need them.

Per-workspace data isolation

Each Quill deployment binds to exactly one workspace viaQUILL_WORKSPACE_ID. Cross-tenant collisions fail closed at startup, not silently at runtime — a missing binding is a deploy bug we want loud.

Audit trails on every action

Pipeline runs, document edits, role changes, publishes — every action is logged with actor, target, and timestamp. Streamable to your SIEM. Retention configurable up to seven years on enterprise plans.

Minimal retention by default

Customer repository contents are read for generation and kept only as long as they back active documents. Soft-delete with a 30-day recovery window; purge after, unless legal retention applies.

[ compliance ]

Where we stand.

We publish status honestly. "In progress" means the audit is actively scheduled. "Available" means we'll send the report under NDA. "On request" means it exists; ask and we'll send.

soc 2
Type II
in progress · target Q4
iso 27001
planned
after SOC 2
gdpr
DPA on request
EU sub-processor list
hipaa
BAA available
enterprise plans
[ authentication & access ]

Sign in the way the rest of your stack already does.

SAML SSO

Okta, Azure AD, Google, OneLogin, JumpCloud, anything SAML 2.0. Configurable session lifetimes. Just-in-time provisioning. Available on enterprise plans.

Role-based access

Per-workspace, per-document, per-action roles. Reviewers, publishers, viewers, admins. Optional required reviewers and approval chains for regulated environments.

Session policies

IP allowlists. Configurable timeouts. Forced re-auth on destructive actions. Cookie security best practices (HttpOnly, Secure, SameSite). Industry-standard defaults.

[ reporting vulnerabilities ]

Found something? Tell us.

We treat responsible disclosure seriously. We don't run a formal bug bounty yet (we're sizing one — Trigger: when traffic warrants), but we do credit reporters publicly with permission and we always say thank you, in real ways.

How to reach us

Email security@quilldocs.ai with details. PGP available on request. We acknowledge within 24 hours and commit to initial triage within 72.

What's in scope

quilldocs.ai, the Quill portal, the public API surface as it ships. Out of scope: third-party integrations (report to them), social engineering, and physical attacks against our office (we don't have one).

Have a question we didn't answer?

We answer security questionnaires quickly. Most teams finish procurement review without a call — what you see here is what we send.