Data Processing Agreement

Between the Local Education Agency ("LEA" or "District") and Speaky ("Provider")

This Data Processing Agreement ("DPA") is entered into by and between the LEA identified on the signature page and Speaky, the operator of the language learning platform at speaky.space.

This DPA is aligned with the Student Data Privacy Consortium (SDPC) National Data Privacy Agreement (NDPA) framework and is intended to ensure the protection of Student Data in compliance with the Family Educational Rights and Privacy Act (FERPA), the Children's Online Privacy Protection Act (COPPA), and applicable state student data privacy laws.

This DPA supplements and is incorporated into any underlying service agreement between the LEA and Provider.


Article I: Purpose and Scope

1.1 Purpose

The purpose of this DPA is to describe the duties and responsibilities to protect Student Data, including compliance with all applicable federal, state, and local privacy laws, rules, and regulations, all as may be amended from time to time.

1.2 Description of Services

Provider operates Speaky, an AI-powered language learning platform that enables students to practice speaking a target language through real-time voice conversations with an AI tutor. The Service includes:

  • Real-time AI voice conversations in the student's target language
  • Speech-to-text transcription of student speech
  • AI-generated conversation reviews and performance feedback
  • Vocabulary tracking with spaced repetition flashcard review
  • Language proficiency assessments
  • Classroom features enabling teachers to view student progress and send instructional messages

1.3 Scope

This DPA applies to all Student Data that Provider collects, receives, stores, processes, or transmits in connection with providing the Service to the LEA.


Article II: Definitions

"Authorized Representative" means an employee or agent of the LEA authorized to execute this DPA.

"Data Breach" means any unauthorized release, disclosure, or acquisition of Student Data that compromises the security, confidentiality, or integrity of the Student Data.

"De-Identified Data" means data from which all personally identifiable information has been removed or obscured such that the remaining data cannot reasonably be used to identify a specific individual.

"Educational Records" means records directly related to a student that are maintained by an educational agency or institution, as defined by FERPA (20 U.S.C. § 1232g).

"Personally Identifiable Information" ("PII") means information that, alone or in combination with other information, can be used to identify a specific individual, including but not limited to: name, email address, voice recordings, conversation transcripts, and learning performance data.

"Student Data" means any data, whether gathered by the Provider or provided by the LEA or its students, that is descriptive of the student, including but not limited to: demographics, contact information, enrollment information, assessment and achievement data, disciplinary information, conversation transcripts, voice-derived transcripts, vocabulary data, learning progress data, AI-generated performance reviews, and other information contained in Educational Records.

"Sub-processor" means any third party engaged by Provider to process Student Data on Provider's behalf.


Article III: Data Ownership and Control

3.1 Ownership

All Student Data remains the property of and under the control of the LEA or the student's parent/legal guardian, as applicable. Provider has no ownership rights in any Student Data.

3.2 Purpose Limitation

Provider shall use Student Data solely for the purpose of fulfilling its obligations under the service agreement and this DPA — specifically, providing the language learning Service to students as authorized by the LEA. Provider shall not use Student Data for any other commercial purpose, including but not limited to advertising, marketing, or building user profiles unrelated to the educational service.

3.3 Prohibited Uses

Provider shall not:

  • Sell Student Data to any third party.
  • Use Student Data for targeted advertising or any form of marketing to students or their families.
  • Use Student Data for AI model training, development of synthetic data, or content generation without prior written consent from the LEA.
  • Disclose Student Data to any third party except Sub-processors as described in Article VI and as necessary to provide the Service.
  • Attempt to re-identify De-Identified Data.

Article IV: Confidentiality

4.1 Employee Obligations

All Provider employees and contractors with access to Student Data shall comply with the terms of this DPA. Provider shall require and maintain appropriate confidentiality agreements from each employee or contractor who has access to Student Data.

4.2 Access Restriction

Provider shall restrict access to Student Data to only those employees and contractors who require access to perform their obligations under the service agreement.


Article V: Data Security

5.1 Security Measures

Provider shall implement and maintain an adequate cybersecurity framework to protect Student Data. Provider's current security measures include:

  • Encryption in transit: All data transmitted between students' browsers and the Service is encrypted using TLS/HTTPS. Real-time voice conversations are transmitted over encrypted WebSocket connections (WSS).
  • Encryption at rest: All database storage is encrypted using AES-256 encryption provided by our database hosting provider (Neon).
  • Password security: User passwords are hashed using bcrypt with a cost factor of 12.
  • Session security: Authentication tokens are stored in HTTP-only, secure, SameSite cookies.
  • Access controls: Database access requires authentication and is restricted to authorized application services.
  • Cryptographic token generation: Password reset and verification tokens use cryptographically secure random number generation with time-limited expiry.

5.2 Cybersecurity Framework

Provider's security practices align with the following recognized frameworks and certifications (maintained by Provider's infrastructure sub-processors):

Sub-processorCertifications
Neon (database hosting)SOC 2 Type 2, ISO 27001, ISO 27701
Vercel (application hosting)SOC 2 Type 2, ISO 27001
Google Cloud (AI and speech services)SOC 2, ISO 27001, ISO 27701, FedRAMP
Stripe (payment processing)PCI DSS Level 1
Amazon Web Services / SES (email)SOC 2, ISO 27001, FedRAMP

5.3 Security Audits

Provider shall conduct a security assessment no less than once per year and upon any Data Breach. Upon 10 business days' notice and execution of a confidentiality agreement, Provider shall provide the LEA with a summary of the most recent security assessment, subject to reasonable redaction of proprietary information.

5.4 LEA Audit Rights

The LEA may audit Provider's security and privacy measures upon at least 10 business days' written notice. Such audits shall be conducted during normal business hours and shall not unreasonably interfere with Provider's operations.


Article VI: Sub-processors

6.1 Authorized Sub-processors

Provider uses the following Sub-processors to process Student Data:

Sub-processorPurposeStudent Data ProcessedLocation
Google (Gemini API)AI conversation partnerReal-time audio, conversation context, language/proficiencyUnited States
Google (Cloud Speech-to-Text)Speech transcriptionReal-time audio, target languageUnited States
NeonDatabase hostingAll Student Data stored in the databaseUnited States (AWS)
VercelApplication hostingWeb request data (IP, browser info)United States
Amazon SESTransactional emailStudent email, nameUnited States
Cloudflare (R2)Voice recording storageUser and AI voice recordingsUnited States
StripePayment processing (organization billing)Organization billing dataUnited States

A complete and current Sub-processor List is maintained at Sub-processor List.

6.2 Sub-processor Obligations

Provider shall enter into written agreements with all Sub-processors requiring them to protect Student Data in a manner no less protective than the terms of this DPA. Each Sub-processor agreement shall provide that the Sub-processor:

  • Shall protect Student Data in accordance with applicable law and the terms of this DPA.
  • Shall not sell Student Data.
  • Shall not use Student Data for any purpose other than providing the contracted service.

6.3 Sub-processor Changes

Provider shall notify the LEA at least 30 days before adding a new Sub-processor that will process Student Data. The LEA may object to the new Sub-processor within 30 days of notification. If the LEA objects and Provider cannot reasonably accommodate the objection, either party may terminate this DPA.

6.4 Provider Liability

Provider shall remain fully liable for the acts and omissions of its Sub-processors with respect to Student Data.


Article VII: Data Breach Notification

7.1 Notification Timeline

In the event of a Data Breach, Provider shall notify the LEA within 72 hours of confirming that a Data Breach has occurred. If notification within 72 hours would disrupt an investigation by law enforcement, notification shall be made within a reasonable time after the investigation is no longer compromised.

7.2 Notification Content

The breach notification shall be written in plain language and include:

  1. What Happened — A description of the incident.
  2. What Information Was Involved — The types of Student Data affected.
  3. When It Occurred — The date or estimated date of the breach and the date of discovery.
  4. What We Are Doing — Steps taken to mitigate harm and prevent recurrence.
  5. What You Can Do — Recommended actions for the LEA.
  6. For More Information — A point of contact for further inquiries.

7.3 Cooperation

Provider shall cooperate with the LEA in investigating and remediating any Data Breach and shall provide reasonable assistance in the LEA's notification to affected individuals, as required by law.


Article VIII: Data Retention and Disposition

8.1 Retention During Agreement

During the term of the service agreement, Provider shall retain Student Data only for as long as necessary to provide the Service.

8.2 Disposition Upon Request

Upon written request from the LEA, Provider shall dispose of (delete) or provide a mechanism to transfer Student Data within 60 days of receiving the request.

8.3 Disposition Upon Termination

Upon termination or expiration of the service agreement, Provider shall dispose of all Student Data within 60 days, unless:

  • The LEA directs Provider to return the data instead of deleting it.
  • Retention is required by applicable law or regulation.

Provider shall provide written confirmation of data disposition upon request.

8.4 Survival

The obligations of this Article VIII, along with Articles III, IV, V, and VII, shall survive the termination of this DPA and the underlying service agreement.


Article IX: Artificial Intelligence Provisions

9.1 AI Training Prohibition

Provider shall not use Student Data to train, fine-tune, or develop artificial intelligence or machine learning models, nor to develop synthetic or inferred data, without prior written consent from the LEA.

9.2 Third-Party AI Processing

Provider uses Google's Gemini API to power the AI conversation feature. On the paid tier:

  • Google does not use data sent to the API for model training.
  • Google retains conversation data for up to 55 days solely for abuse monitoring and safety enforcement.
  • Google acts as a data processor under the Google Cloud Data Processing Addendum.

Provider shall ensure that any third-party AI services used to process Student Data comply with the requirements of this DPA.

9.3 AI Content Safety

Provider implements content safety measures to prevent the AI from generating inappropriate, harmful, or off-topic content in student conversations. Provider shall monitor and improve these safety measures on an ongoing basis.

