TRUST CENTRE
What we collect, why, and how to check us.
This page states what we collect and why, how consent binds every check, where processing happens, how the system is secured, and how any report we have issued can be authenticated. It is written in plain language, for careful readers.
What is collected, why, and for how long.
FAEFACT is designed around the Digital Personal Data Protection Act. The obligations are not retrofitted; the system was built with them in place. The account below is given in plain language first, legal language second.
| WHAT IS COLLECTED | WHY | FOR HOW LONG |
|---|---|---|
| Identity documents & liveness capture | To confirm the document is real, current, and held by the person presenting it. | For the retention period stated in the consent record, then removed. |
| Records returned by authoritative sources | To establish the specific facts the requester is entitled to check. | Not retained beyond the check. The finding persists; the raw record does not. |
| Consent records | To prove that consent existed before processing began. | For as long as the report they authorise exists. |
| Sealed reports & audit entries | To preserve what was checked, when, against what, and with whose consent. | For the retention period the engagement defines. |
The subject’s rights
The person being verified holds these rights. We state each plainly; the Act’s term for it follows.
You can ask what we hold about you, and we will show you.
RIGHT TO ACCESS INFORMATION
You can have inaccurate data corrected, and data that is no longer required erased.
RIGHT TO CORRECTION AND ERASURE
You can withdraw consent at any point. Processing stops, and the withdrawal is recorded.
WITHDRAWAL OF CONSENT
You can raise a grievance, and we are obliged to answer it.
RIGHT OF GRIEVANCE REDRESSAL
You can nominate another person to exercise these rights on your behalf.
RIGHT TO NOMINATE
The Act is the Digital Personal Data Protection Act, 2023. Where this page and the Act could be read differently, the Act prevails.
No consent, no verification.
Consent is obtained before processing, referenced in every report, and revocable. Each of those three words is structural, not aspirational.
OBTAINED FIRST
The subject grants consent before any check opens. The system has no path that begins without it.
REFERENCED ALWAYS
Every report carries the identifier of the consent that authorised it. Report and consent are one record; neither stands alone.
REVOCABLE
The subject can withdraw consent. Withdrawal is written to the same trail as the grant, and processing stops.
A verification without consent does not exist in our system, by design.
Sensitive data is verified without external exposure.
A verification request enters the boundary carrying two things: the claim and the subject’s consent. Checks against authoritative sources run inside. What leaves is the sealed finding — not the records it was checked against. The diagram below is the architecture, plainly labelled.
SUBJECT
The person being verified. Presents a claim; grants consent before anything runs.
CONSENT RECORDED FIRST
FAEFACT BOUNDARY
Checks run here, against authoritative sources, inside the boundary.
RAW RECORDS DO NOT LEAVE
SEALED REPORT
What leaves the boundary. The finding — not the records it was checked against.
SIGNED · TIMESTAMPED · TRACEABLE
SUBJECT
The person being verified. Presents a claim; grants consent before anything runs.
CONSENT RECORDED FIRST
FAEFACT BOUNDARY
Checks run here, against authoritative sources, inside the boundary.
RAW RECORDS DO NOT LEAVE
SEALED REPORT
What leaves the boundary. The finding — not the records it was checked against.
SIGNED · TIMESTAMPED · TRACEABLE
How the system is secured.
Three mechanisms carry the security of the system. Each is stated structurally: what it does, and what it makes impossible.
S-01
Encryption
Data is encrypted in transit and at rest. Keys are held and rotated separately from the stores they protect, so access to one is not access to the other.
S-02
Access controls
Access is role-scoped and least-privilege. A person sees what their function requires and nothing else, and every access is attributable to a named account.
S-03
Audit logging
Every read, write, and disclosure is written to the same append-only trail that seals reports. Entries are timestamped and cannot be edited after the fact.
CERTIFICATIONS
This section lists certifications as they are obtained, and not before. An audit in progress is not a certification held, and it will not be presented as one. When a certification is granted, it appears here with its scope and its date.
Authenticate any report by its ID.
Every report we issue carries a reference ID on its first page. Any FAEFACT report can be authenticated against our records by that ID. A forged report fails this check. Today the check runs by correspondence: send us the ID, we run it against the record, and we reply with the finding. This page does not simulate a result.
The report ID is printed on the first page of every FAEFACT report.
This page is revised as the system is revised. Questions from legal, security, and compliance reviewers are welcome.
Talk to the Team →