Skip to main content
Oregon Privacy Laws

Oregon is a member of the Student Data Privacy Consortium (SDPC)

Updated over 11 months ago

If your administrator or IT department is asking about SLP Toolkit compliance with the Oregon student data privacy laws, we've got you covered. You can find information about how to comply with the regulations below. Although we are well versed in the new statutes, we are not legal experts (we stick to speech pathology and software). So you should consult your district about how to fully comply too.

1. Useful information

You can view all the student data elements that we collect, along with the reason we collect them in the knowledge base article below. You can print out a copy or save a PDF for your records.

We use subcontractors to store and access student data. Their information and their policies concerning privacy and security are listed in the knowledge base article below.

SLP Toolkit complies with FERPA and more information can be found in the article below.

SLP Toolkit uses best practices to securely store and transmit data to the SLPs with authorized access. You can read more about how we keep your data safe in the article below.

2. Data Sharing & Privacy Agreement

The Oregon Student Privacy Alliance (OSPA) is made up of Oregon School Districts that set common standards and expectations for student privacy. Here is a link to the Oregon Student Privacy Alliance within the SDPC. OSPA

For school districts that are OSPA members within the Student Data Privacy Consortium (SDPC), we've got you covered. You can download the agreement they have provided here (click here)

NOTE: If your district would prefer a generic agreement, you can generate and download a signed data sharing & privacy agreement (DSPA) using this form (click here).

Hopefully, this demystifies the Oregon student privacy laws and you can get on with helping the students. As always, let us know if there are any questions about this or other privacy standards by sending an email to privacy@slptoolkit.com or contacting support.

Did this answer your question?