Student Records. Notwithstanding any provision to the contrary within this Agreement, any party contracting with SBBC under this Agreement shall fully comply with the requirements of Sections 1002.22 and 1002.221, Florida Statutes; FERPA, and any other state or federal law or regulation regarding the confidentiality of student information and records. Each such party agrees, for itself, its officers, employees, agents, representatives, contractors or subcontractors, to fully indemnify and hold harmless SBBC and its officers and employees for any violation of this section, including, without limitation, defending SBBC and its officers and employees against any complaint, administrative or judicial proceeding, payment of any penalty imposed upon SBBC, or payment of any and all costs, damages, judgments or losses incurred by or imposed upon SBBC arising out of a breach of this covenant by the party, or an officer, employee, agent, representative, contractor, or sub-contractor of the party to the extent that the party or an officer, employee, agent, representative, contractor, or sub-contractor of the party shall either intentionally or negligently violate the provisions of this section or of Sections 1002.22 and/or 1002.221, Florida Statutes.
Student Records. To the extent that Provider will come into possession of student records and information, and to the extent that Provider will be involved in the survey, analysis, or evaluation of students, incidental to this Contract, Provider agrees to comply with all applicable requirements of the Family Educational Rights and Privacy Act.
Student Records. The School shall maintain student records for current and former students in accordance with the requirements of State and federal law, including the Family Education Rights and Privacy Act, 20 U.S.C. § 1232g, as may be amended from time to time. Should a student transfer to another school, the School shall transfer the student's records to the new school in a timely manner and may maintain copies of the departing student’s academic records created during the student’s attendance at the School.
Student Records. Satisfactory records must be maintained for student admission, advisement, counseling, and evaluation. Grades and credits for courses must be recorded on the student transcript and permanently maintained by the sponsor in a safe and accessible location.
Student Records. All student records shall be kept in a secure location preventing access by unauthorized individuals. PROVIDER will maintain an access log delineating date, time, agency and identity of any individual accessing student records who is not in the direct employ of the PROVIDER. PROVIDER agrees to provide access to and copies of student records to LEA and/or the parents/guardians of LEA'S student. PROVIDER shall not forward to any other person other than parents/guardians or LEA any student record without the written consent of the parent/guardian or LEA. When disposed of, student records must be shredded. No student records may be released or sold to another entity.
Student Records. In the course of providing the Service, Khan Academy may collect or have access to Student Records. “Student Records” are information relating to a student which is personally identifiable, or which is linked to personally identifiable information in a manner that would allow a reasonable person to identify the student with reasonable certainty, and is (i) provided to Khan Academy by a student or by the School District, or (ii) collected by Khan Academy, during the provision of the Service to the School District pursuant to this Agreement. Student Records shall not include information a student or other individual may provide to Khan Academy independent of the student’s engagement in the Service at the direction of the School District. As between the parties, the School District or the Student owns and controls all right, title and interest to all Student Records. To be sure that personal information of Student Users is properly designated as “Student Records,” Student User accounts must be (1) created by the School District, (for example, when a teacher creates the user name, login and password to establish School User accounts, or when the teacher rosters a class using Google Classroom, Clever, or similar single sign-on service), or (2) created by a School User at the direction of a School, in each case, using a School email address and associated with a School’s class on the Service. User accounts created with a personal email address will not