DOCUMENTATION / LEGAL
Complete Data Inventory
A feature-by-feature inventory of information processed by Lyxia in TSHE.
This inventory describes fields and content the bot implementations can process. A category may contain no record for you if you never use that feature or the feature is disabled.
Shared Discord and server data
| Category | Data elements |
|---|---|
| Account identity | Discord user ID, username, display name, nickname, avatar, bot status, membership/join dates |
| Server structure | Server, channel, thread, message, role, emoji, sticker, invite, interaction, and voice-channel IDs; role names, colours, positions, permissions, and channel hierarchy |
| Activity | Commands and interactions, timestamps, message/reaction activity, joins/leaves, role changes, invite attribution, and aggregate counters |
| Submitted content | Messages, replies, edits, deleted content, embeds, components, stickers, links, attachments, filenames, media metadata, and copied media bytes |
Lyxia moderation and archive data
| System | Data elements |
|---|---|
| Message snapshots | Author identity/profile display fields; message/channel/server IDs; content; embeds; components; stickers; references; attachments; edit history/count; created, captured, edited, and deleted timestamps |
| Archives | Archive code/type/title, creator, source channel, messages and positions/status, author identity, timestamps, content, embeds/components/attachments, reactions, replies, and copied image/GIF/video/audio/document data plus names, types, sizes, dimensions, and original URLs |
| Cases and warnings | Case number/type/status, subject and moderator IDs, reason, duration/expiry, evidence, linked cases, timestamps, active warnings, and renewable punishments |
| Notes and punishments | Subject/moderator IDs, note/reason, action/type, role, status, expiry, edit/create dates, proof, and related case IDs |
| AutoMod and reply protection | User/channel/message IDs, rule/module, content snippets or stored content, blocked target, original/sanitised content, incident counts/windows, escalation level/action, archive/case references, and timestamps |
| Reports | Reporter and target IDs, target message/content, reason, source channel/module/rule, attachment/evidence, status, counts, resolution, staff actor, and timestamps |
| Appeals | User/case/server IDs, application answers and messages, status/decision/reason, Discord thread/message IDs, blocks, staff actions, and timestamps |
| Security and access | Blacklists, verification/gate state, lockdown permission snapshots, external bot API request source/method/path/status/IP/payload/response/errors, and staff audit requests |
| Dashboard privacy | Session records, privacy opt-outs, export/deletion timestamps, authentication cookie, and authenticated Discord user ID |
Lyxia ticket, application, and staff data
| System | Data elements |
|---|---|
| Tickets | User/server/channel IDs, category/index, permission level, claim owner, added users, created/inactive/closed times, warning state, whitelist state, reason, closer, rating/review, priority, messages, attachments, and transcript |
| Applications | Applicant/server/channel IDs, application type/index, question answers, completion/closure state, decision reason, reviewer/closer, cooldowns, timestamps, discussion, and transcript or review history where generated |
| Staff records | Staff status/role, saved roles, strikes, promotions/demotions/resignations, call time, task creator/assignees/title/description/notes/attachment/deadline/status, review author/subject/rating/reason, and per-feature performance counters |
| Moderation/report integration | User, executor, reporter and target IDs; action, reason, duration, proof/attachment, transcript reference, active state, severity, and timestamps |
Lyxia community-feature data
Profiles, progress, economy, and activity
- Message/command/activity counts, XP, level, leaderboard and game results/streaks.
- Economy balance, total earned, bank and rank levels, streaks, jobs, quests, shop items, boosters, lootboxes, begging and robbery statistics.
- Birthday day/month and privacy preference where supplied.
- Invite creator/code/use/join attribution, valid/fake/left counts, member-since checks, giveaway entries, eligibility, winners, host, prize, start/end, and bonus entries.
- Poll choices/voters, suggestions and votes, starboard messages/reaction counts, and social-action user/target/count.
Preferences and member tools
- AFK reason, timing, auto-remove preference, mentions while AFK, mentioner, channel, and message.
- Reminder subject/content, due time, channel, and status.
- Saved messages/embeds and sent-message references, including creator and supplied media.
- Timezone preference and update time.
- VIP period/history, nickname, custom role/emoji choices, renewal data, and granting staff member.
- Booster history, username, boost state, custom roles/emoji, and dates.
- Family-tree relationships and proposals: users, parents, spouses, children, relationship type, channel/message, and expiry.
- Temporary voice ownership, channel/control-message IDs, visibility/lock, password where configured, region, user limit, allowed/banned/moderator user IDs, and dates.
- Anti-ping protected users and staff member who added them; role-nickname configuration; buggy-message preference/state.
Operations, integrations, and payments
- Dashboard Discord OAuth/session information and necessary cookies.
- Privileged dashboard actions: actor ID/username, action, resource, permission, route, method, IP address, user agent, metadata, result, and timestamp. Lyxia retains these audit actions for 90 days.
- Bot/server performance and aggregate counts, member totals, latency, memory use, command outcomes, errors, security events, and feature usage.
- Invoice/customer identifiers, creator, email, item, amount, currency, fee, status, validity, provider link, channel/message, and timestamps. Full payment-card data should not be submitted and is not an intended bot field.
- Linked Roblox user ID, Roblox ID, username, and linking time.
- YouTube/Kick channel/account identifiers and notification/live-stream state when those integrations are configured.
- Game/server status endpoints and status information when enabled; configuration can contain credentials but credentials are restricted operational secrets, not member-profile data.
- Web/API request metadata and error reports, including source, route, status, IP, payload/response, and timestamps where logged.
Data not intentionally requested
Do not provide passwords, Discord tokens, two-factor codes, recovery codes, full payment-card details, government identifiers, medical records, exact home addresses, or other unnecessary sensitive information. If such information is posted, automated snapshots or an evidence archive may capture it before staff can remove it; contact [email protected] promptly.