Legal
Privacy Policy
Effective date: 5 November 2026
Data Protection Officer (DPO) Appointment & Contact
In compliance with the Nigeria Data Protection Act (NDPA), the Di Badili Leadership Sustainability Initiative (Operating as DiBadili Institute, also known as Become Change Institute) has appointed a designated Data Protection Officer to oversee our data privacy strategy, monitor compliance across all our platforms (including becomechange.institute, anda.becomechange.institute, neurafiki.becomechange.institute, craftframework.becomechange.institute, devmapper.africa, abiolaoshunniyi.lovable.app, paulineabiolaoshunniyi.lovable.app, africatradeconnect.com, and africa-trade-connect-tech-stack.vercel.app), and serve as the primary point of contact for data subjects and regulatory authorities.
If you have any questions about this Privacy Policy, wish to exercise your data privacy rights (such as data access, correction, restriction, or deletion), or have a complaint regarding how we handle your personal information, please contact our DPO directly:
- Name of DPO: Abiola Oshunniyi
- Designation: Data Protection Officer (DPO)
- Mailing Address: P.O. Box 2550, Festac Town, Lagos, Nigeria.
- Official Contact Email: dpo@becomechange.institute
- Contact Phone Number: +2348188466444
Our DPO will review and respond to all valid requests, inquiries, or grievances within the statutory timelines provided under Nigerian data protection laws.
1. Who we are and our role
CRAFT is operated by the Di Badili Leadership Sustainability Initiative (Operating as DiBadili Institute, also known as Become Change Institute), P.O. Box 2550, Festac Town, Lagos, Nigeria (“we”). For your account (name, email, sign-in and security records) we are the controller. For the information an organisation puts into its workspace — assessments, findings, plans, evidence and reports — the organisation is the controller and we act as its processor under our Data Processing Terms.
We are registered with the Nigeria Data Protection Commission (NDPC), registration number NDPC/DPC/15933.
Our Data Protection Officer is the contact for all privacy matters: dpo@becomechange.institute (see the DPO section above).
2. Data we collect
- Account data: name, email address, organisation memberships and roles.
- Security data: sign-in session records, multi-factor sign-in status (the authenticator secret is encrypted; recovery codes are stored only as one-way hashes), rate-limit counters and audit-log entries (who did what, when, and the IP address and browser type of the request).
- Workspace data: assessment responses and scores, findings, corrective actions, plans, budgets, ESG report checks, organisational design reviews, health-security assessments, regulatory source checks and uploaded evidence.
- Directory and validation data: if you create a validator, firm, funding-partner or organisation profile, the details you choose to publish in the directory; engagement records (who invited whom, consent, named team members, signed independence declarations); the scores, comments and outcome of an independent validation; ratings and comments given about a validator; and concerns reported from a public verification page, with the contact details the reporter chooses to give.
- Screening: when an organisation runs exclusion, debarment and sanctions screening, the names it enters (the organisation, its leaders and partners, with any country, birth year or registration number given) are checked inside CRAFT against the official UN, US, EU and UK sanctions lists, which CRAFT downloads; the names are not sent to anyone. Clear cases are decided by written rules (for example, a different country or birth year) and shown with the rule; a person can overturn any of them, and similar names with nothing else to go on are decided by a person. Results, decisions and manual checks of debarment lists are kept with the organisation's records.
- Awards and issues: the grants and contracts an organisation records, measures a funder applies to them, and issues raised about the organisation (for example audit findings or funder visit findings), with the organisation's own responses. The funder named on an award can see that award and the issues on it. No one else outside the organisation sees its issue history unless the organisation shares it with a named person, as a summary (counts and time to fix) or in full. Issues not marked verified are never shared, and the organisation can stop sharing at any time.
- Support data: messages you send to the support assistant (redacted before storage) or through the contact form, with the name, organisation and email you give; and our replies and internal notes on your request. They are kept, encrypted, in our internal support tracker, which only our Super Admin can open.
- Usage data: how far each account has got with setting up and using the platform (for example which onboarding steps are done and when you last signed in), kept in our own database; and, only if you agree, anonymous browsing analytics from PostHog (see “Product analytics and session replay”).
- We do not collect payment card data, and we do not use advertising trackers.
3. How we use it and our lawful bases
| Purpose | Lawful basis |
|---|---|
| Provide the service: sign-in, workspaces, scoring, reports, exports | Contract with you or your organisation |
| Security: authentication, multi-factor sign-in, rate limiting, audit trails, fraud and abuse prevention | Legitimate interests and legal obligations to secure personal data |
| Transactional email: invitations, reminders, scheduled reports, escalations | Contract; legitimate interests |
| Optional product analytics of support-chat events | Consent (off unless you opt in) |
| Product analytics and session replay on public pages (PostHog, EU) | Consent (off unless you accept; separate choice for replay; withdraw at any time) |
| Error monitoring (Sentry, EU): scrubbed technical error reports that contain no personal data | Legitimate interests in finding and fixing faults and keeping the service secure and reliable |
| Super Admin analytics of onboarding progress, funnels and activity, and “finish setting up your workspace” reminder emails | Legitimate interests in helping new organisations complete setup and in running the service; you can opt out of the emails with one click |
| Lifecycle emails (a nudge to start your assessment, a one-month feedback request, check-ins, and milestone and anniversary messages) and the feedback survey | Legitimate interests in helping organisations get value from CRAFT and in improving it; you can switch off each kind with one click |
| Newsletter about CRAFT and DiBadili Institute programmes and services, including new services we are developing and news and offers from our partners | Consent (only if you subscribe; withdraw at any time) |
| Answering requests and complaints; meeting legal duties | Legal obligation; legitimate interests |
4. Analytics we run ourselves, and setup reminders
Our Super Admin team can see aggregate and per-account figures computed from CRAFT’s own database: which onboarding steps an account has completed, where sign-ups stop, and recent activity such as sign-ins and the date work was last saved. No third party receives this data, and it is used to support organisations and improve the service, not for advertising. Our lawful basis is legitimate interests. It is limited to Super Admins and covered by the audit trail. To learn what people look for in the directory and can't find, we also keep the words typed into directory searches (without recording who searched) and counts of profile views.
If an account has not finished setting up its workspace we may occasionally send a “finish setting up your workspace” email. It is sent through our email provider listed on the Sub-processors page, contains no assessment content, and includes a one-click link to stop these emails. Using the link does not affect your account or any security or service email.
Lifecycle emails. After you finish setting up your workspace we may send you a small number of emails from the CRAFT team: a reminder about two weeks later if your organisation has not started its readiness assessment; a request for feedback after one month; a message at three months, six months, one year and every six months after that, marking how long your organisation has been on CRAFT (these show counts from your own workspace, such as assessments completed or documents in your Data Room, and are sent to the person who set the workspace up or, if they have left, to the organisation’s administrator); and, if you have not signed in for 30 days or more, an occasional check-in (at most one every 90 days). We never send more than one of these to you in any 14 days, and only on Tuesdays to Thursdays. They are sent through our email provider listed on the Sub-processors page and are signed by the CRAFT team; replies go to our communications inbox.
How to opt out. Every one of these emails has an Unsubscribe from these emails link that works without signing in (you confirm with one click on the page it opens), and a link to your email preferences page, also reachable from Settings when you are signed in. There are two categories you can switch off independently: Check-ins and feedback (the two-week nudge, the one-month feedback request and check-ins) and Celebrations (milestone and anniversary messages). Welcome, invitation, security and validation emails are service messages and are not affected. To measure whether these emails help, the buttons in them go through a link on our own site that records that the link was used; we do not use tracking pixels or any third-party tracking in email.
The feedback survey. The one-month email (and our anniversary emails) link to a short survey with a personal link that works without signing in, expires after 60 days and can be answered once (you can change your answers for 24 hours). It asks how likely you are to recommend CRAFT, how easy it has been to use, what you have used most, one thing to improve, and whether you would like a 20-minute call. Answers are stored in our database and are seen only by the Super Admin team, who use them in aggregate (for example a Net Promoter Score) and to follow up. If you ask for a call, we email your name, email address, organisation and preferred times to our communications inbox so that we can arrange it; nothing else from your answers leaves our database. Our lawful basis is legitimate interests in improving the service. You can ask us to delete your answers by contacting our Data Protection Officer at dpo@becomechange.institute.
5. Newsletter
If you choose to subscribe, we use your name and email address to send our newsletter about CRAFT and DiBadili Institute programmes and services, including new services we are developing and news and offers from our partners. Subscribing is a separate choice: the box is never ticked for you and you do not need it to use CRAFT. We keep a record of when you subscribed and the wording you agreed to. Every newsletter has an unsubscribe link, and you can also unsubscribe by emailing dpo@becomechange.institute; we stop as soon as you do. We send the newsletter ourselves: we never sell your details, and we never give them to a partner or anyone else for their own marketing unless you separately agree.
6. Product analytics and session replay (PostHog, EU)
Only if you choose Accept analytics (or turn on Product analytics under Choose) we use PostHog, hosted in PostHog’s EU cloud, to understand which public pages are used and where visitors get stuck. Nothing is loaded from or sent to PostHog before you choose, and Reject is as easy as accept. Your choice, its date and the policy version are stored in your browser (craft_consent) and we ask again when this section changes. If your browser sends a Do Not Track or Global Privacy Control signal we treat it as a rejection.
Where it applies. Only the home and other public information pages, sign-up and sign-in, onboarding (step names only), the directory and profile pages, training (module and exam progress), public validation pages, policy pages, and the help and guide pages. Recording stops as soon as you move into any other page.
Never recorded. Assessments and scoring, evidence, the data room, findings and corrective actions, reports and dashboards, engagements and reviews, evidence requests, referrals and badges, validations you manage, the review panel, workspace (/app) pages, administration, settings, vaults and finance pages. On these pages we send no page views, clicks, replays, heatmaps, errors or performance data. The only thing sent from them is a small content-free milestone such as “engagement created”, with no organisation, name, identifier or address.
What is collected on the pages above. Page views and page leaves (address without any query string), clicks as element positions (button and link text and attribute values are masked), heatmaps, front-end error messages and stack traces (with query strings and email addresses removed), page-speed measurements (Web Vitals), your browser, device type and approximate country, and funnel milestones such as signed up, onboarding step completed, validator profile created, training module completed, exam started/passed/failed (no answers), engagement created, and directory searched (the kind of profile and whether anything matched, never what you typed).
Session replay is a second, separate choice and is on only if you allow it. Recordings are anonymous screen replays of those pages. Everything you type is masked (including passwords and form fields), all text is hidden except on public information pages, images and canvases from uploads are blocked, and network requests, headers and bodies are not recorded.
If you are signed in, we identify you to PostHog only by a salted one-way hash of your account identifier, with three properties: role, country and language. We never send your email address, name, organisation name, scores, evidence, free text or any URL query string, and anonymous visitors are not given person profiles.
Storage and retention. PostHog keeps an anonymous identifier and session identifier in your browser’s local storage (keys beginning ph_); it sets no cookies. Events and recordings are kept for the retention period configured in our PostHog project and are then deleted automatically. We keep that period as short as is useful.
Withdrawing consent. Open Cookie & analytics settings in the footer of any page at any time and turn analytics or replay off, or press Reject. We then stop collecting, and your browser’s PostHog identifiers are deleted. To ask us to delete data already collected, contact our Data Protection Officer at dpo@becomechange.institute.
7. Error monitoring (Sentry, EU)
When something breaks in CRAFT, in your browser or on our servers, we send a technical error report to Sentry (Functional Software, Inc.), hosted in Sentry’s EU data region (Frankfurt), so we can find and fix the fault. This is based on our legitimate interests in keeping the service working and secure; because the reports contain no personal data by design, it needs no consent banner and is separate from the analytics choice above.
What a report contains. The type of error and where in our code it happened (stack trace), the page as a route pattern (for example /engagements/$id, never the identifiers, query string or fragment), your browser and operating-system type, the release of CRAFT and its environment, and a small sample of performance timings. Email addresses and long numbers are removed from any message before it leaves.
What it never contains. Your name, email address, account identifier or IP address; cookies, request headers (other than the browser type), request or form contents; scores, evidence, comments, findings or organisation names; session recordings, screenshots or on-page text. We do not use Sentry’s session replay, user-feedback or profiling features. Sentry also removes IP addresses and sensitive fields on its servers. Nothing is stored in your browser for this and no cookies are set.
8. Independent validation, the directory and public pages
Directory. Profiles are opt-in and show only what you enter. Validator emails and organisation contact details are not shown; profiles use a random identifier in their address.
Evidence access. A validator sees an organisation’s evidence only if named on the engagement, approved by the organisation, and after signing an independence declaration. Access is read-only, ends on a date, and is logged. When the review is finalised every team member’s access ends.
Public verification page. Anyone with a validation’s verification ID can see the organisation’s name and country, the rung and outcome, the validator’s name, firm and accreditation, the method and dates, the status, and the next verification point. An organisation may also choose to show its registration number, rung history, qualifications and a DevMapper link. Evidence, scores and comments are never shown. The statement PDF and the verification page carry the same facts. A copy of the page stays accurate only while you check it.
Ratings and feedback. After a validation is finished, the organisation (and the engaging funding partner, where there is one) may rate the validator once. A rating shows the party, the organisation’s country, the stars, the comment and any reply from the validator, not names or emails; we keep the rater’s email to enforce one rating per party and to deal with abuse. Feedback that is false, abusive or exposes personal data can be removed by the CRAFT programme team; the row and the reason are kept for the record. We also compute statistics from finished validations (for example how often a validator’s scores differ from an organisation’s self-assessment) to decide which validations deserve a second look. These flags are advice to our programme team and, for validations they have been allowed to follow, to funding partners; they are not published.
Independent Review Panel. When someone raises a dispute or complaint, we keep the case summary, the written responses and evidence references, the panel’s membership (with each member’s signed no-conflict declaration), each member’s vote and reasons, the written decision and what it changed. Parties see the summary, the responses, the panel members’ names and the decision with its reasons, not who voted how. Panel members see the case and, once seated, the frozen review it concerns; they get no other access to an organisation’s data. Cases are kept as part of the validation’s record. Our lawful basis is legitimate interests in resolving disputes fairly, and contract for the parties to a validation.
Reports of concern. A concern reported from a public page is stored for the CRAFT programme team and, if you gave contact details, used only to reply. Reports are rate-limited and not published. Our lawful basis is legitimate interests in keeping validations accurate, and for engagement records, contract.
9. Networks
Joining. Any signed-in organisation, funder or coordinator can set up a network or a funder's grantee cohort. Its coordinators can invite your organisation to one of its levels (for example a state or country chapter). Before you decide, you see who set the network up (their account email) and whether CRAFT has verified it. Your organisation joins only if someone authorised to act for it accepts, and it can leave at any time. CRAFT can archive a network that is misused.
What the network sees. Your organisation chooses totals only (the default: it is counted in the network's results but never named to coordinators) or named results (coordinators at its level and above see its name, overall score and band). Results for a group of fewer than five organisations are not shown, including in exports and briefs, unless every organisation in that group chose named results. The network never sees your evidence files. Coordinators can see participation counts and send reminders, which go directly to your organisation.
What you submit. When your organisation submits to an assessment round, we keep a copy of that assessment's scores as they were, so rounds can be compared. Optional perspective scores, the member value survey (which network services you used and how useful they were) and the exchanges your organisation says it took part in are used only in totals, and only for groups of five or more (or smaller groups where every organisation chose named results).
Capacity Assessment results. Your organisation's latest completed whole-organisation Capacity Assessment for each module is counted in the network's results under the same choice: with totals only it appears only in group figures (and never for a group of fewer than five organisations unless every organisation in it chose named results); with named results coordinators at its level and above also see its name, overall percentage and growth level. They never see your answers, evidence notes, improvement plan or grant-stage assessments.
Programme scorecards. When a network runs a programme response scorecard, the scores entered for a place or coordinating body (for example a state) are visible by name to the network's coordinators at that level and above.
Coordinators. Coordinators' names and email addresses are visible to other coordinators of the same levels. Every change to a network, and every view or export of named results, is recorded in the audit log.
10. How documents are checked
When evidence is uploaded, the server reads the document’s text to check that it matches its name or declared type. The extracted text is not stored; only the result (match, possible mismatch, unreadable) and matched keywords are kept. Scanned documents are read by optical character recognition inside your own browser; only the recognised text is sent for the check, and the image never leaves your device for OCR.
We do not use workspace data to train AI models, and we do not sell personal data.
11. Who we share it with
Inside CRAFT, workspace data is visible only to members of that organisation’s workspaces, people the organisation grants access to (for example an independent validator or reviewer), and platform operators where needed for support, security or legal compliance.
We use a small number of service providers as sub-processors, listed with their purpose and data on the Sub-processors page. Support messages you choose to make public are published, after personal details are redacted, as issues in the public CRAFT GitHub repository; conduct and security reports are never published.
12. Your rights
Depending on where you are, data protection law gives you rights to access, correct, delete, restrict or object to processing of your personal data, to data portability, and to withdraw consent. These include the Nigeria Data Protection Act 2023, Kenya’s Data Protection Act 2019, South Africa’s Protection of Personal Information Act, Ghana’s Data Protection Act 2012, Uganda’s Data Protection and Privacy Act 2019, Rwanda’s Law No. 058/2021, the EU and UK GDPR, and similar laws elsewhere.
- Download a copy of your data from the platform (privacy export).
- Ask for erasure from within your organisation; another organisation admin or owner approves it.
- Or contact our Data Protection Officer at dpo@becomechange.institute. We respond to verified requests within 30 days.
Where workspace data belongs to an organisation, we pass requests about it to that organisation as controller.
13. Retention
Workspace records are kept while the organisation needs them for accountability, then deleted or anonymised at its request. Finalised reports, assessments and checklists are kept as frozen snapshots so they stay verifiable.
An approved erasure request removes the person’s memberships, replaces their identity in audit actors and assignment fields with a pseudonym, and purges archived evidence files. The audit trail and a minimal record of the request are kept to show it was handled. Rate-limit counters are deleted within minutes; multi-factor secrets and recovery-code hashes are deleted when you turn multi-factor sign-in off.
14. International transfers
Our service providers may process data outside your country. Where a transfer requires safeguards — for example under the Nigeria Data Protection Act, POPIA or the GDPR — we rely on adequacy, the provider’s standard contractual clauses, or another lawful transfer mechanism, and we keep the list of providers and locations on the Sub-processors page.
15. Cookies and browser storage
| Name | Purpose | Type | Duration |
|---|---|---|---|
nf_jwt | Keeps you signed in | Strictly necessary | Session; renewed while active |
craft_mfa | Shows a multi-factor code was entered in this browser | Strictly necessary (HttpOnly, Secure) | 12 hours |
craft_lang_hint | Suggests an interface language from your approximate country (only when you have not chosen one) | Functional cookie | 30 days |
| Language preference | Remembers the language you chose | Functional (browser storage) | Until cleared |
craft_session_lock and workspace selection | Inactivity sign-out across tabs; remembers the selected organisation | Strictly necessary / functional (browser storage) | Until cleared |
craft_consent | Remembers your analytics choice, the date and the policy version | Strictly necessary (browser storage; no cookie) | Until cleared or the policy version changes |
ph_* (PostHog) | Anonymous visitor and session identifiers for analytics and replay | Analytics, only with your consent (browser storage; no cookie) | Until you withdraw consent or clear your browser data |
| Offline queue | Holds edits made offline until they sync | Functional (browser database) | Until synced or cleared |
All analytics is off until you choose. We use no advertising or tracking cookies. If you only tick the support-chat option, PostHog (EU) records just the type of support event, never message content, and keeps its identifier in memory only. Change your choice at any time with Cookie & analytics settings in the footer. Analytics policy version 2026-10-17.
16. Security
We protect data with encryption in transit (HTTPS with HSTS), field-level encryption of sensitive fields at rest, role-based access per organisation and workspace, optional and organisation-enforceable multi-factor sign-in, segregation-of-duties checks, rate limiting, strict security headers and audit logs. See Security for details and how to report a vulnerability.
17. Children
CRAFT is for organisations and professionals. It is not directed at children and we do not knowingly collect children’s personal data.
18. Complaints
Please contact our Data Protection Officer first at dpo@becomechange.institute. You may also complain to your data protection authority, for example the Nigeria Data Protection Commission, Kenya’s Office of the Data Protection Commissioner, South Africa’s Information Regulator, Ghana’s Data Protection Commission, Uganda’s Personal Data Protection Office, Rwanda’s National Cyber Security Authority, or your EU or UK supervisory authority.
19. Changes
We update this policy when our processing changes and change the effective date above. Material changes are highlighted at the top of this page.
© 2026 DiBadili Institute. CRAFT (ICARF v4.0) is an open-source public good. Software GPL-3.0 | Framework CC BY-SA 4.0.