Skip to main content
LLDPS Africa
Data Governance

How we govern your data.

LDPS Africa runs on producer data. The principles below describe how that data is owned, scoped, used and eventually deleted. They are enforced in code — not just in policy.

Customers own their operational data

KPI records, feed purchases, audits and financial entries you upload belong to you. We process them on your behalf to run the platform. You can export or delete them on request.

Aggregated benchmarks are de-identified

Benchmark bands and industry averages are computed from cohort percentiles. No band, average or industry counter exposes a single customer’s data. Cohorts below a minimum size threshold are suppressed rather than published.

Access is scoped by role and organisation

Row-level security restricts every read and write to the authenticated user, their organisation, or — for background jobs — a narrow service role. Cross-organisation reads are technically impossible from the customer surface.

Sensitive operations are auditable

Role changes, audit runs, KPI snapshots and financial ledger entries are written to append-only operational logs with before/after state. This trail underpins our investor and compliance reporting.

AI is grounded, not generic

Our AI advisory only consumes the customer’s own KPIs, benchmarks and audit findings. Customer data is not used to train third-party foundation models. Prompts and outputs are logged per organisation.

Deletion is real

On account deletion we remove personal data and either delete or irreversibly aggregate operational data within 30 days, subject to legal retention obligations. We confirm completion by email.