Skip to content

Mappy2 Privacy Policy

Last updated: June 16, 2026

This Privacy Policy explains what data Mappy2 processes, why it is used, how it may be shared, and how to request deletion.

Mappy2 is a private Discord bot and web administration tool operated by Mysticdrew for use within the JourneyMap Discord server. It supports JourneyMap community management, moderation assistance, custom commands, ticket intake, support workflows, and optional GitHub issue creation.

Mappy2 is private JourneyMap infrastructure. It is not offered as a general-purpose bot platform or service for third-party Discord servers.

For privacy questions or data requests, contact Mysticdrew in the JourneyMap Discord server.

Data Mappy2 Processes

Mappy2 processes only the data needed to provide its JourneyMap Discord moderation, ticket, command, GitHub, and web dashboard features.

Discord Account and Login Data

When an authorized JourneyMap staff member logs in to the Mappy2 web dashboard with Discord OAuth, Mappy2 may process:

  • Discord user ID.
  • Discord username, display name, discriminator, avatar identifier, and related profile data returned by Discord.
  • Discord OAuth access token for the active web session.
  • Discord guild list and guild permission data returned by Discord so Mappy2 can determine dashboard access.

Mappy2 uses this login data for JourneyMap administration only. It is not used to provide bot management for third-party Discord servers.

JourneyMap Server and Configuration Data

Mappy2 may store configuration data for the JourneyMap Discord server, including:

  • Discord guild IDs.
  • Channel IDs, role IDs, message IDs, and thread IDs used by Mappy2 features.
  • Command names, command responses, embeds, and command settings created by authorized JourneyMap staff.
  • Moderation settings such as command prefix, moderation log channel, member log channel, muted role, spam protection settings, and markdown-link sanitization settings.
  • Ticket panel, category, question, validation, forum channel, intake channel, and log channel settings.
  • Mappy2 dashboard administrator records, dashboard permissions, and guild access records.
  • Optional GitHub repository settings and GitHub token data configured by authorized JourneyMap staff.

Moderation Data

When moderation features are enabled, Mappy2 may process message content and metadata in the JourneyMap Discord server to detect spam, sanitize links, delete messages, apply moderation actions, and post moderation logs.

Mappy2 may store moderation observation records such as:

  • Discord guild ID, user ID, channel ID, and message ID.
  • Message type.
  • Hashes or fingerprints derived from normalized message text, links, or attachments.
  • Whether a message contained a markdown-style link.
  • Moderation action records, reason codes, and action metadata.

Mappy2's spam observation records are intended for short-term spam detection and are automatically cleaned up after the configured retention window. The default retention window is about 6 hours.

Mappy2 may also post moderation log messages inside configured JourneyMap Discord channels. Those Discord messages are stored and controlled by Discord and by the JourneyMap Discord moderation process.

Ticket Data

When a user opens or completes a JourneyMap support ticket handled by Mappy2, Mappy2 may store:

  • Discord guild ID and user ID.
  • Ticket category and panel IDs.
  • Ticket status and progress.
  • Ticket question answers.
  • Attachment metadata and Discord attachment URLs included with ticket answers.
  • Intake channel IDs, prompt message IDs, forum channel IDs, forum thread IDs, and related Discord IDs.
  • GitHub issue URLs if a ticket is sent to GitHub.

Ticket answers may contain information that the user chooses to submit for JourneyMap support. Users should avoid submitting passwords, payment details, government identifiers, private keys, or other highly sensitive personal information.

Audit and Staff Activity Data

Mappy2 may store audit records for dashboard and administrative actions by authorized JourneyMap staff, including:

  • Acting Discord user ID.
  • Guild ID.
  • Action type.
  • Target type and target ID.
  • Action details needed for accountability and troubleshooting.

How Mappy2 Uses Data

Mappy2 uses data to:

  • Authenticate authorized JourneyMap staff through Discord.
  • Determine which dashboard sections a staff member may access.
  • Store and apply JourneyMap Discord bot configuration.
  • Run custom commands in the JourneyMap Discord server.
  • Detect spam and suspicious links.
  • Apply configured moderation actions.
  • Create, manage, and archive JourneyMap support ticket workflows.
  • Post moderation, ticket, member, and administrative logs where configured.
  • Create GitHub issues from ticket threads when authorized JourneyMap staff use that feature.
  • Troubleshoot, secure, maintain, and improve Mappy2.

Mappy2 does not sell personal data and does not use personal data for advertising.

Sharing and Third Parties

Mappy2 may share or transmit data in these cases:

  • Discord: Mappy2 uses Discord APIs and operates inside the JourneyMap Discord server. Messages, logs, tickets, roles, channels, threads, OAuth data, and other Discord data are also subject to Discord's own policies.
  • GitHub: If GitHub integration is configured and authorized JourneyMap staff create a GitHub issue from a ticket, Mappy2 sends selected ticket content, attachment links, labels, and Discord thread links to the configured GitHub repository.
  • Hosting and infrastructure providers: Mappy2 may run on hosting, database, logging, backup, or network infrastructure needed to operate the service.
  • Legal or safety reasons: Data may be disclosed when required by law, to protect users, to investigate misuse, or to protect Mappy2 and connected services.

Mappy2 does not sell Discord API data or share it with advertising networks or data brokers.

Retention

Retention depends on the type of data and how Mappy2 is used in the JourneyMap Discord server:

  • OAuth session data is kept for the active dashboard session and expires or is cleared when the user logs out or the session ends.
  • Cached Discord guild access data is short-lived and used to reduce repeated Discord API calls.
  • Spam observation records are automatically cleaned up after the configured retention window. The default is about 6 hours.
  • JourneyMap Discord configuration, custom commands, staff permissions, ticket configuration, ticket records, moderation events, and audit logs are kept while needed to operate Mappy2, support JourneyMap administration, or preserve moderation and support history.
  • Discord messages and logs posted by Mappy2 remain in Discord until deleted under the JourneyMap Discord moderation process.
  • GitHub issues created by Mappy2 remain in GitHub until deleted or changed in GitHub.

Data may be deleted earlier when it is no longer needed, when Mysticdrew or authorized JourneyMap staff request deletion, or when deletion is required by applicable law or platform policy.

Deletion Requests

To request deletion of Mappy2-stored data, contact Mysticdrew in the JourneyMap Discord server.

Please include enough information to find the relevant data, such as:

  • Your Discord user ID.
  • The ticket, command, moderation event, or dashboard record involved, if known.
  • The approximate date or channel involved, if known.

Some data may also exist in Discord channels, Discord logs, GitHub issues, backups, or other third-party systems. Mappy2 can only directly control data it stores or posts through accounts it operates. JourneyMap staff may need to delete Discord messages or GitHub content separately.

Security

Mappy2 uses access controls and Discord permissions to limit dashboard and bot actions to authorized JourneyMap staff. Dashboard access and Discord channel access should be granted only to trusted staff.

No system is perfectly secure. Do not submit passwords, payment details, private keys, government identifiers, or other highly sensitive personal information through Mappy2 tickets, commands, or configuration fields.

Children

Mappy2 is intended for use within Discord and depends on Discord accounts. Users must meet Discord's minimum age requirements and the JourneyMap Discord server rules.

Policy Changes

This Privacy Policy may be updated from time to time. Continued use of Mappy2 after changes are posted means the updated policy applies.

Contact

For questions, concerns, or data requests, contact Mysticdrew in the JourneyMap Discord server.