What we keep, and how you can check it.
Sign-in
You sign in with your email and a one-time code. There are no passwords to leak. The connector uses OAuth 2.1 with PKCE, and each tool needs a named permission: read, write, or read of sensitive files.
The connector holds no keys to the data
The connector and the signing engine are separate services. The connector cannot reach the database; it asks the engine, which checks the account on every request.
Signer links
Each signer gets their own private link. A cancelled request's links stop working. A reminder replaces the old link with a new one.
The signed file
When the last person signs, the file is certified with a digital signature and its SHA-256 fingerprint is recorded. Any later change to the file changes the fingerprint, and a PDF reader shows that the file was altered.
The certifying signature uses our own certificate, so Acrobat shows the signer's identity as unknown. The record at sign.futuras.ai is what you check the file against.
Where it is stored
Documents and records are stored in Canada.
Identity photos in guided sessions
If a guided session captures a photo of a signer's ID, the image is encrypted with AES-256-GCM and can be opened only by the account that sent the request. It is deleted 30 days after the sender files it, and after 90 days at the latest.
What the public record shows
The reference, the status, the completion time, the signers' names and the file's fingerprint. No email addresses, no network addresses, no signature images.