Security and privacy

How we look after your centre's data

Your parents trust you with their children. You trust us with their information. Here's exactly what we do to protect it - the real specifics, not boilerplate.

POPIA compliance

ClassNest is built around the Protection of Personal Information Act (POPIA), which has been in force since 1 July 2021. POPIA is South Africa's equivalent of GDPR - it tells every organisation how to handle personal information.

For your centre. You are the "responsible party" under POPIA for the personal information of your parents, children, and staff. ClassNest is your "operator" - we process the information on your instructions, within the limits of what the software needs to do its job.

What the app helps you do.

  • Respond to parent access requests: every piece of information the app holds about a parent or child is accessible to you in your account.
  • Honour consent: nothing goes to parents unless you send it. Automatic reminders stay off until you switch them on, and you choose whether each payment gets a receipt.
  • Keep a clear record of invoices sent, statements issued, and communications logged against each parent.
  • Mark children as withdrawn when a family leaves, so they drop out of your daily lists and billing while their records stay available for your own record-keeping.

If you want a practical walk-through of POPIA for your centre, see our POPIA Compliance Checklist.

Where your data lives

ClassNest runs on managed cloud infrastructure. We don't run our own servers; we use providers whose specialty is running secure infrastructure at scale.

  • Database and files: Supabase (managed PostgreSQL), hosted in the European Union (Ireland), where the GDPR gives protection at least as strong as POPIA. Your centre's records, invoices and uploaded documents sit here.
  • Application hosting: Vercel. The ClassNest web app runs on Vercel's global edge network.
  • Transactional email: Resend. Invoice emails, statements, and reminders go out through Resend's authenticated mail infrastructure.
  • Document generation: invoice and statement PDFs are produced by our own service, hosted on Fly.io in Johannesburg.

Supabase and Vercel are independently audited to SOC 2 Type II and ISO 27001, so the infrastructure your data runs on meets enterprise security standards.

Encryption

  • In transit: every connection between your browser and ClassNest uses TLS 1.2 or higher. No plaintext traffic, ever.
  • At rest: your database is encrypted on disk using AES-256 by Supabase. Backups are encrypted the same way.
  • Email: invoice and statement emails are sent via TLS; PDFs attached to emails are encrypted in transit along with the message.

Access controls

Inside your account. Only you, the owner, can sign in and see your centre's data. Every sign-in is verified through Supabase's authentication system. Passwords are stored as salted hashes; we never see them in plaintext.

Inside ClassNest. Administrative access to production systems is restricted to ClassNest core personnel and used only for support, maintenance, and diagnosing issues you report.

Support access to your account. We don't log in to your account unless you ask us to help with something specific and grant permission in writing. When support is done, access ends.

Backups and recovery

Your data is backed up regularly, and backups are kept separately from the live system. Before any change to the database, we take a fresh backup first.

If data loss ever happens on your centre's account, we restore from the most recent good state and explain exactly what was affected and what we did. We don't hide incidents.

How we handle children’s data

We hold only what your centre chooses to record: each child's name, date of birth, class, enrolment details, parent contacts, any medical or allergy notes, and documents you upload, such as a birth certificate. Documents are stored privately and open only through short-lived secure links from your account.

What we never do.

  • Sell your data to anyone. Ever.
  • Share it with advertisers, marketers, or data brokers.
  • Use it to send communications to parents on your behalf without your explicit action.
  • Look at your data for any reason other than supporting you or keeping the service running.

Third parties who touch your data

We're explicit about every third-party service that could hold any piece of your centre's data. Each one is used for a specific purpose and bound by their own data protection terms.

ProviderWhat they doSecurity posture
SupabaseManaged database hosting your centre's recordsSOC 2 Type II, ISO 27001
VercelApplication hosting (the app you log in to)SOC 2 Type II, ISO 27001
ResendInvoice, statement, and reminder email deliverySOC 2 Type II
Fly.ioCreates invoice and statement PDFs (Johannesburg)SOC 2 Type II
SentryTechnical error reports, so we can fix problems quicklySOC 2 Type II, ISO 27001
PayFastClassNest subscription payments (SA payment gateway)PCI-DSS compliant

PayFast handles your ClassNest subscription payments. Your card and banking details are entered directly into PayFast's secure interface; ClassNest never sees or stores them.

If something goes wrong

POPIA requires us (and you) to report personal information breaches as soon as reasonably possible. The Information Regulator's guidance expects notification within 72 hours as best practice, and that's the standard we work to.

If we discover a security incident that affects your centre's data, we'll:

  • Contain the incident and work out what happened.
  • Notify you directly at your account email address with what we know, what's affected, and what we're doing about it.
  • Notify the Information Regulator in line with POPIA timelines.
  • Publish a post-incident summary once the investigation closes, so you can see exactly what went wrong and what we changed.

If you think you've found a security issue in ClassNest, please email support@classnest.co.za with the details. We respond within 48 hours, usually faster.

How we build and run ClassNest

  • Every centre is kept separate. Access rules in the database itself make sure one centre can never read another's records, even if the app had a fault.
  • Security review before release. Anything that parents or the public can reach, such as the parent page and enrolment forms, is reviewed for security before it goes live.
  • Monitoring. The app and its software dependencies are checked for known vulnerabilities every week, uptime is monitored around the clock, and errors are reported to us as they happen.

If your centre has specific security or compliance requirements - NDAs, data processing agreements, RFP responses, security questionnaires - email support@classnest.co.za. We handle these directly.

Questions about security?

Email support@classnest.co.za with your question. We respond within 48 hours, usually faster, and we'll answer specifics - where your data is stored, how it is backed up, contractual terms - in detail.

Two of us built this. One of us answers the WhatsApp.

Try ClassNest free, or let us show you around in a 15-minute call.

The ClassNest founders