POPIA compliance
The Protection of Personal Information Act asks every organisation to guard personal information, and to be able to show that it does. vFileLock and POPIA Bridge turn several of those duties into working controls and evidence.
vFileLock supports your compliance. It does not replace your own duties. Compliance also needs your policies, your Information Officer and your people.
Four things vFileLock adds
A check before every share
A record of every event
A view for your Information Officer
Evidence for breach handling
POPIA's conditions, and what supports them
POPIA sets eight conditions for lawful processing. This table shows what vFileLock and POPIA Bridge add to each. Where nothing is listed, the duty stays with you.
| Condition | POPIA sections | What vFileLock and POPIA Bridge add | What stays with you | Status |
|---|---|---|---|---|
| 1. Accountability | 8 | A record of every lock, share, approval, open and refusal, with the person, the time, the IP address and the device. An Information Officer's view over all of it. | Appointing responsible people, and your policies. | Live |
| 2. Processing limitation | 9 to 12 | A share goes to one named person, for a set time and a set number of opens, view only by default. The policy check is told only what it needs: never the recipient's full address, never the file. | Your lawful basis for processing, and consent where it is needed. | Live |
| 3. Purpose specification | 13 and 14 | Every share that needs approval carries a purpose, kept in the record. Locked files leave when their last share ends, and never later than the level allows. Planned your Information Officer sets how long the record is kept at each level. | Deciding the purpose, and your retention schedule. | Live with a planned step |
| 4. Further processing limitation | 15 | Forwarding is blocked: a forwarded link does not open, and the attempt is recorded. Lowering a level needs approval. | Deciding when a new use fits the first purpose. | Live |
| 5. Information quality | 16 | The fingerprint of every locked file is recorded, so a file can be shown to be the one that was shared. | Keeping the information itself complete and correct. | Live |
| 6. Openness | 17 and 18 | Recipients see who sent the file, its label and the terms before they open it. | Your records of processing, and telling people when you collect their information. | Live |
| 7. Security safeguards | 19 to 22 | Files locked on the device, a split key, six levels with forced rules, clearances and approvals. A tamper-evident record that anyone entitled can verify. Breach attempts recorded as such. | Your wider security measures, your agreements with operators, and notifying the Regulator and the people affected. | Live |
| 8. Data subject participation | 23 to 25 | When a person asks who saw their information, your Information Officer can answer from the record: who opened which file, and when. | Receiving and answering the request, and correcting information. | Live |
Special personal information and children
POPIA sets stricter rules for special personal information, such as health and criminal records and biometric information (sections 26 to 33), and for children's information (sections 34 and 35).
- When you lock a file you choose its POPIA category: personal information, financial, contact details, health, criminal record, biometric, children's information, or no personal information.
- Health, criminal record, biometric, children's and financial information always get the rules, whatever a person's switch says. Your organisation can add its own categories.
- For special personal information, POPIA Bridge asks for approval by default.
- If the check cannot be reached, a file with personal information is not shared. The owner is asked to try again.
The records
- Every event is recorded: lock, level change, share, approval, code sent, wrong code, terms accepted, open, refused open, forward attempt, revoke, extend, burn and expiry.
- Each entry holds the time, who acted, the IP address and device, the file's type, size, level and category, the fingerprint of the locked file, the outcome and the reason.
- Each file has its own hash chain. Changing or deleting an entry breaks it. The newest entry of every chain is lodged in POPIA Bridge's own record.
- The record itself is careful with personal information. The recipient's address goes in masked, with a keyed hash. Keys, codes and file contents never go in.
- Reading the record is recorded too.
Supports: accountability, security safeguards, and a person's right to know who accessed their information.
The Information Officer's view
POPIA gives the Information Officer the job of making sure the organisation complies (sections 55 and 56). vFileLock gives that person a place to work from.
- Every document flow in your organisation, filtered by person, owner, level, kind of file, POPIA category, event, dates and file.
- Exports as CSV and JSON with the chain check, so an auditor can recheck the chain from the export alone.
- The approvals queue, for the shares your rules send to the Information Officer.
- The list of breach attempts.
- A chain-of-custody export for any document.
Planned as a signed PDF. - Named auditors can read the same records, except Top Secret, and change nothing.
Supports: accountability, and the Information Officer's own duties.
Breach handling
Section 22 of POPIA asks an organisation to notify the Regulator and the people affected when there are reasonable grounds to believe personal information was accessed without authority. vFileLock helps you find out fast, contain it and prove what happened. The notification itself stays with you.
Detect
Breach attempts are recorded as such: the wrong clearance, a share the rules do not allow, a person who is not the named recipient, a second device, a forwarded link. The owner gets an e-mail on forward attempts and lockouts, and your Information Officer sees the breach list.Contain
The owner revokes or burns the share at once. The key half is destroyed, so every copy of the link is dead. Raising the file's level ends any share that breaks the new level.Assess
The record shows who opened which file, when, from which IP address and device, and every attempt that was refused. The chain check shows that the record itself was not changed.Notify
You decide whether the Regulator and the people affected must be told, and you tell them. The exports give you the facts to put in the notice.Follow up
The chain-of-custody export gives HR and your lawyers the evidence. The classification policy, which every person has acknowledged, says plainly that every action is recorded.
Planned a legal hold that stops deletion while a matter is open.
Where your information is
- vFileLock runs in South Africa, on VOIMAR's own network. No foreign cloud.
- Each organisation is its own tenant. Nothing reads across tenants.
- VOIMAR's servers hold locked files only. VOIMAR never sees what is inside a file.
- Planned the country of each open recorded, and a rule that limits opens to South Africa or to a list of countries. POPIA has its own rules for sending personal information outside South Africa (section 72), and those decisions stay with you.
What stays with you
No product makes an organisation compliant on its own. These remain your own duties:
- your privacy policy, and your lawful basis for processing;
- registering your Information Officer with the Information Regulator;
- telling people when you collect their information, and answering their requests;
- your retention schedule, and the records the law requires you to keep;
- your agreements with operators and other third parties;
- notifying the Regulator and the people affected after a security compromise;
- training your people.
vFileLock makes that work visible and provable. More on POPIA Bridge.
See vFileLock with your own files and rules
Bring your Information Officer, your security officer and your IT lead. Or open vFileLock and lock your first file.
