Purpose and responsibility
This policy sets data protection requirements for BRANDBOXX LTD, trading as Brandboxx. It applies to staff, managers, processors and contractors who handle personal information for our services or Academy. It describes how information must be handled and how privacy concerns must be escalated.
Adigun Olamiposi Noah is the contact responsible for privacy requests through hello@brandboxxhq.com. Management remains responsible for assessing any duty to appoint a Data Protection Officer, register with the NDPC or file compliance returns. Naming a privacy contact does not claim a professional certification or regulatory registration. Staff must report privacy problems to the contact and follow approved instructions.
Use only what the work needs
Before collecting information, record the purpose, people affected, data needed, lawful basis, recipients and retention rule. Give a clear privacy notice at the point of collection. Do not treat acceptance of website terms as blanket consent for all data use.
Only request fields and documents needed for the chosen service. Do not collect passwords, bank PINs or payment verification codes in forms or support messages. Check that documents are linked to the right applicant. Correct known errors and record important changes without hiding the history of an application.
Reusing details for a director who is also a shareholder is allowed within the relevant application. It must not copy one client's details into another client's request. A saved document should only be reused for the correct person and purpose.
Restrict access and sharing
Give each worker access needed for their role and assigned work. Review access when duties change and remove it promptly when someone leaves. Workers must use their own authorised accounts, protect login details and keep client information confidential.
Use approved upload and document systems. Do not make identity documents public or place them in personal cloud folders, public links, code repositories or unapproved messaging groups. Keep private links limited in access and duration where supported. Confirm identity and authority before sending a file to a new recipient.
Keep necessary records of access, changes, disclosures and refunds. Restrict access to those records too. Avoid putting full identity numbers, uploaded documents, secrets or payment credentials into logs. Use anonymised examples for training and testing where possible.
Sensitive information and children
Assess any legally sensitive information before collection. This can include biometric identification data and information revealing health, religion or similar protected matters. Record the additional lawful condition and safeguards required. Do not assume ordinary photos are biometric identification records.
For information about a child or someone unable to give legal consent, verify the representative's authority and obtain parent or guardian consent when required. Use proportionate checks and collect no more evidence than necessary.
Providers and international transfers
Assess providers before giving access. Record the information handled and its storage and access locations. Written arrangements must address instructions, confidentiality, security, further providers, incidents, rights requests, and return or deletion.
For transfers outside Nigeria, document the lawful transfer route and the required protection. Obtain regulatory approvals where applicable. Do not rely on a website terms checkbox or a provider's reputation as the only safeguard.
Record agents' actual responsibilities. Use a separate data processing agreement where Brandboxx acts only on a business customer's instructions. This policy does not replace that agreement.
Retention and deletion
No general automatic expiry is currently set for account documents. Records may remain available while the account is active and the platform operates, where needed for the service or document access. Management must review the need to retain drafts, identity records, applications, completed files, payments, Academy records, support messages, logs and backups. The platform remaining available is not, by itself, a reason to retain all personal information forever.
Handle a client deletion or account closure request by checking the relevant records, ongoing applications, disputes and legal duties. Delete or anonymise information when no valid reason remains. Record any lawful exception, explain it to the client and review it when the reason ends. Arrange deletion or return with providers, including any delayed removal from backups. Do not promise immediate removal from every provider or backup before confirming that it has happened.
Explain the difference between removing a saved file from the reuse shelf and erasing all copies. Do not tell a person that their data has been deleted unless the relevant action has actually been completed or any remaining lawful retention has been explained.
Privacy requests and complaints
Record requests, verify identity proportionately, identify the relevant records and assess the requested right. Protect information about other people when answering. Explain any lawful refusal or restriction, and retain a record of the response.
Meet the legal deadline that applies to each request or formal regulatory notice. Escalate urgent matters promptly. Internal approval delays must not cause a legal deadline to be missed.
Incidents and breach reporting
Anyone who suspects a lost file, wrong recipient, exposed document, stolen account or other data incident must report it immediately. Contain the exposure, preserve evidence, record when it became known, identify affected people and assess likely harm. A processor must notify the controller that engaged it on becoming aware of a breach.
Where a breach is likely to risk people's rights and freedoms, notify the NDPC within 72 hours of awareness as required by the Act. Where it is likely to create a high risk to an affected person, communicate with that person immediately as required, using clear language and practical protective steps. Check any applicable exceptions or additional duties, and document decisions. Do not wait for a complete investigation before making a required notification.
Review and implementation
Carry out required impact assessments and consultation before high risk processing. Review identity verification integrations before enabling them. Train workers, check access and deletion arrangements, and review this policy after material changes or incidents. Management must keep a record of responsibilities, reviews and actions needed to put these requirements into practice.
Contact Brandboxx
BRANDBOXX LTD · RC 9918679
Flat B, Arowolo Street, FUTA Southgate, Akure, Ondo State, Nigeria
Customer support: Website support or WhatsApp 09138347603.
Official correspondence and privacy requests: hello@brandboxxhq.com.
Privacy contact: Adigun Olamiposi Noah.