Skip to content

Trust

Security at Aback Sign

What we do to protect your documents, the people who sign them and the record of what happened. We describe the protections that exist today, precisely, and say where the limits are.

Last updated 17 November 2026

1. Documents and storage

  • Uploaded PDFs are checked byte by byte before they are accepted: file signature, structure, encryption, page count, page size and file size. Encrypted, malformed and already digitally signed PDFs are refused with a clear reason.
  • Files are stored in private object storage under random, server-generated keys. File names are never used as storage paths, and there are no public links to stored files.
  • Every upload becomes an immutable document version with a SHA-256 digest. Envelopes refer to exact versions, and the digest is checked again before a final PDF is produced.
  • Downloads are authorised on every request and sent with no-store caching.

2. Signing links

  • Each recipient gets their own link with a 256-bit random token. Only a SHA-256 digest of the token is stored.
  • Opening a link changes nothing. A recipient continues with an explicit button, so email security scanners that fetch links cannot start a session, mark a request as viewed or use a link up.
  • Continuing starts a two-hour signing session bound to one recipient and one envelope, held in an HttpOnly, SameSite=Strict cookie scoped to that session's pages. It is separate from account sign-in.
  • Links stop working when a request is completed, declined, cancelled or expired, and earlier links stop working when a new one is sent.
  • Senders can require an access code shared outside email, or a one-time code sent to the recipient's email. Verification locks after repeated failures.

3. Integrity of the signing record

After an envelope is sent, its documents, recipients, fields and terms are locked in the database itself, not only in application code. Field values and signature images cannot be changed after submission, and the audit trail is append-only.

  • Each audit event is hashed, and the events of an envelope are chained: each link commits to every event before it. The chain head is written into the evidence file.
  • The completion package contains the signed PDF, a completion certificate and a structured evidence file, each with its SHA-256.
  • Anyone can check whether a file matches a completed envelope on the verification page. The file is hashed in their browser, and only the digest is sent.

A matching hash shows that a file is byte-for-byte the one Aback Sign produced. It does not by itself prove who signed, their intent, or that a signature is legally effective for a particular document.

4. Accounts

  • Passwords are stored as salted PBKDF2-SHA256 hashes. Sign-in responses do not reveal whether an email has an account.
  • Sessions use HttpOnly, Secure, SameSite cookies, expire after 14 days, and can be reviewed and revoked from Security settings. Changing a password signs out other devices.
  • Workspace roles are enforced on the server for every request. Every query is scoped to the workspace the signed-in person belongs to.

5. Application and infrastructure

  • Aback Sign runs on Cloudflare Workers with D1, R2 and Queues. Preview and production use separate databases, storage, queues and secrets.
  • Responses carry a Content-Security-Policy with no third-party script origins, frame-ancestors none, nosniff and a strict referrer policy. Signing pages never send a referrer to other sites and are never cached.
  • Requests that change state must come from the application's own origin. Sign-in, signing, verification and public endpoints are rate limited.
  • Logs never contain passwords, cookies, signing tokens, document contents or signature images.

Known limit: the Content-Security-Policy currently allows inline scripts, which the rendering framework needs. Replacing this with per-request nonces is planned.

6. What we do not claim

Signatures in Aback Sign are visual electronic signatures: an image the signer types, draws or uploads, placed on the PDF, together with an audit trail. The final PDF is not signed with a certificate. Aback Sign does not verify legal identity and does not offer qualified or regulated signature methods such as Aadhaar eSign or DSC. Whether an electronic signature is appropriate for a document depends on the law that applies to it.

7. Reporting a vulnerability

Email security@aback.group with the details and steps to reproduce. Please do not access other people's data or degrade the service while testing. We will acknowledge your report and keep you informed as we fix it.