Data privacy & security plan
How GameSalad for Education protects student and staff personally identifiable information (PII) under contracts with educational agencies (EA).
1. Implementing data security and privacy contract requirements
Outline how you will implement applicable data security and privacy contract requirements over the life of the Contract.
GameSalad follows security best practices including regular security review, training, and encryption of data in motion and at rest. Where available, third-party systems access has 2FA enabled.
2. Safeguards that protect PII
Specify the administrative, operational and technical safeguards and practices that you have in place to protect PII.
GameSalad encrypts data in motion and at rest. Employee administrative interfaces do not show non-email PII by default.
PII usage is optional, and the client is given options for using the platform without providing PII.
3. Training on the laws that govern PII
Address the training received by your employees and any subcontractors engaged in the provision of services under the Contract on the federal and state laws that govern the confidentiality of PII.
Employees receive quarterly training on cybersecurity best practices.
4. Contracting processes
Outline contracting processes that ensure that your employees and any subcontractors are bound by written agreement to the requirements of the Contract, at a minimum.
Employee policy includes the need to comply with contracts.
5. Managing data security and privacy incidents
Specify how you will manage any data security and privacy incidents that implicate PII and describe any specific plans you have in place to identify breaches and/or unauthorized disclosures, and to meet your obligations to report incidents to the EA.
Security incidents are verified and reported by email within 48 hours of the company being informed of or discovering the breach.
If the investigation continues after 48 hours, the customer will be informed of the extent of the breach and the data included as soon as possible.
Systems have alerts that automatically notify system admins of unusual activity, and all activity is investigated.
6. Transitioning data to the EA
Describe how data will be transitioned to the EA when no longer needed by you to meet your contractual obligations, if applicable.
In most cases, data will not be transitioned but erased. If data is requested, it will be transferred via secure FTP or an expiring Dropbox link, as agreed with the requester.
7. Secure destruction
Describe your secure destruction practices and how certification will be provided to the EA.
No special security measures are in place for data destruction. Accounts are deactivated and PII is removed from database records. PII will not be removed from database backups due to infeasibility, but data backups have a rotation schedule ensuring eventual full deletion.
8. Alignment with the EA's policies
Outline how your data security and privacy program/practices align with the EA's applicable policies.
The company regularly evaluates its security practices' alignment with the NIST Cybersecurity Framework (CSF) v1.1.
See also the GameSalad Privacy Policy and how Bowlbot handles student conversations and safety. Questions about a district agreement? Contact us.
Last updated