A signature you can prove.
Rakesign seals each signed PDF and records each step, from the first email to the last signature. Anybody can check the result in Adobe Reader.
Is Rakesign legally binding?
Yes. Laws in Canada, the US and the EU accept electronic signatures when you can show who signed, that they meant to sign, and that the document did not change.
Rakesign records each of these facts. The email one-time code links the signer to an address. The signer acts on purpose to sign. The AATL seal shows that the PDF did not change. The audit certificate puts all of it in one record.
Controls on every envelope.
AATL certificate
Our signing certificate is on the Adobe Approved Trust List. Adobe Reader shows the signature as valid.
Tamper-evident PAdES seal
Each signed PDF gets a PAdES seal. A change to one byte breaks it, and a trusted timestamp keeps it verifiable for years.
Email one-time code
Each signer types a one-time code from their inbox before they sign.
Audit certificate
Each envelope ends with an audit certificate: who opened it, when, from where and how they signed.
Encryption
AES-256 encryption at rest and TLS in transit. No person touches the signing key.
SOC 2 Type 2
Independent audit of our security controls over time. Report on request, with policies and subprocessors in the Trust Center.
Visit the Trust Center
Questions and answers
Yes. Rakesign signatures are designed to meet ESIGN and UETA in the US, eIDAS in the EU and PIPEDA in Canada. Each PDF carries an AATL seal and an audit certificate.