Information Tides Accesses
Tides accesses Discord API data needed to provide features that server owners and authorized staff enable or use. Depending on the server configuration, this may include:
- Server, channel, role, emoji, invite, scheduled event, moderation, and permission information.
- User and member information such as Discord user ID, username, display name, avatar, roles, join date, timeout status, boost status, and server membership events.
- Message data such as message content, attachments, embeds, author, channel, timestamps, edits, deletions, reactions, and poll-related data when needed for configured features.
- Voice state information such as joining, leaving, or moving voice channels, used for music and voice activity features.
- Discord OAuth profile information for dashboard login, such as user ID, username, avatar, and guild list information needed to verify dashboard access.
How Tides Uses Information
Tides uses Discord data only to provide bot and dashboard functionality requested or configured by server owners, staff, or users. Uses include:
- Moderation commands, moderation cases, punishment logs, report handling, appeal handling, role restrictions, and timed moderation actions.
- Automod checks for blocked words, links, invites, spam, duplicate messages, excessive caps, attachments, message lines, and configured custom conditions.
- Message, member, moderation, voice, server, and audit-style logs configured by server staff.
- Welcome messages, leave messages, join roles, role messages, Membership Screening follow-up, role persistence, and role connection automation.
- Tickets, ticket transcripts, ticket inactivity handling, and optional transcript attachment storage.
- Giveaways, reaction roles, custom commands, templates, sticky messages, AFK, leveling, leaderboards, public server stats, and music commands.
- Dashboard authentication, permission checks, configuration editing, and displaying server configuration to authorized users.
Message Content
Tides may access message content when required for configured server features, including prefix commands, automod, logging, deleted or edited message review, custom commands, templates, leveling, tickets, and transcripts. Tides does not use message content for advertising, profiling, data brokerage, or training artificial intelligence or machine learning models.
Member Data
Tides may access member data and member events to support welcomes, join roles, screening completion, moderation eligibility, role changes, role automation, join and leave logs, persistent moderation roles, and staff tools that need current member state. Tides does not request the Discord Presence privileged intent and does not track individual online/offline presence status.
Stored Data
Tides stores only the data needed for enabled features. Stored data may include:
- Guild configuration, command settings, automod settings, template settings, logging settings, ticket settings, and appeal settings.
- Moderation cases, notes, reports, appeal submissions, appeal messages, role persistence records, pending timed actions, and giveaway records.
- Leveling data such as user IDs, XP, voice XP, message counts, voice time, usernames, and display names.
- Ticket records and ticket transcripts when transcript features are enabled by server staff.
- Dashboard session records for authenticated dashboard users.
Deleted-message cache, when enabled by server staff, is stored in memory only, is limited per server, and expires after 30 minutes.
Data Sharing
Tides does not sell Discord API data and does not share it with advertisers, data brokers, or unrelated third parties. Data may be shared only as needed to operate Tides, comply with law, respond to Discord platform requirements, or provide features explicitly requested by users or server staff.
Some Tides features interact with third-party services when configured, such as music sources, social notification feeds, hosting providers, database hosting, or Discord itself. These services receive only the information needed for that feature to work.
Retention
Different data is kept for different lengths of time depending on the feature:
- Server configuration is kept while Tides is used in the server or until it is deleted or replaced.
- Moderation cases, reports, notes, appeal records, role persistence, leveling records, giveaways, tickets, and transcripts are kept as long as needed for server management, accountability, or configured feature history.
- Dashboard sessions expire automatically.
- In-memory deleted-message cache expires after 30 minutes.
Server owners or authorized administrators may request deletion of server data when it is no longer needed.
Security
Tides is hosted on private server infrastructure. Bot tokens, client secrets, database credentials, and API secrets are stored in server-side environment configuration and are not intentionally exposed publicly. Dashboard access uses Discord OAuth sessions and server permission checks. Access to production infrastructure and stored data is limited to the bot owner/operator and authorized server staff where applicable.
User Choices and Data Requests
Server administrators can configure or disable Tides features such as logging, automod, tickets, transcripts, leveling, reports, templates, and join roles. Users or server owners may request access, correction, or deletion of data associated with them where appropriate and technically possible.
To make a request: Join the Tides support server and open a support ticket, or contact the Tides bot owner.
Children
Tides is intended for Discord users and servers that comply with Discord's Terms of Service, including Discord's age requirements. Tides is not directed to children under the minimum age required to use Discord.
Changes
This policy may be updated as Tides changes. The effective date above will be updated when material changes are made.