School Privacy Notice

In a school workspace, the school district (the LEA) is the data controller and owns the student education records. ReviSports Inc., a Utah corporation with its principal place of business in West Haven, Utah (“ReviSports,” “we,” or “us”), acts only as a “School Official” with a legitimate educational interest under the FERPA school-official exception, 34 CFR 99.31(a)(1)(i)(B).

That means we handle student data under the district's direction and control, use it only for the services the district engaged us to provide, and do not redisclose it except as the district directs or the law requires.

The controlling document is the district's signed Data Privacy Agreement (the Utah National Data Privacy Agreement, or “UT-NDPA”). If anything in this notice differs from that signed agreement, the signed agreement controls.

• FERPA (Family Educational Rights and Privacy Act, 20 U.S.C. 1232g; 34 CFR Part 99): parents control a student's education records until the student turns 18, when the rights transfer to the student (an “eligible student”).
• COPPA (Children's Online Privacy Protection Act): in the school context, the district authorizes collection of a student's information for the limited educational purpose, and we make no commercial use of it.
• Utah SDPA (Utah Student Data Protection Act, Utah Code 53E-9-301 et seq.) and State Board Rule R277-487: stricter security, breach-reporting, deletion, and registry duties on top of FERPA.
• UT-NDPA: the signed contract between ReviSports and the district, Utah's adoption of the Student Data Privacy Consortium (SDPC) standard.

We collect, receive, or create the categories of student and user data needed to run the district's athletic-program services: identity and profile, athletic profile, account and sign-in, film and media, performance and statistics, team communications, guardian relationships and consent records, scheduling and participation, and safety / audit records.

The complete, field-by-field inventory (the “data dictionary”), with each element's purpose, sharing, and retention, is the Schedule of Data (Exhibit B) attached to the district's Data Privacy Agreement. We keep that inventory in sync with the actual platform schema and minimize collection to what the services require.

We use student data to provide and secure the services the district engaged us for: roster and team management, film upload and review, statistics, scheduling, and team-scoped communication. We process it under the district's direction and the Data Privacy Agreement.

Model training (where your district authorizes it). Where the district authorizes it in the signed Data Privacy Agreement, we also use school-workspace data, including game film, to train and improve our athletic-analysis machine-learning models (“Modeling Technologies”). The resulting models are used only to operate and improve the Platform, stay on ReviSports' own systems, and are never sold, licensed, or transferred to any third party, except to a successor in a merger or sale of substantially all of our assets, which stays bound by these same commitments. A later district deletion instruction removes the underlying film from our systems but cannot reverse training already performed under the agreement.

These protections are absolute in a school workspace:

• No advertising of any kind. A school workspace is ad-free. We never serve contextual or targeted advertising in it, and never use student data to target ads anywhere.
• No sale or commercialization. We do not sell, rent, trade, or otherwise commercialize student data.
• No public exposure. School data stays inside the school workspace and is never published to public surfaces or moved into the consumer product.

ReviSports also runs a separate consumer/personal product. School-workspace data is architecturally walled off from it: the two are never queried together, a school-only user has no public profile and cannot post publicly (school posts reach only team, parents, and staff), and school film is never shared or traded into the consumer product. Different districts are different data controllers, so school data is not shared across districts either.

Game film is shareable for legitimate coaching and recruiting purposes by default, but the district (as controller) holds controls that only ever restrict, never force, sharing:

• A district-wide switch to restrict public sharing of school footage.
• A per-clip lock that makes a specific film or clip non-shareable and non-extractable (for example, footage tied to a disciplinary matter, or any clip a stricter district wants held back).
• A district-wide switch to turn coach-to-coach film trading on or off.
• A structural rule that film traded to another school keeps highlight, extract, and re-share rights with the originating team; a receiving coach gets view-and-internal-breakdown access only.

Honoring any directory-information opt-out for a published image is the school's responsibility as the publisher and controller; we provide the controls above, but we do not auto-blur or auto-exclude.

An external party (for example, a college recruiter) cannot directly message a minor student through the school workspace. The attempt is routed to a district-designated approver (by default the District Admin, which the district may delegate to a school-level role such as an athletic director or coach). Whether a parent or guardian is also required in that approval is a setting the district controls. A student who is 18 or older (an eligible student) controls their own communication.

We maintain a written information-security program with administrative, technical, and physical safeguards appropriate to the sensitivity of student data: encryption in transit and at rest, role-based access controls, an immutable audit log of access to and changes affecting student records, two-factor authentication required for platform administrators, and periodic security review. Student data is stored within the United States.

If we discover a security incident involving student data, we notify the district without unreasonable delay and within the timeframe the Utah SDPA and R277-487 require, and we cooperate with the district's response. The district, as controller, notifies affected parents and eligible students and any required state authority.

School-workspace data is retained and deleted on the district's instruction under the Data Privacy Agreement, not under the consumer retention tiers. There is no consumer-style cold archive of school data; the underlying film is deleted on the district's instruction. Where the district has authorized model training, a model already trained under the agreement persists as a separate derived artifact, but the underlying student data itself is not retained for further training beyond the district's instruction.

When the district instructs deletion of a student's records, we delete the student's login account, scrub the personally identifiable fields from the athlete record (keeping shared team statistics anonymized rather than making them vanish for other students), preserve the required consent / verification record for a minimum of 7 years, preserve audit-log entries, and clean up stored media on a best-effort basis.

If litigation, an investigation, or a child-safety matter requires preservation, the affected records are placed under a legal hold that suspends deletion until the hold is lifted.

Because the district controls the education records, parents and eligible students exercise their FERPA rights (to inspect, review, and seek amendment of records) through the district. We support the district in fulfilling those requests. What parents and guardians are told about a district-provisioned account is set out in the School Parental Notice.

Every message is screened automatically, and the screening is done by software. In a school workspace as everywhere else, each message sent in a team channel, a group, or a direct message is checked at the moment it is delivered for bullying and harassment, sexual content, grooming or predatory approaches, threats of violence, self-harm, and hate. A fast first pass looks at the message alone; only if it flags does a second, higher-context review read the surrounding conversation and decide. Nobody reads student conversations as a matter of course. The excerpt sent to our AI providers for classification is de-identified first: speakers appear as anonymous labels and only message text is included, with no names, usernames, account identifiers, or timestamps. Student message content is never used for advertising, profiling, or content recommendations, and never to train the district-facing analytics described in Section 4.

Where a concern is confirmed, the school is told, not the parent. This is the opposite of how our consumer product works and it is deliberate. In a club organization a confirmed concern alerts the minor's parent or guardian. In a school workspace it alerts the school's designated officials, because the district is the party responsible for its students and holds consent on their behalf under the Data Privacy Agreement. The school then handles the matter under its own policies. We do not route these alerts to individual parents in a school workspace.

Designated school officials can read messages within their own school, and every read is logged. An owner, administrator, or athletic director of a school organization may read group, custom, and direct messages within that school without being a participant. This access does not extend to other schools, including other schools in the same district. It is read only: an official cannot send a message into a conversation they are not part of. Every time an official opens message content this way we write an audit record of who opened it, which conversation, and when, and the district can ask us for it.

Flagged content is preserved, including by our providers. When something is flagged, that record is evidence, so it is kept past our ordinary retention periods both by us and by the AI provider that examined it, and we cannot delete the provider's copy on the district's instruction. Content that is not flagged is not retained by a provider for this purpose. Because this interacts with the district-controlled deletion described in Section 10, it is a term we want stated in the Data Privacy Agreement rather than discovered later.

Serious findings may go to authorities directly. Apparent child sexual abuse material is reported to the National Center for Missing and Exploited Children because federal law requires it. Our AI providers carry the same obligation independently and may report such findings themselves. Beyond what the law compels, where we believe in good faith that a student is at risk of serious harm we may contact law enforcement, child protective services, or the school directly. We will normally inform the district, and will not where doing so could put a student at greater risk.

In a school workspace, the district's Data Privacy Agreement governs student data, and it controls over the consumer Terms of Service and consumer Privacy Policy on any student-data-privacy or security matter. The consumer terms do not govern data inside a school workspace.

Parents and students should direct FERPA requests to their school district. For questions about ReviSports' role as a School Official, contact us: