Find your way.

This policy applies to TSHE, Lyxia, the bot dashboards, tickets, staff applications, appeals, archives, transcripts, and related server services. It combines the processing performed across Lyxia's systems.

Joining means acceptance

By joining, remaining in, accessing, or participating in TSHE, you agree to the Server Terms of Service and acknowledge the Privacy Policy, including the operation of Lyxia. If you do not agree, you must leave the server and stop using its services.

Acknowledgement is not blanket consent

Joining or remaining in the server confirms that you have been given this notice and agree to the server Terms. Personal-data processing is not treated as relying exclusively on consent: core safety and service processing may be necessary to provide the service, enforce the Terms, protect users and infrastructure, or comply with legal obligations. Optional processing may rely on your choice or consent where applicable.

Who is responsible

TSHE, operated by f34rless.dev, determines why and how the server-specific processing described here occurs. Privacy requests should be sent to [email protected]. Discord and any named integration providers separately control the data they process under their own policies.

What is collected

The exact information depends on what you do and which features are active. It can include:

• Discord account, server, role, channel, message, interaction, voice, invite, and audit identifiers.
• Usernames, display names, nicknames, avatars, account/server dates, roles, permissions, and bot/account status.
• Message text, replies, embeds, components, stickers, reactions, edits, deleted messages, links, and attachments.
• Copied images, GIFs, video, audio, documents, filenames, types, sizes, dimensions, and source URLs in archives or evidence.
• Reports, cases, warnings, notes, punishments, AutoMod events, evidence, appeals, staff decisions, and escalation history.
• Tickets, ticket participants, answers, messages, priorities, claims, ratings, closure reasons, and transcripts.
• Staff applications, application answers, discussion/review state, decisions, cooldowns, and associated role changes.
• Commands, interactions, counters, activity statistics, levels, invitations, giveaways, polls, suggestions, reminders, AFK status, social interactions, economy balances/progress, staff work, and reviews.
• Preferences and feature state such as timezone, VIP/booster details, custom roles or emoji, temporary voice permissions, blacklists, music state, and linked Roblox details.
• Dashboard/OAuth sessions, cookies, login identifiers, authorized guild information, IP address, user agent, route/method, actions, error details, and security/audit events.
• Invoice or transaction references when used, including customer/invoice identifiers, item, amount, currency, fee, email address, status, validity, and provider link. The bot is not intended to collect full payment-card details.
• Aggregate bot, server, performance, command, interaction, moderation, and operational statistics.

See the Complete Data Inventory for the feature-by-feature breakdown.

Why it is used

• Operate the server, bots, commands, dashboards, verification, roles, tickets, applications, appeals, reminders, and requested features.
• Prevent spam, raids, harassment, fraud, evasion, unsafe content, unauthorized access, and other abuse.
• Detect and enforce rule violations; preserve context; support fair staff review and appeals.
• Route support, maintain transcripts, administer staff workflows, and deliver requested notifications.
• Diagnose failures, measure reliability, audit privileged actions, secure infrastructure, and improve configuration.
• Process requested invoices or integrations and maintain necessary transaction records.
• Establish, exercise, or defend legal claims and comply with applicable law, valid requests, and Discord requirements.

Lawful bases

Depending on the activity and applicable law, processing may rely on:

• Contract or requested service: operating features you request and enforcing the Server Terms.
• Legitimate interests: community safety, moderation, fraud prevention, evidence integrity, service security, auditing, and improvement, balanced against member rights.
• Legal obligation: retaining, disclosing, or acting on information when the law requires it.
• Consent or affirmative choice: optional features where consent is the appropriate basis; it can be withdrawn for future optional processing.
• Protection of vital interests: exceptional circumstances involving an immediate threat to someone’s safety.

Who may access or receive it

• Authorized TSHE owners, administrators, moderators, reviewers, and support staff according to role and operational need.
• The member who created or is authorized to receive a ticket/archive transcript.
• Anyone given a shareable archive or transcript link; such links must be treated as confidential.
• Discord, because the community and bots operate through Discord.
• Hosting, tunnel/CDN, database, email, security, and infrastructure providers needed to deliver the services.
• A selected integration provider—such as a payment/invoice, Roblox, YouTube, Kick, game-status, or other linked service—when that feature is used.
• Law enforcement, regulators, courts, emergency services, Discord Trust & Safety, or affected parties where disclosure is legally required or reasonably necessary for safety, rights, fraud prevention, or legal claims.

Data is not sold, and the bots do not use advertising cookies. The dashboards use necessary authentication/session cookies. Infrastructure providers may process network and request data under their own terms.

Automated processing

Lyxia, Discord AutoMod, and enabled safety modules can automatically inspect content and account/activity signals, create logs, restrict content, issue or recommend actions, or escalate an event. A person can request staff review through the appropriate ticket or appeal route. Security-sensitive detection rules and confidential evidence may not be disclosed where disclosure would enable evasion or harm others.

Retention and deletion

• Lyxia’s always-on message snapshots are scheduled for automatic purge after 90 days.
• Created archives and copied archive media remain until an authorized administrator deletes them.
• Lyxia dashboard-action audit records are scheduled for deletion after 90 days.
• Temporary proposals, sessions, reminders, polls, voice channels, notices, and similar workflow data can expire or be removed when completed, revoked, or no longer active.
• Tickets, applications, transcripts, moderation, appeals, security, staff, invoice, and audit records otherwise remain for as long as reasonably needed for their purpose, disputes, safety, enforcement, accounting, backups, or legal obligations; no shorter automatic period is promised unless stated above.

Deletion requests may result in erasure, anonymisation, restriction, or retention of a limited record where continued storage is necessary and lawful. More detail appears in Retention & Deletion.

Your choices and rights

Depending on your location and applicable law, you may ask to access or export your data, correct it, delete it, restrict or object to processing, withdraw consent for optional future processing, or receive portable data. Lyxia also supports future-collection preferences for message snapshots, AutoMod logs, and report-target records; opting out may be limited where collection is required for safety or enforcement.

Email [email protected] with your Discord user ID and request. Identity verification may be required. See Data Requests.

Children

The server is not available to anyone below Discord’s permitted age. Members aged 13–17 receive the same privacy rights and additional care appropriate to their age. Do not submit unnecessary sensitive information. Where applicable law requires parental authorization for optional consent-based processing, that processing will not be based merely on passive server membership.

Security and international processing

Reasonable access controls, authenticated dashboards, permission checks, logging, rate limits, and technical safeguards are used. No system can guarantee absolute security. Discord and infrastructure providers may process data in other countries under their own transfer safeguards and policies.

Updates and complaints

Material policy changes will be published here or announced where practical. Contact [email protected] first so the issue can be investigated. You may also complain to the data-protection authority available in your country; UK users can consult the Information Commissioner’s Office.

Effective and last updated: 3 September 2026.