Candidate 2026-09-01 · Version 2026-09-01.1

Terms of Use

Service operator: NOT CONFIGURED — production blocked
Trade name: Adaptive Tutor
Mailing address: NOT CONFIGURED — production blocked
Privacy contact: admin@adaptivetutor.ai
Support contact: admin@adaptivetutor.ai

These candidate Terms govern proposed access to Adaptive Tutor's hosted service and distributed clients. The operator identity, launch jurisdictions, payment rules, and counsel approval are incomplete, so this draft must not be treated as effective production terms.

1. Authority and Eligibility

A person may create or use an account only when they have legal and organizational authority to do so. A child or student must use the service only with authorization and supervision appropriate to the learner. An educator must not assume that employment alone authorizes creation or management of a particular learner's account.

2. Child, Guardian, Educator, School, and Operator Responsibilities

Child or student

A child or student must not create or use an account unless a parent, guardian, school, or other legally authorized adult has approved the account and provides the supervision appropriate for the learner. The learner must use only their own account and follow classroom and household rules.

Parent or legal guardian

For direct-to-family use, the parent or legal guardian is responsible for authorizing the learner account, reviewing the notices presented for the child, providing any consent required for collection and use of the child's information, supervising use, and making access, correction, export, or deletion requests for the child.

Teacher or other educator

An educator may invite, manage, or view a learner only when the educator has documented authority from the school or the parent or guardian. A job title alone does not create authority. Educators must follow school policy and must not place information for an unauthorized learner in the service.

School or district

When a school or district contracts for or directs use of the service, it is responsible for defining authorized educational purposes, approving staff access, providing notices, obtaining consent when required, responding to education-record requests, and executing the applicable services agreement or data-processing addendum. The final allocation of controller, processor, school-official, and direct-notice duties must be stated in the signed agreement.

Service operator

The operator is responsible for limiting processing to the disclosed educational and operational purposes, applying role and tenant controls, supporting verified rights requests, maintaining security and deletion procedures, managing subprocessors, and notifying the responsible adult or school as required by the final agreement and applicable law.

3. Educational and AI Service

Adaptive Tutor provides educational practice, tutoring, curriculum assignment, progress tools, classroom workflows, and optional AI-generated material. It is not a substitute for professional legal, medical, mental-health, emergency, or safety advice.

Automated output can be incomplete, incorrect, biased, inappropriate, or unsuitable for a learner. An authorized adult should review important educational, grading, placement, health, safety, or factual decisions rather than relying on an automated response alone. Personal provider-key users remain subject to that provider's terms and charges.

4. Accounts and Security

Provide accurate registration and purchaser information and keep it current.
Protect credentials and do not share an account across unauthorized users.
Use only the learner, classroom, family, and school records you are authorized to access.
Notify support promptly about suspected compromise, unauthorized student access, unsafe output, or incorrect account relationships.

5. Acceptable Use

Do not use the service for unlawful, abusive, exploitative, sexual, violent, self-harm-promoting, deceptive, discriminatory, or fraudulent activity.
Do not attempt to bypass security, rate limits, authorization, learner-safety controls, payment controls, or model-provider restrictions.
Do not upload or disclose information about another person unless you have authority and an educational or operational need to do so.
Do not scrape, bulk-extract, resell, or use the hosted service to build a competing dataset or service in violation of law, privacy rights, or these terms.
Open-source license rights remain governed by the applicable license and are not reduced by this hosted-service acceptable-use rule.

6. Payment, Renewal, Cancellation, and Refunds

