We collect only the personal data described below. Fields that might seem natural to add — a beneficiary's date of birth, gender, ethnicity, religion, or health information — are deliberately excluded unless a specific, documented purpose and, where required, explicit consent exists. This is a design rule built into the operations platform itself, not just a policy statement.
7.1 Beneficiaries
- Full name
- Cohort assignment and enrollment date
- Status in the program (prospective, active, completed, placed, inactive, or withdrawn)
- Community or area served (used for aggregate reporting, not to pinpoint an individual's home)
- Contact email and phone number (optional, collected only where useful for program communication)
- Consent to public sharing — a specific yes/no flag, defaulting to no (see Section 9.2)
- Internal case notes (staff-only, never shown outside the Academy)
- Outcomes — dated records such as course completions, certifications, internship starts, employment, freelance income, or venture starts, each with a short description
- Where the employer pathway applies: placement records (organization, role, start/end dates, and periodic confirmation that a placement is still current)
- Any physical assets assigned to them (e.g., a laptop), for accountability purposes only
7.2 Donors
- Name (or “Anonymous,” which is an accepted and respected choice)
- Donor type (individual, organization, corporate, diaspora, or anonymous)
- Contact email (optional)
- Donation records: amount, currency, date received, and an optional bank/transfer reference
- In-kind donation records: category, description, quantity, and an estimated value used for recognition and reporting only — never added into the Academy's cash totals
- Internal notes (staff-only)
- A future public-recognition consent flag, once the donor portal is built (see Section 9.3), governing whether a donor's name may ever be shown publicly
7.3 Partner organizations
- Organization name and contact email
- Relationship flags: whether the organization hosts interns, hires graduates, is a formal partner, and/or is linked to a donor record
- A public-naming consent flag (“is_public”), defaulting to no, governing whether the organization's name or logo may appear publicly (see Section 9.4)
7.4 Staff, program staff, finance staff, mentors, and volunteers
- Name and login/account information
- Role assignment (which determines system access, per Section 6.3)
- For mentors: which beneficiaries they are assigned to mentor
- Records of who logged a given outcome or record, for accountability
7.5 Website and donor-portal visitors (future, Section 17)
- Standard web analytics (pages visited, general location by IP, device/browser type) — collected in aggregate, not tied to an identified individual, unless the visitor creates a donor account
- Contact-form submissions (name, email, message)
- For registered donors: login credentials and account activity
7.6 We do not collect
- Date of birth, age, gender, ethnicity, religion, or health information about beneficiaries, unless a specific purpose arises — in which case this policy's sensitive-data safeguards (Section 9, Section 16) apply before collection begins
- Government identification numbers, unless a specific legal or financial requirement (e.g., a grant acquittal report) requires it, and only with a documented basis
- Any payment card or bank account credentials — donation records capture only the amount and an optional reference, never card numbers or account credentials