For schools, departments, and boards
What a privacy review needs to know
MarkScanner helps secondary math teachers mark handwritten paper assessments. It drafts marks and feedback against a rubric the teacher approves, and the teacher decides the final results. This page is for the people who review a tool before teachers use it with student work: privacy offices, IT, department heads, and principals.
Last reviewed October 15, 2026
At a glance
How student data is handled
- Who uses it
- Teachers. Students don’t have accounts and never sign in; they write on paper as usual. Each teacher has their own account, and other teachers can’t see their classes or student work.
- What is collected
- The teacher’s account details; class rosters the teacher adds (student names and identifiers); scanned student work and assessment materials; and the draft marks, comments, teacher edits, and approved results.
- Where it’s stored
- MarkScanner’s database and file storage are hosted in Canada.
- AI processing
- Scanned work is sent to Google’s Gemini API, on a paid tier, to read handwriting and draft marks and feedback. It isn’t used to train AI models, by Google or by us. AI processing may take place outside Canada.
- Teacher control
- Every mark and comment is a draft until the teacher approves it. The teacher can change any of it, and nothing goes back to a student without that approval.
- Deletion
- Teachers can delete a class, an assessment, a student, or a submission. Deleted items sit in a trash for 30 days before permanent removal, and backups expire within 90 days.
- Exports
- Class results as CSV, and feedback sheets and class summaries as PDF, for any approved assessment.
- Sign-in and access
- Teachers sign in with an email and password. On our side, access to production systems is limited to MarkScanner’s maintainers.
The privacy policy is the formal version, including service providers and retention. The trust page is the plain-language summary.
Honest about the gaps
What MarkScanner doesn’t have yet
- Single sign-on (Google, Microsoft, or board accounts).
- Brightspace, Google Classroom, or other LMS integrations. Results move by CSV.
- Organization accounts with central administration. Each teacher has their own account.
- A SOC 2 report or other third-party security certification.
- Self-serve account deletion. Email us and we’ll handle it.
MarkScanner is an early product from a small company in London, Ontario. We’d rather tell you this up front.
For your review
What we can provide
- Written answers to your board’s privacy or security questionnaire.
- A call with you or your privacy office to walk through how data moves.
- The current list of service providers and where they process data.
- A conversation about a data processing agreement, if your board requires one.
Calls ring through weekdays, 10 am to 5 pm ET; otherwise leave a voicemail.
Responsibilities
Who decides what
In Ontario, school boards are institutions under the Municipal Freedom of Information and Protection of Privacy Act (MFIPPA), and many boards review a tool before teachers use it with student work. Whether MarkScanner fits your board’s requirements is your board’s assessment to make. We don’t claim compliance on any board’s behalf; we’ll give you the information you need to decide.
Teachers are responsible for having their school’s or board’s authority to upload student work and rosters. If your board hasn’t reviewed MarkScanner yet, a teacher can still evaluate it with fictional or anonymized papers, or our one-quiz trial, where student names are optional.
Departments
Evaluating MarkScanner as a department
A simple way to start: one or two teachers mark a real assessment, then the department decides together. We help set up the first assessment and talk through what to look for: how the draft marks compare with your own, how much you changed, and whether the feedback is something students can act on.
See the worked examples, how MarkScanner compares with Crowdmark and Gradescope, and pricing. To talk about your department, email [email protected].