Privacy Policy

1. Operator and contact information

Website: https://yinyang-interactive.com.

2. Children, schools, and COPPA

Number Ninjas is designed for educational use by children, including children under 13. Number Ninjas remains responsible for its own obligations under the Children’s Online Privacy Protection Act (COPPA); schools do not assume Number Ninjas’ COPPA compliance obligations. Consistent with Federal Trade Commission guidance, a school may act as a parent’s agent for COPPA consent when Number Ninjas is used for the school’s educational benefit and children’s information is used for no other commercial purpose. School authorization applies only to the educational use described in the notice and agreement accepted by an authorized school or district representative. An individual teacher should authorize use only when the teacher has authority from the school or district to do so.

Roster access and school-connected student processing do not begin until the applicable school authorization is recorded. The school directs its educational use and remains responsible for obligations that apply specifically to the school, including its management of education records and determination of the FERPA basis it uses, where applicable.

Parent and guardian rights for children under 13

Subject to appropriate identity and authority verification, a parent or guardian may:

• request a description of personal information collected from the child;
• review personal information we maintain about the child;
• request correction where appropriate;
• request deletion;
• refuse or withdraw permission for further collection or use; and
• direct Number Ninjas to stop further collection.

Send requests to privacy@yinyang-interactive.com. For a school-managed account, we may coordinate with the school to verify the requester and manage school-controlled education records. That coordination does not eliminate Number Ninjas’ COPPA responsibilities.

3. Information we collect

Teacher Google identity information

Google account identifier, email address, and display name used for teacher sign-in and account matching. Google may include a profile photo when the profile scope is used for the teacher’s display name; Number Ninjas ignores it and does not store or display it.

Student Google identity information

Student sign-in requests the Google account identifier and email address for authentication and matching against a student already provisioned through an authorized Classroom roster. The email address is used transiently during that check and is not retained on the active student record. Student display names come from the authorized Classroom roster.

Classroom course information

For teachers, active course identifiers, names, sections, rooms, states, and Classroom links used to display and select courses.

Classroom roster information

After school authorization and an incremental Google permission grant, we may receive student Google identifiers, display names, class membership, and email addresses provided by Google. Student email addresses are used transiently for account matching or fallback and are cleared before the active student record is stored. Student display names from an authorized roster are retained so teachers can identify students in the dashboard.

Coursework information

Relevant coursework identifiers, titles, descriptions, due dates, points, state, links, and student/coursework context. At a teacher’s direction, Number Ninjas may create or manage Google Classroom coursework. We do not currently send calculated grades to Google Classroom.

Student gameplay and learning information

Assignments, math questions, answers, correctness, timing, scores, game modes, fact focus, progress, mastery, and teacher reports.

Diagnostic information

Diagnostic definitions, participation, questions, answers, correctness, timing, scores, attempts, and longitudinal results.

Character and reward information

Character choices, equipped items, earned cosmetic rewards, inventory, and unlock progress.

Teacher information

Google identity, school and course relationships, authorization records, assignments, diagnostics, settings, and dashboard activity.

Guest information

Autogenerated alias, random pseudonymous guest/session identifier, aggregate game activity and progress, temporary game state, rewards, and character state. Individual question payloads and answers are not retained for guest sessions.

Cookies and persistent identifiers

Essential session cookies authenticate signed-in and guest sessions. An analytics-preference cookie records a teacher’s choice. We do not create a device fingerprint or use advertising or cross-service tracking identifiers.

Security and operational logs

Minimized request, response, error, and security metadata used to operate, troubleshoot, and protect the service. Infrastructure may process an IP address transiently for network security, and exceptional security or error logs may contain it; those logs are subject to the maximum 30-day log lifecycle. IP addresses and approximate location are not stored as part of a child’s gameplay profile.

Teacher-only analytics

If a teacher enables analytics, Rybbit receives teacher interaction and error events. Student and guest events are not sent to Rybbit.

Feedback

Optional teacher feedback may include text, teacher contact or account information, and an optional screenshot. Feedback first goes to Number Ninjas systems. Screenshots are redacted before storage and must exclude classroom and student content.

