BUILT FOR KIDS.
BUILT TO BE SAFE.

NORTH is designed from day one to be safe inside a K–12 classroom — no student logins, no full names, no source code hosted by us, no advertising. Plain-language summary below; the binding legal terms live in our full .

FERPA-alignedCOPPA-alignedNo student PII beyond first name + initialNo student logins

// Four principles

HOW WE THINK ABOUT STUDENT DATA.

No student logins, ever

Students never create an account on CivicRoot. The teacher manages the roster on the student's behalf, and student-facing curriculum (First Light, the public lessons, Starter Kits) is fully open — no sign-in required to learn or build.

Minimum viable data

We store first name + last initial only — the smallest amount of information needed to give a teacher a usable roster. No PII beyond what a classroom seating chart already shows.

Student code lives on the student's tools

Real engineering happens on GitHub, Replit, and Hugging Face — accounts the student or family controls. CivicRoot never hosts student source code or repositories, which sidesteps the largest district IT and data-residency concerns.

Teacher-managed, school-approved

The on-site teacher is the data controller for their cohort. They add students, mark milestones, and decide what (if anything) gets published to the public showcase. Nothing goes public without explicit teacher approval.

// On the record

EXACTLY WHAT WE STORE — AND WHAT WE DON'T.

We store

Student first name + last initial
Teacher-entered only. E.g. "Maya R." — never full names.
Age group (9–12, 13–15, 16–18)
Used to assign the right NORTH track. No date of birth stored.
Optional pronouns
Only if the teacher provides them.
Curriculum progress (per module)
Whether a module is complete. Marked by the teacher.
Teacher email (the on-site contact)
So the teacher can sign back into their cohort dashboard.
Project submissions (when made public)
Title, description, links — published only with teacher approval.

We never store

×Full student names
×Student email addresses
×Dates of birth
×Home addresses or phone numbers
×Student logins or passwords (students never log in)
×Photos of students
×Grades or transcript data
×Behavioral or disciplinary records
×Biometric data
×Location/GPS data
×Advertising or marketing identifiers

// Roster flow

THE TEACHER-MANAGED ROSTER MODEL.

STEP 01

TEACHER SIGNS IN

Only the on-site teacher (the school's contact) has an account. They sign in with their school email — no student credentials anywhere in the system.

STEP 02

TEACHER ADDS THE ROSTER

First name + last initial only. The teacher controls who's on the list, and can remove a student at any time from their cohort dashboard.

STEP 03

STUDENTS LEARN — NO LOGIN

Curriculum, First Light, and Starter Kits are open to anyone. Students never type a password. The teacher tracks who completed what.

// Your rights

FAMILIES & SCHOOLS ARE IN CONTROL.

For parents & guardians

[+] Ask the teacher to remove your child's record at any time — it's deleted from our database.
[+] Decide whether your child's project gets published to the public showcase (default: no).
[+] Your child can keep their code on their own GitHub/Replit when the program ends — they own their work.

For schools & districts

[+] Export your cohort's roster and progress data at any time (CSV).
[+] Request full deletion of cohort data at end of program — handled within 30 days.
[+] NORTH is LMS-agnostic — you can deliver it through Canvas, Schoology, Google Classroom, or your own portal without sharing extra data with us.

// Questions?

TALK TO US BEFORE YOU ADOPT.

We're happy to walk principals, IT directors, and parent groups through exactly how NORTH handles data — and to sign a district-specific data agreement if your policies require one.

BUILT FOR KIDS.BUILT TO BE SAFE.