Terms of Service & Privacy Policy

Last Updated: 15. April 2025

We may update our Terms of Service or Privacy Policy from time to time. Please check this page regularly for the latest information.

1. Terms of Service

By using SeanBot (the "Bot"), you agree to comply with Discord's Terms of Service and all applicable laws. Your continued use signifies acceptance of these Terms.

1.1 Prohibited Use

You agree not to use the Bot for any purpose that violates these Terms or applicable law. Prohibited uses include:

  • Spamming or Commercial Solicitation
  • Abusive behavior, harassment, or hate speech directed at any user
  • Illegal activities of any kind
  • Any actions that disrupt the Bot's functionality or interfere with the Discord platform

1.2 Indemnification

You agree to indemnify, defend, and hold harmless SeanBot and its developers, agents, and affiliates from and against any and all claims, damages, liabilities, losses, costs, or expenses (including reasonable attorneys' fees) arising out of or related to your use of the Bot, your violation of these Terms, or your violation of any third-party rights.

1.3 Disclaimer of Warranties and Limitation of Liability

THE BOT IS PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS, WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED. We do not guarantee uptime, performance, or error-free operation. Features may change or be removed without prior notice.

IN NO EVENT SHALL SEANBOT OR ITS DEVELOPERS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, loss of profits, data, use, or goodwill, resulting from your use of, or inability to use, the Bot. Your use of the Bot is entirely at your own risk.

1.4 Termination and Enforcement

We reserve the right to restrict or terminate your access to the Bot, or remove the Bot from any server, at any time, without prior notice or liability, if misuse or violation of these terms is detected.

1.5 Intellectual Property and License

Ownership. All rights, titles, and interests in and to the Bot, including its source code, design, features, and content, are and will remain the exclusive property of SeanBot and its developers. You may not copy, modify, distribute, sell, or lease any part of the Bot or its included software, nor may you reverse-engineer or attempt to extract the source code.

User Content License. By submitting content to the Bot, such as commands, messages, appeal or report text, ticket content, or saved profile data, you grant SeanBot a worldwide, non-exclusive, royalty-free license to use, reproduce, and display that content solely as necessary to operate, maintain, and improve the Bot for that server, including processing commands, generating logs or transcripts where enabled, and providing the feature you used. This license ends when the data is no longer needed for that purpose or is deleted under this policy, and does not give SeanBot any right to use your content for unrelated purposes.

1.6 Service Suspension and Modification

We reserve the right, at any time and without liability, to modify, suspend, or discontinue the Bot, any of its features, or the service entirely, with or without notice. We are not liable to you or any third party for any exercise of this right, including for any loss of data or stored content.

1.7 Feedback and Idea Submission

Any feedback, comments, or suggestions ("Feedback") you provide to SeanBot or its developers is given voluntarily and will be treated as non-confidential. You grant us an irrevocable, perpetual, worldwide, royalty-free license to use, incorporate, and implement any Feedback without any obligation of compensation or attribution to you.

1.8 Severability and Waiver

Severability. If any provision of these Terms is held to be invalid or unenforceable by a court of law, that provision will be modified to the minimum extent necessary to make it valid and enforceable, and the remaining provisions will remain in full force and effect.

Waiver. Our failure to enforce any right or provision of these Terms will not be considered a waiver of those rights.

1.9 Relationship to Discord and Wizard101

SeanBot is an independent, third-party application developed solely by Mek. The Bot is not affiliated with, endorsed, or sponsored by Discord, Inc. Discord is not responsible for the Bot's content, operation, or any liability arising from your use of the Bot. All rights and responsibilities related to the Discord platform itself remain governed by Discord's own terms and policies.

Wizard101 features (such as the Wizard101 tools, guild roster, and raid or team-up features) are unofficial fan tools. Wizard101 is a game published by KingsIsle Entertainment. SeanBot is not affiliated with, endorsed, sponsored, or approved by KingsIsle Entertainment or any other owner of Wizard101, and the game's name, artwork, and game data belong to their respective owners. Wizard101 data shown by the Bot may be incomplete, inaccurate, or out of date. The Bot is not responsible for the Wizard101 game, its content or updates, its terms of service or privacy policy, or any action taken against your game account. Your use of Wizard101 features is at your own risk, and you remain bound by KingsIsle's own terms and policies.

Dependency on Discord and other services

The Bot depends on the Discord API and on the permissions granted to it by the server owners who add it and by the users who interact with it. The Bot also depends on third-party hosting, database, and other service providers needed to run it. If Discord changes its API, permissions model, or rules, or if a server changes its settings, or if a third-party service is unavailable, the Bot may lose features, behave differently, or be temporarily unable to function in part or in whole. We are not responsible for changes or interruptions caused by those third parties.

1.10 Copyright Infringement / DMCA Notice

If you believe any content made available through the Bot infringes upon your copyright, you may submit a written notice to us. The notice must comply with applicable law and include (i) identification of the copyrighted work claimed to have been infringed, (ii) identification of the material that is claimed to be infringing and where it is located on Discord (e.g., server/message ID), and (iii) your contact information. Upon receipt of a valid notice, we will take appropriate action, which may include removing or disabling access to the allegedly infringing content. For submissions, please use the formal contact method provided in the Privacy Policy.

1.11 Governing Law and Venue

These Terms and any action related thereto will be governed by the laws of Norway, without regard to its conflict of laws provisions. The exclusive jurisdiction and venue for any action or proceeding arising out of or related to these Terms shall be the courts located in Norway. You and SeanBot each waive any objection to jurisdiction and venue in such courts.

1.12 Experimental and Beta Features

From time to time, we may offer certain features of the Bot in an experimental, "Beta Features". Beta Features are provided "as is" and "as available" and may contain bugs, errors, or inaccuracies. Using Beta Features is entirely voluntary and at your own risk. We make no guarantees regarding the performance, functionality, or continuation of any Beta Features, and they may be changed or withdrawn at any time without notice or liability.

2. Privacy Policy

SeanBot is an application running on the Discord platform, so using the Bot also puts you under Discord's Terms of Service and Privacy Policy, which are not ours. This policy covers what we collect, how we use it, and what you can ask us to do about it.

Our role for server data

For data that belongs to a particular Discord server, SeanBot generally acts as a service provider for that server. The server owner and staff decide which features to enable, how to configure them, and where logs or transcripts are sent. SeanBot provides the tools and processes the data needed to run those features, but it does not control the server itself and does not decide how the server uses its own data.

What we do not collect

We do not ask for or store your Discord password or authentication tokens. We do not keep your full message history across servers. We do not sell personal data. We do not use your content or activity data for advertising or unrelated promotional purposes. We do not build cross-server profiles about individual members from unrelated servers.

In short

  • This policy covers SeanBot the Discord bot and the SeanBot website.
  • We collect different things depending on which features a server turns on.
  • Server staff control which features are enabled in their own server.
  • We do not sell personal data.

Security

We use reasonable administrative, technical, and physical measures to protect the data we hold against unauthorized access, loss, and misuse. We do not represent or warrant that our measures will prevent every breach, leak, or unauthorized access. If we become aware of a security incident that may affect personal data, we will take reasonable steps to address it and will notify affected users or server owners where appropriate and where required by law.

Legal requests and disclosures

We may disclose data where we are required to do so by law, where necessary to protect the safety of people or servers, or where another legally valid request applies. We do not publish or advertise involuntary disclosures, and any such disclosure is limited to what is necessary for the purpose at issue.

2.1 What we collect

We collect only what a feature needs to work. Most of it comes from the Discord API or from the server's own settings, and the rest is what you type into a feature. Nothing is collected just because the API happens to make it available.

Identity data from Discord

When a feature needs it, we may use Discord identity information such as a username, numerical Discord ID, avatar hash, or public flags. We do not take more identity data than the feature needs.

Server and configuration data

Each server that adds SeanBot has its own settings. We store the server IDs, channel IDs, role IDs, and other configuration needed to run the features that server enabled. That can include things like log channel choices, ticket settings, report settings, timezone settings, and server-specific module settings.

What you tell the bot

Some features rely on information you submit directly. Examples include timezone choices, event sign-ups, ticket text, report text, appeal text, and Wizard101 profile details such as wizard names, schools, and levels. We store that information only for the server and feature it was submitted to.

Activity summaries and timestamps

Some features keep usage information for a server. This is usually metadata or summaries rather than the full text of everything said in the server. Examples include last-message timestamps, voice or message activity summaries, emoji usage summaries, server counters, and command or interaction records used by that server.

Short-lived deletion and edit snapshots

If a server enables message-deletion or edit logging, and where message content storage is allowed by the Bot's configuration, we may keep a short-lived snapshot of recently deleted messages so the log can reconstruct what was removed. Depending on that server's settings, a snapshot may include a truncated version of the message text, embed titles or descriptions, attachment links, and counts of mentions, role mentions, or @everyone/@here usage. We do not store your full message history across the server. These snapshots are not kept for every server or every feature, they expire automatically after a configured retention period, and they are removed once they have been used for a deletion log.

Website and operational data

Running the site and the Bot can produce technical data such as connection records, usage counts and error reports. Where that happens it is limited to what operation, debugging, security and service improvement need, and it is handled under the same approach as everything else in this policy. It is not used to build profiles about you beyond what the related feature requires. Cookies and other browser storage are covered separately in the Cookie Policy.

Third-party services

The Bot and the SeanBot website run on third-party services: Discord itself, plus hosting, database, analytics or error-reporting, and security providers. Those providers collect and handle data under their own terms and privacy practices, which this policy does not cover, so using the Bot also puts you under theirs.

Retention. Different kinds of data are kept for different lengths of time, and the detail is in section 2.2 below.

2.2 Use of Data

Your data is used solely to operate, maintain, and improve the Bot's core features: answering user requests, running commands, managing events and tracking, saving preferences, and keeping a server safe from abuse. It is not used for advertising or unrelated promotion.

We do not sell your personal data. We may share limited data with Discord, our hosting, database, analytics, and security providers, authorized Server Administrators, and public authorities where required by law. These parties receive only the information necessary for their relevant purpose.

Data Retention. We retain data only for as long as necessary to provide the service or comply with legal obligations. Different kinds of data are retained differently:

  • Server configuration and feature data is generally kept for as long as the bot remains in that server, and may persist briefly after removal so that features such as moderation or ticket history remain usable to the server.
  • Snapshots used for deletion/edit logging are short-lived. They are stored only where a server has enabled that logging, and they expire automatically after a per-server retention period. They are also removed once they have been used for a deletion log.
  • User-specific data is generally deleted or de-linked when the bot is removed from the user's last shared server or upon a valid deletion request, subject to applicable legal exceptions and to data that a server has separately exported or stored through its own staff tools.
  • Anonymized and aggregated usage data may be retained longer for statistical analysis and service improvement.

Retention settings for some features are controlled at the server level. For example, a server may configure how long message-deletion snapshots are kept. Those server-level settings are separate from SeanBot’s own retention practices.

2.3 Your Privacy Rights

You may ask us to:

  • View your data: Request a copy of the personal data we hold about you.
  • Correct your data: Ask us to fix personal data that is inaccurate or incomplete.
  • Delete your data: Ask us to delete your personal data, subject to applicable legal exceptions.
  • Stop new server data collection: A Server Administrator may remove the Bot from their server to stop the collection of new Server Data and associated Usage Data for that server.
  • Make a complaint: Contact the Norwegian Data Protection Authority (Datatilsynet) or another relevant supervisory authority.

Requests are handled manually. We may ask you to verify that you control the relevant Discord account before completing a request, and response times depend on the request and the verification needed. Removing the Bot does not automatically delete data already stored.

For formal legal inquiries, please contact us via Discord DM: @energetic_starfish_67605.

2.4 Children's Privacy and Age Restriction

The Bot is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you are under the age of majority in your country, or if you are using the Bot on behalf of a server that includes members under the applicable age, you are responsible for ensuring that use of the Bot complies with Discord's rules and any applicable parental-consent requirements. If you believe we have inadvertently collected personal information from a child under 13, please contact us immediately via Discord DM and we will take reasonable steps to delete it.

2.5 What Server Staff Can See

SeanBot is configured, controlled, and observed by the administrators and staff of each individual Discord server that adds it. Those server staff members are not SeanBot owners or developers; they are the community running the server. When you join or interact with a server using SeanBot, that server's staff may be able to see some of your activity through the bot. What they can see depends on which features that server enabled, and where they chose to send logs.

Data visible to server staff through SeanBot

  • Moderation actions and warnings. If a server uses moderation, warnings, timeouts, kicks, bans, or related logging, staff can view warning history and moderation points for members of that server, along with the reason, timestamp, and staff member who issued each action. Those records are stored for that server, not across all servers you join.
  • Event, sign-up, and roster data. If you sign up for raids, events, polls, team-ups, or register a Wizard101 wizard, that server's staff can see the information you submitted through those features inside their server (for example your chosen name, school, level, or event sign-up).
  • Reports and ticket content. If you file a report, appeal, or support ticket in a server, the staff members with access to that review process may be able to read what you wrote, including any message content, attachments, or reason you provided. Ticket transcripts may be saved as HTML archives and shared with assigned staff or the ticket creator, depending on that server's settings.
  • Server activity, voice, and analytics. If a server enables activity, voice, emoji, or server statistics features, staff may see aggregated or per-member usage information for that server, such as message or voice participation, emoji usage trends, server counters, or last-message timestamps. These are typically summaries or timestamps rather than the full text of what you said.
  • Deleted and edited message logs. If a server turns on message-deletion or edit logging, SeanBot may keep a short-lived snapshot of recently deleted messages so it can reconstruct what was removed. Depending on that server's settings and the bot's configuration, those snapshots may include a truncated version of the message text, embed titles or descriptions, attachment links, and counts of mentions, role mentions, or @everyone/@here usage. They do not include your full message history across the server, they are not stored for every server or every feature, and they expire automatically after a configured retention period. They are also removed once they have been used for a deletion log.
  • Timezones and personal settings. If you set a timezone or similar personal preference in a server, staff with access to that server's configuration may see that setting as it exists in that server.

What server staff generally cannot see through SeanBot

  • Your activity in other servers. A server's staff can only see data that SeanBot recorded inside their own server. They do not get a view of your activity in other servers that also use SeanBot.
  • Your private DMs with the bot for public server features. Where a feature is meant to be public to a server, private bot DMs are not a hidden channel for staff to read. Server-specific data is tied to that server's configuration.
  • Your account credentials or Discord login. SeanBot never receives or stores your Discord password or authentication tokens. Server staff do not get those either.
  • More than the server enabled. If a server does not enable a feature, the related data is generally not collected for that server. Staff visibility is limited to the features and logging channels that server actually configured.

Important: Server owners and staff are responsible for the server they run. SeanBot provides the tools and logs; we do not control how a server's staff use, store, export, or share the data their own server generates. If a server enables transcript archives, moderation logs, or report reviews, those materials may be readable by the staff members with access to them, and may be exported or retained outside of SeanBot at that server's discretion. We are not responsible for misuse by server staff. If you are concerned about a specific server, the most direct remedy is to leave that server or ask its staff what they log and how long they keep it.

Nothing in these Terms or this Privacy Policy creates any right, obligation, or contract between you and the staff or owners of any individual server, or any promise by SeanBot about how a server will use the tools we provide. Disputes about a particular server's conduct are separate from any dispute with SeanBot.

3. General Provisions and Dispute Resolution

3.1 Dispute Resolution

Any disputes arising from these terms will first attempt to be resolved through good-faith negotiation. If a resolution cannot be reached, the parties agree to mediation or court jurisdiction.

3.2 Policy Modifications

We reserve the right to modify these Terms and Policies at any time. We will provide at least 30 days notice of material changes by updating the "Updated" date at the top of this page.

Your continued use of SeanBot after the effective date of the revised Terms signifies your acceptance of the changes.