Signatures

On the proposal page, the client chooses Accept and sign, then:

1. types their full name, which is required, and optionally their job title;
2. sees their name previewed as a signature;
3. ticks the box confirming that they accept the terms of the proposal;
4. confirms.

A proposal can be signed only while it is Sent or Viewed and, if it has a valid-until date, until the end of that day (UTC).

Each signature is stored as an audit record with these fields:

The consent box must be ticked to sign, but it is not stored as a separate field. The IP address and user agent are never shown on the proposal page.

The fingerprint is a SHA-256 hash of the proposal's blocks, taken when the client signs. After signing, the proposal page shows it as Document fingerprint (SHA-256).

It covers the blocks only, not the title, the total value or the valid-until date. Those are protected by the lock that follows the signature.

• The proposal becomes Accepted and is locked: its content, title, value, currency, valid-until date, client and status cannot change again.
• The person who created the proposal gets an email and an in-app notification.
• The client gets a confirmation email. The signed proposal stays available at the same link, showing who signed, when, and the fingerprint.
• Remaining follow-ups stop, and the proposal.accepted event goes to your integrations.

The client can choose Decline instead and, optionally, give a reason. The proposal becomes Rejected, its creator is emailed the reason and notified in the app, follow-ups stop, and the proposal can no longer be signed.

This is a typed-name electronic signature with an audit record. Declario does not verify the signer's identity; the email address in the record is the one you entered for the client.

Whether this is sufficient for a particular agreement depends on the agreement and on the law that applies to it. If you need a specific type of signature, check with your legal adviser.