Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Student Privacy topic
No spam. Unsubscribe anytime.
Long debate on Clever rostering: board approves contract with follow-up requests about student data, sub-processors and security
Summary
The School Board approved a Clever single sign-on and rostering agreement after extended debate over student-data sharing and sub-processors; staff committed to multiple follow-ups including security documentation and a list of academic software paid for but not activated.
Get email alerts on the Student Privacy topic
No spam. Unsubscribe anytime.
The School Board approved a contract with Clever for single-sign on and rostering services after a lengthy discussion about student data privacy, third-party sub-processors and security safeguards. Two board members recorded dissenting votes; the motion passed by majority.
Members pressed staff and district IT leadership for clarification about what student demographic and educational data are shared with Clever and with its listed sub-processors (the transcript lists companies including Amazon, Apple, Google and others). Board members asked whether the district or Clever provides personally identifying data elements (for example date of birth and local student identifier) to downstream vendors, and they requested documentation showing the security and data-minimization framework Clever uses.
IT and privacy staff said each contract is vetted for data-security controls and vendor agreements typically include clauses restricting data use and requiring compliance with FERPA and Florida student-data rules. Staff said Clever functions as a centralized roster and integration hub; releasing data from Clever to other vendors requires a separate contract and scrutiny. Staff agreed to follow up with several requests from the board:
- A list of any academic/learning software purchased by the district for 2024-25 that has not been turned on and made available to students. - Clever's security framework and summaries of sub-processor safeguards for each listed company. - Whether date-of-birth is being provided to any instructional vendors (and, if so, a justification). - Confirmation of auditing and logging features Clever provides to track authenticated access.
Why it matters: Board members expressed concern about sensitive student data and requested both contractual safeguards and technical audits such as penetration testing and privacy/security assessments; staff confirmed routine penetration testing and said district privacy and security teams review contracts.
Next steps: Staff agreed to gather and return with the requested vendor- and data-specific details; the board also requested that the district's privacy and information-security teams consider external assurance or penetration testing as part of ongoing oversight.
