Buy a Childcare App or EdTech Business: Subscription Evidence, Rights and Data Duties

Define who pays, who uses the service and what is earned

Separate adult childcare administration, parent communication, school software, student learning and child-directed features. Identify actual contracting customers, account holders, users, ages where relevant and jurisdictions. A childcare name does not alone determine the applicable privacy regime; a school contract is not automatic exemption evidence.

Reconcile signed subscriptions and actual delivered service with invoices, discounts, cancellations, credits, refunds, collections and deferred amounts. State how any MRR or ARR metric is defined and its period. An annual prepayment can carry future service duties and is not automatically achieved annual profit. Examine customer renewal, seat/license limits and actual usage under the proposed buyer arrangement. Distinguish existing records from forecasts and system-wide market growth.

Verify product ownership and permanent technical costs

Obtain actual code, curriculum/content, contractor, employee, trademark/domain, hosting, app-store and vendor documents. Have counsel and technical specialists verify ownership or licensed rights, required consents, dependencies and proposed buyer access using the rights register. Owning a company does not establish ownership of every library, teaching asset or dataset it uses.

Map permanent engineering, security, hosting, support, customer success and any necessary teaching/content work through the coverage worksheet. Budget actual payroll/contractors, infrastructure, payment/vendor fees, maintenance, releases and supported corrections. Seller unpaid development and deferred maintenance are costs to understand, not automatic earnings add-backs. Use the earnings guide for a consistent measure; no revenue-growth percentage or generic subscription multiple establishes value.

Review child/student data before disclosing or migrating it

FTC staff FAQs flag an April 2025 amended COPPA Rule and direct readers to the revised Rule; school-service questions discuss operator responsibilities and consent limits.

Have qualified privacy counsel review current governing requirements and actual users, purposes, notices, permissions, school agreements, vendors, retention/deletion and the proposed transaction. The reviewed FAQ is nonbinding staff guidance, not a complete current-Rule, FERPA or state-law compliance assessment. Do not assume the school takes every operator responsibility or that existing permission covers new uses.

FTC business guidance recommends understanding what personal information a business holds.

Create an approved data map and access plan before diligence. Use authorized aggregate/redacted evidence initially. Have responsible technical/legal parties test permitted access, secure handover, retention and deletion duties. A seller-provided login is separate from permission to copy or repurpose children’s records.

Fund service continuity and accepted acquisition duties

Identify actual customer renewal/assignment conditions, service levels, pending bugs, promised features, prepaid periods, credits and support obligations. Agree the responsible operator, funding, completion evidence and lawful collection rights through the delivery register. Obtain necessary customer/vendor/platform acceptance; a purchase agreement alone does not complete each migration or permit.

Test lower renewals, delayed collections and permanent replacement engineering costs in the cash-flow tool with explicit assumptions. Separate price, operating cash, required remediation, financing and a qualified tax assessment. Generic QSBS, opportunity-zone, asset-sale or liability-shield promises do not establish this buyer’s treatment. Proceed on supported actual rights, economics and funded service rather than an EdTech trend forecast or invented transaction outcomes.