Monday, February 8, 2021

SOPPA Information for Teachers -- Part 4

 Here it is, the final installment on the information for teachers regarding SOPPA! Finally, you learn what this all means for you directly! 

Keep in mind all that you've read so far. Can you make any educated guesses? Keep in mind, the ultimate goal of this law is to ensure student privacy and offer more transparency about how student information is used.


As a classroom teacher, you are likely going to find that SOPPA puts a little bit of a cramp in your style. Any websites or applications that collect student information (think: the student has to log in to use it) will have some rules attached to your use of it in the classroom.

  • Does our school district already have a contract with the operator? If so, you can go ahead and use that application or website! If not, you can't use it. In order for you, as the teacher, to have students use a website or application that collects student data (the student has to log in to use it), the district has to already have a signed contract in place. This is how the transparency happens: the operator shares what data they are collecting and how it is being used; the district reviews this to be sure it is compliant with SOPPA; the district posts this information to make it publicly available.
  • You will have to know where to find that list of contracts so you can see if the websites or tools you want to use are available. This is TBD. Once it is determined where this can be found, it will be shared with you.
  • You will need to know how to go about making a request for being able to use a website or application that is not on the list. That process is also TBD. It still needs to be figured out who will be in charge of that because that individual will be responsible for ensuring compliance is happening and then entering into the contract with the operator.
  • I'm sure your next question is, "How long will it take to get something approved?" Honestly, I have no idea. This is a new process for all of us, so that is also TBD. Part of it will be reliant upon our efficiency; part of it will be reliant upon the operator's efficiency.
In short, bad news: it will take a little bit of legwork and time to get access to any new online tools for kids to use; good news: we will have a much clearer understanding of how student data is being used which will ultimately make it safer for students to be online.

Here's an example (I am assuming I am correct in this):
  • Flipgrid: This tool will need a signed contract because students are required to sign in to use it. 
  • Padlet: This tool will not need a signed contract because students are not required to sign in to use it.
  • Khan Academy: This tool may or may not need a signed contract because there are some features that require students to log in. If students are merely accessing the site and using the videos without logging in, then a signed contract is not necessary. If students are signing in, however, a signed contract will need to be in place. Students would not be able to use the features available by signing in without that contract being completed.
Working in compliance of this law is going to require some extra sleuth work on your part. I know -- you are already very busy. I didn't make the law :-) Ultimately, we need to remember that if this is going to keep kids' information safe, then it's a good thing.

Questions? Drop them in the comments and I will see if I can find you the answers!

Resources for this post:
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)