Privacy policy

Primerz provides an AI-assisted lesson platform for schools and educators. We are based in Hong Kong SAR, and we are the organisation responsible for the personal data described here.

There are two kinds of people on Primerz, and we collect very different amounts from each of them.

• Account data — for educators and school staff: your name, email address and profile picture from your sign-in provider, your school, your role, and your language preference.
• Lesson content — the lessons an educator authors, the material attached to them, and the work a lesson produces: messages, drafts, uploaded files, generated images, and the pages or slides a student builds.
• Teaching and usage records — which step a student reached, whether their work was judged complete, and which model ran, how many tokens it used and what it cost.

A student who joins with a class code gives a display name and nothing else — no email address, no password, no profile. We also set one cookie to keep you signed in and one to remember your language.

To run the lesson you asked for: composing the tutor's instructions, judging submitted work, and generating the images, pages and slides a lesson produces. To show a teacher what their class is doing, live during a lesson and in a report afterwards. And to keep the service working, secure and affordable to run.

We do not sell personal data and we do not use it for advertising. We do not build profiles of students for any purpose other than teaching them, and we do not give any provider permission to use their content for purposes of its own.

Primerz is built on third-party infrastructure. To perform one task, the content that task needs may be sent to the provider that performs it: Supabase (database, sign-in and file storage), DeepSeek (the tutor, the assessment of work, and the authoring assistant), Google (document and image analysis), Leonardo and Flux (image generation), ElevenLabs (speech and transcription), Langfuse (tracing, so we can diagnose and improve the tutor's instructions) and Vercel (hosting). Each processes that content on our instructions, under its own terms.

Most people who use Primerz are school students, and many are under 18. That is why a student joining by code gives us a display name and nothing more. The school or teacher is responsible for having the right to use Primerz with their class, and can ask us to remove a class's records at any time. Teachers should not ask students to type personal, sensitive or identifying information into a lesson.

Lesson records belong to the teacher who ran the lesson, so we keep them for as long as that teacher needs them — the class history and the reports that come out of it. Drafts that were never published, and student sessions a teacher no longer needs, are deleted on request.

You can ask us for a copy of your data, ask us to correct it, ask us to delete it, or object to a particular use of it. Educators can write to us directly; students should ask their teacher first, because we often cannot identify a student who joined with only a code and a display name. We answer these requests under Hong Kong's Personal Data (Privacy) Ordinance and equivalent laws where they apply.

Data is encrypted in transit. Access is restricted by rules that scope a lesson to its own owner, so one educator cannot read another's class. Credentials that connect us to third-party services are encrypted before they are stored. No system is perfect: if we learn of a breach affecting your data, we will tell you — and where a school is involved, the school.

If we change how we handle data we will update this page and the date at the top. Material changes are announced to educators by email. Questions, requests and complaints go to team@primerzai.com.