Identity and Biometric Verification Notice

EriWave uses NIN verification and a short face-liveness check to confirm that a person signing an agreement is physically present and matches the identity being used. Routine worker login uses a code sent to the email verified during signing.

This notice explains what happens before you continue.

When you activate a business workspace you declare that you are a director, proprietor, trustee or partner of the company, or authorised by one to act for it. The declaration is recorded against your verified identity. Before your first agreement is sent, we compare your verified name with the company's CAC record, using either a CAC status report you upload (read once and not kept) or, for a fee, an instant review through Dojah. Only the outcome is stored. The record used for the paid review lists other people; we keep only their names and roles in memory for the check and do not store them.

If a company already has an EriWave workspace, another director can claim it. The claimant passes the same check. The current holder is then paused from sending and has seven days to verify its own business. If it does not, the company moves to the claimant; the holder keeps any agreements it has already sent, and a holder with none is erased with any remaining balance forfeited.

If you run a company but are not one of its directors, you can ask a director to approve you. We email a link to the company's registered email address. The director confirms their identity with their NIN and a live camera check, which EriWave pays for, and must match a director, proprietor, trustee or partner on the CAC record. We keep only a keyed hash of the director's NIN, their role, and the time and wording they agreed to; we do not keep their name, raw NIN or images. The director is not given an account, and you are told only that a director approved you.

The identity check may process:

• Your eleven-digit NIN.
• Your name as returned by the identity-verification provider.
• Your date of birth, used only to confirm that you are 18 or older. EriWave does not store the date itself.
• A short liveness video processed by Amazon Web Services.
• A reference image selected from the liveness check and used transiently for comparison.
• A government photograph returned temporarily by Dojah.
• Liveness and face-match results.
• The contact details NIMC holds for you, as returned with your NIN record, when you sign an agreement or act as a next of kin or reference. See “Contact details from NIMC” below.
• Provider references, timestamps, consent records, and limited security metadata.

When you sign an agreement, or confirm one as a next of kin or reference, EriWave keeps the contact details NIMC holds for you (currently your phone number) so we can reach you if there is a dispute or a fraud report about that agreement.

• They are encrypted and stored apart from your agreement.
• Only EriWave's senior administrators can see them, only after re-entering their password and giving a recorded reason. Every view and edit is logged, without the details themselves.
• They are never shown to the other party to an agreement, put in a signed document, sent in an email, or included in an export.
• They are kept separately from the contact details you or the sender entered, which are not changed.
• They are deleted on the same schedule as the latest agreement you signed or supported. That schedule is being confirmed; see our retention schedule.

EriWave does not keep your NIN itself in a form it can read back. Owners who verify to activate a workspace are not covered by this section.

EriWave is only available to people aged 18 or older.

The date of birth returned from the NIN check must confirm this before an owner can activate a workspace or a person can sign. If the provider does not return a valid date of birth, the identity check cannot pass.

First, EriWave asks Amazon Web Services to confirm that a real person is present in front of the camera.

Next, EriWave asks Dojah to verify the NIN.

EriWave compares the liveness reference image with the government photograph returned during the verification request.

The government photograph is not intentionally stored in EriWave's database. EriWave stores a masked NIN and a protected keyed reference instead of the raw NIN.

EriWave uses the liveness reference image and government photograph only to complete the current identity comparison.

EriWave does not intentionally store either image in your user account after that request completes.

A future signature requires a new identity check. Routine login to an existing worker account uses your verified email and a single-use code instead of NIN or facial verification.

An employer may see:

• That identity verification succeeded.
• The verified name used for the agreement.
• A masked identity reference where the product requires it.
• Signing and verification timestamps included in the sealed record.

An employer must not receive your raw NIN, government photograph, liveness selfie, verification reference image, liveness score, or face-match score.

A failed or incomplete check does not prove fraud, theft, dishonesty, or criminal conduct.

Face liveness and face comparison are probability-based tools and can make mistakes. Lighting, camera quality, network problems, appearance changes, and provider availability can affect the result.

EriWave will not create an employer-visible failure record merely because an automated verification could not be completed.

If the check does not work after the permitted retries, contact support@eriwave.com.

EriWave may ask for information needed to confirm your request safely. Support staff must not ask you to send a raw NIN, password, or unrestricted identity photograph through ordinary email.

A verification reference image is not retained or used as an employer-visible profile photograph.

If EriWave later offers profile photographs, they must be uploaded separately as an optional choice. Refusing profile-photo use must not block signing, login, or access to your worker record.

A person signing an agreement uses this consent wording:

I have read the Identity and Biometric Verification Notice. I agree to EriWave using my NIN and liveness selfie to verify my identity for this action. The other party receives my verification status, not my raw NIN, registry photograph, or verification selfie. We also keep the contact details NIMC holds for you, encrypted and visible only to EriWave's senior administrators, so we can reach you if there is a dispute or fraud report.

A next of kin or reference confirming an agreement uses:

I have read the Identity and Biometric Verification Notice. I agree to EriWave using my NIN and liveness selfie to verify my identity for this action. The other party receives my verification status, not my raw NIN, registry photograph, or verification selfie. We also keep the contact details NIMC holds for you, encrypted and visible only to EriWave's senior administrators, so we can reach you if there is a dispute or fraud report about an agreement you support.

An owner verifying to activate a workspace uses:

I have read the Identity and Biometric Verification Notice. I agree to EriWave using my NIN and liveness selfie to verify my identity for this action. The other party receives my verification status, not my raw NIN, registry photograph, or verification selfie.

The checkbox is not pre-checked.