Maple eSign

Every signature leaves evidence you can inspect.

Maple combines identity controls, explicit consent, a tamper-evident event history, deterministic PDF sealing, and Canadian infrastructure around every agreement.

See the evidence modelRead the security details

A complete workflow, backed by a complete record

Maple combines the product capabilities people expect with evidence that stays attached to every completed agreement.

256-bit
Bits in the sealed document hash
11
Advanced workflow capability groups
2
Signing languages, English and French Canadian
1
Tamper-evident history for each agreement

Every event strengthens the final record.

Each recorded action links to the event before it. Completion adds the sealed document hash and Certificate of Completion.

Agreement event

Signer consent recorded

Example

Actor role

Signer

Recorded at

14:32:08 UTC

Prior hash

2f4c9d71…78a0

Current hash

7c9f21ae…2a11

Security built into the workflow.

CHAINavailable
Tamper-evident audit history

Document events are recorded in an append-only, hash-chained audit trail.

SEALavailable
Repeatable document sealing

The same completed input produces the same sealed output, Certificate of Completion, and recorded document hash.

VERIFYavailable
Recipient identity controls

Maple supports optional SMS verification, flexible field types, conditional fields, signer attachments, and typed, drawn, or uploaded signatures.

ROLEavailable
Team-scoped access

Author sessions, API tokens, templates, documents, and webhooks are scoped to the correct team.

EVENTavailable
Verified integrations

HMAC-signed webhooks let connected systems verify completion, decline, and void events before acting.

LOCALEavailable
Bilingual signing

The signing experience is available in English Canadian and French Canadian, including localized consent and recipient emails.

Canadian infrastructure, described precisely.

Core application, database, and document-storage resources are designed for Canadian regions, with the remaining policy boundary stated clearly.

Canadian infrastructure model

Application compute

Canadian regional deployment

Signing and document workflows run from the configured Canadian region

Database and object storage

Canadian regional deployment

Agreement data and document objects use the configured Canadian region

TLS endpoint

Regional endpoint design

Encrypted browser and API traffic terminates at the configured service edge

Organization policy

Policy enforcement pending

Maple does not turn regional configuration into an absolute residency guarantee

Regional configuration is a technical fact. An absolute residency guarantee requires enforced organization policy and an approved agreement.

Strong product controls, without inflated promises.

Built into Maple
Document events are recorded in an append-only, hash-chained audit trail.
Completed documents can be sealed into a PDF with a Certificate of Completion and recorded SHA-256 document hash.
Optional SMS identity verification can be required for individual recipients before document access.
The signing experience is available in English Canadian and French Canadian, including localized consent and recipient emails.
Important context
The sender remains responsible for the agreement, signer authority, and any jurisdiction-specific legal requirements.
Maple does not publish a third-party security certification claim.
Maple does not currently publish a formal accessibility conformance statement for the complete product.
A customer-facing retention and deletion policy has not been approved for publication.
The sender controls how recipients receive the final package after completion.

Trust should be inspectable

Bring the agreement. Keep the evidence.

Maple keeps identity, consent, document integrity, completion, and integration events attached to the same record from start to finish.

See everything includedGet support