Signature bound to the document
A signature is tied to the document content, so a change after signing can be detected.
Security and digital trust
IMZA combines signer identity controls, secure signing workflows and verifiable evidence,organizations can protect each document from preparation to completion.
Signature types
IMZA supports two signature levels. They differ in how the signer is verified and how the signature is created.


Legal effect depends on the applicable law, the certificate and the circumstances of signing.
How signed documents can be checked after signing.
A signature is tied to the document content, so a change after signing can be detected.
The signed document can be verified to confirm it matches what was signed.
Qualified signing uses the signer's certificate and token.
Verification can show whether a document changed after signing.
Controls that decide who can act on a document.
Participants are authenticated before they act on a document, according to the workflow settings.
Each participant has a defined role in the workflow, such as signer.
Some controls apply only to certain signing methods, such as local signing with a token.
Available controls vary by workflow and configuration. Contact us to confirm what applies to your use case.
What to discuss with us when assessing IMZA for your organization.
Deployment options and data-location arrangements are defined with each organization.
IMZA is built around the Algerian legal framework and trusted digital identity, with an architecture ready for international standards.
IMZA is a document management and signing platform. The issuance of qualified certificates is delegated to certification authorities (TSPs).