How Signatura protects your documents, your signatures, and your audit trail.
All client-server traffic is encrypted with TLS 1.3. Documents and database records are encrypted at rest with AES-256. OAuth refresh tokens for cloud-storage integrations (Google Drive, Dropbox, OneDrive) are stored only server-side, encrypted with a separate key, and never exposed to the browser.
When a document is fully signed, Signatura computes a SHA-256 hash of the final PDF and records it in our database. Anyone can re-verify a Signatura-signed document at app.getsignatura.com/verify by uploading the PDF — we re-hash it in the browser and confirm whether it matches our completion record. This lets you detect modification of the file after it left Signatura. The verification check is against Signatura’s records, not a third-party attestation.
Each completed document is delivered as two files: the signed PDF, and a separate Certificate of Completion PDF listing every signer, their IP and timestamp, and the document’s SHA-256 hash for offline reference. The certificate is never merged into the signed document — writing a file’s own hash inside it would change the file and break the match — so the PDF you hold re-hashes to exactly the value the certificate prints.
For every signing event, Signatura logs:
The audit trail is preserved for the duration of your account and as required by applicable record-keeping laws, and is queryable per-document by the document owner via the dashboard.
Signatura runs on Supabase (PostgreSQL + storage), hosted in the United States. We use a small set of sub-processors and rely on each vendor’s published data-protection terms (which generally include Standard Contractual Clauses or Data Privacy Framework certification where the vendor offers them) for international transfers.
See the full sub-processor list at getsignatura.com/sub-processors. We give at least 10 days’ notice before adding or replacing a sub-processor, by updating that list and emailing customers who subscribe to updates.
Signatura sets no analytics, advertising, or cross-site tracking technology — not on this site and not in the app. Because we set no non-essential cookies there is no consent banner, and none is required: under the EU ePrivacy Directive and equivalent laws, strictly necessary cookies do not require prior consent. This claim is meant to be checked rather than trusted — open your browser’s developer tools, load any page of this site or the app, and read the network tab.
Specifically, we do not use:
We honor the Global Privacy Control browser signal, and because we neither sell personal information nor share it for cross-context behavioral advertising, GPC changes nothing about how we treat you — every visitor is already handled as opted out. Some sub-processors set their own essential operational cookies when their service is in use, such as Stripe during checkout and Cloudflare for traffic management; those deliver the service and are not used by Signatura for tracking. The complete inventory of what we do set, down to the individual key, is in our Cookie Notice. Auto-Sign is the one feature that sends document content to a third party, and it is opt-in per session — the section below sets out exactly what is sent and what is retained.
Every database table has Postgres row-level security (RLS) policies enforcing per-user and per-organization access. Server-side edge functions verify each request with supabase.auth.getUser() or signing-token claims; we do not rely on client-side checks for authorization. SQL is parameterized end-to-end — no string interpolation.
Each signer gets a private, token-scoped signing link. Links stay fresh for 72 hours and are refreshed automatically by reminders and re-sends; if a link does go stale while the document window is still open, the signer can request a fresh one themselves — no round-trip through the sender.
Account holders can export all of their data as machine-readable JSON — documents, templates, contacts, audit logs, settings, and more — in one click from Settings > Security, and delete their account with password confirmation (completed signed documents and their audit trails are retained as a legal record, as described in our Privacy Policy).
Signers without an account have the same self-service rights: a code-verified form at getsignatura.com/signer-privacy lets any signer export or erase their data. Auto-Sign users can separately download or delete their AI analysis data at any time.
The Auto-Sign feature uses Anthropic Claude to detect signature, date, and text fields in your documents. It is opt-in per session. Pages are sent to Anthropic’s API for real-time analysis. Anthropic does not retain your content after the API call, and its data-processing agreement prohibits training on customer inputs. The analysis result returned to Signatura (field positions and types only — not document content) is cached on our infrastructure for up to 1 hour to avoid re-running the analysis if you reload the page, and is then automatically deleted. You can disable Auto-Sign at any time without affecting any other feature.
If we become aware of a personal-data breach affecting you, we will notify you and any applicable supervisory authority without undue delay and within the timeframes required by applicable law. Notices will include the nature of the breach, the categories and approximate number of affected individuals and records, the likely consequences, and the measures we have taken or intend to take.
If you discover a security issue, please disclose it responsibly to [email protected]. We will acknowledge your report within 2 business days and provide regular updates while remediating.