MahanuMahanu legal & trust documents
Pre-launch draft. These documents describe the intended hosted service; they are not effective until the operator, contact details, applicable jurisdictions, and effective date are completed and counsel approves them. They do not replace legal advice.
Want the plain-language version? Start with the FAQ. It answers what's public, what you own, how kids and privacy modes work, and how the assistant and sponsors are bounded — and links back here for the detail. The documents below are the binding, versioned sources: regulators and the Terms require them to stand on their own, so the FAQ summarizes them rather than replacing them. Guides never restate a legal rule; they link to it.
The public set
| Canonical document | What it governs |
|---|---|
| Terms of Service | The contract for the hosted service, accounts, projects, availability, and termination. |
| Privacy Notice | Personal-data categories, purposes, recipients, rights, and international processing. |
| Subprocessor Register | The providers that process hosted-service data for Mahanu. |
| Acceptable Use Policy | The binding safety floor for hosted-service use and public listing. |
| Bot & Automation Policy | Bot accounts, third-party bot operators, and the required Mahanu conduct bot. |
| Guardian Addendum | A guardian’s additional duties and controls for a supervised account. |
| Reporting & Appeals | How to report public material or a policy breach, and how decisions are reviewed. |
| Retention & Deletion | The retention schedule, account deletion, backups, and legal holds. |
| Copyright & IP Policy | Content rights, publication permissions, and copyright notices. |
| Support without surveillance | The canonical product policy for the future Support & Resources directory and grants. |
Authority and versioning
If the public documents conflict, the Terms govern the hosted-service contract; the Privacy Notice governs personal-data processing; and the Acceptable Use Policy governs conduct and enforcement. The other documents govern their named subject. Product guides never silently amend them.
Each effective document must carry an effective date, a version, a plain-language change summary, and a durable archived copy. A material change requires advance notice and, where law requires it, renewed consent. The final footer must identify:
[Mahanu Operator legal name], registered address, and contact;[email protected],[email protected], and[email protected]contact routes;- applicable governing law, courts, and any required EU/UK representative or data-protection contact; and
- the supported launch jurisdictions.