Skip to content
ChessOS
Start free

← Student data

Student data agreement: DRAFT TEMPLATE, pending legal review

Status: draft for discussion. A lawyer has not reviewed it. Do not sign it. It describes what the ChessOS product does today; it is not a statement that ChessOS or any school meets any law, including FERPA, COPPA or a state student-privacy law. Square brackets are for counsel and the parties to fill in.

1. Parties

This agreement is between [School or district name] (the school) and [ChessOS legal entity, to be decided] (ChessOS) and covers the school's chess club on ChessOS Organizer.

2. Purpose and limits

ChessOS holds student information only to run the school's chess club: its members, club meetings, tournaments and leagues with other schools. ChessOS does not use student information for advertising or to train models, and does not sell it.

3. What student information the product holds

• A student's name, grade, chess rating and results.

• Contact details kept on a student's record, which the school should enter as a parent's or guardian's, in a protected area. Every read of those details by an officer is logged.

• Nothing is collected about students under 13 beyond a record managed by a parent or guardian: ChessOS does not create accounts for children under 13.

• The advisor's name, role, school and school email address.

4. Who can see it

• Officers of the school's chess club, according to the role each holds.

• Other schools in a league see the lineups for their own matches only. Coach names and emails are shown only to the commissioner and the opposing coach.

• Public pages show team names and, in school leagues, a first name with a last initial.

• The school chess club is not listed in the public club finder unless the advisor opts in.

5. What the school can do

• Export a copy of the students' records at any time.

• Erase a student: the record is reduced to "Former student" and its contact details, guardian links and notes are deleted. Results already published in an event's record stay until the event is deleted. [Counsel: decide whether this satisfies the school's deletion obligations.]

• Decide whether a guardian is invited to link a student's record to a ChessOS Player profile (optional, off by default, accepted only by the guardian).

6. Subprocessors

[A published list of subprocessors, to be completed before signing.]

7. Security

[A written security program, to be completed before signing. The product keeps contact details in a protected area with a read log and uses per-club row-level security.]

8. Retention and deletion

[Retention periods and deletion on request, to be decided with counsel. Today: records stay until the school erases them or deletes the club.]

9. Incidents

[Breach notification terms, to be drafted by counsel.]

10. Term and signatures

[Term, termination, governing law and signature blocks, to be drafted by counsel.]