Skip to content

Mappy2 Terms of Service

Last updated: June 16, 2026

Mappy2 is a private Discord bot and web administration tool operated by Mysticdrew for use within the JourneyMap Discord server. It is used to support 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.

By using Mappy2 features in the JourneyMap Discord server, submitting a ticket handled by Mappy2, or using the Mappy2 web dashboard as authorized JourneyMap staff, you agree to these Terms.

Operator and Contact

Mappy2 is operated by Mysticdrew. For questions, support, policy requests, or data requests, contact Mysticdrew in the JourneyMap Discord server.

Discord Terms Still Apply

Mappy2 is built for Discord and uses Discord APIs. Your use of Mappy2 must comply with Discord's Terms of Service, Community Guidelines, Developer Terms, Developer Policy, and the rules of the JourneyMap Discord server.

These Terms apply only to Mappy2. They do not replace Discord's terms, GitHub's terms, or JourneyMap Discord server rules.

Authorized Use

Mappy2 is intended only for use in the JourneyMap Discord server and related JourneyMap administration workflows.

JourneyMap Discord members may interact with Mappy2 through server features such as commands, moderation workflows, ticket intake, and support processes made available in the server.

Only authorized JourneyMap staff may access the Mappy2 web dashboard, configure Mappy2, manage tickets, manage commands, use administrative features, or trigger GitHub integration features.

You may not invite, copy, configure, or use Mappy2 for another Discord server unless Mysticdrew gives explicit permission.

JourneyMap Staff Responsibility

Authorized JourneyMap staff are responsible for using Mappy2 appropriately. This includes:

  • Choosing which JourneyMap Discord channels, roles, logs, ticket panels, commands, and GitHub repositories Mappy2 uses.
  • Making sure Mappy2 ticket questions and support workflows request only information that is useful for JourneyMap support or moderation.
  • Avoiding collection of unnecessary sensitive personal information.
  • Using GitHub tokens and other credentials only when needed and with the least access required.
  • Managing who has access to the Mappy2 web dashboard and Discord channels where Mappy2 posts logs or tickets.

Acceptable Use

You may use Mappy2 only for legitimate JourneyMap Discord community management, support, moderation, and administration.

You may not use Mappy2 to:

  • Break Discord's rules, GitHub's rules, or JourneyMap Discord server rules.
  • Harass, threaten, abuse, or target people.
  • Send spam, phishing content, malware, deceptive links, or other harmful content.
  • Collect passwords, payment details, government identifiers, or other highly sensitive information.
  • Interfere with Mappy2, Discord, GitHub, or other connected services.
  • Attempt to access dashboard sections, server data, support tickets, credentials, or moderation records you are not authorized to access.
  • Evade moderation actions, security controls, rate limits, or permission checks.

Moderation and Ticket Actions

Depending on JourneyMap Discord configuration and staff actions, Mappy2 may delete messages, sanitize suspicious links, apply timeouts or mute roles, post moderation logs, create private ticket intake channels, create forum ticket threads, and create GitHub issues from ticket content.

These actions are based on bot configuration, Discord permissions, staff actions, and automated moderation rules. JourneyMap staff remain responsible for reviewing and managing the community.

GitHub Integration

If GitHub integration is configured, authorized JourneyMap staff may use Mappy2 to create GitHub issues from Discord ticket threads. Ticket answers, attachment links, Discord thread links, ticket category labels, and related information may be sent to the configured GitHub repository when that action is used.

JourneyMap staff are responsible for configuring the correct repository, using appropriate GitHub tokens, and making sure ticket content is suitable for the destination GitHub repository.

Availability and Changes

Mappy2 is private JourneyMap infrastructure. Features may change, break, be unavailable, or be removed at any time. Mappy2 access may be limited, disabled, or changed if it is misused, creates security risk, violates these Terms, or can no longer be operated safely.

No Warranty

Mappy2 is provided as-is and without warranties of any kind. Mysticdrew does not guarantee that Mappy2 will be uninterrupted, error-free, secure, or suitable for a particular purpose.

To the fullest extent allowed by law, Mysticdrew is not responsible for indirect, incidental, special, consequential, or punitive damages related to Mappy2.

Policy Changes

These Terms may be updated from time to time. Continued use of Mappy2 after changes are posted means you accept the updated Terms.

Questions

For questions about these Terms, contact Mysticdrew in the JourneyMap Discord server.