Last updated: 11 November 2026
Privacy & Data Protection Statement
How NextFound CodeLabs Ltd. processes personal data for the schools that use NextFound Academics, and what stays under each school's own control.
Sections
This statement explains how NextFound CodeLabs Ltd. ("NextFound", "we", "us" or "our"), the company that owns and operates NextFound Academics ("the platform"), handles personal data when a school uses its Portal to run its entrance examinations, academic records, fees and communication with parents, students and staff. In this statement, a "Portal" means a school's portal provided through NextFound Academics, including its staff, student, parent, guardian and candidate pages, whatever web address it is reached at. This statement applies wherever it is opened, on NextFound's own website or in any Portal, because it describes the same practices everywhere.
Who we are
NextFound Academics is owned and operated by NextFound CodeLabs Ltd. ("NextFound"), a company registered in [Nigeria, registration number XXXXXXX], with its registered address at [registered address].
Privacy contact: legal@nextfound.com.ng.
The contract between each school and NextFound CodeLabs Ltd. is set out in our Terms of Service.
This statement is written to align with the principles of Nigeria's Data Protection Act 2023 and the NDPR, and with the same general principles (lawfulness, purpose limitation, data minimisation, accuracy, storage limitation, integrity and confidentiality) that similar laws elsewhere share.
1. Who we are, and who this covers
NextFound Academics is a software platform used by schools to run entrance examinations, day-to-day school administration, student and parent portals, and fee collection. Each school that uses it, and everyone who uses that school's Portal (its staff, students, parents, guardians and entrance-examination candidates), is covered by this statement. If you are a parent, student or staff member, your school is the organisation you should contact first about your own information (see section 9); we support your school in answering you.
If you ask for a walkthrough on NextFound's website, we receive the name, school, email address and phone number you give us, by email, and use them only to reply to you and arrange the walkthrough. For this, NextFound is the controller of those details. They are not added to any school's records and are never shared or sold.
2. Controller and processor
For the personal data a school enters about its own students, parents, staff and candidates, the school is the data controller: it decides what is collected and why, and it is the organisation a parent or staff member should approach first with a question or a request about their own data. NextFound CodeLabs Ltd. acts as the school's data processor: through NextFound Academics we provide and operate the software the school uses to store and process that data, under the school's instructions, and we do not sell it, share it with other schools, or use it for anything beyond running the platform and supporting the school.
3. What personal data is processed
| Category | Examples |
|---|---|
| Student and candidate records | Name, date of birth, gender, state of origin, class and department, admission or candidate number, photograph, previous school, academic results, assignments and projects, attendance, entrance-examination attempts and answers, the admission decision, ID cards and documents issued, library loans and school-store purchases |
| Health and religion (sensitive personal data) | Where the school's admission form asks for them: blood group and genotype; any history of convulsions or asthma and its treatment; immunisation status; food and drug allergies; other health challenges; any disability; religion and denomination |
| Guardian and parent contact details | Name, relationship to the child, phone numbers, email address, home address, occupation, the signature and date on the admission form, and sign-in details for the parent portal |
| Staff records | Name, role, contact details, photograph, signature image, login credentials, work assigned to and by them, and, where the school uses staff attendance, the times they clock in and out. Where the school keeps its staff records in the Portal: gender, date of birth, marital status, home address, state of origin, next of kin, job title, employment dates and history, leave, and documents the school attaches. Where it runs payroll: pay, deductions and payslips, bank name and account, and tax identification number |
| Financial records | Fees charged, discounts, payments recorded, receipts issued, and who recorded them; for a payment made online, its amount, date and reference (never card or bank details, which only the payment provider sees); the school's expenses and their receipts |
| Communications | Messages between a school and a parent, and between members of staff, with their attachments; the content of the notices sent about results, fees and school work, and whether each was delivered; a school's requests for help to NextFound, with any screenshots attached |
| Admission applications | Where a school takes applications through its admissions page or office. To make an account: the child's name, the class applied for, a parent or guardian's name, phone number and email address (required when applying online, as the application number and any password reset code are sent only there), and a password (kept only as a hash). The application form: the child's date of birth, sex, state of origin, religion and home address; the previous school, last class and reason for leaving; for up to two parents or guardians, their name, relationship to the child, phone, email and occupation; blood group, genotype, allergies and any condition the school should know about; and, for a senior secondary class, the department wanted. Documents the class asks for: a passport photograph, birth certificate, last school report, transfer letter or immunisation card. The school's assessment and decision: the entrance examination sitting, PIN, answers and scores, or the interview's date, outcome and note; the decision and the class offered. Payments: the form fee and acceptance fee, with their receipts, and who recorded them. Once admitted: the pupil's and parent's portal sign-in details, as for any student |
| Location and device checks | Only where a school uses them. Staff clock-in by phone: how far the phone was from the school at the moment of clocking, how accurate that reading was, and a marker for the phone that member of staff clocks in from. Exams taken in a Portal: a marker for the device a paper was started on, and a note of each time the student or candidate left the page or full screen, or tried to copy or paste, during the paper |
| Technical and usage data | Sign-in times, the IP address a request came from, the browser and kind of device it reported, who is signed in at the moment, a record of significant actions taken in the system (the audit log), and, for a person who has allowed phone notifications, the address their device's push service gave for delivering them. When something goes wrong (an error, or a request that fails, is refused for too many attempts, or is slow), a short record of it is kept for NextFound's engineers: the time, the page asked for, the address it came from and the kind of account signed in (a number, never a name). It never includes a password, a form's contents or the secret part of a link, and it is deleted after 30 days |
A school decides what it enters; we do not ask schools to collect anything beyond what the platform's own forms request, and we do not add hidden fields to collect more.
Location. The platform asks a device for its location in one place only: when a member of staff clocks in or out by phone, at a school that has switched that on (and when a manager sets the school's own position). The browser asks the person's permission first. The phone's position is sent at that moment, used to measure the distance to the school, and then discarded: the position itself is never stored, and location is never read at any other time or followed in between. No page of the platform uses a device's camera or microphone, and the platform instructs the browser to refuse all three on every page other than the staff clock-in pages, where only location is allowed.
4. Why it is processed
- To run the school's entrance examinations, academic records, report cards, assignments and results.
- To take and consider applications for admission: the application, its fees, the entrance examination or interview, the school's decision, and enrolling a child who is admitted.
- To record and reconcile fees and payments, and to produce receipts.
- To send parents and guardians the notices they would otherwise be told by phone or letter: a payment received, a report card ready, new work set for their child.
- To let the right staff, and only the right staff, see and change the records their role covers, and to keep a record of who changed what.
- To record staff attendance where a school uses it, and to confirm that a clock-in was made at the school and from that person's own phone.
- To give a teacher a record of what happened around an exam taken in a Portal, which the teacher weighs for themselves; it is a record, not a verdict.
- To keep the service itself running securely: sign-in, rate-limiting against guessing, and diagnosing a fault.
5. Legal basis
Personal data is processed under the contract between a school and NextFound CodeLabs Ltd. (our Terms of Service), for the school's own legitimate interest in running its administration (and, for its staff and the platform's own security logs, the platform's legitimate interest in keeping the service secure and dependable), and, for anything a person is separately asked to agree to, their consent. Child by child, the school may use the child's photograph in its publicity, send optional messages such as birthday greetings, and share the child's details with WAEC, NECO or the BECE examining body to register them for an external examination. Each is allowed unless a parent says no: a parent can withdraw any of them, or allow it again, at any time in the parent portal (Privacy & my data), or by a signed form the school records. Every decision is kept with its date and how it was given, so the school can show what it was told.
6. How your school's data is kept apart
Every school on this platform has its own separate database and its own separate folder of files — not a shared table filtered by a school identifier, but a database of its own. A query made for one school's data can never accidentally return another's, because the software is built so that no database connection is ever shared between two schools within the same request. A cookie or sign-in issued by one school's address is rejected if it is ever presented at another school's address. Uploaded files (student and staff photographs, signatures, question images) are served only to the people the record says may see them, checked on every request.
7. Security measures
- Passwords are stored only as hashes, which cannot be turned back into the password, and changing a password ends every other sign-in on that account within about a minute. There is one short-lived exception: when a candidate is admitted, the first password of their new student account is kept encrypted so that it can be shown to them once, and is deleted as soon as they have signed in and changed it. In the same way, when a child is admitted through an application, the first passwords of the pupil's and (if new) the parent's portal accounts are kept encrypted so the family's admissions page can show them, each deleted as soon as it is changed.
- For admissions: an examination PIN is kept encrypted so the slip can show it, and works only on the school's own computers through the secret link of a sitting the school has opened; a payment code given at the school office is never stored, only a keyed fingerprint of it. Making an admissions account asks the browser to solve a small puzzle and is refused if it comes too fast, so that programs cannot make accounts in bulk; the puzzle uses no outside service and collects nothing.
- A school's own email server password, SMS API token and online-payment keys, where it sets them up, are encrypted before they are stored, under a key specific to that school; they are never shown again once saved, and a copy of the database does not expose them. Staff bank account numbers and tax identification numbers are encrypted in the same way.
- A forgotten password (a parent's, or an admissions account's) is reset with a six-character code sent only to the email address on the account. Only a keyed one-way fingerprint of the code is stored, with the time and the IP address it was asked from; it lasts 15 minutes, is cancelled after five wrong tries, and works once. When a code is sent, the page shows the address partly hidden (for example ma**********@**ail.com) so its owner can recognise it.
- Sign-in attempts, password-recovery requests and test-message buttons are rate-limited against guessing, and so are making an admissions account, finding an application number, typing a payment code and signing in at an examination hall. Attempts are counted by the IP address a request came from (and the account tried); only a one-way fingerprint of that address is stored with the count, never the address itself, and it is deleted when its waiting time ends, within an hour.
- Significant actions — creating or changing a record, a staff member's access, a payment — are written to an audit trail recording who did it, when, and from where.
- The platform loads no advertising, analytics or tracking scripts, fonts or images from outside its own servers; its security policy blocks pages from embedding anything foreign. The one exception is the learning simulations a school may offer its students, described in section 12. (NextFound's own announcements, described in section 11, are part of the platform and are not affected by this.)
- Traffic to the platform is encrypted in transit (HTTPS/TLS).
8. Retention and deletion
A school's data is kept for as long as the school's account with the platform remains active, or for as long as applicable law requires records of that kind to be kept, whichever is longer. A school may ask for its data to be deleted once its account ends, subject to any legal or regulatory requirement to retain particular records for a set period (for example, financial records).
Admission applications. An admissions account whose form fee is not paid within 7 days of being made is removed, with everything in it. When a child is not offered a place, or an offer is not accepted in time, the application's personal details (the form, documents, photograph, contact details, examination PIN and sign-in) are removed 30 days after that decision; what stays is the application number, the class applied for, the decision, examination marks without a name, and the payments, which are financial records. An admitted child's application stays with their student record.
Backups. Every school's database is backed up each night, so that it can be restored after a fault. A backup is a complete copy as the records stood that night. Backups are kept on a fixed schedule (the last seven days, then one a week for four weeks, then one a month for three months) and are deleted after that. Something corrected or erased in a Portal therefore remains in earlier backups until they are deleted, at most about three months later; a backup is used only to restore a school's records, never to look someone up.
The school's data export. The School Admin can download a copy of the school's records at any time from Settings, Export all the school's data. It contains exactly the following.
- Included: a spreadsheet file (CSV) for each kind of record the school keeps in the platform, including student and staff records, classes, results, attendance and staff clock-ins, fees, payments, payroll, messages and the school's activity log; every file uploaded to the school's Portal, including photographs, signatures, attachments and documents; and a guide (README) explaining each file.
- Left out on purpose: passwords, sign-in tokens, and the keys and passwords of outside accounts the school has connected (these are never exported, so that a copy of the export cannot be used to sign in anywhere); and the platform's internal working records, such as queued background tasks and message-delivery queues.
- Not stored, so not in the export: documents the platform draws when they are asked for, such as receipts and report cards as PDF files. Their contents are in the export as records, and the documents themselves can be downloaded again from the Portal at any time.
- Not the school's records: NextFound's own business records about the school, such as NextFound's invoices to the school, its support conversations with NextFound, and the activity log of NextFound's own console, are kept by NextFound and are not part of the export.
- Who and how long: only the School Admin can request the export or download it, and each export is deleted seven days after it is made.
When a family asks for a child's data to be erased and the school approves it, the child's name is replaced by a placeholder, and their contact, health and religious details, photograph, sign-in, messages and admission form are removed. Results, attendance and fee records the school must keep stay, under the placeholder name; a parent with no other child at the school is anonymised in the same way. Erasure cannot be undone.
9. Rights over your data
Depending on the law that applies to you, you may have the right to ask to see the personal data held about you, to have inaccurate data corrected, to have it deleted, to object to certain processing, or to receive a copy of it in a portable form. Because your school is the controller of its own records, the quickest route is to ask your school directly. A parent can do so in the parent portal (Privacy & my data): ask for a copy of everything held about a child, or for it to be erased. The school answers within thirty days, and a copy is downloaded from the portal. If you contact us instead, we will pass your request to the relevant school and support them in answering it.
10. Children's data
Much of what a school records is about children. A school is responsible, as controller, for having a proper basis to collect and hold information about the students in its care, in the way it already does for paper records; the platform's role is to hold and process that information securely on the school's behalf, under the same isolation and security measures described above, and to make it visible only to the people the school's own settings say may see it, and never to another school. NextFound staff see a school's records only when they enter its Portal to support it, for example to answer a request from the school: each such visit must give a reason, is shown to the school while it lasts (the school can end it), and is written to the school's own activity log, together with everything done during it.
11. Cookies and tracking
The platform sets only cookies it needs in order to work, at most three kinds:
- The sign-in cookie, for everyone: a signed cookie that records who is signed in and to which school. It ends when the browser is closed, and the sign-in it records ends sooner: on signing out, after a period without use, or after a fixed number of hours.
- A staff clock-in cookie, only on a phone a member of staff has clocked in from: a random marker that shows it is the same phone next time. It holds nothing about the person and is kept on the phone for up to five years; the school can reset which phone is registered for a person at any time.
- An exam cookie, only on a device a paper was started on: a random marker that shows whether the paper is later opened on a different device. It is kept for two days.
None of them carries an advertising identifier, follows anyone from one website to another, or is read by any third party. The platform also keeps small items in the browser's own storage on the device, such as a notice already shown, the place reached in a menu, or work in progress (a message being written, results being entered) so that it is not lost if the connection drops. These stay on the device. The platform runs no third-party analytics, advertising or tracking scripts of any kind, on any page, for anyone.
NextFound's own announcements. NextFound may show a school's staff announcements within the platform about updates, new features, planned maintenance, and other products and services offered by NextFound. These are part of the platform itself: they are shown to everyone in the chosen schools alike, never chosen or targeted using anyone's personal data, and never involve a third party. They are not shown to parents, students or candidates. NextFound does not show third-party advertising in any Portal.
12. Sub-processors and delivery channels
A Portal tells its staff, students and parents about things that concern them in up to four ways:
- In-portal notifications: updates and messages shown within the Portal itself, to the person they are for. These never leave the platform.
- Email, sent through the mail server the school has configured or, where the school has none, through the platform's own mail account as a stand-in.
- SMS text messages, sent through BulkSMS Nigeria, using the school's own account where it has one (or the platform's, where the platform provides it). A text is a short notice. It names the child, and a notice about fees states the amount charged, received or overdue; a text never carries a mark, a grade or a report card, only that a report card is ready. A school can reword its own notices.
- Phone notifications (push notifications), only to a person who has allowed them on their own device. They are delivered through the push service of that device's browser or operating system (Google for Chrome and Android, Apple for iPhone and iPad, Mozilla for Firefox). Each notification is encrypted on the platform with keys belonging to that person's device before it is sent, so the push service can deliver it but cannot read it. A person can switch them off at any time in their device's settings.
Email, SMS and phone notifications carry short notices, and whether and when they arrive can depend on the provider, the person's device and its settings, and their network connection.
A school may also give its own developers, or a partner it engages (an accounting system, for example), read-only access to parts of its data through keys its School Admin creates and can revoke at any time, and may have its own systems told when something happens (webhooks, which carry ids, not names or contact details). The school, as controller, decides who that is and is responsible for them.
Online payments. Where a school accepts fees online, payments are taken by Paystack, through the school's own Paystack account. The parent enters card or bank details on Paystack's page, never in the Portal, and the platform never sees or stores them. To start a payment the platform gives Paystack the amount, a payment reference and the paying parent's email address; Paystack tells the platform whether the payment succeeded. Admissions fees paid online work the same way, with the applicant's parent or guardian's email address. Where a school pays salaries through Paystack, it receives each member of staff's name, bank account and amount for that purpose. Paystack handles this information under its own privacy policy, as the school's payment provider.
Learning simulations. Where a school offers them, a student can open interactive science and mathematics simulations made by PhET Interactive Simulations at the University of Colorado Boulder. A simulation is loaded directly from PhET's own servers (phet.colorado.edu) into a frame on the page, so PhET's servers receive what any website receives from a visitor: the device's IP address and its browser details. The platform sends PhET nothing about the student (no name, school or class) and does not tell it which page the request came from. A school can switch simulations off, for the whole school or for single classes.
The underlying database and application hosting is provided by HostAfrica, from data centres located in Nigeria, acting as a sub-processor under contract with us, bound to the same confidentiality and security expectations as this statement. Files uploaded to a Portal (photographs, signatures, attachments) and the nightly backups are kept in object storage provided by LineServe, in Lagos, Nigeria. Email sent through the platform's own mail account is delivered by SendByte (sendbyte.africa), which receives the recipient's email address and the content of the message in order to deliver it; its servers are in [country where SendByte's servers are].
13. Where data is hosted
Each school's data is stored on servers operated for this deployment of the platform, hosted by HostAfrica in data centres located in Nigeria. Uploaded files and backups are kept with LineServe, in Lagos, Nigeria (section 12). Some of the services described there are operated outside Nigeria: the push services of Google, Apple and Mozilla (which carry phone notifications they cannot read) and PhET's simulation servers (which receive no information about a student beyond what any website receives from a visitor). Where personal data is transferred outside Nigeria, it is done only as the Nigeria Data Protection Act 2023 permits for cross-border transfers.
14. Changes to this statement
We may update this statement as the platform changes. The date at the top shows when it was last revised, and a material change that affects how personal data is handled will be brought to schools' attention rather than only noted here silently.
15. Contact
Questions about this statement, or about how the platform handles data, can be sent to legal@nextfound.com.ng. A parent, student or staff member asking about their own personal data should start with their school, which holds the records and can act on the request directly.