Everything you want to know about Contracts and electronic signature

Wthaiq is a platform specialising in ready-made legal and administrative documents for companies and entrepreneurs in Egypt, with a complete e-signature path inside the platform: you choose the document, fill in your details, send it for signature, and receive a final signed copy that anyone can verify publicly.

Any person or company that needs trusted legal documents — entrepreneurs, startups, mid-sized and large companies, and individuals. In practice, the most frequent uses are: employment and hiring contracts in HR teams, shipping and supply contracts, non-disclosure agreements, and powers of attorney and law-firm forms.

Whoever creates a document and sends it for signature needs an account, because the documents and the signing log belong to it. The signing party needs no account and no app: they open the secure link they receive and confirm their identity with a verification code sent to their email.

We currently serve the Egyptian market, and we are working on expanding to other countries in the region. A party living outside Egypt can sign a contract issued from the platform through the link sent to them.

Once your document is created, enter the other party’s email and they receive a secure signing link. When signing is complete a copy reaches every party. The final copy comes with a timestamped log of every event and a reference number that can be verified later.

Yes. You add each party with their details, and every one of them receives their own link and their own verification code. The final copy and the completion certificate are issued only after all parties have signed.

Yes, from the dashboard you can see the status of every contract: Pending signature / Signed. Each party's events appear alongside with their timestamps, so you know who has signed and who hasn't opened the link yet.

A signed contract is not amended: its digital fingerprint fixes its content at the moment of signing, and the verification page exposes any change to it. The correct route is to issue an addendum correcting the clause in question, or a new contract signed by the parties, and to keep both documents together.

The contract stays in “Pending signature” and no obligation arises against anyone who has not signed. You can track the status from your dashboard and resend the link or get in touch, then cancel the workflow and issue a new version if the terms change.

Yes, it is recognized under Egyptian E-Signature Law No. 15 of 2004 and its executive regulations.

Three things together: the signature is tied to its owner by a verification step (a code sent to their email), the owner has sole control of the signing method, and any later change to the document can be detected through the SHA-256 hash and the event log. Missing any one of them weakens the evidence, even if the file looks signed.

Electronic Signature Law No. 15 of 2004 and its executive regulations give an electronic signature evidentiary weight, provided its conditions are met. Whoever relies on the document is the one who must produce what supports it: the final copy, the completion certificate, the fingerprint, the event log, and the public verification link. So keep this full package with every contract.

Yes. For transactions where the law requires a specific form, official notarization, or registration with a particular authority, the traditional route is advisable. If you are unsure about a high-value or formally prescribed transaction, consult your lawyer before choosing a signing method.

A scanned signature is just a drawing inside a file. It can be copied and pasted into any other document, and it carries no proof of who put it there or when. An electronic signature in Wthaiq, by contrast, comes with identity verification through a code sent to the signer, a timestamp, a digital fingerprint of the final copy, an event log, and a public verification link.

Your data is encrypted in transit over a secure connection (TLS 1.2+), and every document has a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs) that reveals any change to it. Access is restricted by permissions, and every important event is recorded in an audit trail you can refer back to. We do not claim encryption at rest. Together, these layers are what make a contract provable, not just a stored file.

This law governs the collection and processing of personal data in Egypt and grants the data subject rights such as being informed of processing and accessing and correcting their data. In practice: we collect what is needed to deliver the service and prove the signature, and nothing more.

You and the contract parties you invite. The public verification page reveals neither the contract text nor its amounts — it shows the signing status, the reference number, the hash and partially masked party names, so third parties can verify without seeing what the contract says.

The fingerprint is a short, fixed-length string computed from the contract's text when its signing is complete, using the HMAC-SHA256 algorithm with a secret key held by the platform; it works like a fingerprint. Changing a single letter or comma changes the entire string, so the verification page recomputes it from the stored content and compares it with the saved one, revealing any change immediately. For uploaded PDF contracts, it is computed over the final file itself using SHA-256.

You can request deletion of your data by contacting us, bearing in mind that records tied to signed contracts may have to be retained to prove legal validity or to meet a legal obligation, because deleting them weakens both parties' position in a dispute.

