Groovit Privacy Policy

Our Commitment to Student Privacy

Childrens Wellbeing, Inc. (“Company,” “we,” “us,” or “our”) operates Groovit (“Groovit”), an interactive educational platform that combines physical movement with academic learning for students in kindergarten through eighth grade.

Protecting children’s privacy is central to how Groovit is designed.

We collect only information reasonably necessary for the educational service. Schools may use first names or classroom aliases. If a school supplies a full name, it is stored in the student profile. We do not store photographs or videos from camera gameplay.

We are committed to protecting student information in accordance with applicable privacy laws, including the Children’s Online Privacy Protection Act (COPPA), the Family Educational Rights and Privacy Act (FERPA), and the California Student Online Personal Information Protection Act (SOPIPA).

This Privacy Policy explains what information we collect, how we use it, how we protect it, and the rights schools and parents have.

1. Who This Policy Covers

This policy applies to children using Groovit through participating schools, teachers, school administrators, parents with authorized accounts, and visitors to Groovit.com.

Groovit is designed primarily for school-authorized educational use.

Where permitted under COPPA, participating schools may provide authorization on behalf of parents for the collection and use of student information solely for school-authorized educational purposes.

We do not use information collected through school-authorized student accounts for unrelated commercial purposes.

2. Information We Collect About Students

We believe children should be able to learn and play without providing unnecessary personal information.

Groovit student profiles use limited information, including:

• A student name or classroom alias supplied by authorized school staff, and a login identifier.
• School and classroom membership.
• Grade level and teacher assignment.
• A school-issued login identifier or email address, if used.
• An age entered by authorized school staff, if applicable.
• Game progress, quiz answers, scores, rewards, and participation records.

Account-creation tools may include first-name and last-name inputs, which are combined into a stored name. Schools should use classroom aliases where full names are unnecessary; an alias can be used in these name inputs.

Schools should avoid including students’ last names in usernames, email addresses, or other login identifiers.

We do not require students to provide their home address, personal phone number, or personal email address to participate.

3. Camera Use and Movement Detection

Groovit allows students to control educational games through real physical movements, such as jumping, squatting, and ducking.

When camera-based gameplay is enabled, the platform uses the device’s camera to detect body position and movement in real time.

Groovit does not store photographs, camera images, camera recordings, or videos of students.

Our camera technology works as follows:

• Camera images are processed temporarily in device memory to detect movement.
• For individual play, body-position detection happens locally on the student’s device. For Class Run, it happens on the classroom computer.
• The camera feed is not recorded, uploaded, or stored by Groovit.
• The platform does not use facial recognition to identify students.
• Groovit does not create or store facial identity profiles or faceprints.
• Students can play supported games using keyboard or on-screen controls without enabling the camera.

During signed-in camera gameplay, limited numerical estimates of selected body-position points and movement-control decisions may be transmitted to our secure cloud infrastructure for technical troubleshooting. These records do not contain photographs, camera frames, video, or audio.

Gameplay outcomes, including quiz results, scores, and progress, may be saved to support the student’s educational experience.

Teacher-Led Classroom Activities

Groovit’s teacher-led Class Run feature may use an optional locally installed DuckJump camera service on the classroom computer. That computer processes the camera images and sends movement events to the browser on the same computer; cloud servers do not perform this camera inference. School IT should verify compatible hardware, camera coverage, installation and browser connection permissions before enabling this feature.

This feature detects movement at numbered floor positions. The teacher associates those positions with participating students.

A temporary camera preview may pass locally from DuckJump to the browser on the classroom computer during setup and check-in. The preview is cleared when the activity begins.

Classroom answers and results may be saved for teacher reports.

Camera photographs, video, and pose coordinates are not included in those classroom reports.

4. Student Answers and Written Reflections

Students may answer educational questions or enter short written reflections through activities such as Daily Missions.

This information may be saved to the student’s account and made available to authorized teachers or school administrators.

We use this information only to support educational activities, classroom reporting, student progress, and the operation of Groovit.

Students should not include contact information, passwords, or private health information in written reflections.

Schools and parents may request review, correction, or deletion of this information.

5. Account and Classroom Information

School-managed accounts may contain limited information necessary to provide the educational service.

This may include account identifiers, classroom assignments, authorized parent-account links, sign-in credentials, and teacher-managed classroom PINs.

Groovit may store educational records including:

• Game participation and session results.
• Math and other curriculum progress.
• Quiz answers and performance.
• Rewards, achievements, and teacher-issued coins.
• Associated dates and classroom activity records.

These records allow students to resume their progress and teachers to support classroom learning.

6. Cookies, Browser Storage, and Technical Diagnostics

Groovit uses essential cookies and browser storage to maintain sign-in sessions, remember classroom information and preferences, and support saved gameplay.

