Document the processing
Record personal information categories, purposes, sources, sharing, retention, and safeguards.
Compliance / South African POPIA
POPIA work is a processing condition record, not a policy cover page.
We build private workflows that help organizations map personal information, processing conditions, operator agreements, information officer records, and breach response evidence into review-ready files. The workflow prepares the record; the client and its advisers make the legal call.
Information mapOperator recordsBreach fileRegulator review
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
Where POPIA work loses time
The condition follows the processing.
The recurring work is connecting each processing activity to its purpose, legal basis, safeguards, operators, and the records that support the position.
Keep the agreement record
Organize operator agreements, information flows, and review dates for the responsible owner.
Prepare the incident file
Assemble facts, risk notes, notification drafts, and follow-up for review.
The POPIA boundary
The system prepares the record. It does not register or declare compliance.
Official routes stay official
Information Regulator communications, registrations, and filings remain with the organization and its advisers.
Advice stays expert
Applicability, conditions, and enforcement questions remain with the client and its advisers.
No automatic notification
Regulator and affected-person notifications remain explicit human decisions.
A first POPIA workflow
Start with one processing activity or incident type.
Choose the activity
Pick one process, system, or incident family with a clear owner.
Map the record
List the information, purposes, sharing, retention, operators, and safeguards.
Run the evidence check
Compare current records with the defined fields and review missing or stale items.
Build the review pack
Prepare the summary, source index, and open questions for the responsible owner.
POPIA preparation is easier when the processing, operator, and safeguard are one record.
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Common questions.
Does this make us POPIA compliant?
No. It organizes information and evidence. Applicability and compliance stay with the client and its advisers.
Can it file with the Information Regulator?
No. It prepares the evidence and draft. Registration, filing, and regulator communication stay with the organization.
How is this different from the LGPD page?
That page covers Brazilian LGPD records. This page is specific to South African POPIA processing conditions and regulator evidence.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the activity
Which POPIA record is hardest to keep current?
Tell us the processing activity, the operators, and the review owner. We will scope the first workflow around the records you already hold.