Rawr

Rawr Privacy Policy

Effective date: 20/08/2026 Last updated: 17/08/2026

Rawr is a Discord application that provides community utilities, message relaying, role and linked-role tools, entertainment features, and moderation tools. This policy explains what information Rawr accesses, how it is used, where it may be retained, and how to make a privacy or deletion request.

1. Who operates Rawr

Rawr is operated by Aiko IT Systems (as we will refer to as “we”, “us”, or “our”).

Privacy contact: privacy@aitsys.dev Support and abuse reports: support@aitsys.dev

Rawr is an independent application and is not operated or endorsed by Discord Inc. Discord processes information under its own Privacy Policy.

For personal data processed by Rawr for the purposes described in this policy, Aiko IT Systems acts as the data controller unless another role is required by applicable law or the circumstances of a specific processing activity.

2. Scope

This policy applies when you:

share a Discord server, channel, direct-message context, or other Discord space with Rawr;
invoke a Rawr command or interaction, press one of its buttons, or use one of its select menus;
authorize Rawr through Discord OAuth for a linked-role feature;
are the subject of a Rawr moderation, role-management, message-relay, or safety action; or
contact us for support, a report, or a privacy request.

Server administrators decide whether to install Rawr and which permissions and channels to make available to it. Some Rawr features are restricted to designated servers, channels, staff roles, application-team members, or the application owner.

3. Information Rawr accesses or processes

Rawr does not use a general-purpose application database in the reviewed codebase. It nevertheless processes Discord data in memory, stores limited operational logs on its host, uses Rawr’s first-party internal guild-blacklist service, and creates records or copies inside Discord. Discord-hosted messages and attachments are persistent data even when Rawr does not copy them to its own database.

3.1 Discord account and server-member information

Depending on the feature, Rawr may access:

Discord user, member, server, channel, role, message, interaction, and application IDs;
usernames, display names, nicknames, mentions, avatars, and server avatars;
server membership and role information, including booster roles, staff roles, gaming roles, and role selections;
public primary-server tag information exposed by Discord, including the tag, badge, and identity server ID;
Discord-provided member safety signals used by the configured community, such as the spammer flag, unusual direct-message activity indicator, and quarantined-username search signal;
communication-timeout state and information needed to perform a kick, ban, timeout, role change, nickname repair, voice restriction, or channel/server lock; and
voice-channel state to the extent needed to disconnect a member or apply a voice-channel restriction.

3.2 Messages, commands, reactions, and user-generated content

Rawr may transiently access message-object fields made available by Discord, including:

message text;
embeds, components, stickers, and reactions;
attachment names, descriptions, URLs, and file contents when a feature re-uploads an attachment;
author, channel, server, mention, reply, TTS, and message-flag information; and
command text and parameters supplied through prefix commands, slash commands, context-menu commands, buttons, select menus, and modals.

Rawr uses this information for the following concrete features:

recognizing configured prefix commands and designated content triggers;
responding when Rawr is mentioned or when a configured community phrase or event is detected;
relaying a message from a designated source channel to a designated destination channel, including its text, allowed mentions, stickers, and attachments;
cross-posting messages in configured announcement channels;
allowing authorized staff to send, reply with, edit, or delete a message through Rawr;
allowing authorized staff to inspect an existing Discord message in an ephemeral message viewer;
reaction-based moderation and interactive workflows; and
temporarily recording which members participated during a configured slow-mode event so Rawr can produce a damage report.

When Rawr relays, reposts, or sends content, the resulting copy is a new Discord message and may remain visible and retained by Discord until it is deleted. Deleting the source message does not necessarily delete a relayed or reposted copy.

Rawr does not use message content to train machine-learning or artificial-intelligence models, sell advertising, build marketing profiles, or create unrelated analytics.

Rawr may send direct messages in limited circumstances. Recurring automated direct messages are sent only to specifically configured users who have agreed to receive them. Rawr may also send direct messages for moderation, safety, or administrative purposes, such as notifying a member of a timeout, kick, ban, or other action. These messages are sent only to the affected member and are not used for advertising, marketing, or unrelated promotional communications.

