Terms of Service — Draft

These proposed terms would govern [PRODUCT NAME] for customers and authorized users of [COMPANY LEGAL NAME]. They are not an operative agreement.

No clickwrap or terms-acceptance record exists. There is no acceptance checkbox, version record, timestamp, institutional-authority check, or order-form workflow.

[LEGAL REVIEW REQUIRED] Define the contracting customer, authorized users, acceptance method, authority to bind an institution, and [MINIMUM AGE] after the business model and jurisdictions are confirmed.

The implemented LMS supports account and course administration, enrollments, modules/pages, announcements, discussions, course files, assignments, student submissions, grades and feedback, calendars/activity views, quizzes, and deterministic auto-grading.

Attendance, external analytics, data exports, email delivery, password recovery, payments, subscriptions, refunds, production object storage, and AI recommendations are not implemented.

Final terms, product pages, and order documents must describe only enabled and tested production features, with demos or previews labelled clearly.

Administrators create accounts with a name, email address, and temporary password. Users must replace an administrator-set password before entering protected pages and then authenticate with email/password and an Auth.js JWT session cookie.

Self-registration, invitation email, forgot-password recovery, MFA, and account-sharing detection are absent.

Proposed user duties are to provide accurate information, keep credentials private, use only assigned access, and report suspected compromise to [SECURITY CONTACT].

The product accepts user-authored text, links, Markdown, discussions, quiz content, and uploaded files, so misuse and content risks must be addressed.

The separate Acceptable Use Policy contains proposed rules. It becomes enforceable only after valid approval and acceptance.

No abuse-report intake, safeguarding escalation, automated moderation, malware scan, or account-suspension workflow is implemented.

Users and staff can submit original work, course content, communications, grades, feedback, quiz material, and files. The application stores and displays that material to users authorized by role and course membership.

[LEGAL REVIEW REQUIRED] The final agreement must define ownership of institutional records, student work, teacher materials, and feedback, plus the limited operational license needed to host, process, secure, back up, and display content.

No data-export feature or documented export format exists.

Restrictive database relations preserve certain submission and quiz records and can prevent hard deletion of users, assignments, courses, or quizzes carrying academic history.

[LEGAL REVIEW REQUIRED] Define ownership, administrative access, export scope/formats, request authentication, academic-record exceptions, retrieval windows, and deletion timing.

Ownership or license rights in the software, designs, documentation, and branding must be verified for [COMPANY LEGAL NAME]. Final terms should grant only a limited right to use the service and address feedback, open-source software, copying, and reverse engineering under applicable law.

No payment processor, customer/order/subscription model, price enforcement, invoice, tax, renewal, cancellation, failed-payment, or refund workflow exists.

[LEGAL REVIEW REQUIRED] Add plans, prices, currency, taxes, billing cycles, renewal, cancellation, and provider terms only after they are approved and implemented. The Refund Policy intentionally promises no refund period.

No trial, freemium entitlement, conversion, expiry, or trial-data lifecycle exists.

If a trial is introduced, decide [TRIAL LENGTH], [FEATURE LIMITS], [CONVERSION], [NOTICE], [CANCELLATION], and [TRIAL DATA RETENTION] before advertising it.

No uptime monitoring, SLA, staffed support desk, maintenance schedule, service credits, backup targets, or disaster-recovery evidence is present in the repository.

Add [SUPPORT HOURS], [UPTIME COMMITMENT OR NONE], [MAINTENANCE], [RTO/RPO], and [REMEDIES] only after operations can measure and meet them.

[LEGAL REVIEW REQUIRED] Warranty terms, non-excludable rights, exclusions, indemnities, and [LIABILITY CAP] must be tailored to the verified operator, users, price, insurance, risks, and governing law. This draft supplies no numeric cap or blanket exclusion.

No account suspension/deactivation, customer termination, termination export, purge, or legal-hold workflow exists.

[LEGAL REVIEW REQUIRED] Define [TERM], [TERMINATION RIGHTS], [NOTICE/CURE], [SUSPENSION GROUNDS], [EXPORT WINDOW], [ACTIVE DELETE PERIOD], and [BACKUP OVERWRITE PERIOD], while preserving required academic records and student rights.

[LEGAL REVIEW REQUIRED] Insert [GOVERNING LAW], [COURTS OR ARBITRATION], [VENUE], [NOTICE ADDRESS], and any mandatory complaint route only after jurisdiction-specific advice. No country is assumed by this draft.

No terms-versioning, acceptance log, notification provider, or re-acceptance workflow exists.

Define [CHANGE NOTICE METHOD], [ADVANCE NOTICE PERIOD], effective-date rules, active paid-term treatment, and any right to terminate.

Current data handling and controls are summarized in the Privacy Policy and Data Protection Readiness page.

Those pages are evidence-labelled drafts, not contractual security promises or proof of legal compliance.

[LEGAL REVIEW REQUIRED] Counsel must draft assignment, severability, waiver, force majeure, entire agreement, document priority, notices, survival, and language-control clauses. Legal notices must identify [COMPANY LEGAL NAME], [REGISTRATION NUMBER], [LEGAL ADDRESS], [LEGAL EMAIL], and [PHONE IF REQUIRED].