Built for documents that carry consequences.

When an agreement is fully signed, the document is flattened with every signature and value in place, then hashed with SHA-256. That fingerprint is stored on the certificate of completion, so any later modification to the file is detectable — and anyone holding the file can check it themselves at /verify, without an account, with the document hashed in their own browser rather than uploaded. Field placement is mapped precisely onto each page's real coordinate space, including rotated and cropped pages, and that mapping is protected by an automated regression test.

Agreement activity can include: sent, delivered, viewed, signed, declined, reminded, bounced, and executed. Recorded events carry a timestamp and, where the request exposes it, the originating IP address. The same trail appears in your dashboard and is printed into the sealed certificate.

Document content can be sent to Anthropic for field detection during preparation, drafting, pre-send review, search and extraction after completion. Some processing runs automatically as part of those workflows. Documents and signed PDFs are scoped to your workspace. Provider retention and training terms have not yet been verified for publication; this page does not promise a specific AI retention or training policy.

Every workspace's data is isolated at the database level with row-level security policies: documents, envelopes, contacts, and records are scoped to the workspace that owns them, and every query is filtered by that scope before it returns a row. Signer-facing links are unguessable per-signer tokens; public endpoints are rate-limited.

Accounts sign in with email and password managed by Supabase Auth. You can enable two-step verification with an authenticator app in Account security and sign out all devices. Once enabled, an authenticator code is required to access your workspace after signing in. Password entry includes guidance against commonly guessed passwords; provider security settings require ongoing operator verification. API access uses per-workspace keys that are shown once and stored only as hashes; revoke exposed integration keys separately.