Security

Production traffic uses HTTPS. Uploaded PDFs stay in private storage. Signing links are sealed with AES-256-GCM, and each document is fingerprinted with SHA-256.

Transport and storage

Production traffic uses HTTPS. Uploaded PDFs go to private object storage. They are not on a public URL. Signing links are sealed with AES-256-GCM and stored as a SHA-256 hash. The raw link is what the signer receives.

Records

Each document is fingerprinted with SHA-256 when it is uploaded. After an envelope is sent, those PDFs cannot be replaced. A new version keeps the original files, voids that envelope, and asks signers to review and sign the new draft once you send it. The completed PDF carries a certificate of the ceremony. Audit events are append-only: the database rejects updates, deletes, and truncates. Webhooks are signed with HMAC-SHA256 over the timestamp and the raw body.

Accounts

Passwords are hashed with bcrypt. API keys are shown once and stored only as a hash. Sandbox keys are the default in Settings. A live key is a separate choice on that page. Signing email is sent with Resend.

Questions go to support@hurrysign.com. There is no external uptime monitor yet.