Skip to main content
MANGKANOR
DocsInviteDiscordFeaturesDiscoveryLogin
Mang Kanor›Privacy Policy
MANG KANOR POLICIES

Privacy Policy

How Mang Kanor processes Discord information, ticket content and website requests.

Effective 17 October 2026Last updated 17 October 2026
On this page What this policy covers Information processed Why information is used AI and external service providers Who can access ticket information Storage and retention Your choices and requests Security Updates and questions Back to Mang Kanor ↗

01. What this policy covers

This policy explains information handled by the Mang Kanor Discord bot and its public website. Individual Discord communities also have their own staff, rules and retention practices. Mang Kanor is separate from Discord and is not responsible for Discord's independent privacy practices.

02. Information processed

Depending on which features you use, Mang Kanor may process Discord user IDs, server and channel IDs, display names, command inputs, configuration settings, profile or progression records, and ticket metadata.

When a ticket is opened and the AI feature is enabled with applicable consent, the bot may process the ticket's messages, attachments, supported images or GIFs, conversation history, and relevant summaries. This information is used to respond within the correct ticket and assist authorized staff.

Operational records may include request results, durations, errors and abuse warnings. The website offers optional Discord sign-in using the identify and guilds permissions. With your approval, Mang Kanor receives your Discord user ID, username, display name, avatar and list of servers you belong to for the private server picker. It checks whether the bot is present in those servers. The server picker does not provide access to a public ticket directory.

03. Why information is used

This information is used to operate requested commands, maintain game and profile progress, route support requests, generate ticket summaries, allow staff handoffs, diagnose failures and protect the service from misuse.

We do not describe personal conversations as public data, and public website visitors cannot look up support transcripts using a ticket number.

04. AI and external service providers

AI-assisted support may send necessary ticket excerpts and supported attachments to an external AI model provider to generate responses or visual observations. Image processing may involve fetching authorized Discord attachments. Provider systems may process that content under their own service terms.

Discord login uses a signed Secure, HttpOnly, SameSite=Lax session cookie lasting up to seven days, a temporary authorization cookie lasting ten minutes, and an encrypted HttpOnly guild access grant cookie lasting up to seven days. The encrypted grant contains limited Discord OAuth access and refresh credentials so the server picker can verify your guild list; these credentials are never exposed to website JavaScript or sent to the Mang Kanor bot. Logging out clears all three cookies.

Discord, hosting and database infrastructure providers may also handle information necessary to deliver the service. Mang Kanor's public website does not include advertising trackers or third-party analytics scripts in its current implementation.

05. Who can access ticket information

Ticket members and properly authorized server staff can access information made available in their own ticket channels. Closed-ticket transcript archives are intended for restricted staff channels. Server administrators manage staff roles, channel visibility and server-level permissions.

There is no public website transcript portal at this time. If Discord cannot deliver a member's closure DM, the bot should not report the transcript as delivered merely because a staff archive exists.

06. Storage and retention

Some server settings and feature records are stored in the bot's database. Opted-in ticket memory, warnings and ticket metadata may persist beyond a single session. Private transcripts can also be retained in the server's restricted Discord archive.

Retention is not identical for every record or Discord server. Aggregate ticket AI performance metrics are pruned after 30 days in the current implementation. Other ticket or profile records are not automatically deleted on the same 30-day schedule.

Server administrators control Discord channel and archive deletion where their permissions allow. Removal from a live channel does not necessarily remove an already saved staff transcript.

07. Your choices and requests

You can avoid sharing unnecessary personal information and ask server staff about access to or correction of your ticket content. Where the bot offers an AI consent or handoff workflow, your choice affects whether AI assistance continues within that ticket.

To request review, correction or removal of information under our control, contact the support team. We may need enough information to verify that you are the affected member or an authorized server administrator before acting. Deletion can be limited where data remains in Discord archives operated by others or must be retained for legitimate reasons.

08. Security

We use scoped server and ticket handling, permission checks and credential redaction safeguards to reduce accidental disclosure. No internet-connected system is completely risk-free. Please do not send login credentials, API tokens, payment details or other secrets to the bot.

09. Updates and questions

Service providers and Discord infrastructure may operate across different locations. This policy may change when features, integrations or data practices change. Updates will appear on this page with a new date.

To ask about this document or make a request, contact the Mang Kanor team through its official Discord support channel when available. If you are using Mang Kanor in another server, you can ask that server's administrators how to reach the bot team. Do not post passwords, tokens, identification documents, or private transcript contents in a public channel.

End of Privacy Policy.

Mang Kanor

© 2026. All Rights Reserved.

Terms of UsePrivacy PolicyCopyright Dispute PolicyCookie PolicyEnd User License Agreement