3.3 Moderation and safety information

Rawr may process and create moderation records containing:

the IDs, usernames, roles, and avatars of the affected member and acting moderator;
the action taken, category, free-text reason, timestamp, and success or failure state;
public primary-server tag and identity-server ID when the tag-blacklist feature applies;
timeout, kick, ban, push-to-talk, voice-ban, role, nickname, or message-deletion information;
command-usage metadata such as the acting user, channel, target, and time; and
lists of member IDs for whom an automated blacklist-tag cleanup succeeded or failed.

These records are generally posted to access-restricted Discord moderation channels. Blacklist-tag cleanup summaries are attached as JSON files and may be pinned in a staff channel. Staff command logs ordinarily contain command-use and target metadata plus controls for fetching the current Discord message; they do not intentionally duplicate the message body into the log entry itself.

3.4 Guild-blacklist information

Rawr uses an access-controlled, first-party internal service to maintain a manually curated list of Discord server IDs associated with the configured public-server-tag moderation feature. The blacklist contains server IDs. Rawr keeps a runtime copy of the listed server IDs in memory. Authorized application-team members can check, add, import, or remove server IDs. Imported files are fetched from Discord, parsed in memory, and the resulting server IDs are sent to the internal service.

3.5 Discord OAuth and linked roles

If you voluntarily use the linked-role authorization command, Rawr sends you to Discord’s OAuth authorization page and requests the identify and role_connections.write scopes. Rawr then uses the returned token to update the application role connection with boolean metadata reflecting whether your membership in Rawr’s configured server includes its administrator, moderator, or owner role.

The authorization prompt is time-limited in the reviewed workflow. Rawr generates and validates a unique OAuth state against the pending authorization request. The OAuth extension keeps the returned access-token data in the running process so it can complete and manage the authorization, but Rawr does not intentionally write OAuth states or tokens to a database or local file. This in-memory data is discarded when the process ends and may be cleared earlier if the authorization is revoked. Discord receives and processes this authorization under its own terms and privacy policy.

3.6 Minecraft administration

Authorized moderators can use Rawr to send administrative commands to a configured Minecraft server. User-supplied Minecraft player names, messages, or moderation reasons may therefore be sent to that Minecraft server and may appear in the Minecraft server’s own console or logs. Rawr may return server output to Discord.

3.7 Operational logs and technical information

Rawr writes debug-level operational logs to a local daily rolling file and to console/debug output. Logs may include startup and connection events, command or feature failures, Discord IDs, usernames or display names in some feature-specific messages, server or channel context, API response errors, stack traces, and other diagnostic details. Full message content is not intentionally logged as a normal analytics dataset, but exception details or upstream error payloads could contain information from the failed operation.

The local rolling-file configuration retains two daily log files.

4. How Rawr uses information

We use the information described above only to:

provide the command, interaction, entertainment, relay, role, OAuth, and Minecraft features requested by users or authorized administrators;
operate community moderation and safety workflows selected by the relevant server administrators;
maintain booster roles, linked roles, server tags, channel permissions, and other configured server functions;
prevent abuse, enforce server rules, investigate errors, secure Rawr, and keep it reliable;
create staff-visible moderation and accountability records; and
comply with valid legal obligations and enforce our applicable terms and policies.

We do not sell or license Discord API data, disclose it to data brokers or advertising networks, use it for targeted advertising, contact users outside Discord based on Discord data, or use it for employment, housing, insurance, credit, or similar eligibility decisions.

5. Automated moderation and human review

Rawr is used as part of Gameland’s moderation and community-safety infrastructure. Members who join and participate in Gameland are subject to Gameland’s server rules and associated moderation processes. Rawr may therefore process member, message, role, safety-signal, and moderation information where necessary to enforce those rules. Individual consent is not requested for each moderation action.

In Gameland’s current Rawr configuration:

