Security
The trust primitive is provenance, not opinion
What Kybex claims, what it does not, and how your data is protected.
What we vouch for
Kybex makes narrow claims about your documents and makes them checkable.
Every file is fingerprinted
Each upload is hashed with SHA-256 the moment it arrives. The fingerprint travels with the document, so a recipient can confirm the file they received is byte-for-byte the file that was uploaded.
Versions, never overwrites
Re-uploading creates a new version. Earlier versions stay intact, which is what makes “unaltered since this date” something we can stand behind.
A history that cannot be quietly edited
Uploads, edits, shares, every opening and download of a share, requests, account changes and internal support access are written to an append-only log whose entries are linked to each other. Altering or removing one is detectable. The log holds no personal content and no IP addresses.
What we do not vouch for
Kybex does not verify that a value is true. A value marked “confirmed” has been confirmed by the account holder, and institutions are told so beside every value. An organisation marked “Confirmed by Kybex” has had its identity checked by our team; that is not a licence or an endorsement.
How your data is protected
Accounts are separated in the database
Each account's data is kept apart from every other's by access rules inside the database, not only by the application. A person, a company, an institution and the Kybex team each reach only what their kind of account is for, and the application and the database enforce it independently.
Identity numbers are encrypted before storage
National ID, BVN, passport and similar numbers are encrypted with a key held outside the database. Most screens show only the last four characters. Revealing a full number is logged.
Private storage
Documents are held in private storage and are never publicly addressable. Recipients only ever receive short-lived download links issued per file, and each issue is recorded.
A code from outside the session for destructive actions
Deleting an account needs a code sent to your email and entered in the app, so a stolen, open browser session cannot wipe a vault. The check is made by the database. Deletion then waits 21 days, with reminders and a one-click cancel.
Encryption in transit and at rest
All traffic is encrypted, and stored data is encrypted at rest by our infrastructure providers, who are listed on the Subprocessors page.
Control over what leaves
Scoped, expiring, withdrawable shares
A share carries only what the sender selected, expires (30 days by default), and can be withdrawn at any time. A share link resolves to that share and nothing else. Expired, withdrawn, held and unknown links all give the same neutral answer.
Links that cannot be passed on
A share can be limited to the first person who opens it, or to an institution that is signed in. The first opening is claimed by an explicit click, so mail scanners do not use it up. The sender sees when it was claimed and can release or withdraw it.
You are asked before you share with a stranger
Before anything goes to an organisation Kybex has not confirmed, or to a bare email address, the sender must say they know who it is, and is shown what is being sent, including whether it contains ID documents.
Every opening is recorded for you
You can see when each share was opened, how many times, by which institution if it was signed in, and which files were downloaded. We do not keep the visitor's address.
How we run it
Auditable internal access
The Kybex team cannot read a vault by default. Opening one needs a recorded grant with a stated reason, and it appears in your history. The team itself is invited, held to roles, and audited.
We attack it ourselves, and publish what we found
In October 2026 we ran a full adversarial review of the platform, working as an outsider with only a browser and a free account, as someone holding a leaked share link or API key, and as someone with a stolen session. It found 27 weaknesses, including one critical: a new account could have claimed another organisation's identity. Every critical and high-severity finding was fixed and re-checked against the live site. The attacks that worked became permanent tests: 154 database-level attacks run on every change, adding a table, function or permission fails the build until a person has reviewed it, and probe scripts run against the production site itself. The review also recorded what it did not test, so a gap is never mistaken for a pass.
What we have not done yet
This was our own adversarial testing, not an independent audit. A few findings remain open and tracked (for example a stricter browser content policy, and a cap on automated document-reading cost), and we have not yet commissioned an independent penetration test. We will not describe the platform as independently certified until one has been done.
Your data is yours to take or erase
Settings → Your data downloads everything you hold, and lets an owner delete the account. See the Privacy Policy for what is kept afterwards.
Reporting a vulnerability
Write to security@kybex.io. Test only against accounts you own, do not access anyone else's data or degrade the service, and give us a reasonable time to fix before you disclose. We will acknowledge your report and keep you informed.
See also the Subprocessors, the Privacy Policy and the Data Processing Addendum.