9.4 AI Fairness

Provider shall make reasonable efforts to audit AI technologies used in the Service for biases and fairness, including but not limited to accent/dialect bias and cultural representation in language instruction.


Article X: FERPA and COPPA Compliance

10.1 FERPA

Provider acknowledges that Student Data may include Educational Records subject to FERPA. Provider agrees to:

  • Use Educational Records solely for the educational purposes authorized by the LEA.
  • Not re-disclose PII from Educational Records to any third party except Sub-processors as described in this DPA.
  • Maintain appropriate security measures to protect Educational Records.
  • Allow the LEA to retain control over Educational Records.

Provider acts as a "school official" with a "legitimate educational interest" as those terms are used in FERPA and its implementing regulations.

10.2 COPPA

Provider acknowledges that Student Data may include information subject to COPPA. Provider relies on the LEA to provide consent on behalf of parents for the collection of student data for educational purposes, as permitted by COPPA and its implementing regulations. Provider agrees to:

  • Use Student Data from children under 13 solely for the educational purposes authorized by the LEA.
  • Not disclose Student Data from children under 13 to third parties except Sub-processors as necessary to provide the Service.
  • Not use Student Data from children under 13 for commercial purposes unrelated to the educational service.
  • Provide parents, through the LEA, with the ability to review and request deletion of their child's data.

10.3 State Laws

Provider shall comply with applicable state student data privacy laws. The LEA shall inform Provider of any state-specific requirements that supplement this DPA.


Article XI: General Provisions

11.1 Term

This DPA shall be effective as of the date of execution and shall continue for the duration of the underlying service agreement, unless earlier terminated.

11.2 Termination

Either party may terminate this DPA upon 30 days' written notice. Termination of this DPA shall also terminate the underlying service agreement with respect to the processing of Student Data. The obligations regarding data disposition, confidentiality, and security shall survive termination.

11.3 Governing Law

This DPA shall be governed by the laws of the state in which the LEA is located.

11.4 Amendments

This DPA may only be amended by a written instrument signed by both parties.

11.5 Severability

If any provision of this DPA is found to be unenforceable, the remaining provisions shall continue in full force and effect.

11.6 Entire Agreement

This DPA, together with the underlying service agreement and the exhibits hereto, constitutes the entire agreement between the parties regarding the handling of Student Data.


Exhibit A: Schedule of Student Data Elements

The following data elements may be collected or generated by the Service:

Required Data Elements

Data ElementPurpose
Email addressAccount creation and authentication
Name (first and/or last)Display in the application and classroom features
Target language selectionCore functionality — determines conversation language
Proficiency level (CEFR)Core functionality — determines conversation difficulty

Data Elements Generated Through Use

Data ElementPurpose
Conversation transcripts (student speech, text)Core functionality — record of learning activity
Conversation transcripts (AI responses, text)Core functionality — record of learning activity
AI response audioConversation replay functionality
Voice recordings (student speech audio)Pronunciation review, teacher assessment
Voice recordings (AI tutor speech audio)Conversation replay functionality
Conversation metadata (topic, scenario, date, duration)Learning progress tracking
AI-generated conversation reviews (ratings, tips, vocabulary)Performance feedback
Vocabulary word bank entries (words, definitions, context)Vocabulary learning and spaced repetition review
Spaced repetition review data (review dates, scores)Flashcard scheduling algorithm
Proficiency assessment resultsProgress measurement
Usage statistics (conversations, minutes, messages, words learned)Progress tracking and reporting to teachers
Badges and milestonesStudent motivation and progress recognition
Teacher-student relationship dataClassroom organization
Teacher messages to studentsInstructional communication

Data Elements NOT Collected

  • Social Security numbers
  • Biometric identifiers (fingerprints, facial recognition)
  • Disciplinary records
  • Health or medical records
  • Free/reduced lunch status
  • Disability or IEP information
  • Race, ethnicity, or demographic data (beyond language selection)

Exhibit B: Cybersecurity Framework

Provider's security practices are supported by the following:

Infrastructure Security Certifications

  • Neon (database): SOC 2 Type 2, ISO 27001, ISO 27701, HIPAA
  • Vercel (hosting): SOC 2 Type 2, ISO 27001, PCI DSS v4.0
  • Google Cloud (AI/speech): SOC 1/2/3, ISO 27001, ISO 27017, ISO 27018, ISO 27701, FedRAMP
  • AWS (email): SOC 1/2/3, ISO 27001, FedRAMP
  • Stripe (payments): PCI DSS Level 1, SOC 1/2

Application-Level Security Measures

  • TLS/HTTPS encryption for all web traffic
  • WSS encryption for all real-time voice connections
  • AES-256 encryption at rest (database)
  • Bcrypt password hashing (cost factor 12)
  • HTTP-only, Secure, SameSite authentication cookies
  • Cryptographically secure random token generation
  • Time-limited password reset and verification tokens
  • Role-based access controls in the application