There are certain questions that seem perfectly ordinary in educational software until one stops to ask why they are being asked at all.
An email address is a good example.
For years, asking for an email address during account creation has been standard practice nearly everywhere online. It is familiar. It gives a student something recognizable to type into a login box. It can also be useful when a school has approved Google sign-in or another email-based workflow.
But most of my own students do not need email to use Innovation Assessments. They enter a classroom number and a short PIN. That takes them where they need to go. If the platform can identify the right student, enroll that student in the right course, save the work, and return the teacher’s feedback without collecting another piece of personal information, why collect it?
Well, get this: now we do not.
Student registration now begins with the minimum
The public student registration page has been reframed as Obtain Student PIN or Password. It asks for the student’s first and last name—or, in an Alias-Only course, the permitted first name and a system-created alias. It does not ask the student for an email address, and it does not offer the student an opportunity to connect a personal Google account.
Behind the scenes, the software creates a unique internal username so that the account can function normally. That internal value may look a little like an email address because it occupies the same long-established database field, but it is not the student’s real email address and does not receive mail.
This means a student can still:
– receive a classroom PIN;
– enter a course;
– complete and save work;
– receive scores and feedback; and
– participate in live classroom activities.
None of that requires us to know the student’s email address.
Schools remain in control when email really is useful
There are schools that authorize student email and Google sign-in, and there are circumstances in which those tools genuinely help. Innovation Assessments has not removed that choice.
Instead, the choice now belongs to the teacher or school. A teacher may deliberately enter an approved school email address while adding or editing a student. The page displays a reminder to confirm that the school permits the information to be stored. A student cannot independently attach a Google account and quietly expand the information connected with the record.
That distinction matters to me. The software should not make a privacy decision on behalf of a school merely because collecting more information is convenient.
A cleanup tool for existing rosters
The My Students page now includes a tool to sanitize existing student email addresses. When a teacher chooses to use it, the system replaces real addresses with unique internal `@myschool.com` identifiers while preserving the student account, enrollments, submissions, scores, and feedback.
The tool requires classroom PIN login to be enabled first, because students need a working way to return after their email-based login has been removed. It also avoids changing accounts shared with another teacher, where one person’s cleanup decision could otherwise disrupt another class.
This is intentionally not an automatic sweep. A teacher sees a warning before proceeding because students who previously signed in by email or Google will need to use the classroom number and PIN afterward.
Alias-Only courses go a step further
Some schools permit only a first name and an alias to appear in an outside instructional system. Innovation Assessments now supports that model at the course level. An Alias-Only course creates a privacy-safe surname and a non-identifying account reference, while the teacher keeps the real-name connection in the school’s own authorized records.
This is not the right arrangement for every classroom. It is available for the schools that need it, without forcing the same restriction upon everyone else.
Privacy is often a series of small decisions
There is no single button that makes educational technology private. Privacy comes from asking practical questions over and over:
Do we need this information? Who is permitted to enter it? Who can see it? How long should it remain? Can the same educational purpose be accomplished with less?
Removing the student email box may look like a small change. Technically, it was not quite as small as it looked! The registration, login, Google identity, PIN, roster, and account-cleanup workflows all had to agree with one another. Pedagogically, however, the idea is beautifully simple: collect what the class needs and do not casually collect what it does not.
That is the direction in which I want Innovation Assessments to continue growing.
—
*Transparency note: This article was generated with AI assistance from a review of the current Innovation Assessments source code and was reviewed for publication by Innovation Assessments.*
