Pigeonz.Academy
Privacy PolicyTerms of ServiceDelete accountStudent Data NoticeSchool AgreementGoogle data controlsSchool IT

School Student Data Agreement

Effective date: November 10, 2026

Document version: pigeonz-2026-11-10-v1

This public agreement describes the student-data terms offered by YinYang Interactive LLC for Pigeonz.Academy. The accepting school or district is identified in its electronic authorization record or separately signed agreement. These terms are designed to support school privacy review and do not guarantee or certify legal compliance.

Shared school pigeons and cosmetics

For school accounts using games that support shared characters and cosmetics, Pigeonz.Academy stores the selected pigeon, verified character unlocks, cosmetic grants, equipped outfits and seen state under that account’s internal identity. Each game determines activity completion and reward eligibility on its own server. The platform receives source identifiers, eligibility and retention deadlines; sharing cosmetics does not share answers, academic scores or classroom histories with other games. Each game retains its own reward catalog and weights. Guest identities and local guest rewards are separate and are not merged into school accounts.

Cosmetic grants and unlocks expire with their supporting activity or a shorter classroom deadline. Wearing an item in another game does not extend its retention. School exports and coordinated deletion include this central state and pending reward deliveries.

1. Parties and authority

The provider is YinYang Interactive LLC, operator of Pigeonz.Academy. “School” means the school or district identified through the authorized representative’s Pigeonz.Academy onboarding or account, unless a separately executed agreement identifies it differently. A person accepting electronically for a School represents that they have authority to do so, and that acceptance binds that School.

2. Scope and educational purpose

Pigeonz.Academy may process student information only for school-authorized Google Classroom or ClassLink district roster import; student authentication and account matching through the school-enabled provider; educational gameplay and learning activities; assignments; diagnostics; progress and mastery; teacher reporting; teacher-directed Google Classroom coursework; and the security, support, operation, maintenance, and improvement necessary to provide the authorized educational service.

This Agreement applies to the game scope recorded in the School’s authorization. The School may authorize selected games only, or all current and future Pigeonz.Academy games covered by this Agreement. The all-games option includes future games only when they follow the same disclosed data categories, educational purposes, processors, retention rules and other student-data practices. Selecting every current game individually does not authorize future games. Existing selective approvals remain selective until a new approval records the broader choice. The scope remains subject to the authorization’s school/classroom boundaries, expiration and revocation. Materially new data categories, purposes, or disclosures require updated notice and additional authorization where required before processing begins.

3. COPPA

Pigeonz.Academy remains responsible for its own COPPA obligations. Consistent with FTC guidance, a school may act as the parent’s agent for consent when student information is collected solely for the school’s educational benefit and for no other commercial purpose. School authorization is limited to that educational use. Pigeonz.Academy will not use school-authorized student information for unrelated commercial purposes, and this Agreement does not transfer Pigeonz.Academy’s COPPA obligations to the school.

4. FERPA school-official framework

Where the school chooses to rely on FERPA’s school-official exception, the parties intend that Pigeonz.Academy: performs an institutional service or function for which the school would otherwise use employees or contractors; has a legitimate educational interest in relevant records solely to provide the authorized service; is under the school’s direct control regarding the use and maintenance of education records; uses personally identifiable information from education records only for the purposes for which the school disclosed it; and does not redisclose that information except as permitted by this Agreement, the school’s written direction, or applicable law. Where applicable, Pigeonz.Academy must also meet the criteria specified in the School’s annual FERPA notice for being a school official with a legitimate educational interest. This clause does not represent that every school relies on that exception or that FERPA regulates Pigeonz.Academy in exactly the same manner as a federally funded school.

5. Ownership and limited rights

The school and student retain applicable rights in education records and student-provided information. Pigeonz.Academy receives only the limited rights necessary to provide, secure, support, maintain, and improve the authorized educational service under this Agreement and the Privacy Policy.

6. Advertising and commercial restrictions

Pigeonz.Academy will not sell student information; use it for behavioral advertising or targeted advertising based on student data; market to students based on education records; provide it to data brokers; use it for unrelated profiling or unrelated product development; or train general-purpose AI or machine-learning models with identifiable student information. Appropriately de-identified aggregates may be used for service analysis only where they cannot reasonably identify a student.

