Skip to content
New: The 2026 Outside Provider Safety Report. Get it by email×
New: The 2026 Outside Provider Safety Report. Get it by email×
New: The 2026 Outside Provider Safety Report. Get it by email×

LEGAL

Data Processing Agreement

Effective May 2026 · Version 5.0 · Part of the enrops Terms of Service

This agreement is incorporated into the enrops Terms of Service. It governs how enrops processes personal data on behalf of the providers, schools and parks that use the platform. If it conflicts with the Terms on data processing, this agreement controls. By accepting the Terms electronically or creating an enrops account, a program agrees to it without a separate signature; a countersigned copy is available on request.

1. Definitions

  • "Personal Data" means information relating to an identified or identifiable individual that enrops processes on the Operator's behalf, including End User Data.
  • "End User Data" means data about the Operator's children/students, parents/guardians, and employees/contractors that the Operator (or parents/guardians through the Operator) enters into the Platform.
  • "Children's Data" means Personal Data of a child under 13 within the meaning of COPPA (16 C.F.R. § 312.2). For purposes of state-law minor protections that extend to additional age groups (for example, Oregon's prohibitions for individuals known to be under 16 and similar provisions under other state laws), "Minor Data" means Personal Data of an individual whom the Operator or enrops knows, or reasonably should know, is under the age threshold specified by the applicable state law.
  • "Processing," "Controller," "Processor," "Data Subject," and "Sensitive Data" have the meanings given under applicable data protection law, including the Oregon Consumer Privacy Act (OCPA).
  • "Subprocessor" means a third party engaged by enrops to process Personal Data.
  • "Applicable Data Protection Law" means all privacy and data protection laws applicable to the processing, including COPPA (16 C.F.R. Part 312), OCPA (ORS 646A.570-589), the comprehensive consumer-privacy laws of other U.S. states where the Operator or its end users are located, and, where applicable to the Operator, FERPA (20 U.S.C. 1232g; 34 C.F.R. Part 99) and state student-data-privacy laws.

2. Roles and Scope

The Operator is the Controller and enrops is the Processor. enrops processes Personal Data only to provide the Platform and only on the Operator's documented instructions. For purposes of this DPA, the Operator's "documented instructions" consist of (i) the Agreement and this DPA, (ii) the Operator's configuration of and use of the Platform's features in the ordinary course, and (iii) any additional written instructions the Operator provides to enrops. enrops processes Personal Data only to provide the Platform on those instructions. enrops will inform the Operator if, in enrops's reasonable opinion, an instruction violates Applicable Data Protection Law, and in such case enrops may suspend performance of the affected instruction until the parties resolve the issue, without breach of the Agreement.

3. Subject Matter, Duration, Nature and Purpose

  • Subject matter: provision of the enrops Platform (enrollment, parent communications, certification, and operational management).
  • Duration: for the term of the Operator's account and until deletion/return under Section 11.
  • Nature and purpose: storing/retrieving records as configured; delivering transactional communications on the Operator's behalf; generating reports/analytics for the Operator's use. enrops does not process Personal Data for any purpose beyond providing the Platform, and does not sell Personal Data, use it for targeted advertising, or use it to profile minors.

4. Categories of Personal Data and Data Subjects

  • Data Subjects: children/students enrolled in the Operator's programs; their parents/guardians and emergency/authorized-pickup contacts; the Operator's employees and contractors.
  • Categories: identifiers (name, age/DOB, contact details); emergency/pickup contacts; children's health/medical information (allergies, conditions, medications, special needs) as Sensitive Data; account and usage records. The Platform is not designed or marketed to collect, and the Operator will not enter into the Platform, biometric identifiers, government ID numbers, precise geolocation, payment card numbers (handled by the payment Subprocessor), or child-submitted data. If the Operator enters any such data despite this restriction, the Operator is solely responsible for the consequences of that entry and for any required notices, consents, or compliance obligations triggered by that data, and enrops may delete it.

5. Operator (Controller) Obligations

The Operator represents and warrants that it will: provide required notices to and obtain any consents required from parents/guardians (including verifiable parental consent under COPPA where it applies, in accordance with the FTC's 2025 amendments to the COPPA Rule) before entering Children's Data; collect only data its program needs (data minimization), with particular care for health/medical information; ensure children do not access the Platform directly; and have the legal right to provide all Personal Data it enters. The Operator further acknowledges that, with respect to Children's Data, enrops is acting as an agent of the Operator (and, where applicable, of the parent/guardian) under the COPPA Rule, and that the Operator is responsible for directing parents to the Operator's own privacy notice and for serving as the primary point of contact for parental access, review, and deletion requests. The Operator will also notify enrops promptly in writing if (a) the Operator becomes, or contracts with, an educational agency or institution subject to FERPA, or (b) the Operator's program is subject to a state student-data-privacy law (such as California SOPIPA / AB 1584, New York Education Law § 2-d, or Illinois SOPPA) that requires a written addendum.

6. enrops (Processor) Obligations

enrops will: (a) process Personal Data only on documented instructions; (b) ensure personnel authorized to process Personal Data are bound by confidentiality; (c) implement the technical and organizational measures in Annex A; (d) respect the Subprocessor terms in Section 8; (e) assist the Operator under Sections 9-10; (f) make available information reasonably necessary to demonstrate compliance and allow for audits under Section 12; and (g) delete or return Personal Data under Section 11.

7. Confidentiality

enrops keeps Personal Data confidential and limits access to personnel who need it. Access to Children's Data and children's health/medical information is further restricted to authorized personnel with a specific operational need.

8. Subprocessors

The Operator provides general authorization for enrops to engage Subprocessors (currently: Stripe, payments; Supabase, database/backend; Resend, transactional email; Netlify, hosting). enrops imposes data protection obligations on each Subprocessor no less protective than the obligations applicable to enrops under this DPA and remains liable for the acts and omissions of its Subprocessors to the same extent enrops would be liable for performing those services itself, subject to the limitations of liability in the Agreement. Before adding or replacing a Subprocessor that processes Personal Data, enrops will give at least 30 days' advance notice (by email to the Operator's registered account address and/or by updating the Subprocessor Disclosure) and an opportunity to object on reasonable data-protection grounds; if the parties cannot resolve the objection within 30 days, the Operator may terminate the affected portion of the Platform without penalty and receive a pro-rata refund of any prepaid fees attributable to the unused portion of the term.

9. Data Subject and Parental Requests

Taking into account the nature of the processing, enrops will assist the Operator in responding to requests from Data Subjects (and parents/guardians regarding Children's Data) to exercise rights of access, correction, deletion, and portability, and in fulfilling parental review/deletion requests. enrops will promptly forward any such request it receives directly and will not respond on the Operator's behalf except on instruction.

10. Security Incident and Breach Notification

enrops will notify the Operator without undue delay, and within 72 hours, after becoming aware of a Personal Data breach affecting the Operator's data, to the extent known at the time of notice, describing the nature, categories/approximate number of records and Data Subjects affected, likely consequences, and measures taken or proposed to be taken; enrops will supplement the initial notice as additional information becomes available. enrops will reasonably assist the Operator, at the Operator's cost for assistance beyond what is required of enrops as a processor/service provider under Applicable Data Protection Law, with the Operator's notification and remediation obligations under all applicable state and federal breach-notification laws (including ORS 646A.600-628 where medical or health information is involved, and the comparable laws of other states where affected Data Subjects reside). The parties acknowledge that enrops's notice to the Operator is not, by itself, a substitute for the Operator's notice obligations to Data Subjects, parents/guardians, or regulators, which remain the Operator's responsibility as Controller. enrops maintains an Incident Response Procedure.

11. Deletion and Return of Data

On termination, enrops will, at the Operator's choice, return (in a commonly used, machine-readable format) and/or delete all Personal Data after a 30-day export window, and delete existing copies within a commercially reasonable period thereafter, unless retention is required by law. Children's health/medical information is prioritized for prompt deletion. Backups purge on the providers' standard cycles.

12. Audit and Compliance

enrops will make available information reasonably necessary to demonstrate compliance. On 30 days' notice, no more than once per year (unless required by a regulator or following a breach), enrops will respond to a reasonable questionnaire or provide available third-party assessments. On-site audits, if reasonably required, are at the Operator's expense, during business hours, subject to confidentiality.

13. Sensitive and Children's Data

The parties acknowledge that Children's Data and children's health/medical information are Sensitive Data and that processing them must comply with COPPA. enrops applies heightened access controls, encryption, minimization, and retention limits.

14. FERPA Module (Applies ONLY to FERPA-Covered Customers)

This Section applies only where the Operator has notified enrops in writing that the Operator is, or contracts with, an educational agency or institution subject to FERPA, and only with respect to the records covered by that notice. Where it applies, with respect to "education records," enrops acts as a "school official" with a "legitimate educational interest" under 34 C.F.R. 99.31(a)(1)(i)(B): performs a service the institution would otherwise use its own employees to perform; is under the institution's direct control over use/maintenance of education records; uses education records only for the authorized purpose and will not re-disclose except as permitted (34 C.F.R. 99.33); and will be referenced in the institution's annual FERPA notification. Where the Operator is not FERPA-covered or has not so notified enrops, this Section does not apply and nothing in this DPA implies that enrops is otherwise subject to FERPA or that the relationship is FERPA-governed.

15. State Privacy Laws; Processor Duties

enrops acts as a "processor"/"service provider" under OCPA and comparable state laws and will: process Personal Data only per instructions; assist with consumer-rights requests and data protection assessments; and ensure the Subprocessor and security obligations above. Each party complies with its obligations under Applicable Data Protection Law. For the CCPA/CPRA where applicable, enrops is a service provider: it will not sell or share Personal Data; will not retain, use, or disclose it for any purpose other than performing the services (or as permitted by the CCPA); will not retain/use/disclose it outside the direct business relationship; and will not combine it with other sources except as permitted. enrops certifies its understanding of and compliance with these restrictions. BECAUSE OPERATORS ARE LOCATED ACROSS THE UNITED STATES, the parties will comply with the consumer-privacy and student-data-privacy laws of each state where an Operator or its end users are located, not only Oregon, and will execute any state-specific student-data-privacy addendum reasonably required (for example, California SOPIPA, New York Education Law 2-d, or Illinois SOPPA).

16. Cross-Border Transfers

enrops processes Personal Data in the United States. If the Operator or its end users are located outside the U.S., or if enrops engages a Subprocessor outside the U.S., the parties will implement an appropriate transfer mechanism before such transfer occurs.

17. Liability; Order of Precedence

Each party's liability under this DPA is subject to the limitations of liability in the Agreement, except where Applicable Data Protection Law does not permit such limitation. This DPA supplements and does not replace any more specific written agreement the parties sign.

18. Governing Law

This DPA is governed by the laws of the State of Oregon, consistent with the Agreement.

Annex A: Technical and Organizational Security Measures

Encryption (TLS 1.2+ in transit; at rest via providers); role-based least-privilege access with tighter controls on children's/health data; MFA for admin access; managed-infrastructure hosting with security review and vulnerability monitoring; access/error logging and incident detection; data minimization and retention limits; regular backups; personnel confidentiality; documented incident response (72-hour internal target); subprocessor management.

Annex B: Current Subprocessors

Stripe (payments, US); Supabase (database/backend, US); Resend (transactional email, US); Netlify (hosting, US). Maintained in the enrops Subprocessor Disclosure.

Execution

By accepting the Agreement electronically or otherwise creating an enrops account, the Operator agrees to be bound by this DPA without the need for a separate signature. Operators that require a countersigned copy can request one at hello@enrops.com.

Questions about this agreement: hello@enrops.com