Newcomb — Security Posture

How we handle your documents.

Newcomb reads privileged, regulated material, so the security model is part of the product, not an afterthought. This page describes how Newcomb is built to handle your documents and what the pilot commits to. It changes when the facts do.

Last updated June 10, 2026.

Exhibit — Data flow
  1. 01

    Your documents

    Vendor terms, your policies, customer contracts

  2. 02

    Encrypted upload

    TLS in transit

  3. 03

    Tenant-isolated store

    Postgres row-level security · encrypted at rest

  4. 04

    Analysis

    Extract & compare · LLMs under no-train, zero-retention terms

  5. 05

    Signed memo

    Hash-chained · immutable · sourced to quoted clauses

Nothing leaves your tenant boundary except to the listed subprocessors, under terms that prohibit training on and retaining your content.

EXHIBIT

01

Identity & access

There are no passwords to steal. You sign in with your company’s SSO (SAML or OIDC) or a single-use magic link that expires in fifteen minutes. Multi-factor authentication is supported, and signing a memo requires a fresh step-up — your signature attests to the memo, so we confirm it’s you before it is recorded.

Sessions are short and revocable. “Sign out everywhere” invalidates every active session at once.

EXHIBIT

02

Tenant isolation

Every customer’s data lives behind Postgres row-level security. Isolation is enforced in the database, not just the application: a query carrying one tenant’s identity cannot read another tenant’s rows even if application code is wrong. An automated test suite proves zero cross-tenant reads on every tenant-scoped table before each release.

EXHIBIT

03

Your content is never training data

We do not train or fine-tune any model on your documents, your memos, or your edits. Analysis runs against enterprise large-language-model providers under terms that prohibit training on the content we send, and we use zero-retention processing where the provider offers it. Our subprocessors are listed in Exhibit 08, and the list changes only with notice.

EXHIBIT

04

The signed record is immutable

Newcomb is built so that a signed memo is immutable. When counsel signs a memo, that version is frozen: each signed version is hash-chained to the one before it, so later tampering is detectable, and signed versions are protected from modification. Liveness never edits a signed memo — a changed source produces a new proposed version, and the superseded version stays on the record exactly as it was signed.

EXHIBIT

05

Every conclusion is sourced

Every conclusion Newcomb draws is tied to a quoted, anchored clause; by design, a conclusion that can’t be traced to its source isn’t shown. Anything the analysis can’t classify with confidence is routed to counsel for review rather than passed silently. The system drafts; a person decides.

EXHIBIT

06

Append-only audit log

Sign-ins, intakes, source changes, and administrative actions — and, as signing and step-up land, those events too — are written to an append-only audit log: who did what, to which memo, and when. Administrators can export the log as CSV for their own records.

EXHIBIT

07

Encryption

All traffic is encrypted in transit with TLS. Data at rest — documents, parsed text, embeddings, and the database — is encrypted using our infrastructure provider’s managed encryption.

EXHIBIT

08

Subprocessors & hosting

Newcomb runs on managed cloud infrastructure in the United States. Analysis uses enterprise large-language-model providers under no-training terms, with zero-retention processing where the provider offers it. The current subprocessor list — infrastructure, model providers, and email delivery — is provided to design partners with the pilot agreement and updated with notice.

EXHIBIT

09

Deletion & retention

On request, we delete your data: the original documents, their parsed text, embeddings, every derived artifact, and exports. Deletion is destructive and is confirmed by naming exactly what is erased. Backups expire on a documented schedule, after which deleted content is unrecoverable.

During the pilot, all of this is governed by a written agreement signed before any production data is uploaded.

Reporting & questions

Design partners receive the full subprocessor list, the data-processing agreement, and a deletion runbook with the pilot agreement. To report a vulnerability or ask a security question, email security@newcomb.app.