The Contracts Every Edtech Company Needs (2026 Checklist)

An edtech company is a software and content business that often serves children and schools, which adds a layer of sensitive legal duty on top of the usual startup contracts. The risks cluster around three things: who owns the courses and content, how children's data is handled, and the terms on which schools and institutions buy. The contracts below cover users, content, data, and the business. Use this checklist, and treat the children's-data items as the ones that carry the heaviest penalties if ignored. ## User-facing contracts Terms of use (user agreement). The binding terms for learners and, where relevant, parents, covering the service, acceptable use, fees, and liability limits. Common gap: terms that do not address accounts used by or on behalf of children. Privacy policy and data processing agreement (DPA), with children's-data terms. Set out how you collect and use personal data, with specific care for minors. Common gap: treating children's data like adult data, which breaches children's-privacy rules such as COPPA in the US, the UK's age-appropriate design expectations, and India's DPDP framework. Institutional or B2B school agreement. For selling to schools, universities, and districts, covering data ownership, security, service levels, and who controls student data. Common gap: unclear whether the school or the company is the data controller for student records. ## Content contracts Content licensing agreement. For course material, video, and media you license in or out, setting the scope, term, and territory of the licence. Common gap: using third-party content without a clear licence for your actual use. Instructor or content-creator agreement with IP terms. For the teachers and creators who build your courses, setting payment, revenue share, and whether the company owns or licenses the content. Common gap: no clear IP terms, so it is unclear whether you can keep selling a course after a creator leaves. ## Business, team, and partners Employment and contractor agreements with IP assignment. Ensure the company owns the platform code and product the team creates. Common gap: missing IP assignment, which investors flag in diligence. Reseller or channel-partner agreement. For partners who sell your product into schools or regions, setting territory, pricing, and data duties. Common gap: letting a partner handle student data with no data terms. Cloud and SaaS vendor agreements. For the infrastructure you run on, covering uptime, security, and data location. Common gap: no data-residency terms where a market or a school requires local storage. Non-disclosure agreement (NDA). For partners, investors, and pilot schools before sharing sensitive details. Common gap: running a school pilot with no confidentiality or data agreement. Investor documents. Convertible instruments, SAFEs, or share subscription and shareholders' agreements for funding. Common gap: stacking instruments without tracking conversion and dilution. ## Jurisdiction notes This is general information, not legal advice. The exact documents you need, and how each one is enforced, depend on where you operate. Stamp duty, registration, the enforceability of non-compete and non-solicit clauses, and the validity of electronic signatures all vary between the United States, the United Kingdom, and India, and often between states within them. Check your local rules or ask a qualified lawyer before you rely on any template. Children's data is the area that varies most and penalises mistakes hardest. The US has specific children's-privacy rules such as COPPA, the UK applies an age-appropriate design standard, and India's DPDP framework sets its own rules for processing children's data. Accessibility standards for educational products and the rules on selling to public institutions also differ by country. Check the children's-data and procurement rules in every market you sell into. ## Where to start Because you serve learners who are often children, children's-data terms come first: a privacy policy and data processing agreement that meet rules such as COPPA in the US, the UK's age-appropriate design standard, and India's DPDP framework. Getting this wrong carries the heaviest penalties an edtech faces. Next, settle content ownership with every instructor and creator, so you can keep selling a course after they leave, and make sure you have proper licences for any third-party material you use. For school and institutional sales, state plainly who controls student data. Keep full IP assignment from your team for investor diligence. Because children's-privacy, accessibility, and public-procurement rules all vary by country and change over time, review these before entering each new market. ## Keeping these contracts in one place Most edtech companies keep their contracts scattered across email threads, shared drives, and spreadsheets. The signed PDF sits in one inbox, the renewal date lives in someone's calendar, and the clause that was negotiated hard last year is forgotten by the time it matters. The documents on this list only protect you if you can find them, read them, and act on their dates. Drafting, review, e-signing and e-stamping, tracking, and governance of contracts like these can live in one AI workspace tuned to how your own company writes and negotiates, built on Claude, with public per-seat pricing and a 7-day trial. Adira is one such workspace, India-first and global-capable; it reads a document and flags the risky positions, edits clauses in plain English, and keeps every version and date on a timeline. Its Command Centre, a single view of upcoming renewals, obligations, and overall risk, is on the roadmap rather than live today. The point is not the tool. The point is that a reader who finishes this list thinking "our contracts really are scattered" has already found the real gap.