Funding applications
A lender receiving a Mothusi-generated funding pack can verify that the evidence inside has not been altered between the export and the review.
Mothusi holds sensitive evidence about real businesses, real people, and real money. The data-governance posture is designed for the audit teams of programmes, banks, DFIs, and government partners who need it to survive their own compliance reviews.
POPIA-compliant. GDPR-compatible. SOC 2 and ISO 27001 audits underway.
Each principle is operational, not aspirational. Programme officers, funders, and operators can verify each one against the live platform.
Every business has a single growth record. The operator can view, export, and request deletion of their data at any time. The record follows the business, not the programme.
Programme officers see operators in their cohorts. Funders see operators who have explicitly shared with them. Mentors see operators they are assigned to. No blanket access by default.
All data is encrypted in transit (TLS 1.3) and at rest. Sensitive evidence (banking, identification, contracts) carries additional field-level encryption.
Production deployments can be hosted in the data-residency region required by the institutional partner. Default is Azure South Africa for African deployments; other regions on request.
Every change to an operator's record is logged: who, when, what changed. Audit logs are retained per the partner's compliance requirement.
Operator data is not used to fine-tune underlying AI models. Mothusi uses retrieval and context engineering, not retraining. Bespoke arrangements require explicit contracted consent.
Status reported honestly per certification. "Current" means active compliance today; "targeted" means audit underway; "in-progress" means active remediation work.
Active compliance with the Protection of Personal Information Act for South African operators.
EU data residency available; data subject rights honoured for EU operators.
Certification audit programme initiated; expected completion 2026.
Audit programme initiated; expected completion 2026.
Accessibility audit in progress against the public site and operator app.
TLS 1.3 in transit. AES-256 at rest. Field-level encryption on sensitive evidence types.
Microsoft Azure infrastructure with regional residency options. Multi-zone failover.
Institutional buyers do not just need data. They need data they can prove was not altered. Every signal in a Mothusi growth record is hashed at creation and chained to the prior signal. The record exports with a signed manifest. Third parties can verify the integrity of the record without ever contacting Mothusi.
Every signal written to a growth record is cryptographically hashed at the moment of creation. The hash captures the signal content, the timestamp, the source, and the operator identifier.
Each operator's record maintains a linked hash chain. The hash of each new signal references the prior hash, so the entire record forms a verifiable sequence. Any insertion, deletion, or modification breaks the chain in a detectable way.
When an operator or programme exports a growth record (for a funding application, an audit, or a board review), Mothusi attaches a signed manifest containing the full hash chain and the platform's public key.
Any third party can verify the manifest against the public key without contacting Mothusi. The record stands on its own as a citable, audit-grade artefact.
A lender receiving a Mothusi-generated funding pack can verify that the evidence inside has not been altered between the export and the review.
A donor reviewing programme outcomes can verify that the reported member-level evidence is the same evidence the platform captured at the time.
A buyer evaluating a supplier, an insurer assessing risk, a regulator inspecting compliance - each can read the same record and trust the integrity of the data.
When a member exits a programme or moves between deployments, their full growth record exports with the integrity proof intact. The record follows the business.
An operator on Mothusi has the right to view every signal captured about their business, export the full growth record in a portable format, request correction of specific evidence, request deletion of specific data, and revoke access for any third party (programme, mentor, funder) at any time.
These rights are not optional or contingent on programme participation. They survive programme exit. They survive lender disengagement. The record follows the business.
Where the operator is participating in a programme that requires data retention for audit purposes, the retention obligation is named in the programme terms, the retention period is finite, and the operator is notified at programme entry.
Mothusi maintains a documented incident response process covering detection, containment, eradication, recovery, and post-incident review. Institutional partners receive notification of incidents affecting their operators within the timeframes required by their data-processing agreement.
Where an incident affects the integrity of operator evidence (corrupted records, mistaken signals, unauthorised access), the operator is notified, the record is restored from audit trail, and the corrective action is documented in the affected growth records.
A current security and data-handling briefing is available to institutional procurement teams on request.
Data and security is one of four trust pillars. The others are responsible AI, methodology governance, and open citation.
From business support to measurable enterprise development. Across sectors, countries, and real operating environments.