Pricing is always published and up to date on the pricing page, with a breakdown of what each option includes. Check it before you buy, so you pick what fits your usage instead of relying on old figures passed around.

You pay by debit or credit card or through PayPal, and the payment window shows the methods available to your account. The transaction runs over an encrypted connection, and the service is delivered to your account as soon as the payment succeeds.

Yes. An electronic payment receipt is sent to your email once the payment is complete. Keep it with the contract and the completion certificate so the document cycle is complete in your company archive.

No, not once the service has been delivered to your account, because it is consumed as soon as it is made available, and a change of mind is not a ground for a refund. The amount is returned in full to the same payment method in three cases only: if the service was not delivered and could not be activated within 24 hours of your request, if a single transaction was charged more than once, or if an amount was debited without any purchase. Write to support with the transaction reference; the details are in the Refund Policy.

No. Whoever creates and sends the contract is the one who pays; the signing party opens the link and signs with no account and at no cost, so you never have to talk them into registering on the platform.

Every final document carries a QR code and a reference number. Scan the code or enter the reference on the public verification page and the contract's status, hash and event log appear without signing in — so third parties can check for themselves instead of taking your word for it.

Contract status, reference number, SHA-256 hash, the contracting parties with partially masked names, and the timestamped event log. The contract text itself is never shown — the purpose is to prove authenticity, not to reveal content.

It is a companion page that gathers the evidence in one place: who signed, when, by which verification method, the document fingerprint, the reference number, and the verification link. This is the page you present in a claim or an audit.

Your copies are stored in your account and can be downloaded again from the dashboard. If you are a party without an account, the reference number alone is enough to check the contract's status and fingerprint on the verification page.

Sharing the verification link is best: the recipient can confirm the contract is genuine and see its status without seeing what it says. If they genuinely need the text, send a PDF copy yourself along with the reference number.

The verification code is sent to your email. Check your spam folder first, then check your email address character by character, and wait a moment before requesting a new code — rapid repeat requests delay delivery. If the problem persists, contact us with the reference number and the email you used.

Ask them to check their spam folder and search for the platform name. Also check the email address character by character — one wrong letter sends the link to a different address — and resend to the correct address if needed.

Signing links are tied to one specific document and party and have an expiry period; they will not work if they are copied incompletely or edited by hand. The fix: ask the contract owner to send a fresh link from the dashboard instead of trying to repair the old one.

Enter the reference exactly as it appears, with no spaces (dashes make no difference), and make sure you are using the reference of the final copy after all parties have signed; a contract that has not been fully signed will not appear as a signed contract on the verification page.

A contract prepared on the platform is fingerprinted from its text stored with us, so no file’s hash will match it. For an uploaded PDF contract, a mismatch means your file is not the final version itself: it may have been printed and re-scanned, re-saved in another program, or compressed. Recalculate the fingerprint for the copy whose link was emailed to you before drawing any conclusion.

A signed copy is not amended. Issue an addendum that corrects the clause and have the parties sign it, or a new contract that replaces the previous one and refers to it, and keep both documents together in the archive so the chain stays clear.

The flow works in a phone browser, with no app. Update your browser, allow it to open links and windows, and try a different browser or network. If the problem persists, contact us with the reference number and your device and browser type.

Integration needs differ from team to team. Contact us through the contact page and tell us your system and the flow you need — creating the contract, sending it for signature, receiving the status and the final file — so we can work out the right setup for your case before any technical commitment.

Three outputs for every contract: a verified identity for each signer, a hash of the final version, and a timestamped event log. Any integration that hands you back nothing but a file produces a document, not evidence — and you will find that out in your first dispute.

The final copy is a PDF file carrying a QR code and a reference number; for anyone who signs with a token, the signature is embedded in it under the PDF signing framework known as PAdES. Templates before signing are available as editable DOCX files.

Keep one package for every contract: the final file, the completion certificate, the reference number, the hash and the verification link. With that package, any reviewer or auditor can confirm everything themselves later, without coming back to us and without relying on anyone's memory.