Skip to content
mimiao
Docs

Getting started

Data security and backups

How school data is protected in Mimiao: database-level isolation, backups every 6 hours with verified restores, platform access boundaries and data export.

Updated:

The short version of how your school’s data is protected — in plain language, without the marketing. The extended version with all the details lives on the Security page.

Your school’s isolation

Mimiao is multi-tenant: there are many schools, but each is isolated at the database level (Row-Level Security). Every query sees only your school’s data, and the database itself guarantees that — not just the application code. Which school you belong to is derived from your sign-in, never from the page address — “walking into” another school by editing a link is impossible.

Backups

  • A database backup is taken every 6 hours.
  • Every backup is verified by a real restore into a test environment.
  • A second copy is stored with a different provider in a different region, protected against overwriting.
  • Once a month, an automated restore drill runs from the off-site copy.
  • Before every system update an extra backup is taken — without it, the update won’t start.

If any of these steps fails, our team is alerted through several independent channels.

Who on the platform side sees your data

The platform’s operations console technically cannot return your school’s record content: no names or contacts, no notes, no payment amounts. The operator sees the school’s name, plan, billing status and a few anonymous counters. The only way inside is support mode: it activates only after your approval, lasts up to 24 hours, shows a banner to everyone in the school, and writes every action into an uneditable log.

Passwords and access

Passwords are stored as irreversible Argon2id hashes — nobody sees them, including us. Sign-in attempts are rate-limited. Access inside the school follows the role: a teacher never sees others’ pay or the school’s till, parents see only their own child. When you revoke someone’s permission, it disappears with their very next request — old sessions don’t live on.

The financial ledger

Financial records are immutable: a payment, refund or accrual can’t be edited or deleted after the fact — only compensated with a new entry that also stays in the history. The database itself guarantees this. For sensitive actions you can enable the four-eyes approval mode.

Your data is yours

The school owner can request a full export at any time: students, lessons, invoices, payments, attendance and homework as CSV files (a ZIP archive). When the archive is ready, a “Data export ready” notification arrives, and the download link stays valid for a limited time. Exports can be run once per day.

If the subscription lapses, the school doesn’t lose its data: the owner keeps read-only access and can pay later. We don’t hold data hostage.