Technology
Page Navigation
- CUSD Tech Homepage
- Resource Center
- Data Governance
- CUSD 1:1 Student Guide
- Software
- Website Subscriptions
- Apps
- Website Unblocking/Blocking
- Pre-Approved Devices
- Staff Links
- Students, Parents and Community Links (Non-Staff)
- Tech Tutorials
- Internet Safety and Cyberbullying
- School Library Information
- SchoolCity
- Chandler Unified School District
- Data Governance
-
FERPA- The Family Educational Rights and Privacy Act
Schools are required to have written documentation from legal guardians to release information from student's educational records. This also means that sharing information to apps and websites requires a legal guardian's consent.
COPPA- The Children's Online Privacy Protection Act
This act places restrictions on software companies about the information they are able to collect about kids under 13. This means that students under the age of 13 are not able to create their own accounts. In some cases, educators are able to create accounts for their students. However, FERPA responsibilities will apply.
CIPA- The Children's Internet Protection Act
This act requires school districts to have filters on internet access in order to protect students. Safety and security measures need to be in place for electronic mail or other forms of digital communication. These, as well as reporting measures, are required for districts to receive E-rate funding.
-
What is safe to share?
Follow these guidelines to ensure that you are using CUSD best practice when using technology tools with students. We want to keep our students' personally identifying information (PII) secure. Just like a puppeteer controls the movements of each limb of their puppet, you should exercise the same control in what information you share. Consider the acronym below to help you.
Parental Consent- Always communicate with parents/guardians about the tech tool, how you intend to use it, and get written consent.
Usernames- Use only first name and last initial (if last name is required).
Personal Information- If a service requires a student birth date, enter the same generic birthday for all students (01/01/2008). Make it simple and uniform so nothing is actually connected to the students' personal information.
Passwords- Passwords should NEVER be the same for every student. It should be unique for each student. If possible, reach out to edtech@cusd80.com for guidance or support on a possible SSO integration.
Email- Do not ask students to sign up for services using their personal email.
Talk- Have meaningful discussions with your students about the importance of data privacy. Work it into many conversations throughout the year. Make it consistent and have it be a natural part of living in a digital world.