Security
Security specs.
How Tavenca protects your documents and the record of who signed them. Everything on this page describes how Tavenca runs today.
Standards
- Encryption at rest
- Encryption in transit
- Document fingerprints
- Trusted timestamps
- Authenticator apps
- HTTPS only
- Keyless cloud access
- Signed email
The standards behind Tavenca’s security. They describe the technology it uses; they aren’t certifications or audits.
Encryption
- In transit
- TLS 1.2 or later on every connection: from your browser to Tavenca (HTTPS only, with HSTS), from Tavenca to its database (with the server’s certificate verified), and to file storage, which refuses anything less.
- Documents at rest
- AES-256 server-side encryption in Amazon S3, with a dedicated AWS KMS key that rotates automatically.
- Database at rest
- AES-256, on Neon’s managed PostgreSQL.
- Signatures and secrets
- Drawn and uploaded signatures and authenticator secrets are encrypted again by Tavenca with AES-256-GCM, using keys kept outside the database.
Documents
- Fingerprints
- The SHA-256 of the original upload, of the copy signers see, and of the completed PDF, each recorded as the file is created.
- Checked on every read
- Files are re-hashed every time they’re opened or downloaded. A file that no longer matches its fingerprint is never served.
- Write-once storage
- Files are stored under random names and never overwritten.
- Locked when complete
- Completed PDFs and certificates are placed under S3 Object Lock until their retention date. The app’s own credentials can’t overwrite or delete them before then.
- Frozen once sent
- After you send, the document, its fields and its signers can’t be changed. Corrections mean voiding and sending again, which keeps the history.
- Safe to open
- Uploads are inspected in an isolated process with memory, time and decompression limits. JavaScript, embedded files, auto-run actions and interactive forms are removed from the copy signers see.
Evidence
- Audit trail
- Every step, from upload to the final signature, is recorded with its time, IP address and device.
- Append-only
- The database itself refuses to change or delete recorded events.
- Hash-chained
- Each event includes the SHA-256 of the one before it, so any edit, deletion or reordering is detectable, and the whole trail can be re-verified independently.
- Trusted timestamps
- Each completed document and its audit trail are timestamped by an independent authority (RFC 3161; Sectigo, with DigiCert as backup). The signed timestamps are attached to the certificate of completion, so anyone can check them with standard tools.
- Consent
- The exact disclosure each signer agreed to is recorded by its SHA-256 fingerprint.
- Certificate of completion
- Who signed, when, from which IP address and device, and how they were verified, with the document’s fingerprints and the head of the audit trail.
- Public verification
- Anyone can check a copy against the record. The fingerprint is computed in their browser, so the file is never uploaded, and the page shows no names or emails.
Signers
- Personal links
- One link per signer: 256 bits of randomness, stored only as a hash, expiring after 30 days or as soon as the document is voided.
- Email codes
- Optionally, signers enter a one-time code from their inbox before the document opens, so a forwarded link alone isn’t enough.
- Safe from link scanners
- Opening a link shows a read-only page. Nothing happens until the signer chooses Review & Sign.
- Only their own fields
- Each signer can see and fill only their own fields, in the order you choose.
Accounts
- No passwords
- Sign in with a 6-digit code sent to your email. Codes expire after 10 minutes and allow only a few attempts.
- Two-step verification
- Add an authenticator app as a second step, with single-use recovery codes stored as salted hashes.
- Sessions
- Random 256-bit tokens in secure, HttpOnly cookies. Sessions end after 7 days of inactivity or 30 days at most, and you can sign out every other device from Settings.
- Security notices
- You’re emailed when two-step verification is turned on or off, or when a recovery code is used.
Application
- Isolation between accounts
- PostgreSQL row-level security on every table, in addition to the app’s own checks. The app’s database login can’t bypass it.
- Browser protections
- A strict Content Security Policy with a fresh nonce on every page, HSTS, no framing by other sites, and origin checks on every change.
- Abuse limits
- Rate limits on sign-in, codes, signing links, uploads, sending, reminders and downloads.
- Careful logging
- Logs never contain document contents, signatures, signing links, codes or cookies.
Infrastructure
- Location
- Documents and records are stored in the United States, in AWS’s Oregon region. The app runs on Vercel, the database on Neon, and files on Amazon S3.
- No stored cloud keys
- Tavenca reaches AWS with short-lived credentials issued through OIDC, so the app holds no AWS access keys.
- Backups
- The database can be restored to any point in the past 7 days. Deleted or replaced files stay recoverable for 30 days.
- Retention
- Completed agreements are kept for 7 years by default.
- Sent from tavenca.com, signed with DKIM and authorized by SPF.
Privacy
- No tracking
- No ads, analytics or third-party scripts, in the app or on this site. Cookies are used only to keep you signed in and to secure signing sessions.
Report a vulnerability
If you think you’ve found a security vulnerability in Tavenca, please email support@tavenca.com with “Security” in the subject. Tell us what you found, how to reproduce it, and what someone could do with it.
While you investigate, please:
- Use only accounts and documents of your own, and stop as soon as you come across anyone else’s information.
- Don’t change or delete data, degrade the service, or run denial-of-service, spam or social-engineering tests.
- Give us reasonable time to fix the problem before you tell anyone else.
We’ll confirm we’ve received your report, keep you updated, and credit you once it’s fixed if you’d like. We won’t take legal action against anyone who reports in good faith and follows these guidelines. Tavenca doesn’t offer paid bug bounties.
These are technical controls. They aren’t a certification or a compliance claim.