a Discord-provided spammer flag or unusual-DM-activity signal may cause an automatic removal when a member joins or is updated, unless an exempt role applies;
a public primary-server tag whose identity server is on the configured blacklist may result in a role and communication timeout, and removal of that tag may result in automatic restoration;
a scheduled search may re-check affected members and continue or revoke the tag-related action;
a Discord quarantined-username signal may be used by an authorized administrator to run a nickname-repair tool; and
authorized staff may issue or reverse timeouts, kicks, bans, voice restrictions, role changes, message deletions, and channel/server locks.

These actions may affect your ability to participate in a Discord community. You may request human review or appeal an action through the separately operated modmail application available in the relevant server. We will consider the context, the information available to us, and the applicable community rules.

We do not use primary-server tags or safety signals to infer protected characteristics. They are used only for the configured community-safety purpose: comparing a public primary-server identity server with the manually curated guild-ID blacklist and enforcing the configured community rules.

6. Legal bases for processing

Where the GDPR, UK GDPR, or similar law applies, our intended legal bases are:

Performance of a contract or steps requested by you: responding to commands and interactions, processing optional linked-role authorization, message relays initiated by authorized users, and providing other requested features;
Legitimate interests: operating and securing Rawr and Gameland, enforcing community rules, preventing abuse, maintaining role and channel systems, keeping appropriate moderation records, and diagnosing failures, balanced against the rights and expectations of affected users;
Consent: where a specific optional feature expressly requests consent and consent is the appropriate legal basis;
Legal obligation: preserving, disclosing, or deleting information where applicable law requires it.

7. Retention and deletion

Rawr retains information only for as long as needed for the purposes described above, subject to legal obligations. The implementation behaves as follows:

Information	Current technical behavior
Recent Discord message cache	Rawr configures its Discord client’s in-memory message cache for up to 2,048 message objects. Entries are transient and may be removed through cache eviction or when the process stops or restarts.
Member, role, channel, and user caches	Held in process memory by the Discord library as needed for operation and discarded on shutdown/restart.
Slow-mode participant list	Held in memory for the event, cleared after the report or process cleanup/restart.
Guild blacklist runtime copy	Server IDs are held in memory until refreshed or Rawr restarts.
First-party internal guild blacklist	Manually curated Discord server IDs remain until an authorized maintainer removes them or deletion is otherwise required.
Local rolling application log	Two daily rolling files.
Console/process logs	Emitted to the process console/debug sink. Retention, if any, depends on the host or process-management infrastructure rather than Rawr’s application-level rolling-file configuration.
Discord moderation logs and attached JSON reports	No automatic expiry in Rawr; they remain until deleted by authorized staff, Discord, or the server’s own retention process. Some cleanup reports may be pinned.
Relayed, reposted, staff-sent, and bot-generated Discord messages	No automatic expiry in Rawr; they remain on Discord until deleted.
OAuth state/access token	Kept only in running-process memory by the OAuth extension; Rawr does not intentionally persist it to disk or a database. It is discarded when the process ends and may be cleared earlier if revoked.
Backups	Rawr’s reviewed code does not create backups.

When we receive a valid deletion request, we will delete or de-identify data that we control unless retention remains necessary for a documented legal, security, abuse-prevention, or moderation purpose. Deleting a Discord message or record may require action by a server administrator. We cannot delete data controlled solely by Discord or another independent service, but we will identify the relevant provider where reasonably possible.

If Rawr is discontinued or loses access to Discord’s APIs, we will stop using Discord API data and delete cached or stored API data under our control as required by the Discord Developer Terms.

We disclose information only as necessary to operate Rawr, at a user’s direction, to comply with law, or to protect users and the service. Depending on the deployment, recipients may include:

Discord Inc. / Discord Netherlands BV: the platform through which commands, messages, files, roles, moderation actions, OAuth, and bot responses are processed and stored;
Aiko IT Systems: operates and administers Rawr and its application infrastructure;
Netcup: provides the virtual-server hosting infrastructure on which Rawr operates;
Cloudflare: provides infrastructure used to host and protect Rawr’s first-party internal guild-blacklist service;
Shockbyte: receives authorized Minecraft administration commands and may retain its own server logs; and

Accessing or rendering third-party content may cause Discord or your client to request content from the relevant provider, which may process that request under its own privacy terms.

