Security for every document you send.

Inkly encrypts your documents, keeps them private to the people you send them to, and records every step of signing, on SOC 2 Type II audited infrastructure.

  • Encrypted in transit and at rest
  • SOC 2 Type II audited infrastructure
  • Tamper-evident signed PDFs
A completed consulting agreement in Inkly with each protection checked: sent over TLS, stored with AES-256, private signing links for two signers, a seven-event audit trail, and a SHA-256 fingerprint that matches the signed PDF.

Encrypted from upload to signed PDF.

  • Encrypted in transit. Every connection to Inkly uses TLS, so documents and signatures can't be read on the way.
  • Encrypted at rest. Stored PDFs, signatures, and the values signers fill in are encrypted with AES-256.
  • Tamper-evident. Each signed PDF's SHA-256 fingerprint is printed on its Certificate of Completion, so any later change shows.
A document travels from the browser to Inkly over TLS and is stored encrypted with AES-256. The signed PDF's SHA-256 fingerprint on the Certificate of Completion matches the file, so it has not changed.

Runs on SOC 2 Type II audited infrastructure.

  • SOC 2 compliance: In progress
  • HIPAA compliance: In progress
  • Audited providers. Inkly's database, file storage, and hosting run on infrastructure whose controls are independently audited under SOC 2 Type II.
  • Providers that support HIPAA workloads. Our hosting and database providers offer HIPAA-compliant services with the required agreements and configuration. Inkly's own HIPAA compliance is in progress; provider capabilities alone do not make Inkly HIPAA compliant.
  • Stored in the United States. Your documents and account data are processed and stored in the U.S.

See who handles your data on the sub-processors list.

Inkly's hosting and its database and file storage both run on infrastructure audited under SOC 2 Type II. HIPAA agreements with both providers are in progress, and the sub-processors are listed publicly.

Your documents are never public.

  • No public addresses. Documents sit in private storage. Knowing where a file is stored isn't enough to open it.
  • Checked every time. Inkly confirms you have access to a document before it creates a link to the file.
  • Links that expire. A download link from Inkly stops working after a minute, and every link that opens a file expires within an hour.
Opening a stored PDF by its address without access is refused. A signed-in workspace member passes the access check and gets a download link that expires in 60 seconds.

Each workspace sees only its own documents.

  • Isolated at the database. Row-level security keeps each workspace's documents, templates, and contacts apart, even if a request asks for someone else's.
  • One private link per signer. Each signer's link opens only the document sent to them, and nothing else in your workspace.
Two workspaces, Brightpath Studio and Northwind Rentals, each see only their own documents, separated by row-level security in the database. A signer's private link opens only the consulting agreement sent to them.

Every step of signing on the record.

  • Consent first. Every signer agrees to the eSign disclosure before they can sign.
  • Every event logged. Sending, viewing, signing, and completion, each with the time, IP address, approximate location, and device.
  • Yours to keep. Every party is emailed the signed PDF with its Certificate of Completion.

Read the eSign disclosure or see what the audit trail records.

A Certificate of Completion. The signer's card shows their signature, when they signed, time on the document, IP address, approximate location, timezone, and device. The activity timeline lists each event with its time, IP address, and location, and the certificate ends with the document ID and the signed PDF's SHA-256 fingerprint.

Your data stays yours.

  • Never sold. We never sell personal data, and share it only with the services that run Inkly.
  • Delete what you send. Deleting a document removes it and its files from Inkly.

Ask for the rest. Anyone, signers included, can ask to access, export, or delete their personal data at hello@inkly.so. The privacy policy covers what we collect and how long we keep it.

A confirmation to delete a document, which permanently removes it with its recipients, signing data, signed PDF, and audit trail, beside a note that Inkly never sells personal data.

Found a security issue? Tell us.

Email hello@inkly.so with “Security” in the subject.

  • Send the details. Tell us what you found and the steps to reproduce it.
  • We confirm and investigate. We reply to confirm we have your report and keep you posted while we look into it.
  • Test with care. Use your own account, and don't access other people's data or disrupt the service.
A security report emailed to hello@inkly.so, then three steps: report received, investigating, and fixed.

Legally binding in the U.S., Canada, and the EU.

Inkly signatures meet the ESIGN Act, UETA, the UECA-based acts across Canada, and eIDAS, and personal data is handled under GDPR.

See how Inkly complies with each law →

  • U.S. FEDERALESIGN
  • U.S. STATESUETA
  • CANADAUECA
  • EUeIDAS
  • EUGDPR

Questions about security.

Audits, where data lives, signers, and legal validity.

See the sub-processors →

Send your first document
in under a minute.

Encrypted, private, and recorded from the first upload to the signed PDF.