Skip to content
UAVProg
Platform

Platform

What you cannot see, and why

The boundaries built into the platform on purpose — private notes, anonymous feedback, and the numbers that are deliberately not attributable to a child.

You can see a great deal about your students: every attempt, every score, the code they wrote, how long they spent. That is the job.

Some things you cannot see, and it is not an oversight. This page says which, and why. It is worth reading properly for two reasons. The first is that a teacher who knows where the line is trusts the tool more, not less. The second is that a parent will eventually ask you, and you should be able to answer.

The shape of it

WITH THE NAME ON IT you already know your roster Scores, on every attempt How many tries they took The blocks and code they wrote Time spent on a mission or quiz Which quiz answers they chose What was handed in late Who has done nothing for a week Their email address, if they have one AS A COUNT ONLY the class, never the child Where the class marked a lesson confusing — how many, per section How many people used a feature Average lesson rating, once enough people have rated it Written feedback on your own course — anonymous, and only once three or more people wrote NEVER, TO ANYONE not to teachers, not to admins The text of a student’s notes Who wrote any particular note Who rated a lesson, and how Whether this student used a particular feature Anyone’s password — including your students’
The left column is deliberately wide: within your own class, teaching requires knowing who did what. The restrictions are on the things that only work if they are private.

Notes are private. Completely.

Students can highlight and annotate lesson text as they read — four colours, including one that means “I find this confusing”.

Nobody reads what they wrote. Not you, not UAVProg, not an administrator. There is no screen anywhere in the product that shows the text of a student’s note, and no export that contains it.

What you get instead is a count. For a lesson you own, an insight panel in the course editor shows how many markers landed on each section of the text, split by colour. Twelve confusion markers on paragraph four is an extremely useful thing to know. Which twelve children, and what they wrote, is not yours.

The reason is simple and it is worth saying to a class: a note is only useful if it is honest, and a note is only honest if nobody is marking it. A student who suspects their teacher reads their annotations writes different annotations — usually none.

Lesson ratings are anonymous

Students can rate a lesson and leave written feedback.

  • Students never see ratings. Not their own class’s, not anyone’s. A lesson does not carry a star count that would tell a child what to think before they start it.
  • If you own the course, you see the average, the spread, and the written comments — with no names and no identifying details attached. Not the role, not the account type, nothing that would let you work backwards to a person.
  • Written comments stay hidden until at least three people have written one. Below that, the panel says so: “Feedback will appear once enough students have responded.” Two comments in a class of twelve are not anonymous, whatever you strip off them.
  • If you merely assigned somebody else’s course, you do not see its ratings at all. The panel degrades gracefully and shows you the confusion and completion signals instead — it does not error, and it does not pretend the data is missing.

Some numbers are deliberately not about anybody

The platform counts how many distinct people used a feature — notes, the simulator, the block editor — in a way that cannot be reversed to individuals. It is not that the answer is hidden from you; it is that the answer was never recorded.

So no screen in the product will ever tell you whether a particular student used notes, and no future version can add one without changing how the counting works. If you want to know whether a child is annotating their reading, ask them.

Two n-gates worth knowing

Quiz statistics shown to students need at least five respondents before anyone sees them. A student who finishes a quiz can be shown how the rest of the class answered — but only once five people have answered, so nobody can work out one classmate’s answers by elimination. Below five they see “Not enough responses yet. Check back later.”

Your view of the same quiz is not gated. You see it from the first response, with names. That asymmetry is intentional: you already know your roster, and you cannot teach a class whose results are hidden from you.

Written lesson feedback needs at least three entries, as above.

The leaderboard is opt-in

Students choose whether to appear on a leaderboard at all. A child who has not opted in is not on it, and there is no teacher control that forces them on.

Separately, you can switch the class leaderboard off entirely for your class: class → Settings → Leaderboard. It is on by default. Turning it off is a reasonable thing to do with a group where competition is not helping.

You may also notice that the Most improved panel is not a leaderboard even though it looks like one. It ranks each child against their own earlier self, never against each other — see Reading your dashboard.

Passwords

Nobody can read a password — not you, not UAVProg’s staff, not an administrator. They are stored scrambled in a way that cannot be undone.

When you reset a class-code student’s password, you are not looking theirs up. You are generating a brand new one, which is why it is shown once and then gone forever: there is nowhere to look it up from afterwards, for anybody. See When a child forgets their password.

What is true about your own class

Inside a class you teach, your analytics are identity-bearing on purpose. Names, scores, attempts, answers. There is no anonymised-teacher mode and there should not be — you cannot help a child you cannot identify.

Two small boundaries even so:

  • The dashboard panels carry names, never email addresses. Every roster in every widget is built from names alone. Emails appear only on the class Students tab, where they exist to tell the two kinds of account apart.
  • Your reach ends at your own classes. Every teacher screen checks that the class is yours before it answers. You cannot see a colleague’s class, and they cannot see yours.

If a parent asks

A short, accurate answer:

The school can see the work their child submits and how they did on it — the same things a teacher would see from marking a book. Their private notes are not visible to anyone, including me. Their lesson feedback is anonymous. Their password cannot be read by anyone. If they joined with a class code, the school did not have to collect an email address for them at all.