The teacher-led Class Run feature may store a classroom spot map or temporary unsaved-answer backup on the teacher’s browser.

These backups expire after seven days. Signing out clears that teacher’s Class Run browser data and invalidates the server session.

We recommend that schools sign out between users on shared devices.

Application Diagnostics

Groovit uses Amazon Web Services (AWS), including AWS CloudWatch Real User Monitoring (RUM) and CloudWatch Logs, to monitor application reliability, identify technical failures, and improve performance.

Limited technical information may include:

• General application error categories and deployed software versions.
• Application file locations associated with errors.
• General areas of the application where issues occur.
• Browser and device information.
• Network IP addresses and approximate location derived from IP addresses, not GPS.
• Technical session labels and performance measurements.

AWS RUM session replay, automatic network-request recording, and RUM tracking cookies are disabled.

Our configured error reports do not include student reflections, camera images, raw error messages, full page addresses, or query strings.

Gameplay and Camera-Control Diagnostics

Groovit may collect limited operational summaries, such as which game screen was opened, whether a game ended, rounded time spent on a screen, frame rate, movement-detection timing, and counts of jumps or crouches accepted by the game.

During ordinary signed-in runner camera play, Groovit also automatically transmits limited technical troubleshooting records through an authenticated API to AWS CloudWatch Logs.

These records may include numerical coordinates and visibility estimates for seven selected head and shoulder points, tracking status, timing measurements, movement-control decisions, and whether the game accepted a jump or crouch.

These diagnostic records do not include student photographs, video, audio, or camera images.

The trace payloads do not include student names, account identifiers, school identifiers, classroom identifiers, or camera hardware serial numbers. Technical request and service metadata may still be processed.

Collection is designed to capture processed pose results, but technical limits or connectivity issues may result in incomplete records.

To associate troubleshooting records from the same browser profile, Groovit stores a randomly generated operational browser label. Additional randomly generated labels distinguish page visits, camera upload sessions, and gameplay attempts.

These identifiers are not student names or hardware serial numbers. Students sharing the same browser profile may share its browser label. Clearing browser storage or using a different profile changes it.

Diagnostic controls may also be available through a special troubleshooting link. These controls allow an authorized user to view a temporary local graph, download diagnostic information, or start and stop AWS diagnostic logging.

Stopping logging prevents new uploads and discards unsent records, although uploads already received by the service may finish. Restarting the camera or reloading the page may resume automatic logging.

Closing the camera stops new capture, although a final limited upload of previously processed diagnostic records may finish.

Access to uploaded troubleshooting records is restricted to authorized operators. There is no public endpoint for reading these traces.

CloudWatch Logs camera troubleshooting records are retained for 30 days under the current operational retention setting. AWS RUM browser diagnostic events are also retained for 30 days.

These diagnostic systems help maintain reliable gameplay. They are not used for targeted advertising or unrelated student profiling.

Personalized Movement Learning

When a student completes movement learning, we save numerical calibration observations, timing measurements, learning outcomes and personalized movement-control settings linked to the student’s account. These settings help recognize that student’s jumps and crouches in practice and levels. They are separate from the operational trace labels described above and do not contain camera images, video or audio.

Stored learning observations and reports have a 30-day retention period from their original capture. Personalized control settings also expire within 30 days. Automated background cleanup removes expired measurements from the application database and restricted AWS archive, including older archive versions. Copying, retrying or recalculating a recording does not restart its retention period. Current, unexpired movement settings are not changed by cleanup; a student may need to repeat movement setup after their settings expire.

The production database uses a rolling set of eight daily disaster-recovery snapshots. A snapshot taken before deletion can retain a copy for up to eight additional days. These backups are not used for ordinary gameplay or analytics, and expired movement data must be removed before a restored database returns to service. Background deletion takes processing time; the retention period is not a promise that every physical copy disappears at the exact expiry instant. Minimal account and revision receipts without movement measurements may remain to prevent delayed requests from restoring deleted records.

7. How We Use Student Information

We use collected information only to:

• Create and manage authorized student accounts.
• Save educational progress and game results.
• Allow teachers and administrators to support student learning.
• Enable educational games and classroom participation.
• Provide authorized school reporting.
• Maintain, secure, troubleshoot, and improve Groovit.

We do not use student information to create advertising profiles or for commercial purposes unrelated to providing the educational service.

8. What We Never Do

Groovit maintains strict limitations on the use of children’s information.

We do not:

• Sell, rent, or trade children’s personal information.
• Use children’s information for targeted or behavioral advertising.
• Allow third parties to use student information for targeted advertising.
• Build marketing profiles of children.
• Use facial recognition to identify students.
• Store students’ photographs, camera images, or videos from gameplay.
• Share student information for commercial purposes unrelated to providing the educational service.

