Electronic signature certificate: The evidence that makes your contract provable.
A signature alone is not enough; what holds up under scrutiny is the evidence around it. On Wthaiq, the signer draws their signature with a finger or mouse, then confirms it with a one-time verification code. Once all parties have signed, the document is automatically sealed with a completion certificate that brings together the signers' details, the verification method, a complete timestamped event log, a digital fingerprint of the document (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs), and a QR code leading to a public verification page. This page explains each component: why it matters in a dispute, and how you can verify it yourself.
What a completion certificate is electronic signature?
A paper contract rests on one thing: the look of the signature. That is the weakest thing to rely on, because a signature can be forged, scanned and pasted, and carries in itself no proof of time, identity or the integrity of the text. The certificate turns this around: Instead of inferring the signature from the way it looks, the signature is surrounded by a chain of facts recorded as they happened.
So the certificate isn't read as a ceremonial sheet of paper but as a technical report: every field in it answers a question that really does come up in a review or a dispute. In the sections that follow we go through these fields one by one, then explain how the certificate is bound to the document itself by a mathematical link that cannot be broken, and how you — or your opponent — can verify it through The public verification page without an account.
And if you're starting from scratch and haven't created a contract yet, start from The contract's full journey explained then come back here to understand its authenticated outputs.
It is: a record of facts, sealed with their time
The signers' details, the verification method, the timestamps, the IP addresses, the fingerprint of the final text and a public verification code — all gathered into one document attached to the contract.
It is: open to independent examination
Any party can match what the certificate says against what the public verification page shows, without taking your word for it or ours.
It is not: merely a signature image
The drawn signature is just one element of the certificate. If the image were removed and the log remained, the evidence would still stand; if the image alone remained with no log, nothing would be proved.
It is not: an accreditation certificate from an external body
It is a document the platform issues about the signing that took place inside it. We don't present it as certification from any regulator or as external accreditation — its strength lies in how verifiable its facts are.
It is not: a substitute for a lawyer reviewing the contract text
The certificate proves that this text was signed in this way at this time. Whether its clauses suit your situation is for your lawyer to assess.
How the certificate is built — in 4 steps.
The certificate isn't written by hand and isn't requested from anyone; it is an automatic record of what the parties actually did inside the platform, assembled step by step during the signing round.
Sign by hand
Open the contract and draw your signature with your finger or mouse — the drawing is captured and tied to you and to this document specifically.
Confirm with the verification code
You'll receive a one-time OTP code and enter it to confirm you own the channel tied to your invitation — proving the act and the identity together.
All parties finish signing
Each party receives a secure signing link by email, signs from any device, and the platform moves the turn along until the last signature.
Receive the certificate and the fingerprint
The contract is sealed with a completion certificate, an event log, a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs), and a public verification page with a QR code, all ready for archiving and for use as evidence.
At the last signature — The document is sealed and its certificate is issued.
This is an illustrative example of what the certificate looks like and how its information is arranged. The data shown in it is for display only; on your own certificate the fields are filled from the real facts of your signing.
wthaiq.com/verify
Electronic signature completion certificate
Illustrative example: the names, numbers and timestamps shown above are for display only.
Anatomy of the certificate: What does each field mean, and which question does it answer?
Go through these fields once and you'll be able to read — or discuss — any completion certificate with confidence.
- Document number
- A unique identifier for this signed copy specifically — not for the contract type and not for the template.Answers: exactly which document are we talking about?
- Contract name and type
- The document title as it stood at the moment of signing, so a copy is never confused with another draft carrying a similar title.Answers: which text did the parties sign?
- Verification code
- The short code anyone can enter on the public verification page to see the document's status.Answers: how can a third party examine this document for themselves?
- Status
- fully signed, or awaiting signature pending the remaining parties. The status is read from the platform, not from the look of the file.Answers: is the contract binding, in the sense that all signatures are complete?
- Date and time of completion
- The timestamp of the last signature — the moment the text was frozen and the certificate issued.Answers: when did the contract become complete?
- Signing parties
- Each party's name, email and role (sender / signer) in a single table, arranged in signing order.Answers: who exactly are the parties to this contract?
- Verification method for each party
- How each party's identity was confirmed: OTP verification for the signer, and account authentication for the sender who owns the document.Answers: on what basis was this signature attributed to this person?
- Signature drawing
- An image of the signature the party drew themselves on screen, shown next to their details.Answers: what form did the signer approve as their signature?
- Timestamp and IP address for every signature
- The time of each individual signature and the network address it came from — shown masked on the public page to protect privacy.Answers: when did each party sign, and from which connection?
- HMAC-SHA256 document fingerprint
- A fixed-length string that represents the final text with mathematical precision, calculated at the moment of completion and recorded on the certificate.Answers: is this the same copy that was signed, or an altered one?
- The numbered event log
- A table of the events in order: the event number, what happened, by whom, the date and time, and the IP address.Answers: what is the full story of the signing, from the beginning?
- QR code and public verification link
- A direct route to The verification page Any party can open it by scanning or clicking, with no account and no fee.Answers: how is this document checked years later, and from any device?
Practical note: From the public verification page you can download the final signed copy, and you can also print the page or save it as a PDF — this is the output usually attached to a case file or an internal review file.
How the certificate is bound to the document — and why it can't be moved to another file?
The weakest form of authentication is a “certificate stapled to a contract”: a sheet of paper that can be pulled off and placed on any document. Linking in Wthaiq rests on four loops, each pointing to the others. So the certificate means nothing apart from the document, and the document means nothing apart from its trail.
Loop one: a single identifier
Every signed copy has its own document number and verification reference. The document number is printed on its pages and the reference on its certificate, and only the reference leads, on the verification page, to this document and no other.
Loop two: the fingerprint of the text
An HMAC-SHA256 fingerprint is computed over the final contract text with a secret key held by the platform, and recorded in the certificate and in the platform's records. The fingerprint does not describe the contract from the outside; it is derived from the text itself.
Loop three: the event log
Every event in the log is tied to this document and to its parties: sending, opening, the verification code being sent, its success, then completion.
Loop four: an external reference
A QR code and a public link bring the examiner back to the verification page to compare what they hold with what the platform holds — so verification no longer depends on the file that reached them.
What this means in practice: If someone presented one contract’s certificate as belonging to another, the first check would expose it: the verification reference recorded on it leads, in The verification page to the details of a contract different from the one in their hands.
HMAC-SHA256 fingerprint: How does a single number expose any silent change?
The closest analogy: a mill that only turns one way. You put a grain of wheat into the mill and flour comes out, and there is no way to recover the grain from the flour. The HMAC-SHA256 fingerprint works on the same logic: the full contract text goes in and a fixed-length digital "flour" comes out, a string of 64 hexadecimal characters from which the contract text cannot be recovered.
And here's the useful part: The mill is extremely sensitive. Mill the same grain twice and you get exactly the same flour, letter for letter. Change the grain by the smallest amount — a digit, a comma, a single space — and the flour comes out completely different, bearing no resemblance to the first and giving no hint of how much was changed.
That is why the fingerprint is calculated the moment signing is complete and recorded on the certificate and on the public verification page. After that the check is simple: the verification page recalculates the fingerprint from the contract content stored on the platform — not from a copy in your hands — and compares it with the original. If the two match, the content hasn’t changed by so much as a character; if they differ, something has changed and calls for closer scrutiny.
The fingerprint doesn't hide the content or encrypt it, and it doesn't stop anyone editing a copy on their own device. What it does, precisely, is make that edit detectable — because the verification page attests to the integrity of the contract held by the platform, so the claim “this is the original copy” collapses wherever the copy presented differs from it.
«Contract value: EGP 250,000.»
«Contract value: EGP 350,000.»
The two texts differ by a single character (2 became 3) — and yet the fingerprints differ in 59 of the 64 in the fingerprint, while the length stayed constant as it always does. This is why a “small edit that goes unnoticed” is impossible. This demo uses plain SHA-256; the contract's fingerprint is computed with the same function combined with a secret key held by the platform (HMAC-SHA256).
Audit trail: Every event, with who did it, when and from where.
This is the backbone of an electronic signature's legal standing: a precise chronological sequence that starts the moment the contract is sent and ends the moment it is completed, documenting the opening of the document, the sending of the verification code, its success and the completion of signing, with a timestamp and an IP address for every step — leaving no room for the question “did they really sign? and when?”.
The value of the log lies not in its existence but in their order: the events are numbered in sequence and shown exactly as they happened, so the trail tells a single story you can review line by line, and it stays an inseparable part of the final completion certificate and of the public verification page.
Contract sent for signing
The other party opened the contract
Verification code sent to the signer
Verification (OTP) successful
Signing is complete and the completion certificate has been issued
What exactly is recorded — and what it proves in a dispute
| Event | What is recorded with it | What it proves in a dispute |
|---|---|---|
| Send the contract for signature | The sequential event number, the timestamp, the sender's role, the IP address | That the invitation to sign came from the sender's account at a specific time — not after the fact. |
| Contract opened by the other party | The timestamp, the party who opened the document, the IP address | That the party read the text before signing — a direct answer to the claim “I never saw the contract”. |
| Send the verification code to the signer | The timestamp, and the masked destination it was sent to (last digits only) | That the verification took place through a channel independent of the session in which the contract was opened. |
| Verification successful (OTP) | The timestamp, the IP address, and its link to the signer themselves | That whoever completed the signature controls the channel tied to the invitation — the basis for attributing the signature to that person. |
| Each party's signature | The timestamp of each individual signature, the order of the signatures, the IP address | Who signed first and who followed — settling any argument about when the agreement became binding. |
| Signing completed and certificate issued | The timestamp, the HMAC-SHA256 fingerprint of the final text, and the verification code | The moment the text was frozen, and which version of it counts when comparisons are made. |
Three real dispute scenarios — and how the audit trail settles them
“I never agreed to the commission rate”
A merchant denies knowing about the commission clause in the onboarding agreement he signed electronically months ago, and asks for his dues to be recalculated.
“I never signed the pay-adjustment addendum”
A former employee claims outstanding payments on the basis of the original contract, and denies signing the addendum that changed the allowance clauses.
Two copies in circulation with two different amounts
A PDF arrives at the office said to be the signed contract, but the amount of the commitment in it differs from the copy the client has on file.
PAdES: When the signature becomes part of the PDF file itself.
What is PAdES? It is a technical standard for signing PDF files digitally, so that the signature is no longer a statement written on the file but is embedded inside the file's own structure along with a digital certificate. The result is that the signature “travels with the file”: wherever the file goes, its signature data goes with it.
Where it sits in Wthaiq: The platform offers three signature levels according to how sensitive the transaction is, and the highest of them is The accredited signing token: a digital signature using an accredited certificate held on the token, embedded in the file to the PAdES standard. Not every contract of yours is signed at this level automatically; it is the level you choose for transactions that deserve the strongest legal standing. For details see The three signature levels on the “How it works” page.
What does that mean in practice for the PDF? That the file's integrity becomes checkable from inside a PDF reader itself: the reader reads the embedded signature and tells you whether the content has changed since the moment of signing. Any later edit to the text, any deleted page, any regeneration of the file breaks that embedded signature, so the problem shows up instead of slipping past in silence.
Two layers that complete each other. The completion certificate and the audit trail answer “who signed, when, and how was their identity confirmed”; the fingerprint freezes the text; and PAdES adds an independent check inside the file itself that doesn't need the platform. Relying on these layers together is what makes the file resistant to silent editing.
Electronic signature
A drawn signature + an OTP verification code. The fastest route for everyday contracts, and it still comes with a completion certificate, an event log, a fingerprint and a verification page.
Signing with ID verification
Verify the signer with an official document and a live face scan before signing — for sensitive transactions.
The accredited signing token
A digital signature using a certificate the client holds on their own token, issued by a licensed certification authority; we embed it in the file to the PAdES standard. The certificate and the token belong to the client, not to the Platform.
An illustration of how the check result appears inside a PDF reader for a file signed to the PAdES standard.
How to check for yourself in under a minute.
You don't have to take our word for it. Verification is open to anyone holding the verification reference: no account, no software to install, no fee.
Open the verification page
Scan the QR code on the certificate, or open The public verification page straight from any browser.
Enter the code
Type the verification reference exactly as recorded on the certificate. Scanning the QR code does it for you.
Read the result
It shows the document's status, the result of the digital fingerprint comparison, the parties' details and how each of them was verified, and the full event log.
Keep the evidence
Download the final signed copy, and print the verification page or save it as a PDF to attach to the case file or the review file.
The four possible results — and how to read each one
The document was signed through the platform, all of its parties have signed, and its content held by the platform matches the original digital fingerprint exactly. This result means the registered contract has not been altered since it was signed.
The contract is valid and on record, but not all of its parties have signed yet. The document and party details are shown, and no completion certificate is issued before the last signature.
The document is signed and on record with us, but its stored content does not match the original fingerprint — meaning that content may have been altered after signing. In practice this is the most important result on the page, because it reveals what the eye cannot.
The number entered is incorrect, or the document is incomplete. In practice it means the file in your hands has no authenticated record with us under that number.
Privacy first: The public verification page does not reveal the contract text. It shows the document's status, its fingerprint, its parties and its event log, and displays sensitive data masked — so a third party can confirm the document is genuine without seeing its commercial secrets. For more on data handling see The compliance and conformity page andTrust center. A notice may also appear saying the document is old and has no digital fingerprint on record for comparison — a case we show exactly as it is, with no dressing up.
Check for yourself — right now
Any party — a court, a lawyer, a partner — can confirm the certificate is genuine by entering the verification code or scanning the QR code, with no account and no fee.
What happens if the document is edited after signing?
The straight answer: nothing stops your opponent editing their copy on their own device — preventing that is technically impossible. What the platform does is make the edit exposed, and that is what matters in litigation. Below are four common scenarios and what happens in each.
Editing the text in a copy in circulation
One of the parties opens the file in an editor, changes a number or a date or deletes a phrase, then resends it as “the original”.
Deleting a page or adding an annex inside the file
A part of the document is cut out, or a new clause slipped in, in the hope that the change passes because the rest of the pages are unchanged.
Editing a file signed to the PAdES standard
A PDF carrying an embedded digital signature is edited, then saved again.
Recreating a “similar” contract from scratch
A new contract is written in different wording, with the signature image and a certificate copied from another contract pasted into it.
And what if the change is legitimate and agreed?
A signed document is never edited — an addendum or a new version is issued and signed by the parties as a separate document with its own number, certificate and log. You end up with an authenticated chain to be read in order, rather than one text whose date is in doubt. Start that from Contract editor.
A scanned signature (image) versus an authenticated electronic signature.
Many companies think they are “signing electronically” when in fact they are swapping scanned signature images. The difference doesn't show on signing day — it shows on the day of the dispute.
| Point of comparison | A scanned signature (image) | An authenticated electronic signature through Wthaiq |
|---|---|---|
| what it actually is | A signature image pasted into a file, not tied to any specific signing event | An act of signing tied to a session, a specific signer and a specific document |
| Proof of the signer's identity | None — the image can be copied from any old document | A one-time OTP verification code that ties the signature to the owner of the channel |
| Time of signing | A date written by hand or in the file name — changeable | A timestamp recorded by the system for each individual event |
| Source of the signature | Unknown | An IP address recorded for every event in the audit trail |
| Detecting changes made after signing | Almost impossible — scanning hides the traces of editing | An HMAC-SHA256 / SHA-256 fingerprint reveals any change, even a single character |
| Event log | None; all that's known is what the parties remember | A numbered log from sending through to completion, attached to the certificate |
| Third-party verification | Needs a paper original and real effort to prove attribution | A public verification page with a QR code: no account, no fee |
| Resistance to impersonation | Copying and pasting a signature image takes no skill at all | The signature is bound to one document, with its own number and verification code |
| Archiving | Multiple conflicting copies in inboxes and device folders | One final copy + a completion certificate + a permanent verification link |
| Where you stand in a dispute | Word against word, and the burden falls heavily on whoever makes the claim | An evidence pack ready to submit: copy + certificate + log + verification output |
For anyone comparing at the operational level: The difference shows in cycle time and follow-up too — collecting signatures goes from days of back-and-forth to minutes, with a clear view of where each party stands. More on this in How we help.
A signature that stands up to any review — because it doesn't rest on intent alone.
The strength of an electronic signature comes not from the picture of the signature but from the evidence around it. That is why Wthaiq ties every signature to a drawing the signer makes themselves, an OTP verification proving they own the channel their invitation was sent to, a timestamped log documenting every event, and a cryptographic fingerprint that freezes the final text — making it almost impossible to deny or alter the signature later.
Drawn signature + OTP verification
The signer draws their signature with a finger or a mouse, then confirms it with a one-time verification code — so the act of signing and the proof of identity come together in a single step.
A detailed completion certificate
With every completed contract comes a certificate gathering each signer's name, email and role, the verification method used, and the time of each signature — one document telling the whole story of the signing.
A full timestamped event log
From sending the contract to the last signature: every event is recorded with its time and the IP address it came from, in a chronological sequence that cannot be deleted or reordered.
HMAC-SHA256 fingerprint
On completion, a mathematical fingerprint of the final text is calculated and recorded on the certificate. Changing a single character afterwards changes the fingerprint completely and exposes the tampering immediately.
A public verification page via QR
A QR code and a public link on every document let any party — a court, a lawyer, a partner — confirm the contract is genuine without signing in and without any fee.
Protection in transit and controlled access
Connections are encrypted with TLS 1.2+, and every document has a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs) that reveals any change, with fine-grained access permissions and an audit trail for every operation. You can find the details in Trust center.
Everything you need to know about signing and the completion certificate.
How does OTP verification work?
After the signer draws their signature, the platform sends a one-time secret code (OTP) to the channel linked to their invitation. The code is produced by a cryptographic random generator, is valid for a few minutes only, and is protected by strict limits on the number of attempts and the sending rate so that it cannot be guessed. When the signer enters the correct code, they prove that they own the channel linked to their invitation — so the act of signing and the proof of identity come together in a single moment, and the successful verification is recorded in the audit trail with its time and IP address.
What does the completion certificate contain?
The completion certificate is the document that summarizes the entire signing process and is attached to the final contract. It includes a unique document number, each signer's name, email, and role, and the verification method used for each party. It also includes the exact timestamp of each signature with its IP address, the verification code, the HMAC-SHA256 fingerprint of the final text, and a QR code for the public verification page. In short, it is the contract's identity card, answering every question that may arise when relying on it: who signed, how their identity was verified, when, and whether the document changed afterward.
What is the HMAC-SHA256 fingerprint, and how does it reveal forgery?
The HMAC-SHA256 fingerprint is a "digital fingerprint" of the contract's final text: a fixed-length string produced by a mathematical process using a secret key held by the platform, which represents that text precisely. Any change, however small (a single character or comma), produces a completely different fingerprint. We compute the fingerprint at completion and record it in the completion certificate and on the public verification page; the verification page then recomputes it from the content stored on the platform at every check and compares it with the original, instantly showing whether the contract has been tampered with. In this way, the contract's integrity turns from a claim into something that can be proven mathematically at any time.
How can anyone verify the contract?
The person checking needs neither an account on the platform nor a fee. Every verified document carries a QR code and a public verification link; when the code is scanned or the reference number is entered on the verification page, the platform displays the document’s status, its validity, its fingerprint, and the time it was completed — without revealing the contents of the contract itself, to preserve privacy. A judge, a lawyer, or a partner can therefore confirm in seconds that the certificate is genuine and that the registered contract has not been altered since it was signed, which gives the contract evidentiary weight that is hard to deny.
The question it answers before the first signature.
Electronic signatures are recognized in Egypt under Electronic Signature Law No. 15 of 2004 and its executive regulations. Every contract whose signing is completed on the platform receives a completion certificate with the signers' details and verification method, a complete timestamped event log, a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs), and a public verification page. Together, this evidence gives the signature probative strength that is hard to deny. The weight of the evidence in each case remains at the court's discretion.
Once the signature is drawn, a one-time verification code (OTP) reaches the signatory. They enter it to confirm that the channel the invitation was sent to is theirs. The successful verification is recorded in the event log with its time and IP address, so the act of signing is tied to proof of identity.
A single document attached to the contract, bringing together a unique document number, each signer's name, email, and role, and the verification method used. It also contains the timestamp and IP address of each signature, the verification code, the HMAC-SHA256 fingerprint of the final text, the numbered event log, and a QR code for the public verification page.
It is a mathematical fingerprint calculated over the final text the moment signing completes and fixed in the certificate. Any later change, even a single character, alters the fingerprint completely, so the verification page recalculates it on every check, and comparing it with the original fingerprint reveals any tampering with the contract.
No. A secure signing link reaches them by email; they open the contract, review it, draw their signature from any device, and confirm with an OTP. They need neither an account nor any app.
On the public verification page they scan the QR code or enter the reference number, and the platform shows the document's validity, its hash and when it was completed — without revealing its content, with no account and no fee, for any party that needs to verify.
Questions lawyers ask — and answers without overstatement.
These are the questions that actually come up in legal review meetings. The answers describe what the platform provides, no more.
What is the legal basis for electronic signatures in Egypt?
Egyptian Electronic Signature Law No. 15 of 2004 and its executive regulations, together with Personal Data Protection Law No. 151 of 2020 as regards processing the parties' data. The details are in The compliance and conformity page.
And we say it plainly: what the platform provides is An evidence pack anyone can examine — a certificate, a log, a fingerprint and a verification page. The weight of that evidence in any particular case is for the trial court to assess, and no one can properly promise a judicial outcome.
What exactly do I submit in litigation or arbitration?
Four connected outputs: the final signed copy as you can download it from the platform, the completion certificate attached to it, the numbered event log, and the output of The public verification page printed or saved as a PDF.
The advantage of that last output is that the opposing party can verify it themselves: nobody is asked to trust what you printed, because the code written on it brings any examiner back to the same result.
How do I answer the claim “the signature was copied or fabricated”?
that a signature here is not judged as a picture. The drawing is only one element, surrounded by things that cannot be copied and pasted: a timestamp for the opening and for the signing, a verification code sent to the signer's channel and entered successfully, an IP address for every event, and all of it tied to one document number.
and anyone claiming impersonation has to explain how they obtained the verification code sent to the signer's channel at that exact minute.
How do I answer the claim “the contract was altered after signing”?
Through mathematical comparison: an HMAC-SHA256 fingerprint is recorded in the certificate at completion, and the verification page recomputes it from the content stored on the platform and states explicitly whether it matches. A match defeats the claim, and any copy that differs from the stored contract shows its alteration when compared with it.
And if the file is signed at the accredited signing token level to the PAdES standard, its integrity can be checked from inside the PDF reader directly, as an extra independent piece of evidence.
Does the opposing party or an expert need an account with us in order to verify?
No. The verification page is public: it opens from a link or a QR scan, and asks for no sign-in and no fee. That is deliberate — a proof tool that needs permission from the interested party is a weak one.
What happens to signers' personal data on a public page?
The public page shows only what verification requires: the document's status, its fingerprint, its parties and how each of them was verified, and the event log — with sensitive data masked, and without revealing the contract text.
and data processing is governed by Personal Data Protection Law No. 151 of 2020; the details and the data subject's rights are in The compliance page.
Which signature level should I recommend to my client for a high-value transaction?
The Platform offers three levels. The first: an electronic signature by drawing plus a one-time code, for everyday contracts. The second: a signature with identity verification using an official document and a live facial image, for sensitive transactions. The third: a signature made with the client's own token, using a certificate from a licensed certification authority, which we embed in the file to the PAdES standard. The highest level we ourselves provide is the advanced signature (AES), through identity verification and a one-time code; the qualified level (QES) is reached by whoever signs with their own token.
The practical rule: raise the level as the value of the commitment or the likelihood of a dispute rises. The full comparison is in The “How it works” page.
What does the platform expressly not claim?
The platform does not give legal advice, does not assess whether a contract's clauses suit your situation, does not guarantee that any particular piece of evidence will be accepted by any particular body, and does not present the completion certificate as an endorsement issued by an external regulator.
What we say, precisely: these are the facts of the signing as they happened inside the platform, and these are the tools that let any party examine them for themselves.
What we say about the certificate — and what we don't say.
What we say and stand behind
- Every contract signed to completion gets a completion certificate automatically.
- A timestamp and an IP address are recorded for every event in the audit trail.
- An HMAC-SHA256 fingerprint of the final text is computed and recorded in the certificate.
- Public verification is open to any party, with no account and no fee.
- Connections are encrypted with TLS 1.2+, and every document has a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs).
What we don't say and don't imply
- We don't present the completion certificate as an endorsement issued by an external body.
- We don't guarantee a court outcome; weighing the evidence is for the court.
- We don't stop anyone editing their own copy — we only reveal the change.
- We don't review your contract's clauses on your lawyer's behalf.
- We don't claim that all signature levels carry equal legal standing.
This plain speaking is deliberate: a signing platform whose stock-in-trade is trust cannot build it on overstatement. For more on our security and privacy principles see Trust center, and for general questions about the service The FAQ page.
Pages that complete this topic
Your next signature comes with its own certificate.
Start e-signing now. Every contract is automatically issued with a completion certificate, an event log, a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs), and a public verification page with a QR code.