Where your data lives, and who can see it.
Impact Kompass holds data about real people, often vulnerable ones. Every organization is isolated, access is checked in the database itself, and every sensitive view is recorded.
Funders see totals. Field teams see names. Sensitive fields need a grant.
| Tier | Funder | Board | Program staff | Data steward |
|---|---|---|---|---|
| Public totalsHeadline figures you choose to publish | Can see | Can see | Can see | Can see |
| Internal totalsBreakdowns for staff, management and the board | Cannot see | Can see | Can see | Can see |
| Names and contactsOnly within assigned programs | Cannot see | Cannot see | Can see | Can see |
| Sensitive fieldsDisability, income, ID numbers: only with a grant | Cannot see | Cannot see | Cannot see | Can see |
How it is enforced
- Its own database
- Each organization has its own database, sign-in and file storage, in a region it chooses. Nothing is pooled.
- Checked on every row
- Row-level security in the database checks role, program and sensitivity before any row is returned, whatever screen asks.
- Encrypted identifiers
- National ID, bank and mobile-money numbers are encrypted at rest, with a keyed hash kept only for matching duplicates.
- An audit log
- Every view of names or sensitive fields, every export, publish, merge and permission change is recorded with who and when.
- Backups and exit
- Daily backups per organization, a full export at any time, and deletion of the database when an organization leaves.
Compliance
Impact Kompass is designed to support the obligations of the GDPR and Ghana's Data Protection Act, 2012 (Act 843): access by need, consent recorded per person and scope, export and deletion on request, and a data processing agreement with every organization.
It runs on Supabase and Vercel, which hold SOC 2 Type 2 and ISO 27001 certifications. Impact Kompass holds no certification of its own.