Agrello guides
Account and billing
Document automation
Integrations
eSignature regulation
Release notes
What makes Agrello signatures ESIGN and UETA compliant?
When determining whether an electronic signature is compliant under the ESIGN Act, following requirements must be fulfilled:
Consent to do business electronically
All parties to an agreement or transaction must agree to conduct the transaction using electronic means. The ESIGN Act Section 101 expressly provides that the consumer has affirmatively consented to such use and has not withdrawn such consent.
.ID signatures cannot be created without prior user consent. Then requesting an electronic signature the user will be asked to confirm the signature by entering the PIN-code on their mobile phone. User can easily reject such request by cancelling the PIN-entry.
Intent to sign
Electronic signatures, like regular wet signatures, are valid only if each party intended to sign.
Agrello signatures do not happen magically. They are created in the process where each signatory is actually intending to sign the document. Signatories can approve or reject the signature requests easily over theAgrello app on their mobile phone.
Association of the signature with the record
An electronic signature must be connected or associated to the document that is being signed by indicating a process by which the signature was created or by creating a graphical or textual statement, which gets added to the signed record.
Agrello uses ASiC-E signature container format (.asic) including the XAdES signature standard put down by ETSI to prevent tampering the original signed digital file and link signatures directly with the record.
Users cannot transfer the issued signature to any other document, because they are valid only together with the associated files.
One of the key differentiator of the Agrello advanced electronic signatures is that we do not tamper with the original signed document. We do not add the watermarks, or handwritten signature images into the document, as it would make the signatures less secure (anyone can then make a screenshot of your signature and reuse it). Our signatures are mathematically connected to the original documents and only valid if the mathematic hash of the signed file matches with the hash stored in signatures.
Attribution
The electronic signature must be attributable to the person who is signing. The attribution of an electronic signature to a person will be determined based on the context and circumstances under which the document is signed. This can be done by a variety of means, such as documenting the communications and actions of the parties, or preserving an audit trail.
Agrello signatures are created with the private key inside Agrello app that is mathematically linked to the public key of the signatory, where a standard validation formula can be used to prove its validity.
The public key of the digital identity is mathematically tied with the identity verification session and the same identity verification session can be tied with only one Agrello account.
Record retention
An electronically signed document must be in the form of an electronic record capable of retention by the recipient at the time of receipt. The sender or the information processing system must not inhibit the ability of the recipient to print or store the electronic record for later reference.
Agrello uses ASiC-E signature container format (.asic) including the XAdES signature standard put down by ETSI to prevent tampering the original signed digital file and link signatures directly with the record. User can download the signature container any time over secure SSL encryption during the transit.
ASIC-E container content (files and signatures) can be validated any time using open source ASIC viewers.
In addition, user can always host the signed document container on secure Agrello platform for previewing and downloading them later.
Copy link