Privacy, in plain words.

01 · Who operates Mochi

Mochi is a Root community bot operated by DevSung / Eula Org, based in South Africa. This policy covers Mochi’s economy, games, leveling, moderation, welcomes, fun commands and AI chat, as well as this policy website. Root’s own services are covered separately by Root’s Privacy Policy.

02 · Information Mochi uses

• Root account and community information: user identifiers, nicknames, community and channel identifiers and names, role memberships and permissions, and membership or join events. Member information returned by Root may include a profile-picture reference and join date; the current bot does not maintain a separate avatar-image collection.
• Game progress: wallet and bank balances, virtual currencies, XP and levels, inventory, daily streaks, cooldowns, game sessions and voluntarily created relationship records.
• Community features: selected welcome, leveling, moderation and update channels; welcome templates; moderation roles; slowmode, autorole and other settings; and update-delivery status.
• Moderation and social records: warning reasons, moderator identifiers and timestamps, timeout and permission-restoration records, a bounded action log, AFK messages, marriage proposals, poll questions, choices and votes.
• Message processing: Mochi receives accessible message content and metadata to recognize commands, answer addressed AI requests, award XP and enforce moderation. Duplicate-message protection stores recent message IDs. XP abuse prevention stores a hash of a member’s latest eligible text and timing information. The purge fallback keeps recent message IDs in memory, not a permanent transcript.

Mochi automatically creates a game account when a member first interacts in an accessible community channel. No separate email, phone number, payment card or real-world identity field is required by the bot. Users may nevertheless include personal information in messages or commands.

03 · Why the information is used

Information is used to operate requested commands, preserve progress, calculate leaderboards, run games and polls, send configured welcomes and level announcements, perform authorized moderation, prevent duplicate rewards and abuse, provide AI replies and diagnose operational problems. Mochi currencies are virtual game points, not money or financial accounts.

Mochi does not sell user data or use it for advertising. The bot code does not use community messages to train its own AI model.

04 · AI and external services

AI chat is available by default. A message starting with mochi, or the ~mochi command, requests an AI response. This sends the text of that request, a limited recent conversation context, bot instructions and the requester’s own account summary to the configured Malvin AI service. The default endpoint is hosted at api.malvin.gleeze.com; operators may configure another HTTPS endpoint.

The summary can include your nickname, balances, inventory, XP, streak and cooldowns. Relevant setup questions can also include the community name and whether the requester has administrator or moderator access. Mochi does not deliberately attach other members’ account records, private warning logs or server credentials to AI prompts. Information you put into your request can still be sent, including information about other people.

Avoid AI chat if you do not want this transfer. Standard economy commands do not need the AI provider. AI output is automated and can be inaccurate. The provider receives requests on its own infrastructure; its retention, processing locations and possible downstream providers are not controlled or verified by Mochi. Mochi’s local conversation limits do not guarantee deletion from that provider.

Fun commands: reaction lookups use Gifukai at api.gifukai.com, and meme lookups use meme-api.com. The current code requests an action or meme feed without deliberately adding Root usernames, identifiers or message text to those lookup requests. Returned media links may be displayed or fetched by Root, your client or the media host, under their own practices.

Root hosts production bot instances and their datastores. Development or testing instances can run on infrastructure controlled by the operator. Third-party processing may occur outside your country. API credentials stay in the server environment and are not intentionally sent in chat responses.

05 · Who can see information

Replies, profiles, balances, leaderboards, polls, AFK notices and social actions may be visible to members who can access the channel where they are posted. Do not treat bot commands or AI replies in a community channel as private messages.

Community owners and authorized administrators or moderators can use the management commands permitted to their role. The bot developer has owner-level bot controls for support and operation. Moderation logs appear in the configured channel, so community administrators should restrict that channel appropriately. Information may also be processed by Root and the external services described above, or disclosed when legally required.

Each installed community has its own bot instance and game progress. This Mochi version does not link progress to WhatsApp, Discord or other communities.

06 · Storage and retention

Game progress and operational settings are persistent so they survive a restart. They are retained while needed to provide the community’s bot features, subject to deletion requests and Root’s platform controls.

Duplicate protection is limited to the most recent 2,500 message IDs per community. The action log keeps up to 200 entries, and warning lists up to 50 entries per member; these limits are counts, not fixed time periods. Gameplay, poll and social records may persist until their implemented cleanup runs or they are removed.

AI context is held in process memory and is reused only within 15 minutes of activity for the same requester and channel. Inactive entries are ignored for future context; the underlying cached entries can remain in memory until overwritten, evicted from the bounded cache or the process restarts. Purge fallback IDs and other temporary caches are also lost on restart.

The bot does not intentionally archive a full community chat transcript. Posted bot messages remain part of Root’s channel history until removed there. Root controls hosted backups and platform-level retention; deleting a live bot record does not necessarily immediately erase backups, existing channel messages or records held by an external AI service.

07 · Your choices

You can avoid addressed AI requests, choose not to use optional social features, ask community administrators about their bot configuration, and request access, correction or deletion of information associated with your Mochi account. Applicable privacy rights depend on your location. Contact us using the details below; verification may be needed to avoid changing someone else’s records.

Administrators can pause bot features or remove the bot from a community. Root handles its own account data and platform history; contact Root for those requests. Root’s age and eligibility requirements apply. Do not provide sensitive personal information through Mochi.

08 · This policy website

This page has no sign-in, advertising, analytics scripts, tracking pixels or bot-account forms added by Mochi. Its hosting provider may process normal technical request information, such as IP address and browser metadata, to deliver and protect the website. Opening an external link is subject to that service’s privacy practices.

09 · Policy changes

We will update this page and its last-updated date when data practices change. Material changes may also be announced through Mochi’s update logs or the community. This policy describes the current implementation; future features that change data use will need an updated notice.

10 · Contact and deletion requests

For a privacy question or a request to access, correct or delete Mochi data, contact DevSung / Eula Org:

Requests are reviewed by the operator. There is currently no self-service account-deletion command. Community administrators can help identify the relevant installation; requests about Root-hosted records and backups may require Root’s assistance.