Who is responsible
The approved controller identity, registered address, Data Protection Officer where appointed, and supervisory-authority contact will appear in the production notice.
This page explains the privacy controls built into adiNGO. The organisation-specific legal notice is currently pending formal privacy-owner approval and must be published before real beneficiary data is collected.
The approved controller identity, registered address, Data Protection Officer where appointed, and supervisory-authority contact will appear in the production notice.
Each collection form must name a specific programme purpose and lawful basis. Optional research and communications are kept separate from essential service processing.
adiNGO is designed to collect the minimum profile, eligibility, programme-delivery, financial, volunteer, or partner information needed for the stated purpose.
Access is limited by role, organisation, programme, geography, ownership, and sensitivity. Approved processors and international transfers must be listed in the production notice.
Retention starts from a documented event and follows an approved schedule. Legal holds, safeguarding duties, disputes, or finance rules may require limited continued retention.
Depending on the applicable law and processing basis, you may request access, correction, deletion, restriction, portability, objection, or human review of an important automated decision.
This demonstration text is not the final GDPR notice. Controller identity, jurisdiction, lawful bases, Article 9 conditions, recipients, transfers, retention periods, complaint routes, children’s information, and local-law obligations require authorised legal/DPO approval.