Skip to content

Legal

Data handling

Last updated 7 November 2026. For schools, and for the people who approve software on their behalf. Covers the Toddle Enhancement Extension and the data Nyuchi holds.

The short version. The extension processes student data only inside the teacher's own browser, reading it from Toddle for the teacher at the screen. It stores none of it and sends none of it to us or anyone else. The personal data Nyuchi does hold is about the people who buy a licence, send feedback or ask for support, never about students.

What the extension reads, and why

It reads from Toddle, using the teacher's own signed-in session, only what it needs to draw the view the teacher has opened, and only what that teacher's Toddle account can already see:

Every query it can send is on a fixed, read-only list; it never writes to Toddle. On the home page and the Attendance dashboard it adds a few fields to Toddle's own request instead of sending a second one, and takes them out again before Toddle's page sees the answer.

Where it is processed

In the browser on the teacher's own device, and nowhere else. Answers from Toddle are held in the Toddle tab's memory, never written to storage, until the tab is closed or reloaded or the browser quits. A student's or a class's details are reused for at most 5 minutes, and a student's day for at most 2, before Toddle is asked again; a student's flags are never reused.

What it stores

In Chrome's storage for the extension, on that device:

And three small values in the browser's storage for Toddle's own site: tee-blur-flags (gbx-hide-flags in versions before 0.9.0), whether flags are concealed; tee-course-view, whether the teacher chose My classes in the home page filter; and tee-academic-year, the number of the academic year Toddle last asked for. An older copy of the switches there, tee-settings, is cleared. No student data is stored. An Excel or CSV export is a file the teacher chooses to save, and is then the school's to manage like any other download.

The licence key, and nothing else, is also kept in Chrome's synced storage for the extension, so Chrome carries it to the other computers signed in to the same Chrome account, unless sync, or a school's Chrome policy, turns that off. That is Chrome's own sync, through your Google account; the extension never sends the key to Nyuchi. A key carries the buyer's email address, so that travels with it. The newest key wins on every computer, and removing it on one removes it on all of them. Who a key is for, and the result of the check for cancelled keys, stay on each computer. A school's licence set by its IT through Chrome policy is different: the extension reads it from the policy on each managed browser, and never copies it into its own storage or into Chrome's sync.

Uninstalling the extension deletes everything in its own storage on that computer. The three values on Toddle's site stay until the browser's data for web.toddleapp.com is cleared. Removing a licence key deletes the key (on every computer signed in to the same Chrome account, so remove it before uninstalling if you want it gone from your Chrome account too); the last check's result and the account email stay until the extension is uninstalled. A school's licence set through Chrome policy is not offered for removal in the extension; it is the school's IT that sets the policy.

What leaves the browser

Nothing it reads from Toddle, except back to Toddle. These are the only requests it makes:

Anything else happens only when the teacher does it: saving an Excel or CSV file, opening an email (mailto:) or phone (tel:) link, or sending a message in Toddle's own chat. Like any web request, each request above lets the server that receives it see the device's IP address and browser type.

One thing more leaves your device, and not to us: with Chrome sync on, Chrome carries your licence key to your other computers through your own Chrome account. The extension itself never sends the key anywhere, Nyuchi included.

A licence key carries the buyer's email address, and may also name who it is for: the buyer's email, or for an organisation licence the school's email domain. Where it does, the extension compares that with the Toddle account signed in, inside the browser only, and sends it nowhere. An organisation licence is set by the school's IT as Chrome policy for the extension, so teachers never see or paste the key; typed into the extension, an organisation key is refused and not stored.

The full data schema

This page is the summary. The extension's data schema is the detail: every query it can send to Toddle, with every field it asks for and what each is used for; every value it stores, with its shape and when it is deleted; and every request that leaves the device. It is written for a school's data protection lead or IT team, and for Toddle. It is checked against the code on every change, so a query the code allows that the schema does not describe fails the build, and where something could not be confirmed from the code it is listed as an open question rather than guessed. Ask privacy@nyuchi.com for a copy.

