1. Purpose and Status of the Contributor Program
The ALBUKHR Contributor Program is an organised participation framework through which selected individuals contribute to the development, operation, knowledge base, projects, and broader objectives of the ALBUKHR ecosystem. The program is designed to create a structured relationship between ALBUKHR and contributors rather than an informal community membership scheme.
Contributor status is granted through an ALBUKHR-controlled invitation and acceptance process. A person does not become a Contributor merely by registering an account, joining a public community, accessing an ALBUKHR website, or participating in a project discussion.
The program exists to give approved contributors a defined place within the ecosystem, a governed route to establish one Internal Project, access to contributor-specific information and community channels, and a clear set of responsibilities and standards.
2. Scope and Definitions
3. Contributor Admission and Activation
3.1 Invitation
Contributor admission begins with an authorised invitation. The invitation may be bound to an email address and will have an expiration and revocation state managed by ALBUKHR systems.
3.2 Acceptance
The invited person must authenticate to the ALBUKHR system, review the applicable contributor policy and privacy notice, and provide the required electronic acceptance before contributor activation can be completed.
3.3 Verification and account integrity
ALBUKHR may verify the identity and account information reasonably necessary to protect the integrity of the Contributor Program. No contributor may operate another person’s account, impersonate another Contributor, or provide knowingly false onboarding information.
3.4 Status
A Contributor may have the status active, suspended, or revoked under the Contributor governance model. Status controls access to contributor-specific resources and does not by itself grant administrative rights.
4. One Contributor - One Internal Project Entitlement
The Internal Project entitlement exists to give a Contributor a structured vehicle through which the Contributor can contribute to the ALBUKHR ecosystem. The entitlement is separate from the contributor account itself and must be used in accordance with the project registration and governance process.
4.1 Ownership and management
The intended project relationship is that the Contributor is recorded as the owner of the Internal Project they create, subject to the system architecture, applicable governance decisions, and ALBUKHR rights reserved under this policy.
Contributor ownership does not automatically create an administrator role. In particular, a Contributor is not automatically granted a scoped administrative role merely because they own an Internal Project.
4.2 One-project restriction
ALBUKHR will enforce the one-Internal-Project entitlement at the database and server-authorisation level, not solely through the web interface. The system should prevent a Contributor from creating a second Internal Project while their one-project entitlement has already been consumed.
4.3 Project entitlement versus approval
Receiving a project entitlement does not mean that the project is approved, active, investable, or guaranteed to receive funding. A submitted Internal Project remains subject to review, revision requests, approval, suspension, archival, and other applicable governance actions.
4.4 Future policy treatment
The technical system should treat the entitlement policy as a governed rule. ALBUKHR may define in a separate approved procedure whether an entitlement is lifetime, consumed on first successful project creation, or released only under specified administrative conditions. Any such rule should be published clearly before it is applied to Contributors.
5. Internal Project Creation and Governance
The Contributor must have an active Contributor status.
The Contributor must have an unused Internal Project entitlement.
The Contributor submits the required project information through the authorised ALBUKHR workflow.
The system records the project as draft or another pre-approval status defined by ALBUKHR.
ALBUKHR reviews the submission under the applicable project-governance criteria.
The project may be returned for revision, rejected, approved, activated, suspended, or archived according to the applicable governance process.
The Contributor must not represent a draft or pending project as an ALBUKHR-approved active project.
5.1 Required project information
The registration workflow may require a project name, project code or system identifier, description, business or operating information, project logo, owner information, supporting documents, and other information determined by ALBUKHR. The project logo requirement is governed by the ALBUKHR project-registration standard, including supported image formats and minimum image dimensions.
5.2 Accuracy
The Contributor is responsible for the accuracy, legality, and completeness of information submitted for their Internal Project. A Contributor must promptly correct material inaccuracies discovered after submission.
6. Contributor Responsibilities
Act in good faith and in accordance with ALBUKHR policies, procedures, and lawful instructions.
Protect login credentials, account access, tokens, invitation information, and other security-sensitive information.
Provide truthful and reasonably complete information during onboarding and project registration.
Use ALBUKHR systems only for authorised purposes.
Respect the confidentiality of non-public ALBUKHR information and contributor discussions.
Promptly report suspected account compromise, unauthorised access, data exposure, fraud, or material policy violations.
Avoid making statements that falsely imply that the Contributor personally represents ALBUKHR, its management, or its official positions unless expressly authorised.
Comply with applicable law and any project-specific requirements communicated by ALBUKHR.
7. Contributor Community and Private Telegram Group
ALBUKHR maintains a private Telegram group for active Contributors to facilitate important contributor discussions, notices, coordination, and ecosystem communications. Access to the private group is an operational benefit associated with active Contributor status.
7.1 Eligibility
The ALBUKHR application should display the authorised private Telegram invitation link only to an authenticated Contributor whose status is active. The link should not be embedded as unrestricted public content in the application interface or exposed through a public API.
7.2 Suspension and revocation
If contributor status is suspended or revoked, ALBUKHR may remove or disable access to contributor-specific community resources, including the contributor Telegram group, subject to any applicable legal or administrative requirements.
7.3 Third-party platform
Telegram is a separate third-party service. ALBUKHR does not control Telegram’s own processing of personal data, content, identifiers, device information, or other information processed by Telegram. Contributors should review Telegram’s applicable terms and privacy information before using the service.
8. Code of Conduct and Prohibited Activities
Contributors are expected to maintain professional, respectful, and lawful conduct in ALBUKHR systems and contributor channels. The following activities are prohibited or subject to disciplinary action where applicable:
fraud, attempted fraud, deception, impersonation, or identity misuse;
unauthorised access, credential sharing, bypassing security controls, or attempting to manipulate system permissions;
misuse or unauthorised disclosure of confidential or non-public project information;
deliberate submission of materially false project information;
harassment, threats, targeted abuse, or discriminatory conduct in contributor channels;
unauthorised fundraising, financial promises, or representations made in ALBUKHR’s name;
interference with project review, governance, moderation, or security processes;
use of ALBUKHR systems for unlawful activity or activities that expose ALBUKHR or other participants to avoidable legal or security risk.
9. Confidentiality and Information Handling
Contributors may receive information that is not intended for public disclosure, including internal project discussions, operational documents, draft decisions, security information, private contributor discussions, and information shared under an explicit confidentiality restriction.
A Contributor must not copy, publish, forward, sell, disclose, or otherwise distribute non-public information to a person or service that is not authorised to receive it. This obligation continues after suspension, revocation, or withdrawal from the program to the extent permitted and required by applicable law.
10. Privacy Notice
This Privacy Notice explains how ALBUKHR may process personal data in connection with the Contributor Program. ALBUKHR will seek to process personal data in a fair, lawful, transparent, purpose-limited, minimised, accurate, appropriately secured, and retention-controlled manner, consistent with applicable data-protection requirements.
For Contributors in Nigeria, ALBUKHR should operate the program with regard to the Nigeria Data Protection Act 2023 (NDP Act) and applicable guidance issued by the Nigeria Data Protection Commission (NDPC). The NDPC describes the NDP Act as establishing protections for data subjects and requirements around fair, lawful, accountable, and secure processing. (Reference: NDPC, Nigeria Data Protection Act 2023 and related guidance.)
11. Personal Data We May Process
Depending on the Contributor’s interaction with ALBUKHR, the program may process categories such as:
Account and identity information: authenticated user identifier, username, email address where available, and related account status.
Contributor records: contributor identifier, invitation identifier, invitation status, contributor status, registration date, suspension or revocation records, and governance history.
Wallet and ecosystem identifiers: wallet address or related identifier where it is required for an ALBUKHR feature and lawfully processed.
Project information: project owner identifier, project submissions, project descriptions, uploaded materials, logo metadata, review records, approval states, and project governance history.
Security and audit information: records needed to investigate security events, enforce access controls, prevent abuse, and maintain system integrity.
Consent and policy records: policy version, privacy notice version, acceptance timestamp, and related evidence required to demonstrate the Contributor’s acceptance of the applicable program terms.
Communications: messages or correspondence sent to or received from ALBUKHR in relation to contributor onboarding, support, project governance, security, or policy matters.
11.1 Data minimisation
ALBUKHR should collect and retain only information that is reasonably relevant to an identified operational, governance, security, contractual, or legal purpose. Optional information should be clearly distinguished from information required to provide the Contributor service.
12. Purposes and Lawful Bases for Processing
13. Data Sharing, Service Providers and Transfers
ALBUKHR may use carefully selected infrastructure and service providers to operate authentication, databases, hosting, storage, security, communications, analytics, and related services. Access should be limited to what is reasonably necessary for the provider’s authorised function and should be subject to appropriate contractual, technical, and organisational controls.
Where personal data is disclosed to a third party, ALBUKHR should assess whether the disclosure is lawful, necessary, proportionate, and adequately protected. Where applicable law imposes requirements for cross-border transfers or international processing, ALBUKHR should apply the required safeguards.
ALBUKHR may disclose information where necessary to comply with law, court or regulatory process, protect rights and security, investigate suspected abuse, or establish, exercise, or defend legal claims, subject to applicable law.
14. Data Retention and Security
14.1 Retention
ALBUKHR should retain personal data only for as long as reasonably necessary for the purpose for which it was collected, for legitimate operational needs, to satisfy legal or regulatory requirements, to resolve disputes, or to enforce agreements. Final retention periods should be defined in the ALBUKHR records-retention schedule and mapped to each data category.
14.2 Security
server-side authorisation for contributor privileges;
access controls and least-privilege permissions;
secure credential and token handling;
audit logging for sensitive contributor and project actions;
controlled access to private community resources;
reasonable technical and organisational measures against unauthorised access, loss, misuse, alteration, or disclosure;
incident handling and breach-response procedures appropriate to the nature of the data and the applicable legal requirements.
15. Data Subject Rights and Privacy Requests
Subject to applicable law and any lawful limitations, a Contributor may have rights relating to personal data, including the right to be informed, access, rectification, objection, restriction, portability, erasure where applicable, and rights concerning certain automated decision-making. The NDPC publicly identifies these categories of rights for data subjects under the NDP Act. (Reference: NDPC, Nigeria Data Protection Act 2023 and related guidance.)
A Contributor may contact ALBUKHR using the designated privacy contact to request access to, correction of, or other action concerning personal data. ALBUKHR should verify the requester’s identity where reasonably necessary before releasing or changing personal data.
A request to delete personal data does not necessarily require deletion of every record. Where retention is required by law, necessary for a legal claim, required for security, or otherwise permitted by applicable law, ALBUKHR may retain the relevant record for the applicable period and should explain any material limitation to the requester.
16. Suspension, Revocation and Access Removal
ALBUKHR may suspend or revoke Contributor status where permitted under its governance framework, including for material policy violations, security concerns, fraudulent or misleading conduct, misuse of project or community resources, or other circumstances that justify protective action.
16.1 Process
Where appropriate, ALBUKHR should record the reason and effective date of the action.
ALBUKHR may apply immediate temporary restrictions where delay would create material security, legal, or operational risk.
Where appropriate, the Contributor may be given an opportunity to provide information or respond through the designated review process.
Suspension or revocation may remove access to contributor dashboards, project-management capabilities, private community resources, and other contributor-only functions, subject to applicable legal rights.
16.2 Project implications
Suspension or revocation of a Contributor does not automatically determine the legal or commercial fate of an Internal Project. Project status, ownership, archival, administration, and other consequences should be handled under the separate project-governance framework and any applicable agreements.
17. Intellectual Property and Project Materials
Each Contributor should submit project materials only where they have the right to do so. A Contributor should not upload third-party content in breach of copyright, confidentiality, licensing, privacy, or other rights.
Unless a separate written agreement states otherwise, this policy does not by itself transfer ownership of a Contributor’s pre-existing intellectual property to ALBUKHR. At the same time, the Contributor grants ALBUKHR the operational rights reasonably necessary to host, review, display, store, process, and administer materials submitted to ALBUKHR for Contributor and project purposes. Any commercial licensing, investment rights, branding rights, or intellectual-property transfer arrangements should be documented separately when required.
18. Risk, No Guarantee and Contributor Representations
The Contributor represents that information supplied to ALBUKHR is accurate to the best of the Contributor’s knowledge and is not intentionally misleading.
The Contributor understands that project review is a governance process and that additional information may be requested.
The Contributor must not present internal drafts, pending projects, community discussions, or unapproved claims as official ALBUKHR approvals or guarantees.
Where an activity involves investment, financial promotion, payments, or another regulated service, the relevant ALBUKHR policy, legal requirements, and approvals apply in addition to this Contributor policy.
19. Policy Changes and Renewed Acceptance
ALBUKHR may update this policy to reflect changes in its contributor program, technology, governance procedures, security requirements, or applicable law. Each published version should carry a version number and effective date.
Where a change materially affects Contributor rights, obligations, privacy practices, access, or project entitlements, ALBUKHR should communicate the change through an appropriate channel. Where renewed acceptance is required, contributor access to the affected feature may be conditioned on acceptance of the new version.
20. Complaints, Contact and Escalation
Contributor and privacy concerns should be directed to the official ALBUKHR contact designated for Contributor Program and privacy matters. The final production version of this document should contain the verified legal entity name, registered or principal address where appropriate, privacy email, contributor support email, and any designated Data Protection Officer or privacy contact details.
21. Acceptance and Electronic Consent
Participation in the Contributor Program is conditional upon completion of the required acceptance step. The production onboarding workflow should show the current policy and privacy notice versions before the Contributor submits acceptance.
21.1 Required acknowledgement
The Contributor should explicitly acknowledge that they have had an opportunity to review the applicable policy and agree to comply with the Contributor Program rules. The acceptance flow should identify the exact version accepted and record a timestamp and authenticated user identity.
21.2 Recommended consent record
Contributor/user identifier
Contributor record identifier
Contributor Policy version
Privacy Notice version
Accepted at (server timestamp)
Acceptance method/source
Additional audit metadata where lawfully necessary
21.3 Activation condition
The Contributor should not be granted active Contributor status solely because a frontend checkbox was selected. The server-side activation workflow should verify the required acceptance and create the contributor status in the authoritative database transaction or controlled workflow.
. Appendix A - Contributor Acceptance Checklist
. Appendix B - Operational Implementation Requirements
The production application should implement the following controls consistently with this policy:
. Appendix C - Legal and Regulatory Reference Notes
This appendix records the principal external privacy reference used to draft the privacy sections. It is not a substitute for a legal opinion and should be reviewed against the laws and regulatory guidance applicable to ALBUKHR at the time of publication.
Nigeria Data Protection Act, 2023 - Nigeria Data Protection Commission (NDPC): Official NDPC Act resource
NDPC General Application and Implementation Directive (NDP Act-GAID 2025): Official NDPC GAID 2025
NDPC privacy guidance / data subject rights summary: NDPC Data Privacy Policy
The NDPC states that the NDP Act 2023 provides for the regulation of personal-data processing, safeguards data-subject rights, and requires fair, lawful, accountable, and secure data-processing practices. The NDPC also describes data-subject rights including information, access, rectification, objection, portability, erasure where applicable, and rights concerning automated decision-making and complaints. These references should be rechecked when the production legal text is finalised.