District Subscriber Agreement
District and subscriber contract framework
This page summarizes the main commercial and operational terms WhyDive expects to address with districts and institutional subscribers.
Effective date: April 6, 2026
Last updated: April 6, 2026
Document version: Public Summary v1.0
Document summary
- Who this is for
- District reviewers, school teams, authorized users, and public visitors evaluating WhyDive Education.
- What this covers
- This page summarizes the main commercial and operational terms WhyDive expects to address with districts and institutional subscribers.
- How to ask a question
- Use the contact page or email [email protected].
- Current status
- Public Summary v1.0
Purpose of a district agreement
Districts and institutional subscribers generally need a dedicated agreement that goes beyond public website terms. That agreement typically governs subscription scope, fees, renewal, implementation responsibilities, data handling obligations, support expectations, suspension or termination, offboarding, and allocation of legal risk.
Services, scope, and order details
The final district or subscriber agreement should identify the services purchased, the implementation scope, the customer entity, the subscription or service term, any school or district limitations, and any related order form, quote, or statement of work that defines pricing and deliverables.
Fees, invoices, and renewal
The agreement should describe fees, invoicing, payment timing, renewal or nonrenewal mechanics, and what happens if payment is late or disputed. If service purchases, pilot fees, subscription fees, or services are treated differently, those distinctions should be stated clearly.
Implementation and support responsibilities
The agreement should allocate practical responsibilities between WhyDive and the customer, including onboarding, roster provisioning, school participation, rollout setup, administrator assignment, support contacts, and any implementation assumptions that affect service success.
Data, confidentiality, and offboarding
The agreement should explain how customer-controlled data, student data, and institutional records are handled; how confidentiality obligations apply; and what happens to covered data at termination, including return, deletion, or limited retention under the DPA or other applicable terms.
Intellectual property and permitted use
The agreement should distinguish between customer data and WhyDive intellectual property, including assessments, diagnostic methodology, reports, templates, software, and service materials. It should also state the license scope granted to the subscriber and any restrictions on redistribution, resale, copying, or reuse outside the agreed service scope.
Warranties, liability, and termination
The agreement should address service disclaimers, any negotiated warranties, limitations of liability, indemnity positions if any, suspension rights, termination rights, and post-termination obligations. These issues are often central to district legal review and should not be left only to the public Terms of Use.
Public terms versus subscriber terms
The public Terms of Use are not intended to replace a district-facing contract. Institutional customers should expect the district or subscriber agreement to govern the commercial and operational relationship more directly where applicable.
Current status
This page is a public-facing summary rather than a final executable district agreement. Production-ready district or subscriber agreement forms are completed during formal procurement review and aligned to the final DPA, pricing model, support commitments, and offboarding rules before use.