The generated public pricing catalog is currently informational and marked coming_soon. It displays the trial, monthly-plan, and recharge terms from the versioned catalog, but checkout is not active, no Stripe customer-charge activation has occurred, and no subscription or recharge purchase is being accepted. These candidate terms remain draft and unapproved.
The checkout screen or signed school order must identify the price, currency, taxes, billing interval, included usage, trial terms, and the purchaser before a charge is submitted.
A recurring subscription is proposed to renew automatically for the interval shown at checkout until it is cancelled. The purchaser must receive any renewal or price-change notice required for the purchaser's location and purchase channel.
A purchaser may cancel through the billing portal or support contact. The proposed default is that cancellation stops future renewals and access continues through the paid period, unless the checkout terms, school agreement, app store, or applicable law require another result.
The proposed refund rule is that fees are non-refundable after service is provided, except where the checkout offer promises a refund, the operator approves one, a duplicate or unauthorized charge is confirmed, or applicable law or an app-store rule requires one. The final refund window and escalation owner must be approved before launch.
If a trial converts to a paid plan, the conversion date and amount must be displayed before enrollment and included in the confirmation. A trial must be cancellable before conversion through the disclosed channel.
Failed payments may lead to a limited grace period and then suspension of paid features. Suspension must not silently delete learner records; the approved retention and export rules continue to apply.
School or district purchases may be governed by an order form, services agreement, DPA, purchase order, or negotiated cancellation terms. The signed agreement controls to the extent it expressly conflicts with the public terms.
Purchases made through an app store are billed, renewed, cancelled, and refunded through that store when its rules require. The product must link users to the correct store management flow and must not promise a refund the operator cannot issue.

7. App Stores and Distributed Applications

The owner must declare each Android, iOS, macOS, Windows, Linux, web, and school-managed distribution channel that will be used and identify which entity is the seller or merchant of record.
For each mobile app store, the submitted privacy nutrition label or data-safety form must match the canonical data inventory, AI/provider routing, account deletion flow, child-directed audience settings, tracking configuration, and SDK inventory.
Store-specific subscription disclosures, consent to recurring billing, account-management links, cancellation, refunds, restore-purchase behavior, family or school purchases, and account deletion rules must be reviewed before submitting a build.
Age rating, kids/family program participation, classroom or managed-device distribution, parental-gate requirements, external payment links, and sign-in requirements must be explicitly approved for each store.

8. Privacy and School Agreements

Use of the service is also governed by the policy version presented at acceptance and, for a school deployment, any signed order, services agreement, or data-processing addendum. The final agreement must state the parties' education-record and privacy responsibilities.

9. Open-Source Software, Branding, and Content

The Adaptive Tutor application source and the exact LexiSphere source revision pinned by each deployed browser release are offered under AGPL-3.0-only through the no-charge, same-origin Corresponding Source archive linked from the source page. The development repositories remain private and are not the public source-delivery mechanism. For covered software, the AGPL controls.

Permission granted by these Terms to access or use the hosted service does not apply to, or make revocable, rights granted under the AGPL. These Terms may separately govern hosted accounts and operations, trademarks and branding, non-software content, user content, school-provided material, and third-party material that is not covered by the AGPL.

10. Suspension, Termination, and Data After Cancellation

The operator may suspend access to protect learners or the service, respond to suspected unauthorized access, comply with law, investigate abuse, or address nonpayment. The final terms must define notice and appeal where appropriate.

Cancellation or suspension must not cause undocumented immediate deletion. Export and deletion requests remain subject to the approved privacy policy, retention schedule, school agreement, and any documented legal or safety hold.

11. Disclaimers, Liability, Disputes, and Governing Law

Warranty disclaimers, liability limits, indemnity, dispute process, governing law, venue, statutory consumer rights, school sovereign-immunity issues, and regional mandatory rights are intentionally not finalized in this candidate. The accountable owner must configure the real operator and launch jurisdictions, and qualified counsel must supply approved language before production release.

12. Changes and Contact

A material change requires a new version, regenerated client and web copies, review of renewed notice or acceptance obligations, and a new signed owner/counsel attestation. Billing, cancellation, refund, and account questions should use the support contact above; privacy requests should use the privacy contact.

Generated deterministically from config/legal/policy-source.json. Do not edit this copy directly. This engineering artifact is not legal advice.