1. Scope and roles
This agreement forms part of our Terms of Service. It applies to personal data a school (the controller) puts into Edgrid or collects through its Edgrid website, which Digitanotion Limited (the processor) handles for the school. It meets the requirements of the Nigeria Data Protection Act 2023, the EU GDPR (Article 28) and similar African data laws.
2. What we process
| People | Students and pupils (often children), parents and guardians, applicants, school staff and teachers, and people who contact the school. |
|---|---|
| Data | Names, contact details, admission numbers, classes, scores, remarks, application details, and messages. |
| Purpose | Hosting the school's website and dashboard, receiving applications and enquiries, managing and publishing results, and checking result PINs. |
| Duration | For as long as the school uses Edgrid, then until deletion under section 9. |
3. Only on your instructions
We process school data only to provide the service and as the school instructs through its dashboard or in writing, unless the law requires otherwise (in which case we tell the school first, where allowed). We never sell school data or use it for advertising.
4. Confidentiality
Only staff who need access to support a school can reach its data. They are bound by confidentiality, and their actions in the admin area are logged.
5. Security measures
- Encryption in transit (HTTPS) for every connection.
- Database-level separation, so each school only ever sees its own data.
- Result PINs encrypted at rest; passwords hashed; limits on wrong attempts.
- Two-step login for Edgrid staff, with roles that limit what each person can do.
- Location data removed from uploaded photos.
- Regular backups and monitoring.
6. Sub-processors
The school agrees that we may use these sub-processors, each bound by data protection terms at least as strict as these:
- Cloud hosting provider (servers and storage).
- Cloudflare (content delivery and security).
- Mailgun (service emails) and Zoho (support email).
- Paystack and Flutterwave (payments; they receive only what is needed to take a payment).
We will tell schools at least 14 days before adding or replacing a sub-processor, so they can object.
7. Helping schools meet their duties
We help schools answer requests from parents and students to see, correct or delete their data, and with data protection impact assessments where needed. Requests we receive directly are passed to the school.
8. Data breaches
We notify the school without undue delay, and in any case within 48 hours of becoming aware of a breach affecting its data, with what we know and what we are doing about it, so the school can meet its 72-hour duty to notify the regulator.
9. Return and deletion
When a school closes its account it can export its data first. We then delete the school's personal data within 90 days, including from backups as they cycle out, unless the law requires us to keep it.
10. Information and audits
We will give a school the information it reasonably needs to show compliance with this agreement, and answer reasonable security questionnaires. Contact [email protected].
11. International transfers
Where school data is processed outside the school's country, we use the safeguards the law requires, such as adequacy decisions or standard contractual clauses.
12. The school's responsibilities
The school confirms it has a lawful basis for the data it uploads, including any consent needed from parents or guardians for children's data and photos, and that its instructions to us comply with the law.