mLearn Institutional Use Guide

For schools, universities, and tutoring centers
Version 1.3 — Effective Date: 2026-07-07

1. How Schools Use mLearn

mLearn is local-first software. Schools can deploy it with the control level that fits their environment:

1. Download the official app from our Releases
2. Choose local, self-hosted, or hosted cloud features according to your own policies and required consents
3. Keep local data on school-managed devices unless you deliberately enable a hosted cloud feature

The hosted Cloud LLM relay at mlearn-cloud.kikan.net is available only to users who are at least 18 years old, or the age of majority in their jurisdiction if higher. That age confirmation is asked only when a user tries to access the hosted Cloud LLM relay. Other deployment models, including school-managed local or self-hosted use, are the responsibility of the deploying organization.

1.1 Acceptance

By deploying the software for student use, you represent that you have authority to bind your institution and that you accept full data-controller responsibility under applicable law.

2. What You Need (Minimal)

2.1 Local AI Setup

Option A: Built-in AI (Simplest)

The app includes a built-in AI model that runs entirely offline. No installation, no server, no configuration. Works on Apple Silicon, modern Intel, and most Linux machines.

Option B: School Ollama Server

Install Ollama on one classroom machine. Load your preferred model (qwen3:4b, llama3, etc.). Students point their app to http://192.168.x.x:11434 in Settings. All inference happens inside the school network.

Option C: Per-Student Ollama

Each student installs Ollama on their own machine. Fully decentralized, no network dependency.

3. Current Hosted-Service Limits

The current hosted service does not provide school administration features. In this version:

• No built-in classroom roster or student user management
• No guardian-consent workflow
• No managed school dashboard yet
• Hosted Cloud LLM remains age-gated at access time
• No backend source code (the mlearn-cloud infrastructure is not open source)

Schools that need managed student administration should use local or self-hosted patterns until a dedicated dashboard exists.

4. Legal & Compliance Responsibilities

By deploying mLearn for students, you (the institution) assume the responsibilities that apply to your chosen deployment:

4.1 Student Data Protection

• In local-only mode, flashcards, settings, and AI conversations remain on student devices
• For self-hosted deployments, you operate the infrastructure you deploy
• For hosted cloud features, review the Privacy Policy for what the hosted service processes
• Comply with your jurisdiction's education and data protection laws
• Obtain necessary parental consent or provide required notifications

4.2 AI Safety & Safeguarding

• Enforce your own acceptable-use policy for student AI chat
• Monitor student use as your institution sees fit
• Provide crisis resources and human oversight
• The optional self-harm screening tool runs locally and can be disabled in Settings if your institution prefers its own safeguarding

4.3 Content & Copyright

• Ensure students have legal rights to any media they load (videos, manga, PDFs, subtitles)
• Enforce your school's device and software policies

4.4 Data Backup

The developer provides no school-managed backup, recovery, or data-loss prevention service in this version. You are responsible for implementing backup procedures for student flashcards, settings, and any other data stored on school devices or institution-managed infrastructure.

5. Liability

The developer of mLearn assumes no liability for institutional deployments. This includes:

• Student data on your devices
• AI outputs generated by local models
• Misuse of the software by students or staff
• Plugin-related security incidents
• Voice cloning or TTS use by your users

We provide the software under the Sustainable Use License v1.0 with no warranty. See the EULA for the full limitation of liability.

6. Summary

By using mLearn with students, you acknowledge that the developer is a software licensor only, not a service provider to your institution or students.

7. Questions?

If your institution has specific deployment needs or questions about local setup, you can reach the developer directly at [email protected].