Audit trail
Every action on a document is recorded, from sending to final signature, in a clear audit trail.
Trust Center
Every completed document comes with a record of each action and a completion certificate.
The audit record is designed to support the evidence requirements for electronic signatures under Egyptian Electronic Signature Law No. 15 of 2004: who signed, when, from where, and that the document was not altered afterwards.
Every action on a document is recorded, from sending to final signature, in a clear audit trail.
How WQ3 protects documents through the signing workflow.
Created, sent, opened, signed and declined, each with a time.
Name, email, IP address and device, and the eKYC result if used.
SHA-256 fingerprint before and after signing, and a certified timestamp.
Every completed document comes with a certificate summarising the trail, with a QR code and reference for public verification.
Start a review with the question you need to answer, then identify the events relevant to it. If the question concerns completion, distinguish opening a document from signing it: an opening event alone should not be treated as acceptance of its terms. This approach helps keep conclusions within what the record actually supports.
Review the sequence rather than relying on one isolated entry. A decline may help explain why a particular signing path did not complete, while event order provides context for what happened before and after signing. In an internal summary, separate facts expressly recorded in the trail from points that need supporting documents or further explanation.
Treat signer information as complementary evidence, not as interchangeable forms of identity proof. Do not treat contact or device details alone as conclusive proof of a person's identity or contractual capacity. When reviewing an agreement signed for an organisation, also examine the supporting documents that establish the person's authority to act on its behalf.
Consider each signer's signature level when assessing the record, because levels can differ within the same document. WQ3 has exactly three levels: electronic signature, remote signing and token signing. eKYC is an account-verification add-on, not a fourth level, and verifying an account holder should not be confused with establishing authority to represent another party.
When you receive a signed document, make the copy in your possession the starting point for review. Use public verification to compare its fingerprint with the stored fingerprint, then examine the signer information, signature levels and sequence of timestamps. This connects your check to the file being reviewed, rather than merely its name or appearance.
If a mismatch appears, request the original final file before relying on the copy for a decision or dispute. A signature's visual appearance is not enough to assess file integrity. Equally, a matching fingerprint concerns the file's integrity against the stored record; it does not replace review of the agreement's terms, the parties' authority or applicable legal requirements.
For an internal or legal review, keep the final document and completion certificate alongside relevant supporting material in the transaction or case file. Note the question being examined, the events supporting your conclusion and any unresolved issues. This helps the next reviewer understand your reasoning instead of reconstructing the context from the beginning.
Decide what the recipient needs before sharing review materials, particularly those containing personal data. Do not treat public verification as a reason to circulate the entire file unnecessarily. The audit trail supports evidence assessment; legal effect still depends on meeting the conditions of Egyptian Electronic Signature Law No. 15 of 2004 and other requirements applicable to the transaction.
Explore more
How WQ3 protects documents through the signing workflow.
Learn moreHow WQ3 handles personal data on this website and in signing workflows.
Learn moreEvery contract signed with WQ3 has a public check page with a QR code and reference, so anyone can confirm it is genuine without an account.
Learn moreCreate your WQ3 account, or talk to us about your organization’s requirements.
Do not treat an opening event as a signature or acceptance. Review the signing event and transaction context before drawing that conclusion.
eKYC verifies the account holder's identity. Authority to represent a company requires separate review of supporting documents.
Request the original final file and verify it again before relying on it. Do not infer the cause from the mismatch alone.
No account is needed to use the public verification page. Reviewers can access it using the QR code or verification reference.
No. It supports evidence review, but legal effect depends on applicable legal conditions and the circumstances of the transaction.