Compliance
How Nzinga meets one strict standard wherever members live, and which parts are in place or still planned.
One standard, local modules
Nzinga is jurisdiction-neutral by design: one strict common standard everywhere. Requirements that differ by country are handled by modules, each reviewed by local counsel before launch there.
Nothing on this page is legal advice or a legal conclusion. It says what is in place and what is planned.
Consent on record, per item
Every recording carries a consent record for each speaker: the choice, the exact text shown, by version and SHA-256, the time and the app version.
An audit log of access
Every access to recordings and consent records is to be logged, append-only, so auditors can see who looked and why.
Impact assessment before launch
A data protection impact assessment and a record of processing are completed before any external member records.
Breach notice within 72 hours
If a breach puts members at risk, we tell the people affected and the relevant authority within 72 hours of finding it: what happened, and what to do.
Planned. A written breach response plan and a named data protection contact come before external members join.
Export and deletion requests
Requests are answered within a published time. Today, export is a button in the app, and a deletion request is completed within 30 days.
Independent security review
An independent security review and penetration test happen before any public launch. Until then, the app runs as a demo and an internal pilot.
Identity verification
We verify only as much as each action needs, rely on partners who already verify people, and never store ID documents.
We do not store voiceprints. Any speaker-consistency check runs on the phone where possible and keeps only a match result. Voice is never used to identify people, and nothing biometric is ever sold.
Age. Adults only. Planned: declared at sign-up and confirmed by the payout check. Recordings with children’s voices are excluded.
Calls. Not built yet. When they are, everyone recorded is a signed-in member who agreed for that call. Non-members are never recorded.
Later. Privacy-preserving credentials, so a member can share “over 18” or “identity checked”, never the document.
Status at a glance
To report a concern, open an issue on GitHub or contact the team.