NEW HAMPSHIRE STUDENT DATA PRIVACY AGREEMENT VERSION (2019)
Hampton School District SAU 90 and
Liminex, Inc. d/b/a GoGuardian
This New Hampshire Student Data Privacy Agreement (“DPA”) is entered into by and between the school district, Hampton School District SAU 90 (hereinafter referred to as “LEA”) and
Liminex, Inc. d/b/a GoGuardian (hereinafter referred to as “Provider”) on The Parties agree to the terms as stated herein.
May 3, 2021 .
WHEREAS, the Provider has agreed or will agree to provide the Local Education Agency (“LEA”) with certain digital educational services (“Services”) as described in Article I and
Exhibit “A”; and
WHEREAS, in order to provide the Services described in Article 1 and Appendix A, the Provider may receive or create and the LEA may provide documents or data that are covered by several federal statutes, among them, the Family Educational Rights and Privacy Act (“FERPA”) at 20 U.S.C. 1232g and 34 CFR Part 99, Children’s Online Privacy Protection Act (“COPPA”), 15 U.S.C. 6501-6506; Protection of Pupil Rights Amendment (“PPRA”) 20 U.S.C. 1232h; the Individuals with Disabilities Education Act (“IDEA”), 20 U.S.C. §§ 1400 et. seq., 34 C.F.R. Part 300; and
WHEREAS, the documents and data transferred from New Hampshire LEAs and created by the Provider’s Services are also subject to several New Hampshire student privacy laws, including RSA 189:1-e and 189:65-69; RSA 186; NH Admin. Code Ed. 300 and NH Admin. Code Ed.
WHEREAS, the Parties wish to enter into this DPA to ensure that the Services provided conform to the requirements of the privacy laws referred to above and to establish implementing procedures and duties.
NOW THEREFORE, for good and valuable consideration, the parties agree as follows:
ARTICLE I: PURPOSE AND SCOPE
1. Purpose of DPA. The purpose of this DPA is to describe the duties and responsibilities to protect Student Data (as defined in Exhibit “C”) transmitted to Provider from the LEA pursuant to Exhibit “A”, including compliance with all applicable privacy statutes, including the FERPA, PPRA, COPPA, IDEA, SOPIPA, RSA 189:1-e and 189:65 through 69; RSA 186-C; NH Admin. Code Ed. 300; NH Admin. Code Ed. 1100; and other applicable New Hampshire state laws, all as may be amended from time to time.
In performing these services, to the extent Personally Identifiable Information (as defined in Exhibit “C”) from Pupil Records (as defined in Exhibit “C”) are transmitted to Provider from LEA, the Provider shall be considered a School Official with a legitimate educational interest, and performing services otherwise provided by the LEA. Provider shall be under the direct control and supervision of the LEA. Control duties are set forth below.
2. Nature of Services Provided. The Provider has agreed to provide the digital educational services described in Exhibit “A”.
3. Student Data to Be Provided. In order to perform the Services described in this Article and Exhibit “A”, LEA shall provide the categories of data described in the Schedule of Data, attached hereto as E xhibit “B”.
4. DPA Definitions. The definition of terms used in this DPA is found in Exhibit “C”. In the event of a conflict, definitions used in this DPA shall prevail over terms used in all other writings, including, but not limited to, a service agreement, privacy policies or any terms of service.
ARTICLE II: DATA OWNERSHIP AND AUTHORIZED ACCESS
1. Student Data Property of LEA. All Student Data or any other Pupil Records
transmitted to the Provider pursuant to this Agreement is and will continue to be the property of and under the control of the LEA, or to the party who provided such data (such as the student or parent). The Provider further acknowledges and agrees that all copies of such Student Data or any other Pupil Records transmitted to the Provider, including any modifications or additions or any portion thereof from any source, are also subject to the provisions of this Agreement in the same manner as the original Student Data or Pupil Records. The Parties agree that as between them, all rights, including all intellectual property rights in and to Student Data or any other Pupil Records contemplated per this Agreement shall remain the exclusive property of the LEA. For the purposes of FERPA and state law, the Provider shall be considered a School Official, under the control and direction of the LEAs as it pertains to the use of Student Data notwithstanding the above. The Provider will cooperate and provide Student Data within fourteen (14) days at the LEA’s request. Provider may transfer pupil-generated content to a separate account, according to the procedures set forth below.
2. Parent Access. LEA shall establish reasonable procedures by which a parent, legal guardian, or eligible student may review personally identifiable information on the pupil’s records, correct erroneous information, and procedures for the transfer of pupil- generated content to a personal account, consistent with the functionality of services. Provider shall cooperate and respond within fourteen (14) days to the LEA’s request for personally identifiable information in a pupil’s records held by the Provider to view or correct as necessary. In the event that a parent of a pupil or other individual contacts the Provider to review any of the Pupil Records of Student Data accessed pursuant to the Services, the Provider shall refer the parent or individual to the LEA, who will follow the necessary and proper procedures regarding the requested information.
3. Separate Account. Provider may, at the request of the LEA, transfer Student Generated Content to a separate student account.
4. Third Party Request. Should a Third Party, including, but not limited to law enforcement, former employees of the LEA, current employees of the LEA, and government entities, contact Provider with a request for data held by the Provider pursuant to the Services, the Provider shall redirect the Third Party to request the data directly from the LEA and shall cooperate with the LEA to collect the required information unless prohibited by law or legal process. Provider shall notify the LEA in advance of a compelled disclosure to a Third Party, unless legally prohibited. The Provider will not use, disclose, compile, transfer, sell the Student Data and/or any portion thereof to any third party or other entity or allow any other third party or other entity to use, disclose, compile, transfer or sell the Student Data and/or any portion thereof, except
(i) with the express written consent of the LEA; (ii) with a court order, law enforcement request, or lawfully issued subpoena; (iii) as reasonably necessary to provide the Services stated in the Service Agreement and/or (iv) as otherwise required pursuant to the statutes referred to in Article IV, subsection 1 (Privacy Compliance). Student Data shall not constitute that information that has been anonymized or de-identified, or anonymous usage data regarding a student’s use of Provider’s services.
5. No Unauthorized Use. Provider shall not use Student Data or information in a Pupil Record for any purpose other than as explicitly specified in this DPA.
6. Subprocessors. Provider shall enter into written agreements with all Subprocessors performing functions pursuant to this DPA, whereby the Subprocessors agree to protect Student Data in manner consistent with the terms of this DPA.
ARTICLE III: DUTIES OF LEA
1. Provide Data In Compliance With Laws. LEA shall provide data for the purposes of the DPA in compliance with the FERPA, PPRA, IDEA, RSA 189:1-e and 189:65 through 69; RSA 186-C; NH Admin. Code Ed. 300; NH Admin. Code Ed. 1100 and the other privacy statutes quoted in this DPA. LEA shall ensure that its annual notice under FERPA includes vendors, such as the Provider, as “School Officials.”
2. Reasonable Precautions. LEA shall take reasonable precautions to secure usernames, passwords, and any other means of gaining access to the services and hosted data.
3. Unauthorized Access Notification. LEA shall notify Provider promptly of any known or suspected unauthorized access. LEA will assist Provider in any efforts by Provider to investigate and respond to any unauthorized access.
ARTICLE IV: DUTIES OF PROVIDER
1. Privacy Compliance. The Provider shall comply with all applicable New Hampshire and Federal laws and regulations pertaining to data privacy and security, including, as applicable, XXXXX, XXXXX, XXXX, XXX 000:0-x and 189:65 through 69; RSA 186-C; NH Admin. Code Ed. 300; NH Admin. Code Ed. 1100 and all other applicable New Hampshire privacy statutes and regulations.
2. Authorized Use. Student Data shared pursuant to this DPA, including persistent unique identifiers, shall be used for no purpose other than the Services stated in this DPA and as authorized under the statutes referred to in subsection (1), above. Provider also acknowledges and agrees that it shall not make any re-disclosure of any Student Data or any portion thereof, including without limitation, meta data, user content or other non-public information and/or personally identifiable information contained in the Student Data, except: (i) with the express written consent of the LEA; (ii) as reasonably necessary to provide the Services stated in the Service Agreement; and/or (iii) as otherwise required pursuant to the statutes referred to in Article IV, subsection I (Privacy Compliance).
3. Employee Obligation. Provider shall require all employees and agents who have access to Student Data to comply with all applicable provisions of this DPA with respect to the data shared under this DPA. Provider agrees to require and maintain an appropriate confidentiality agreement from each employee or agent with access to Student Data pursuant to the DPA.
4. No Disclosure. De-identified Information may be used by the Provider for the purposes of development, research, and improvement of educational sites, services, or applications, pursuant to 34 C.F.R. 99.31(b) and in compliance with the statutes listed in Article IV subsection (1) (Privacy Compliance). Provider agrees not to attempt to re-identify de-identified Student Data and not to transfer de-identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification; and b) prior written notice has been given to LEA who has provided prior written consent for such transfer. The foregoing subpoint (b) in the preceding sentence does not prohibit Provider from transferring De-Identified Information to assist the Provider with its own research if the recipient agrees in writing not to attempt reidentification.
Provider shall not copy, reproduce, or transmit any data obtained under the Service Agreement and DPA and/or any portion thereof; except as necessary to fulfill the Service Agreement and DPA. Notwithstanding the foregoing, nothing shall limit the Provider from disclosing De-Identified Information or Student Data (i) with the express written consent of the LEA; (ii) to its Subprocessors in compliance with Article V, section1(g) (Subprocessors Bound); or (iii) in connection with a merger, acquisition, or sale of all or substantially all of Provider’s assets. The Provider must require the successor to assume all obligations of this DPA. In the event that the Provider anticipates selling, merging or otherwise disposing of its business to a successor during the term of the DPA, the Provider shall provide advance written
notice of the proposed sale, merger or disposal to the LEA prior to the anticipated date of sale, merger or disposal. Such notice shall include a written, signed assurance that the successor will assume the obligations of the DPA. The LEA has the ability to terminate the DPA and a Service Agreement if it reasonably believes that the successor cannot uphold the terms and conditions herein or having a contract with the successor would violate the LEA’s policies or state or Federal law. Prior to publishing any document that names the LEA explicitly or states anything that would allow a third party to reasonably identify the LEA, the Provider shall obtain the LEA’s written approval of the manner in which De-Identified Information is presented in such document. Such approval cannot be unreasonably or untimely withheld by LEA.
5. Disposition of Data. Upon written request from LEA during the term of the Service Agreement, Provider shall dispose or delete all Student Data obtained under the DPA when it is no longer needed for the purpose for which it was obtained. LEA shall have thirty (30) days after termination or expiration (whichever is earlier) of its Service Agreement with Provider to notify Provider in writing that LEA wishes Provider to make available or otherwise transfer data in either a CSV or other mutually-agreeable format. After such thirty (30) day time period has expired, Provider shall use commercially reasonable efforts to dispose or delete all Student Data obtained under the Service Agreement. Nothing in the DPA authorizes Provider to maintain personally identifiable data obtained under any other writing beyond the time period reasonably needed to complete the disposition. Disposition shall include commercially reasonable efforts to complete: (1) the shredding of any hard copies of any Pupil Records; (2) Erasing; or (3) Otherwise modifying the personal information in those records to make it unreadable or indecipherable. Provider shall provide written notification to LEA when the Data has been disposed. The duty to dispose of Student Data shall not extend to data that has been de-identified or placed in a separate Student account, pursuant to the other terms of the DPA. The LEA may employ a “Request for Return or Deletion of Student Data” FORM, A Copy of which is attached hereto as Exhibit “D”). Upon receipt of a written request from the LEA, the Provider will immediately provide the LEA with any specified portion of the Student Data within fourteen (14) calendar days of receipt of said request.
6. Advertising Prohibition. Provider is prohibited from leasing, renting, using or selling Student Data to (a) market or advertise to students or families/guardians; (b) inform, influence, or enable marketing, advertising or other commercial efforts by a Provider; (c) develop a profile of a student, family member/guardian or group, for any commercial purpose other than providing the Service to LEA, or in furtherance of K-12 school purposes; or (d) use the Student Data for the development of commercial products or services, other than as necessary to provide the Service to Client, or in furtherance of K- 12 school purposes.
ARTICLE V: DATA PROVISIONS
1. Data Security. The Provider agrees to abide by and maintain adequate data security measures, consistent with industry standards and technology best practices, to protect Student Data from unauthorized disclosure or acquisition by an unauthorized person. The general security duties of Provider are set forth below. Provider may further detail its security programs and measures in Exhibit “F” hereto. These measures shall include, but are not limited to:
a. Passwords and Employee Access. Provider shall secure usernames, passwords, and any other means of gaining access to the Services or to Student Data, at a level suggested by Article 4.3 of NIST 800-63-3. Provider shall only provide access to Student Data to employees or contractors that are performing the Services. Employees with access to Student Data shall have signed confidentiality agreements regarding said Student Data. All employees with access to Student Records shall pass criminal background checks.
b. Destruction of Data. Provider shall destroy or delete all Personally Identifiable Data contained in Student Data and obtained under the DPA when it is no longer needed for the purpose for which it was obtained or transfer said data to LEA or LEA’s designee, according to a schedule and procedure as the parties may reasonable agree. Nothing in the DPA authorizes Provider to maintain personally identifiable data beyond the time period reasonably needed to complete the disposition.
c. Security Protocols. Both parties agree to maintain security protocols that meet industry standard practices in the transfer or transmission of any data, including ensuring that data may only be viewed or accessed by parties legally allowed to do so. Provider shall maintain all data obtained or generated pursuant to the Service Agreement in a secure digital environment and not copy, reproduce, or transmit data obtained pursuant to the Service Agreement, except as necessary to:
(i) fulfill the purpose of data requests by LEA, (ii) perform the Service(s), or (iii) fulfill the obligations or exercise any rights contained in this DPA. The foregoing does not limit the ability of the Provider to allow any necessary service providers to view or access data as set forth in Article IV, Section 4.
d. Employee Training. The Provider shall provide recurring, periodic (no less than annual, with additional sessions as needed throughout the year to address relevant issues/changes, such as (but not necessarily limited to) new or evolving security threats, changes to security protocols or practices, changes to software and/or hardware, identified vulnerabilities, etc.) security training to those of its employees who operate or have access to the system. Such trainings must be
tailored to the Provider’s business and cover, but not necessarily be limited to, the following topics: common types of attackers (e.g., cyber criminals, hacktivists, government sponsored groups, inside threats, etc.); common types of attacks (e.g., social engineering, spoofing, phishing, etc.) and how the information sought is typically used; identifying threats, avoiding threats, physical security and environmental controls; internal policies and procedures; and safe internet habits.
Further, Provider shall provide LEA with contact information of an employee who LEA may contact if there are any security concerns or questions.
e. Security Technology. When the service is accessed using a supported web browser, Secure Socket Layer (“SSL”), or equivalent technology shall be employed to protect data from unauthorized access. The service security measures shall include server authentication and data encryption. Provider shall host data pursuant to the DPA in an environment using a firewall that is periodically updated according to industry standards.
f. Security Coordinator. Provider shall provide the name and contact information of Provider’s Security Coordinator for the Student Data received pursuant to the DPA.
g. Subprocessors Bound. Provider shall enter into written agreements whereby Subprocessors agree to secure and protect Student Data in a manner consistent with the terms of this Article V. Provider shall periodically conduct or review compliance monitoring and assessments of Subprocessors to determine their compliance with this Article.
h. Periodic Risk Assessment. Provider further acknowledges and agrees to conduct periodic risk assessments and remediate any identified security and privacy vulnerabilities in a timely manner.
i. Backups. Provider agrees to maintain backup copies, backed up at least regularly, of Student Data in case of Provider’s system failure or any other unforeseen event resulting in loss of Student Data or any portion thereof.
j. Audits. Upon receipt of a written request from the LEA with reasonable advance written notice to Provider, the Provider will allow the LEA to audit the security and privacy measures that are in place to ensure protection of the Student Record or any portion thereof, subject to reasonable time and manner restrictions. The Provider will cooperate reasonably with the LEA and any state or federal agency with oversight authority/jurisdiction in connection with any audit or investigation of the Provider and/or delivery of Services to students and/or LEA, and shall provide reasonable access to the Provider’s facilities, staff, agents and LEA’s Student Data and all records pertaining to the Provider, LEA and delivery of Services to the Provider. To the extent allowed by law, all information exchanged during such audit and findings of such audit shall be the confidential information of Provider.
k. New Hampshire Specific Data Security Requirements. The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
(1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute;
(2) Limit unsuccessful logon attempts;
(3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions;
(4) Authorize wireless access prior to allowing such connections;
(5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity;
(6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions;
(7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles;
(8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services;
(9) Enforce a minimum password complexity and change of characters when new passwords are created;
(10) Perform maintenance on organizational systems;
(11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance;
(12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1;
(13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital;
(14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse;
(15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas;
(16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems;
(17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems;
(18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception);
(19) Protect the confidentiality of Student Data at rest;
(20) Identify, report, and correct system flaws in a timely manner;
(21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems;
(22) Monitor system security alerts and advisories and take action in response; and
(23) Update malicious code protection mechanisms when new releases are available.
2. Data Breach. In the event that Student Data is accessed or obtained by an unauthorized individual, Provider shall provide notification to LEA as soon as practicable and no later than within twenty (20) days from when Provider confirms or reasonably believes that a Data Breach has occurred. Provider shall follow the following process:
a. The security breach notification shall be written in plain language, shall be titled “Notice of Data Breach,” and shall present the information described herein under the following headings: “What Happened,” “What Information Was Involved,” “When it Occurred,” “What We Are Doing,” “What You Can Do,” and “For More Information.” Additional information may be provided as a supplement to the notice.
b. The security breach notification described in Section 2(a) shall include, at a minimum, to the extent known by Provider at the time, the following information:
i. The name and contact information of the reporting LEA subject to this section.
ii. A list of the types of personal information that were or are reasonably believed to have been the subject of a breach.
iii. If the information is possible to determine at the time the notice is provided, then either (1) the date of the breach, (2) the estimated date of the breach, or (3) the date range within which the breach occurred. The notification shall also include the date of the notice.
iv. Whether the notification was delayed as a result of a law enforcement investigation, if that information is possible to determine at the time the notice is provided.
v. A general description of the breach incident, if that information is possible to determine at the time the notice is provided.
vi. The estimated number of students and teachers affected by the breach, if any.
c. At LEA’s discretion, the security breach notification may also include any of the following:
i. Information about what the agency has done to protect individuals whose information has been breached.
ii. Advice on steps that the person whose information has been breached may take to protect himself or herself.
d. Provider agrees to adhere to all requirements in the New Hampshire Data Breach law and in federal law with respect to a data breach related to the Student Data, including, when appropriate or required, the required responsibilities and procedures for notification and mitigation of any such data breach.
e. Provider further acknowledges and agrees to have a written incident response plan that reflects best practices and is consistent with industry standards and federal and state law for responding to a data breach, breach of security, privacy incident or unauthorized acquisition or use of Student Data or any portion thereof, including personally identifiable information and agrees to provide LEA, upon request, with a copy of said written incident response plan.
f. If LEA requests Provider’s assistance providing notice of unauthorized access, and such assistance is not unduly burdensome to Provider, Provider shall notify the affected parent, legal guardian or eligible pupil of the unauthorized access, which shall include the information listed in subsections (b) and (c) above.
ARTICLE VI: MISCELLANEOUS
1. Term. The Provider shall be bound by this DPA for so long as the Provider maintains any Student Data. Notwithstanding the foregoing, Provider agrees to be bound by the terms and obligations of this DPA for three (3) years.
2. Termination. In the event that either party seeks to terminate this DPA, they may do so by mutual written consent and as long as any service agreement or terms of service, to the extent one exists, has lapsed or has been terminated.
Either party shall have the right to terminate the DPA and Service Agreement in the event of a material breach of the terms of this DPA by the other party.
3. Effect of Termination Survival. If the DPA is terminated, the Provider shall destroy all of LEA’s data pursuant to Article V, section 1(b).
4. Priority of Agreements. This DPA shall govern the treatment of student records in order to comply with the privacy protections, including those found in FERPA, IDEA. XXXXX, XXXX, XXX 000:0-x and 189:65-69; RSA 186; NH Admin. Code Ed. 300 and NH Admin. Code Ed. 1100. In the event there is conflict between the terms of the DPA and any other writing, such as service agreement or with any other bid/RFP, terms of
5. Notice. All notices or other communication required or permitted to be given hereunder must be in writing and given by personal delivery, facsimile or e-mail transmission (if contact information is provided for the specific mode of delivery), or first class mail, postage prepaid, sent to the designated representatives below.
The designated representative for the Provider for this Agreement is:
Name Liminex, Inc. dba GoGuardian Title Legal Department
Address 0000 X Xxxxx Xxx Xx Xxxxxxx, XX 00000
Telephone Email email@example.com
The designated representative for the LEA for this Agreement is: Xxxx Xxxxxxxx, Director of Technology
Xxxxxxx Xxxxxx Xxxxxxxx XXX00
00 Xxxxxxx Xxxxxx, Xxxxxxx XX 00000
6. Entire Agreement. This DPA constitutes the entire agreement of the parties relating to the subject matter hereof and supersedes all prior communications, representations, or agreements, oral or written, by the parties relating thereto. This DPA may be amended and the observance of any provision of this DPA may be waived (either generally or in any particular instance and either retroactively or prospectively) only with the signed written consent of both parties. Neither failure nor delay on the part of any party in exercising any right, power, or privilege hereunder shall operate as a waiver of such right, nor shall any single or partial exercise of any such right, power, or privilege preclude any further exercise thereof or the exercise of any other right, power, or privilege.
7. Severability. Any provision of this DPA that is prohibited or unenforceable in any jurisdiction shall, as to such jurisdiction, be ineffective to the extent of such prohibition or unenforceability without invalidating the remaining provisions of this DPA, and any such prohibition or unenforceability in any jurisdiction shall not invalidate or render unenforceable such provision in any other jurisdiction. Notwithstanding the foregoing, if such provision could be more narrowly drawn so as not to be prohibited or unenforceable in such jurisdiction while, at the same time, maintaining the intent of the parties, it shall, as to such jurisdiction, be so narrowly drawn without invalidating the remaining provisions of this DPA or affecting the validity or enforceability of such provision in any
8. Governing Law; Venue and Jurisdiction. THIS DPA WILL BE GOVERNED BY AND CONSTRUED IN ACCORDANCE WITH THE LAWS OF THE STATE OF NEW HAMPSHIRE, WITHOUT REGARD TO CONFLICTS OF LAW PRINCIPLES. EACH PARTY CONSENTS AND SUBMITS TO THE SOLE AND EXCLUSIVE JURISDICTION TO THE STATE AND FEDERAL COURTS OF ROCKINGHAM COUNTY FOR ANY DISPUTE ARISING OUT OF OR RELATING TO THIS DPA OR THE TRANSACTIONS CONTEMPLATED HEREBY.
9. Authority. Provider represents that it is authorized to bind to the terms of this Agreement, including confidentiality and destruction of Student Data and any portion thereof contained therein, all related or associated institutions, individuals, employees or contractors who may have access to the Student Data and/or any portion thereof, or may own, lease or control equipment or facilities of any kind where the Student Data and portion thereof stored, maintained or used in any way.
10. Waiver. No delay or omission of the LEA to exercise any right hereunder shall be construed as a waiver of any such right and the LEA reserves the right to exercise any such right from time to time, as often as may be deemed expedient.
11. Multiple Counterparts: This Agreement may be executed in any number of identical counterparts. If so executed, each of such counterparts shall constitute this Agreement. In proving this Agreement, it shall not be necessary to produce or account for more than one such counterpart.
[Signature Page Follows]
HAMPTON SCHOOL DISTRICT SAU 90
By: _GREG XXXXXXXX (May 4, 2021 06:31 EDT)
Director of Technology
LIMINEX, INC. D/B/A GOGUARDIAN
By: _Brian Xxxxxxxxxxx (May 3, 2021 21:39 PDT)
Date: May 3, 2021
E XHIBIT “A”
DESCRIPTION OF SERVICES
-GoGuardian Admin: Content-filtering and alerting
-GoGuardian Beacon: Suicide and self-harm alert and notification tool
-GoGuardian DNS: Network-level filtering
-GoGuardian Gateway: Device-level filtering
-GoGuardian Fleet: Device management
-GoGuardian Teacher: Classroom management
SCHEDULE OF DATA
Category of Data
Check if used by your system
Application Technology Meta Data
technology meta data- Please specify:
Application Use Statistics
Meta data on user
interaction with application
Standardized test scores
Other assessment data- Please specify:
Student school (daily)
Student class attendance
Online communications that are captured (emails, blog entries)
(including, student- teacher chats in chat feature of
Conduct or behavioral
Date of Birth
Place of Birth
Ethnicity or race
Language information (native, preferred or
primary language spoken by student)
Student grade level
Year of graduation
Other enrollment information-Please
Parent/Guardian Contact Information
Parent ID number (created to link parents
First and/or Last
Student scheduled courses
English language learner
Low income status
Specialized education services (IEP or 504)
Living situations (homeless/xxxxxx care)
Other indicator information-Please
Category of Data
Check if used by your system
Student Contact Information
Local (School district)
State ID number
student ID number
Student app username
Student app passwords
First and/or Last
Student In App Performance
Program/application performance (typing program-student types 60 wpm, reading
program-student reads below grade level)
Student Program Membership
Academic or extracurricular activities a student may belong to
or participate in
Student Survey Responses
Student responses to
surveys or questionnaires
Student generated content; writing, pictures
Other student work data
Student course grades
Student course data
Student course grades/performance
Other transcript data - Please specify:
Student bus assignment
Student pick up and/or
drop off location
Student bus card ID
Other transportation data
Please list each additional data element used, stored or collected
by your application
(xxxxx://xxx.xxxxx r xxxx.xxx/xxxxxxxXxx vacy.html) describes
the Student Data and other information
E XHIBIT “C”
De-Identifiable Information (DII): De-Identification refers to the process by which the Vendor removes or obscures any Personally Identifiable Information (“PII”) from student records in a way that removes or minimizes the risk of disclosure of the identity of the individual and information about them. The Provider’s specific steps to de-identify the data will depend on the circumstances, but should be appropriate to protect students. Some potential disclosure limitation methods are blurring, masking, and perturbation. De-identification should ensure that any information when put together cannot indirectly identify the student, not only from the viewpoint of the public, but also from the vantage of those who are familiar with the individual.
NIST 800-63-3: Draft National Institute of Standards and Technology (“NIST”) Special Publication 800-63-3 Digital Authentication Guideline.
Personally Identifiable Information (PII): The terms “Personally Identifiable Information” or “PII” shall include, but are not limited to, student data, metadata, and user or pupil-generated content obtained by reason of the use of Provider’s software, website, service, or app, including mobile apps, whether gathered by Provider or provided by LEA or its users, students, or students’ parents/guardians. PII includes, without limitation, at least the following:
First Name Home Address
Last Name Subject
Telephone Number Email Address
Discipline Records Test Results
Special Education Data Juvenile Dependency Records Grades Evaluations
Criminal Records Medical Records
Health Records Social Security Number Biometric Information Disabilities Socioeconomic Information Food Purchases Political Affiliations Religious Information Text Messages Documents
Student Identifiers Search Activity
Photos Voice Recordings
Videos Date of Birth
Place of birth Social Media Address Unique pupil identifier
Credit card account number, insurance account number, and financial services account number Name of the student's parents or other family members
Indirect Identifiers: Any information that, either alone or in aggregate, would allow a reasonable person to be able to identify a student to a reasonable certainty
Information in the Student’s Educational Record Information in the Student’s Email
Provider: For purposes of the DPA, the term “Provider” means provider of digital educational software or services, including cloud-based services, for the digital storage, management, and retrieval of pupil records.
Pupil Generated Content: The term “pupil-generated content” means materials or content created by a pupil during and for the purpose of education including, but not limited to, essays, research reports, portfolios, creative writing, music or other audio files, photographs, videos, and account information that enables ongoing ownership of pupil content.
Pupil Records: Means both of the following: (1) Any information that directly relates to a pupil that is maintained by LEA and (2) any information acquired directly from the pupil through the use of instructional software or applications assigned to the pupil by a teacher or other local educational LEA employee.
School Official: For the purposes of this Agreement and pursuant to 34 CFR 99.31 (B), a School Official is a contractor that: (1) Performs an institutional service or function for which the agency or institution would otherwise use employees; (2) Is under the direct control of the agency or institution with respect to the use and maintenance of education records; and (3) Is subject to 34 CFR 99.33(a) governing the use and re-disclosure of personally identifiable
information from student records. The definition of “school official” encompasses the definition of “authorized school personnel” under 603 CMR 23.02.
Student Data: Student Data includes any data, whether gathered by Provider or provided by LEA or its users, students, or students’ parents/guardians, that is descriptive of the student
including, but not limited to, information in the student’s educational record or email, first and last name, home address, telephone number, email address, or other information allowing online contact, discipline records, videos, test results, special education data, juvenile dependency records, grades, evaluations, criminal records, medical records, health records, social security numbers, biometric information, disabilities, socioeconomic information, food purchases, political affiliations, religious information, text messages, documents, the name of the student's parents or other family members, place of birth, social media address, unique pupil identifier, and credit card account number, insurance account number, and financial services account number, student identifiers, search activity, photos, voice recordings or geolocation information. Student Data shall constitute Pupil Records for the purposes of this Agreement, and for the purposes of New Hampshire and Federal laws and regulations. Student Data as specified in Exhibit B is confirmed to be collected or processed by the Provider pursuant to the Services.
Student Data shall not constitute that information that has been anonymized or de-identified, or anonymous usage data regarding a student’s use of Provider’s services.
Subscribing LEA: An LEA that was not party to the original Services Agreement and who accepts the Provider’s General Offer of Privacy Terms.
Subprocessor: For the purposes of this Agreement, the term “Subprocessor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its software, and who has access to PII.
Targeted Advertising: Targeted advertising means presenting an advertisement to a student where the selection of the advertisement is based on student information, student records or student generated content or inferred over time from the usage of the Provider’s website, online service or mobile application by such student or the retention of such student’s online activities or requests over time.
Third Party: The term “Third Party” means an entity that is not the provider or LEA.
E XHIBIT “D”
DIRECTIVE FOR DISPOSITION OF DATA
[Name or District or LEA] directs [Name of Company] to dispose of data obtained by Company pursuant to the terms of the DPA between LEA and Provider. The terms of the Disposition are set forth below:
1. Extent of Disposition
Disposition is partial. The categories of data to be disposed of are set forth below or are found in an attachment to this Directive:
[Insert categories of data here]
Disposition is Complete. Disposition extends to all categories of data.
2. Nature of Disposition
Disposition shall be by destruction or deletion of data.
Disposition shall be by a transfer of data. The data shall be transferred to the following site as follows:
[Insert or attach special instructions.]
3. Timing of Disposition
Data shall be disposed of by the following date:
As soon as commercially practicable
By (Insert Date]
(Authorized Representative of LEA
5. Verification of Disposition of Data
Authorized Representative of Company Date
Final Audit Report 2021-05-04
Document created by Xxxxx Xxxxxx (firstname.lastname@example.org)
2021-05-04 - 1:14:25 AM GMT- IP address: 188.8.131.52
Document emailed to Xxxxx Xxxxxxxxxxx (email@example.com) for signature
2021-05-04 - 1:15:10 AM GMT
Email viewed by Xxxxx Xxxxxxxxxxx (firstname.lastname@example.org)
2021-05-04 - 4:39:07 AM GMT- IP address: 184.108.40.206
Document e-signed by Xxxxx Xxxxxxxxxxx (email@example.com)
Signature Date: 2021-05-04 - 4:39:57 AM GMT - Time Source: server- IP address: 220.127.116.11
Document emailed to XXXX XXXXXXXX (firstname.lastname@example.org) for signature
2021-05-04 - 4:39:59 AM GMT
Email viewed by XXXX XXXXXXXX (email@example.com)
2021-05-04 - 4:40:05 AM GMT- IP address: 18.104.22.168
Document e-signed by XXXX XXXXXXXX (firstname.lastname@example.org)
Signature Date: 2021-05-04 - 10:31:58 AM GMT - Time Source: server- IP address: 22.214.171.124
2021-05-04 - 10:31:58 AM GMT
Xxxxx Xxxxxx (email@example.com) Signed