-
Where it runs
- Only on web.toddleapp.com. It has no access to any other site. The flag switch, the student sidebar, the home page's additions, the gradebook's toolbar and controls, and the Attendance dashboard's details run in the extension's own isolated part of the browser, drawn inside closed shadow roots that no script on Toddle's page can read or click into.
-
What it reads
- What Toddle already lets you see — gradebook results, rubric descriptors and levels as your school set them up, class staff, student details, today's timetable and attendance, and a student's flags each time the sidebar opens — through an exact list of read-only queries to Toddle's own API, for you at the screen, reusing the session you are already signed in with. It never asks for your password. Toddle's sign-in headers stay in the tab's memory, in one script in Toddle's page, and go nowhere but Toddle.
-
What it writes
- Nothing. Every request it makes is a read, and writes are blocked outright. Message buttons open Toddle's own chat; the extension sends no message itself.
-
What it sends
- Nothing it reads, anywhere but back to Toddle. No account, no analytics, no tracking, no remote code. Student photos load from wherever Toddle serves them, as on Toddle's own page. Licence keys are checked on your machine: a key may name your email or your school's email domain, and where it does, that is compared with your Toddle account in the browser only. The welcome page it opens on install is part of the extension and contacts nothing.
-
Its three outside connections
- The Send feedback form, only when you press Send: what you typed and the version number, to our feedback form, processed by Formspree; a Toddle compatibility report goes the same way, masked and with no student data, only when you press Send report or have switched on sending them automatically. Only while there is a licence, at most one request a day to licenses.nyuchi.com (versions before 0.9.0 asked licences.nyuchi.dev, the same server) for a signed list of cancelled keys' fingerprints, which sends no key, no identifiers and no Toddle data; if it fails, the last result stands. And only when you use the one-time link from your licence email, one request to licenses.nyuchi.com carrying the link's code and nothing else, which returns your key once.
-
What it stores
- On your own machine: your switch settings, your licence key if you have one (a school's is read from its Chrome policy instead), the result of the last check for cancelled keys, the email of the Toddle account last seen signed in, to check who a licence is for, and the masked Toddle compatibility record; and, in Toddle's own site storage, whether flags are concealed, your My classes choice and the academic year Toddle is showing. Your licence key also follows your own Chrome account to your other computers, through Chrome's sync; it is never sent to Nyuchi. No student data: what it reads is held in the tab's memory until the tab is closed or reloaded, and never written to storage.