Updated July 15, 2026

Security

Wardwell is a managed work surface that reads the sources you connect and prepares context, briefs, and receipts. This page describes how we limit what the service can reach, how small the blast radius stays when something goes wrong, how you cut off access, and what you keep when you leave. It reflects what the running system enforces today, not a roadmap.

Access and tenant isolation

Every customer's data lives behind a per-tenant boundary enforced in the database with Postgres row-level security, not only in application code. The service runs under a restricted database role that cannot bypass those tenant policies, so a query is constrained to a single tenant even if application logic is wrong. Sessions are scoped to one tenant at a time, and a member of one Space cannot read another Space's data.

Counterparty content: comes to rest nowhere

When a connected channel is set to zero-persistence, messages from outside parties are processed in memory and never written to storage. The attention pointer we keep — a permalink, a timestamp, and the thread it belongs to — carries no message body, including on the notification path. This is enforced in code and proven by a standing test suite: a marked message driven through the real ingestion path is absent from every database table and from the bytes sent to Slack. A grant can never quietly widen a zero-persistence channel; only an explicit mode change can.

Append-only receipts

Actions, decisions, corrections, and their receipts are recorded to append-only ledgers. Entries are added, not edited or deleted in place, so the audit trail of what the service did on your behalf cannot be silently rewritten.

Blast radius and the kill switch

The kill switch is your own disconnect. Disconnecting a source in Wardwell is local and irreversible: the stored provider credential is dropped and the service can no longer reach that source. You do not need to contact us, and you do not depend on us to act. Access is scoped narrowly to begin with, so the reach available to cut off is small.

Encryption and backups

Sessions and traffic to the service are encrypted in transit. Stored provider credentials are encrypted, and database backups are encrypted before they leave the host. No system can guarantee absolute security.

Subprocessors

Wardwell relies on a short list of vendors to operate. We publish the current list, including what each one handles, on the subprocessors page.

Data processing agreement

A Data Processing Agreement is available on request. Email [email protected] and we will send the current version.

Reporting a concern

If you find a security issue or have a question about our posture, email [email protected]. Wardwell is in a limited pilot; this posture will continue to harden as the service matures.