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
Security at every step of the signing process
IMZA combines signer identity controls, secure signing workflows and verifiable evidence, so organizations can protect each document from preparation to completion.
Signature types
Choose the signature that fits the document
IMZA supports two signature levels. They differ in how the signer is verified and how the signature is created.
- Signature type
- The kind of signature: electronic (a broad category) or digital (based on cryptography).
- Signature level
- The assurance level, such as simple or qualified, set by the applicable law.
- Signing mode
- How the signer signs, for example in the platform or locally with a token.
- Technical format
- How the signature is stored in the file. PAdES, for example, is a PDF signature standard, not a legal level.
Sign directly in the platform
- What it means
- An electronic signature that records a person's intent to sign a document.
- How it works in IMZA
- The signer signs online in IMZA, in the workflow set up by the sender.
- Typical use cases
- Internal approvals, routine agreements and other documents where speed matters.
- Identity and security
- The level of signer verification depends on how the workflow is configured.
- When to choose it
- When convenience and speed matter and the document does not require a qualified signature.
Sign with a cryptographic USB token
- What it means
- A higher-assurance signature created with a certificate stored on a token held by the signer.
- How it works in IMZA
- The signer connects their cryptographic USB token and signs locally on their own device.
- Typical use cases
- Documents where stronger proof of the signer's identity is expected.
- Identity and security
- The signing key stays on the signer's token. Assurance depends on the token and certificate used.
- When to choose it
- When the document, regulator or counterparty expects a qualified signature.
Legal effect depends on the applicable law, the certificate and the circumstances of signing. A cryptographic signature alone does not establish legal validity or prove who the signer is.
Document integrity and cryptographic protection
How signed documents can be checked after signing.
Integrity verification
The signed document can be verified to confirm it matches what was signed.
Certificate-based signing
Qualified signing uses the signer's certificate and token.
Verification can show whether a document changed after signing. It does not prevent a copy from being edited.
Identity verification and access control
Controls that decide who can act on a document.
Authentication
Participants are authenticated before they act on a document, according to the workflow settings.
Participant roles
Each participant has a defined role in the workflow, such as signer.
Method-specific controls
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.
Infrastructure, privacy and compliance
What to discuss with us when assessing IMZA for your organization.
Deployment and data location
Deployment options and data-location arrangements are defined with each organization.
Algerian legal and PKI context
IMZA is built around the Algerian legal framework and trusted digital identity, with an architecture ready for international standards.
Being ready for a standard is not the same as being certified under it. Ask us about the current status of any certification or compliance requirement that matters to you.
