Skip to content
WQ3

Trust Center

Privacy

How WQ3 handles personal data on this website and in signing workflows.

Why teams use it

Optional analytics only with your consent.

Signers see only the documents sent to them.

Related

01

Privacy policy

How this website collects and uses personal data.

02

Cookie policy

How this website uses essential and optional technologies.

Our privacy commitments

01

Minimum data

We collect only what is needed to provide the service and prove signatures.

02

Law 151 of 2020

We process personal data under Egypt's Personal Data Protection Law.

03

Your rights

Access, correct or ask to delete your data by contacting legal@fedis.com.eg.

Data retention

We keep documents and audit records as long as needed to prove signatures and meet legal obligations, as agreed in your subscription. Full details are in the Privacy Policy.

Review personal information before sending

Privacy starts with preparing the document, not just with the signing step. Before sending an agreement, review personal information in its main text and attachments, and identify what recipients need to understand and sign it. A useful practice is to remove unrelated contact details, internal notes and information about people who are not involved in the transaction.

WQ3 supports roles and permissions and provides a private signing link for each signer, but these controls do not replace reviewing the file you choose to share. Check the recipient list and intended document version before sending: documents are locked once sent. This helps avoid including information in a transaction that does not need it.

Understand what public verification reveals

Contracts signed with WQ3 have a public check page, accessible through a QR code and reference without an account. It supports authenticity checks through document fingerprint comparison and shows signer names, the signature level and the timestamp of every step. Treat this visibility as part of privacy planning, rather than viewing verification only as a technical feature.

Before distributing a completed contract or its completion certificate, consider that both carry the QR code. Explain to signers that the proof record includes identity and timing information. Public verification and document access are different matters; a private signing link should not be taken to mean that all verification information is private too.

Match identity requirements to the transaction

Different contracts can call for different identity requirements. WQ3 offers three signing levels—electronic signature, remote signing and token signing—and allows a different level for each signer in the same document. Electronic know-your-customer verification, or eKYC, is an account-verification add-on, not a fourth signing level.

When preparing a workflow, identify why identity verification is needed instead of assuming every agreement needs the same requirements. An eKYC-verified account can be required with any signing level when the signer's identity must be proven. It is useful to explain the distinction between choosing a signing method and requiring account-holder verification before inviting people to participate.

Treat completed records as personal information

Privacy considerations extend beyond the agreement's wording after signing is complete. The audit trail records actions on the document and travels with the completion certificate; these materials can contain information about the people involved. When planning internal review or subsequent file sharing, consider both the agreement and its associated proof records.

Defining the purpose of sharing these records helps clarify who needs them. For example, an internal review should identify the information needed to answer its question, rather than automatically circulating every related file. If a privacy enquiry concerns a signing record rather than website browsing, explain that context and identify the relevant transaction without attaching unnecessary personal documents in the first message.

Start your first signing journey today.

Create your WQ3 account, or talk to us about your organization’s requirements.

Frequently asked questions

Does a private signing link hide my name from public verification?+

Do not assume so. The public check page shows signer names, signature level and timestamps; the private signing link serves a different access purpose.

Is eKYC an additional signing level?+

No. It verifies the account holder and can be required with any of the three signing levels.

What should I check for privacy before sending?+

Review recipients, document content and attachments, removing personal information unrelated to the transaction before sending.

Does sharing a completion certificate raise privacy considerations?+

Yes. It accompanies the audit trail and carries the QR code for public verification, so consider its intended audience.

How should I describe a signing-related privacy enquiry?+

Specify whether it concerns document content, signing records or public verification, and identify the transaction without attaching unnecessary personal information.