Skip to content
EduMaverickSchool Management Cloud
01

What we collect

A school gives us the information it needs to run its portal: student names, admission numbers, class placement, attendance, assessment scores and results, fee and payment records, guardian contact details, staff employment and payroll information, and the messages and notices sent through the platform.

We also keep the technical records needed to run the service safely, such as sign-in events, device tokens for push notifications, and an audit log of changes made inside the platform.

  • School and staff records entered by the school
  • Student, guardian and fee records
  • Authentication, device and audit logs
02

How we use it

We use the data to provide the service: marking attendance, computing results, charging and reconciling fees, sending the notices a school sends, and supporting the school that entered the data.

We do not sell personal data, and we do not use a school's student or family records to advertise to anyone. A school's data is available only to the people that school has authorised, and every administrative action is written to an audit trail.

  • Running the services the school pays for
  • Notifying families and staff as the school instructs
  • Never selling or advertising with personal data
03

Isolation and access

Every school runs on its own subdomain with its own database. A school's records are never mixed with another school's, and the platform operator reaches them only through a separate, audited console.

Access follows role. A teacher sees the classes they teach, a parent sees their own children, a student sees themselves, and a school administrator sees the school they belong to.

  • One private database per school
  • Role-based access, enforced on the server
  • An audit trail of every administrative action
04

Visiting our website

The public site asks before it measures anything. Until you accept the cookie banner we store nothing about your visit beyond what is needed to serve the page, and declining costs you nothing on the page.

If you accept, we record which pages and buttons you used, the browser and device type, the country the request came from and an approximate city. That identifier belongs to the browser, not to a person, and it is never joined to a school's records. There is no third-party tracker, advertising pixel or external analytics provider: the data stays on our own server.

  • Nothing measured before you accept
  • Declining changes nothing about the page
  • Country and browser type only, never a name or a school record
  • A copy of everything we hold about a visit is downloadable
05

Cookies and tracking

The banner asks once and offers three choices: Accept all, Decline all, or Manage preferences. Four cookies are always set, because the site cannot work without them: a session cookie that protects sign-in and form submissions, a token that guards the forms on this page, a random reference for this browser, and the record of the choice you made. The last two exist only to honour what you decided.

Two more exist only if you accept them. The analytics cookie tells us which pages, plan cards and pricing steps were used, keyed to that browser reference and never to a named person. The marketing cookie keeps your EduMaverick AI conversation open while you are talking to the assistant. Neither is an advertising pixel, and neither is joined to a school's records.

Talking to EduMaverick AI is asked for separately from measurement. The assistant starts only when you type an email address into it, and the conversation is stored against that address so a consultant can continue the thread. Declining analytics does not silence the assistant, and using the assistant does not switch on measurement you declined.

You can change your mind at any time from Manage preferences, including withdrawing everything. The change takes effect on the next request. We keep a dated record of each choice, because the law asks us to be able to show that it was made and when.

  • Necessary: sign-in and form protection, your browser reference and your saved choice. Always on, never offered as a switch
  • Analytics: pages, plan cards and pricing steps, only after you accept
  • Marketing: the EduMaverick AI conversation cookie, only after you accept
  • No advertising pixels and no third-party analytics
  • Change or withdraw everything from Manage preferences
06

Email updates

Newsletter addresses work on double opt-in. When you ask for updates we store the address and send one confirmation email. Nothing else is sent until you click the link in that message; a tick on an enquiry form or in the site chat is only a request to be asked.

Every message carries a one-click unsubscribe link, and an address that withdraws stays on file marked as withdrawn. That is deliberate: deleting it would let a future import treat it as a new address and email it again.

  • Confirmed by you before the first email
  • One-click unsubscribe in every message
  • Withdrawn addresses are never re-added
  • Ask us to delete an address entirely and we will
07

Your rights under NDPR

The Nigeria Data Protection Act gives data subjects rights over their information. A school administrator can export a person's data, request a correction, or request erasure, and those requests are handled inside the platform and recorded.

Where a legal or safeguarding duty requires us to keep a record, for example a fee ledger or a published result, we say so when the request is made rather than refusing it without explanation.

  • Export one person's data
  • Request correction of a record
  • Request erasure where no duty requires retention
08

Retention, hosting and contact

Records are kept for as long as the school's subscription is active and for the period the school's retention policy and Nigerian law require. Closing a school account starts the deletion workflow, with the school given the chance to export what it needs first.

This policy is published alongside the product and reviewed whenever the service changes materially. Questions about privacy can go to the school that uses the platform, or to us directly.

  • Retention follows the school's policy and the law
  • Export before a school closes its account
  • [email protected] for privacy questions

Questions schools ask

Short answers to the things schools raise before they switch.

Can another school see our students?

No. Each school runs on its own subdomain and its own database. There is no shared table of students anywhere in the platform.

Who at EduMaverick can read a school's records?

Only the platform operators, through a separate console that requires the platform owner role. Every action they take is written to an audit trail the school can see.

How does a parent exercise NDPR rights?

A parent asks the school, which holds the relationship with the family. The school administrator can export, correct or request erasure of that person's data from inside the platform.

Is the data used for advertising?

No. Student, family and staff records are never sold and never used to advertise to anyone.

What cookies does the website set?

Four cookies are always on: sign-in and form protection, a reference for this browser, and the record of your choice. Two more exist only if you accept them: usage measurement, and the cookie that keeps your EduMaverick AI conversation open. Every one of them is set by us; there is no advertising or third-party analytics cookie. The full list is under Cookies and tracking above, and you can change or withdraw any of it from Manage preferences.

I asked for email updates by mistake. How do I stop them?

Nothing is sent until you click the confirmation link, so ignoring that email is enough. If you are already subscribed, every message carries a one-click unsubscribe link, and the address is then kept only as a record that you asked us to stop. It is never re-added by an import.

Questions about this policy?

Privacy and data questions are welcome at any time. We answer within one business day, and a school administrator can exercise every right described here from inside the platform.