4. Guest mode and its random identifier

Guest mode requires no Google sign-in, creates an autogenerated alias, and does not permit a child to enter a nickname or other free-text identifier. The random pseudonymous guest/session identifier is used only as reasonably necessary to authenticate the session, maintain aggregate game progress and preferences during the seven-day period, provide user-requested personalization, protect security, prevent abuse, troubleshoot errors, and operate the service. Individual question payloads and answers are processed for the active game but are not retained for guest sessions. A guest identity is not recoverable.

The guest identifier is not used to contact the child, track the child across unrelated websites or services, create an advertising profile, serve behavioral advertising, or market to the child. Guest mode does not store the child’s IP address as part of the gameplay profile, store approximate location, fingerprint the device, or send guest events to teacher analytics.

6. How we use information and minimize collection

We attempt to collect and retain only information reasonably necessary to provide the authorized educational service, maintain security, meet legal requirements, and operate the service. We use information for authentication and account matching, class membership, gameplay, assignments, diagnostics, progress and mastery, teacher reports, teacher-directed Classroom actions, security, support, and maintenance and improvement of the authorized educational service.

We do not sell student personal information; use it for targeted or behavioral advertising; provide it to data brokers; use it for unrelated profiling, marketing, or product development; or use identifiable student information for general-purpose AI training. Appropriately de-identified or aggregate information may be used for service analysis or improvement only where it cannot reasonably identify a student.

7. Service providers

We use the following providers and systems to operate Number Ninjas:

• DigitalOcean, LLC: application hosting and infrastructure, including infrastructure backups.
• PostgreSQL: the primary application database, self-hosted on DigitalOcean infrastructure.
• Redis: session, cache, rate-limit, and active game state, self-hosted on DigitalOcean infrastructure.
• Local Docker and system logging: operational and security logging on DigitalOcean infrastructure.
• Google LLC: Gmail or Google Workspace for support, privacy, security, and other email communications, and Google Classroom when enabled by a teacher.
• Rybbit: optional teacher-only analytics; Rybbit does not receive student or guest events.
• Other child-data processors: none currently.

Providers handling children’s personal information are required by contract or written assurance to use reasonable safeguards and process information only for authorized purposes. We evaluate providers before authorizing child or student information and include them in our retention and deletion processes where applicable.

Processing by DigitalOcean-hosted application, database, cache, logging, and backup infrastructure is integral to operating Number Ninjas and cannot be separately declined while using the applicable service.

8. Retention

Children’s personal information is not retained indefinitely. Our current schedule is:

9. Deletion and stopping collection

Signed-in users may use the account deletion function. Schools may request individual-student, class/course, or school-wide deletion, or stop future collection. Parents may submit verified requests to privacy@yinyang-interactive.com. Active-system deletion is targeted for completion within 24 hours and removes applicable profiles, class memberships, game history, answers, progress, mastery, rewards, character state, diagnostics, Number Ninjas assignments, cached game state, and reasonably linkable derived records.

A stopped or deleted student is placed into a suppression state so routine Classroom roster synchronization does not silently recreate the student. Fresh valid authorization is required before collection resumes. Teacher deletion removes encrypted Google tokens and attempts to revoke the Google refresh token. Coursework already posted to Google Classroom remains in Google Classroom and must be deleted there by the teacher or school. Backup copies expire within their normal maximum 35-day lifecycle and are subject to deletion/suppression reconciliation if restored.

10. Security

We use reasonable safeguards appropriate to the information, including HTTPS, encryption of teacher OAuth tokens at rest, role-based access, server-side class authorization, least-privilege practices, retention and deletion controls, and appropriate vendor safeguards. Number Ninjas also uses network firewall controls to restrict unauthorized access to its infrastructure. We maintain internal security and incident-response procedures. No system can guarantee absolute security. Security concerns may be sent to security@yinyang-interactive.com.

11. Changes to this policy

We may update this policy as Number Ninjas changes. We will update the effective date and provide additional notice and obtain new consent or school authorization where required before materially changing the purposes for which children’s information is collected, used, or disclosed.

12. Contact