Student Data Privacy Agreements

It depends. Students have to sign in via Clever (not Google!). Apps that are available in the Clever Library have a data sharing agreement with Clever that only shares student First Name, Last Name Initial, and Grade-Level. No PII or school district information is shared automatically and none should be entered by staff if prompted.  

Some apps still require service agreements, and those have to be between Pattonville and the vendor... not the teacher and vendor.

Fill out a Request.

Your DTS , in coordination with the Assistant Director of Technology, will vett the resource and initiate the process of getting a signed NDPA (National Data Privacy Agreement) with that vendor or technology provider. 

Sometimes this process is very quick and sometimes this process can take a couple of weeks. It is rare, but occassionally there will be a vendor who will not sign our agreement. If that happens, the DTS will work with you to find a comparable substitute.

Consult your DTS and we will work on getting an agreement for that resource and setting up district Single Single-Sign on for student accounts. Do not have any future groups of students create their own accounts. If we cannot secure an agreement with the vendor, we really need to find a similar type of resource that will meet your needs for which we can get an agreement.

If you have an immediate concern regarding a compromise of student data (e.g. notification of a data breach), please contact Tammy Hasheider.

It depends. 

If you, the teacher, just signs in and uses links from the resource, that's okay. Though you might to read their privacy policy for your own sake to see how the company uses the data they collect about YOU.

If students just enter a code and don't have to login, that's probably okay. Though, some web-based sites can still collect PII (personally identifiable information) about students without requiring them to create accounts. It just depends on how the student is using the site. It can still collect data from the user in the form of entering in information, browser history, geo-location data, and other things that might not necessarily be things the student wants shared. It's still worth reading the privacy policy to see what data they are collecting. And for older students, it's wise to teach them to read through privacy policies too.

A Student Data Privacy Agreement will be needed first. When a students use a school Google account, that also means they are agreeing to terms of service and agreeing to share their data (sometimes a lot of data).

Google does not allow authentication with their Pattonville Google account unless the website/app is verified in our account. We only verify apps or websites for which we know we have a student data privacy agreement.

If you get parent permission, then either the parent or the student should create the account using non-Pattonville credentials the parent knows. If the company has a data breach, we do not want the Pattonville credentials to be at risk since we can't change it on their platform.  Contact Tammy Hasheider before sending home a permission form. IN SOME CASES, CONSENT IS NOT ENOUGH! We may still need to have a agreement to meet FERPA requirements.

All of the online resources that require student logins have specific terms of service and privacy policies which vary from product to product. In most instances, staff do not have the legal authority to accept these terms and conditions on behalf of the district. Most student data privacy agreements hinge on having a service agreement between the LEA (Pattonville) and the vendor. We have an obligation to protect student data, and that is why all technology resources must be vetted.

Additionally, it is unfair to put the burden of data governance and security on the shoulders of our teaching staff. It is a very complicated and complex thing to manage.  While protecting student data is the goal, we know we are also protecting our teachers from liabilities.