About 'The New Earth Project'
Students learn how to think, build, and collaborate like real problem-solvers. They practice evidence-based explanations, test ideas, refine designs, and understand trade-offs across themes like energy, water, food, habitat, and governance.
They learn to communicate clearly through structured handoffs, work with partner classes across states and countries, and rotate roles so every student contributes. Along the way, they build durable skills -teamwork, iteration, creativity, and problem-solving - while developing practical AI literacy by using AI to ask better questions, organize evidence, and clarify their explanations. New Earth feels like play, but the skills are real and long-lasting.
Who Is The New Earth Project For?
The New Earth Project is for students ages 7 - 18 and the teachers who want a ready-to-run, collaborative STEM challenge.
We support Title I, rural, and low-income schools first. Any class, anywhere, can join.
AI & Safety
The New Earth Project uses AI as a safe support tool - not a shortcut. Students use AI to ask better questions, plan tests, and clarify their explanations, but they must verify everything with real evidence. Teachers see every prompt and draft, and AI never grades or replaces student thinking. The platform is pseudonymous, teacher-moderated, FERPA/COPPA-aligned, and designed with built-in filters and privacy-by-default settings to keep students safe while they collaborate.
What Is The New Earth Project?
The New Earth Project is a global, non-competitive build inside Minecraft.
Students team up across schools and countries to design a sustainable “New Earth” together.
Each class contributes one piece, passes it on, and helps build a shared future.
New Earth — Privacy & Safety Explainer
Plain-language overview for families, teachers, and partners
New Earth is designed so the safest settings are ON from the start. Think of it like a car that already locks the doors and buckles the seatbelt—comfort can be adjusted, but safety is the default.
The pieces (in simple terms)
-
- Pseudonymization: We replace names with codes (e.g., “Team-4-Student-A”). A separate, protected list held by the school links codes back to students.
-
FERPA/COPPA alignment: We follow U.S. student-privacy rules: obtain parental/guardian consent where needed, collect only what’s necessary, keep it secure, and never sell student data.
-
Role-based access: People only see what they need: students see their team work; teachers see their classes; admins only what’s required to keep the system safe.
-
Retention schedules: We keep information only for as long as it’s needed for learning and safety, hen delete it on a set schedule.
-
Audit controls: Like a security camera for the system: it records who viewed or changed what and when, so unusual access can be investigated.
What we share with the field (never personal data)
-
De-identified rubrics: Scoring guides and summary patterns (e.g., how “handoff clarity” improves without any names or identifying details.
-
Schemas: A simple map of the data fields (e.g., timestamp, team code, rubric score) so others can build similar programs—no personal data.
-
Observation snapshots: High-level patterns from classroom observations (e.g., role rotation increased participation) without identities.
A quick walkthrough
1 Before: parents/guardians are informed; student accounts use codes; teacher permissions are set.
2 During: students exchange message-packets under teacher supervision; activity is logged under
codes; safety filters run.
3 After: items not needed are deleted on schedule; only minimal, coded data remains for improvement;
shared materials are de-identified.
Questions? Contact your school lead or STEMAIVERSE program staff. We’re happy to share details in plain language.