Where a service provider processes Discord API data on our behalf, we use such providers in accordance with the requirements applicable to service providers under Discord’s Developer Terms and applicable law.

We may disclose information if reasonably necessary to comply with law, respond to a valid legal request, protect rights and safety, investigate abuse, or establish or defend legal claims. We will not sell Discord API data or share it with data brokers, advertising networks, or unrelated monetization services.

9. Security

We use reasonable administrative, technical, and organizational measures intended to protect information. These measures include role-based Discord permissions, staff-only moderation channels, application-team and owner checks for sensitive commands, short-lived in-memory processing for many features, limited rolling local logs, and access-controlled API credentials.

Information stored by Rawr is hosted on infrastructure using encryption at rest, with administrative server access restricted through key-based authentication.

If we discover unauthorized access to Discord API data, we will investigate, remediate, and notify Discord and affected users where required by Discord’s Developer Terms or applicable law.

10. Your choices and controls

Depending on the feature and your permissions, you can:

choose whether to invoke a command, interaction, button, menu, modal, or linked-role OAuth flow;
remove a selected booster color role through Rawr’s role menu;
decline the linked-role OAuth authorization in Discord;
delete your own source message where Discord permits, although this may not delete a relay or moderation copy;
ask a server administrator to review a Rawr-created message or moderation record, or request its deletion where appropriate;
ask us for access, correction, deletion, restriction, or an objection as described below; and
as a server administrator, restrict Rawr’s channels and permissions or remove Rawr from the server.

Rawr does not contain a user-facing privacy export or deletion command. You may submit a request through privacy@aitsys.dev. Certain requests may be limited where retaining specific information remains necessary for moderation, abuse prevention, security, legal obligations, or the establishment, exercise, or defense of legal claims.

Some server-safety processing cannot be disabled for one member while that member remains in a server that has enabled the feature. You may still request human review and deletion of data that is no longer necessary.

11. Access, correction, deletion, and privacy rights

To exercise a privacy right, contact privacy@aitsys.dev and include enough information to identify the relevant Discord account and server, such as your Discord user ID and the server ID. Do not send us your password, bot token, OAuth token, or other login credentials. We may ask for reasonable proof that you control the Discord account before disclosing or deleting information.

Subject to applicable law, you may have the right to:

know whether we process information about you and receive a copy;
correct inaccurate information;
request deletion or restriction;
object to processing based on legitimate interests;
withdraw consent for future processing where consent is the basis;
receive portable information where applicable; and
complain to a competent data-protection authority.

We aim to acknowledge requests promptly and, where the GDPR applies, respond within the periods required by applicable law, ordinarily within one month and subject to lawful extensions. We will explain if we cannot fulfill a request in whole or in part.

12. International data transfers

Rawr, Discord, and the service providers listed above may process information in countries other than yours. Discord’s Developer Terms include specific controller-to-controller transfer terms for Discord EU and UK data.

13. Children

Rawr is not directed to anyone under 13 or below the minimum age required to use Discord in their country. We do not knowingly seek information from people who are not permitted to use Discord. If you believe such information has been processed, contact privacy@aitsys.dev.

14. Changes to this policy

We may update this policy when Rawr’s features, data practices, providers, or legal obligations change. We will update the date above and provide additional notice where a change materially affects users or applicable law requires it. The current version will be available at 20/08/2026 and linked from Rawr’s Discord application profile and/or help command.

15. Contact and reports

For privacy questions or requests: privacy@aitsys.dev For support, safety concerns, or reports that Rawr is being misused: support@aitsys.dev For moderation appeals: Use the separately operated modmail application available in the configured server.

Please never send a Discord password, bot token, access token, or other credential.

16. Privileged intent summary

Rawr requests two Discord privileged intents:

Guild Members: used for member join and update events, role and booster management, configured member searches, public primary-server-tag moderation, Discord safety-signal handling, nickname repair, and related moderation actions.
Message Content: used for configured message relaying and reposting, message-based staff workflows, prefix commands, designated content-triggered community features, and processing message text or attachments when a feature explicitly operates on an existing message.

Rawr does not request the Guild Presences privileged intent and does not use online status or activity data.