7. Security

Pigeonz.Academy will maintain reasonable administrative, technical, and organizational safeguards appropriate to student information, including access controls, HTTPS, encrypted teacher OAuth tokens, server-side authorization, least-privilege practices, retention and deletion controls, network firewall controls that restrict unauthorized infrastructure access, and appropriate provider safeguards. We maintain internal security and incident-response procedures without publishing security-sensitive implementation details.

8. Service providers and subprocessors

Pigeonz.Academy may use providers necessary to operate the service. We will evaluate providers handling child or student information, obtain appropriate written contractual assurances, require reasonable confidentiality, security, and integrity safeguards, and restrict processing to authorized purposes. The current list is maintained in the Privacy Policy’s Service Providers section. It identifies Cloudflare’s public HTTPS proxy and static delivery, DigitalOcean-hosted infrastructure, PostgreSQL, Redis, local logging, backups, and Google services, and ClassLink and school-designated roster services for school-enabled connections. OneRoster is a data standard, not a separate provider. Pigeonz.Academy does not send student answers, scores, progress, or diagnostic results back to ClassLink or the district roster service.

9. School review, access, and export

On a verified request, Pigeonz.Academy will provide the school with the categories of information held, processing purposes, applicable retention dates, access to applicable student/course records, and an export where reasonably available. The school may request correction of inaccurate information.

10. Parent and student requests

Pigeonz.Academy will reasonably assist the school with applicable parent or student education-record and privacy requests. Parents may also contact [email protected] directly for COPPA-related access, correction, deletion, withdrawal, or stop-collection requests. We may verify identity and authority and coordinate school-managed records with the school.

11. Deletion and stopping collection

The school may request individual student, class/course, or school-wide deletion and termination of future collection. Applicable active-system records are targeted for deletion within 24 hours, including profiles, memberships, gameplay, answers, progress, mastery, rewards, character state, diagnostics, Pigeonz.Academy assignments, cache, and reasonably linkable derived records. A stopped or deleted student is suppressed from routine roster recreation unless fresh valid authorization permits renewed collection. Backup copies expire within 35 days and are reconciled against deletion and suppression records if restored. Google Classroom posts remain in Google and are controlled and deleted there by the teacher or school. Pigeonz.Academy deletion does not delete the school’s source ClassLink account or district roster; the school manages those source records. ClassLink-linked identities are covered by the same Pigeonz.Academy deletion and suppression controls.

12. Retention

The Privacy Policy’s retention schedule applies: student gameplay is retained 13 months after collection, diagnostics 25 months after collection, inactive classroom relationships 90 days after becoming inactive, operational/security logs up to 30 days, active Redis game state up to four hours, and backups up to 35 days. The 90-day deadline applies to records associated solely with that inactive classroom; records needed for another active, authorized classroom relationship remain under that relationship’s schedule. Pigeonz.Academy will not retain children’s personal information indefinitely. Non-identifying aggregates may be kept longer only if they cannot reasonably be linked to a student or user.

13. Security incidents

Pigeonz.Academy will notify the school without unreasonable delay following discovery of a security incident involving the school’s student information, and within any shorter period required by applicable law or an applicable school or district addendum. To the extent known and legally permitted, notice will reasonably describe the nature of the incident, categories of affected information, mitigation actions, and relevant next steps.

14. Termination

When authorization is withdrawn, the school stops using Pigeonz.Academy, or this Agreement ends, Pigeonz.Academy will stop new collection under that authorization, revoke or inactivate affected relationships, apply the retention/deletion schedule, suppress stopped or deleted students from routine recreation, and remove encrypted teacher OAuth tokens when the teacher account is deleted while attempting Google token revocation. Published Google Classroom posts remain under teacher or school control in Google.

15. State and district addenda

Where applicable law or a mutually executed state, district, or student-data privacy addendum imposes additional requirements, that addendum controls to the extent of a conflict.

16. Contact

YinYang Interactive LLC
650 Fargo Avenue
San Leandro, CA 94579-2102
+1 (510) 673-4066
Privacy: [email protected]
Support: [email protected]
Security: [email protected]
© 2026 YinYang Interactive LLCSchool IT & network requirements[email protected]