What Nyuchi holds

None of this comes from Toddle, and none of it is about students.

Licence purchases

Nyuchi's licence server and its database, on Cloudflare

The email address the key was issued to, and the address that paid if different; the plan; how many were bought; for an organisation licence, the school's email domains, the seat count and the buyer's answer to the order question (the school and roughly how many teachers); Buy Me a Coffee's purchase and item references; a fingerprint (SHA-256 hash) of the key, never the key itself; when it was issued, emailed and refunded, its expiry, and its status.

The order and payment

Buy Me a Coffee, with cards handled by Stripe

What Buy Me a Coffee collects at checkout. It passes us the email address, the item bought and the answer to the order question. We never see card details.

Licence emails

Sent through Resend

The recipient's address and the email, which carries a one-time link to the licence, never the key itself.

Licence claim links

Nyuchi's licence server and its database, on Cloudflare

For each one-time link: a fingerprint (SHA-256 hash) of the link, never the link itself; the licence it belongs to and a fingerprint of the key it gives; what the server needs to issue that key again; the address it was emailed to; when it was made, when it expires, and when and how it was used (from the extension, the claim page or the Nyuchi console, and for the console the signed-in address that claimed it); and whether a newer link replaced it.

Feedback

Formspree, then recorded in our private GitHub repository

What the person typed (topic, message, an email address if they gave one), plus the extension's version number, or the website page they came from. A Toddle compatibility report from the extension: the masked structure of Toddle's page, never student data.

Support

Intercom

Conversations and emails people send us.

Website analytics

Google Analytics, only with the visitor's consent

Pages viewed, approximate location and device, on this website only.

Who is responsible for what

Who processes data for us

These services handle the data Nyuchi holds, on our behalf. None of them receives student data from the extension.

Cloudflare
Runs the licence server, its database, and the daily list of cancelled keys the extension checks.
Resend
Sends licence emails.
Buy Me a Coffee
Checkout for licences. Stripe processes cards on its behalf.
Formspree
Receives feedback forms from the website and the extension, and the extension's Toddle compatibility reports.
GitHub
Holds feedback as issues in a private repository.
Intercom
Support messenger and support conversations.
Google
Website analytics, with consent; website fonts.
Vercel
Hosts this website.

International transfers

Nyuchi is in Zimbabwe. The services above operate internationally, and most are based in the United States, so the data they handle for us may be processed outside Zimbabwe and outside the country of the school. Student data from the extension is not part of this: it does not leave the teacher's browser. Zimbabwe does not have an adequacy decision from the EU or the UK, so for data that comes to us from there we rely on the safeguards each service provides for international transfers, such as standard contractual clauses in its data processing terms. Ask us and we will tell you which applies to each service.

How long it is kept

Access, correction and deletion

A school, a teacher or anyone else can ask what we hold about them, ask us to correct it, or ask us to delete what we are not legally required to keep. Write to privacy@nyuchi.com. Requests about student data in Toddle belong with the school and with Toddle, because that is where the data is.

If there is a data breach

If a breach affects personal data Nyuchi holds, such as purchase or feedback data, we will tell POTRAZ, Zimbabwe's data protection authority, within 24 hours of finding it, as the Cyber and Data Protection Act [Chapter 12:07] requires; tell the EU or UK regulator within 72 hours where the GDPR requires it; and tell the customers and schools affected without undue delay. We will say what happened, what data was involved, what we are doing about it, and who to contact.

Because the extension stores and sends no student data, a breach on our side cannot expose student data from Toddle.

Data processing agreement

A data processing agreement is available on request from privacy@nyuchi.com. It sets out, in contract form, the data flows on this page: what the extension does and does not process, what Nyuchi holds, the services that process it for us, security, breach notification and deletion.

Related