We disclose student information only as necessary to operate the educational service, under appropriate protections, or as otherwise permitted or required by applicable law.

9. Service Providers and Third Parties

Groovit works with selected technology providers that support secure hosting, storage, email delivery, and application monitoring.

These providers process limited information only as needed to provide their services, subject to applicable contractual, security, and privacy protections.

We do not provide student information to these companies for targeted advertising.

If a use or disclosure of children’s personal information requires separate verifiable parental consent under applicable law, we will obtain that consent before proceeding.

10. Data Retention and Deletion

We retain student information only for as long as reasonably necessary to provide the educational service or satisfy applicable legal obligations.

Our retention practices include:

• Student account information and educational progress are maintained while the school keeps the account active or as directed by the school.
• When a school ends its use of Groovit, or an authorized deletion request is received, we delete associated student personal information within 60 days, unless retention is required by law.
• AWS camera troubleshooting traces are retained for 30 days under the current configuration.
• AWS RUM diagnostic events are retained for 30 days.
• Movement-learning observations and reports expire after 30 days from original capture; personalized settings expire within 30 days. Automated cleanup covers the database and all movement-archive object versions. Production disaster-recovery snapshots expire on their separate eight-day cycle, as described above.
• Temporary classroom browser backups expire after seven days.

Groovit does not store students’ camera photographs or videos, so there are no such recordings retained in our systems.

We do not retain children’s personal information indefinitely.

11. Data Security

We use technical and organizational safeguards designed to protect student information against unauthorized access, loss, misuse, and disclosure.

These include:

• TLS encryption for information transmitted over networks.
• Database encryption at rest.
• Hashed account passwords.
• Role-based and classroom-level access controls.
• Sign-in attempt protections.
• Restricted access to operational logs and diagnostic records.
• Ongoing operational monitoring.

Classroom PINs operate as a separate sign-in method and can be viewed or reprinted by authorized school staff.

No internet-based service can guarantee absolute security, but we regularly evaluate and improve our safeguards as the platform develops.

Unauthorized Access and Incident Notifications

Report suspected unauthorized access or disclosure of student information to privacy@groovit.com. Our privacy coordinator and technical response team investigate reports, preserve relevant evidence, contain affected access and take appropriate steps such as revoking sessions or resetting credentials. This is an operator-managed process, not a promise of automatic detection or automated notices.

We notify the school’s designated contact without undue delay after becoming aware of unauthorized access to or disclosure of its student information, subject to applicable law, and provide known facts and follow-up updates. We coordinate with the school to identify affected students and arrange required parent or guardian notices, record responsibility and delivery, and comply with applicable legal and contractual deadlines. Coordination does not remove our own notification obligations. Specific contacts, delivery methods and contractual deadlines should be recorded in the school agreement.

12. School Consent and Parental Rights

Groovit is intended for school-authorized educational use.

Groovit serves kindergarten through eighth grade and does not impose a separate numerical minimum age for a school-managed student account. Adults manage school onboarding and account creation. Students under 13 may participate only with the required authorization or consent.

Where legally permitted, schools may consent on behalf of parents to the collection and use of student information for school-authorized educational purposes under COPPA.

Before student use, an authorized school representative must receive the privacy notice and document the educational purpose, approved features and authorization. Where a school cannot lawfully authorize a use on parents’ behalf, the necessary parental consent must be obtained first. School authorization does not permit unrelated commercial use or replace Groovit’s own obligations. Schools should make this notice available to parents.

Where FERPA applies, Groovit acts as a service provider to participating schools, which retain control over education records. We process those records under the school’s direction and applicable agreements.

Parents and schools may request to:

• Review personal information collected about a student.
• Correct inaccurate information.
• Request deletion of student information.
• Refuse further collection or use of a child’s personal information, subject to applicable law and service requirements.

Parents should contact their child’s school or reach us directly using the contact information below.

We may coordinate with the school and verify the requester’s authority before providing, correcting, or deleting student records.

13. Children Outside a School Setting

Groovit is designed primarily for educational use authorized by a participating school.

If we learn that student information has been collected without required authorization or consent, we will investigate and take appropriate steps, including deletion when required.

Parents may contact us with any concerns.

14. Changes to This Privacy Policy

We may update this Privacy Policy as our technology, practices, or legal obligations change.

When material changes are made, we will update the effective date and notify participating schools as appropriate, including before changes take effect when required by law.

15. Contact Us

For questions about this Privacy Policy, student information, or privacy-related requests, please contact:

Childrens Wellbeing, Inc.
Operator of Groovit (formerly The SuperMe Club)
Website: https://groovit.com
Email: privacy@groovit.com

We take student privacy seriously and welcome questions from parents, teachers, and school administrators.