Worker Verification Policy

1. Why verification exists

A customer booking through Warsha is letting a stranger into their home, often when they are alone in it. Verification is the only thing standing between that customer and someone who is not who they say they are.

It also protects you. A platform where anyone can claim any identity is a platform where the honest majority carries the reputation of the dishonest few.

2. What is required

Every item below is required before an account may take work.

• A verified phone number.
• The front and back of a valid Egyptian National ID.
• Your confirmation of the identity fields — legal name, date of birth, identity number, expiry date.
• An official criminal-record certificate (فيش وتشبيه), obtained by you and uploaded by you.
• A profile photograph showing your face.
• Your trades and service area.
• Acceptance of the Worker Terms and of this policy.

3. The criminal-record certificate

You obtain the certificate yourself, from the competent Egyptian authority, through the ordinary public process. Warsha plays no part in it.

Warsha has no integration with the Ministry of Interior. It has no API, no privileged access and no ability to look up your record, confirm a certificate's authenticity with the issuer, or obtain one on your behalf. If any Warsha screen ever appears to suggest otherwise, this policy governs and that screen is wrong.

Warsha accepts a PDF, JPEG or PNG, captured or uploaded. The size limit is shown at the point of upload.

A certificate must be legible and current. If it is not, you will be asked for another; that request is not a finding about you.

4. Eligibility

Whether a record affects eligibility is decided under a written, versioned eligibility policy, reviewed by a person, against the version in force on the day of the decision.

Warsha does not operate a rule that any offence within a fixed recent period automatically disqualifies a worker. Such a rule is easy to write and hard to defend, and it would end livelihoods on an arithmetic nobody had examined.

The eligibility policy in force is recorded with its version and its review status. As at this version, no eligibility policy has been through legal review, and Warsha states that rather than implying an approval it has not obtained.

No adverse eligibility decision is ever made automatically. A person makes it, a person confirms it, and the reason is recorded in a form that can be shown to you and examined on appeal.

5. Machine assistance, and its limits

Text extracted from a document is used for one thing: pre-filling the form you then check. You confirm every field. An unconfirmed extraction is never treated as a fact about you.

Extraction confidence is internal. It is never shown to you, never shown to a customer, and never used as a reason for any decision.

No automated process determines whether a document is genuine, whether it is yours, whether it has been altered, or whether your record makes you eligible. Each of those is a human judgement, and each adverse one requires a human to confirm it. A low-confidence or ambiguous extraction never produces a rejection.

The OCR Usage Policy and the AI Usage Policy set this out in full, including what would have to happen before any of it changed.

6. Provisional activation

When your submission is complete you become provisionally active immediately and can take work. Staff review happens afterwards.

Provisional activation means your submission is complete. It is not a finding that your documents are genuine or your record is clear, and Warsha does not describe you to customers as fully verified until review is done.

Review may confirm your verification, ask for a correction, suspend your account, or deactivate it. Section 9 of the Worker Terms explains what each means for work you have already done and money you have already earned.

7. Who can see your documents

Only staff holding the specific capability. Reviewing an identity document and opening a criminal-record certificate are separate capabilities, and the second is the more restricted of the two and requires re-authentication.

Every access is logged with the reviewer, the time and the capability used, whether or not anything was found.

A reviewer sees what they need for the decision in front of them. They do not see your unrelated account history, your messages, or your payment records.

Offence detail is recorded only in a private reviewer assessment. It is never stored on your account record, never returned to any application, and never included in a notification.

8. Corrections, rejection and appeal

If something is wrong you are told what, in terms you can act on. "Your document was rejected" is not a reason; "the back of your ID is cut off at the bottom edge" is.

A rejection is never recorded without evidence of what the reviewer actually saw. That evidence is kept, and it is what an appeal examines.

You may appeal any adverse decision. An appeal is decided by someone other than the person who made the original decision — that separation is enforced by the system, not by convention.

A rejection is not permanent unless it is a finding of fraud. If the reason was a correctable problem, correct it and resubmit.

9. Retention

Your original document is retained for at least one year from upload, so that a dispute, a safety report or an audit arising after the fact can be examined against what was actually submitted.

A reduced copy is held for ordinary review, so that most review work does not require opening the original.

Extraction candidates are superseded once you confirm your fields.

Raw provider responses are not retained. What is kept is the extracted fields, a confidence value, a hash of the document, the provider version and the timestamp — enough to audit what happened, not a second copy of your document in another form.

Longer periods are in the Data Retention Register. Where one has not been settled by legal advice, the register says so.

10. Changes

A change to what is required, how documents are processed, who can see them, how long they are kept, or how eligibility is decided is a material change requiring a new version and your acceptance.

Introducing an external processor for extraction is a material change and an addition to the Subprocessor Register. You will be told before it takes effect.