Data Minimization
Collect less whenever possible and avoid asking for information that is not needed for the learning experience.
Badgie Academy is committed to protecting students, supporting educators, and promoting responsible technology use. This Trust Center explains the privacy, safety, security, accessibility, and school partnership principles that guide the platform.
Badgie Academy is designed around simple privacy principles that keep the student learning experience focused, age-appropriate, and understandable for families and schools.
Collect less whenever possible and avoid asking for information that is not needed for the learning experience.
Use information to support learning, progress, safety, implementation, and school or family communication.
Use plain language, student-safe defaults, and parent or school awareness for younger learners.
Connect privacy to digital citizenship, AI literacy, cybersecurity awareness, and careful technology habits.
Explain what is collected, why it matters, and how schools and families can ask questions.
We collect only the information necessary to support educational experiences.
This is a plain-language summary of Badgie Academy's current data practices. Schools with formal vendor review requirements should read this alongside the full Privacy Policy.
Any information collected is used to provide educational content, support learning, respond to feedback, improve lessons, and help schools and families understand pilot results. Badgie Academy uses information for educational purposes only — never for advertising or unrelated commercial purposes.
Parents and schools should know how the learning experience is being used, what information is needed, and how students can report concerns. Student protection means keeping privacy, safety, and age-appropriate communication central to implementation decisions.
Badgie Academy is built to respect student privacy and keep any data use tied directly to learning.
Student information is not sold. Badgie Academy does not and will not sell student data for advertising, commercial, or unrelated purposes.
Student personal information — names, emails, contact details — is not collected during the current pilot. The platform stores only anonymous learning-progress data (lessons completed, points, badges) linked to a random code, never to a student's identity. Any future collection will be limited strictly to what supports the learning experience or school implementation.
Students have a right to clear information about what is collected and how it is used. Privacy is a design principle, not an afterthought.
Any future data collection will serve instructional, safety, feedback, and student growth purposes exclusively — not advertising or commercial goals.
Parents, guardians, and educators will have clear, plain-language information about privacy practices before any student accounts or data collection are introduced.
Badgie Academy's pilot deployment runs on Cloudflare's global infrastructure. Students have no logins and no passwords, so there is no student credential to steal. Teachers and parents do have accounts, and those hold an email address and a hashed password — the security measures protecting them are described below. No independent third-party security audit has been performed.
All Badgie Academy pages are served over HTTPS via Cloudflare. Every connection between a user's browser and the platform is encrypted in transit.
Badgie Academy is deployed on Cloudflare's enterprise-grade global content delivery network — the same infrastructure trusted by millions of organizations worldwide.
Students never sign in. There is no student password field anywhere in the system, so there is no student credential to steal and no student authentication data at risk.
Teacher and parent accounts exist and hold an email address. Passwords are stored only as a slow one-way hash (PBKDF2-HMAC-SHA256, applied in six chained passes of 100,000 iterations — 600,000 iterations of work per password guess, since the platform caps a single call at 100,000), never in readable form. Sign-in cookies are HttpOnly, Secure, and SameSite=Strict, so page scripts cannot read them and other sites cannot send them. Sign-in attempts are rate-limited.
Badgie Academy collects no student names, email addresses, or contact information. Progress data (lesson completions, points, badges) is stored against a random code — never a student's identity. Student IP addresses are not stored; only a one-way scrambled value used for rate limiting, deleted after 30 days.
The student record is a random code, a generated nickname, and progress. There is no student name or email in the database for an attacker to take. Note that a linked parent account does connect an adult email address to a child's record — see the Privacy Policy, Section 5.
Pages still permit inline scripts and styles, which is weaker than our own target and is deferred rather than fixed. No independent penetration test or third-party security audit has been performed. Both are stated here rather than left out.
If a privacy, safety, or security concern is reported, the response should be calm, documented, and focused on protecting students and restoring trust.
Understand what happened, who may be affected, and what information or safety issue is involved.
Limit further exposure or harm while the concern is reviewed.
Inform the right school, family, or program contacts based on the situation and agreements in place.
Restore normal learning activity only after reasonable steps have been taken to address the issue.
Review what was learned and update content, workflows, or safeguards where needed.
Badgie Academy teaches responsible technology use, but student safety depends on trusted adults, clear reporting paths, and supportive school or family response.
If a student feels unsafe, they should immediately contact a trusted adult, parent, teacher, counselor, or administrator.
Badgie Academy is designed to support school conversations about student privacy, responsible educational use, and appropriate implementation workflows.
Badgie Academy does not receive student education records from schools, does not import rosters, and stores no school-issued student identifier. No FERPA school-official agreement has been signed with any district, and no legal opinion on FERPA applicability has been obtained. Schools should review data needs, access roles, parent communication, and record-handling expectations before production use — and should ask us for an agreement if they need one.
No student account, email field, or password field exists; student nicknames come from a server-enforced fixed list; student IP addresses are stored only as a scrambled rate-limit value deleted after 30 days. No verifiable-parental-consent workflow has been built, and no legal opinion on COPPA applicability has been obtained. For younger learners, implementation should be guided by the school, parent, or program leader who understands the learning context.
Badgie Academy's current pilot is intentionally simple. Future versions will add account and administrative safeguards carefully, with privacy review completed before any new features launch.
Separate student, teacher, parent, and administrator views and permissions.
Add thoughtful sign-in, recovery, and session protections if accounts are introduced.
Give schools and programs clearer controls over classes, student access, and pilot settings.
Review consent, retention, exports, deletion requests, and parent or school communication workflows.
Continue improving keyboard navigation, labels, readability, and assistive technology support.
These answers reflect the current pilot-phase deployment.
From students: nothing personal — no names, emails, or contact details, and no student account. The platform stores learning-progress data (lessons completed, points, badges) against a random code, plus any text a student types into a build reflection, which is saved as typed. From adults: teacher and parent accounts store an email address, a hashed password, and a display name. Full detail is in the Privacy Policy.
Badgie Academy is designed around age-appropriate educational content, safe cybersecurity learning, responsible AI use, and trusted adult involvement.
Students should contact a trusted adult immediately. Adults should document the concern, support the student, and follow school or program safety procedures.
Individual progress is stored — lessons completed, whether each check answer was correct, points, badges, and certificates — against a random code, not a student identity. A teacher signed in to their own account sees per-student totals for their own classroom (lessons completed, points, last active), but not which answer a student chose on a given question.
Badgie Academy's current pilot requires no student account information of any kind. Schools may separately collect their own classroom data — roster records, reflections, surveys — governed by their own policies.
The product favors data minimization, educational purpose, transparency, student protection, and school or parent awareness.
Schools can use Badgie Academy in classrooms, advisory periods, STEM programs, homeschool settings, church schools, after-school programs, and youth organizations.
School leaders, technology staff, teachers, and families should review what data is needed and what workflows are appropriate before a larger rollout.