Your information
Privacy Policy
Last updated:
This policy explains how TAGGY handles information through its Discord bot, fishing and dish washing games, TAGGY dashboard at lojjkli.site/taggy/, and these legal pages. TAGGY is operated by kli, Switzerland ("we", "us" or "our"). kli is responsible for the personal information handled by TAGGY. Contact us at zzzzzworks@gmail.com.
1. Information and purposes
TAGGY receives information from Discord, from people who use its features, from authorized server managers, and from Roblox when Roblox verification is used. The information processed depends on the feature and the permissions granted to the bot.
- Discord profiles and server settings. User, server, channel, role and message IDs; usernames, display names, avatars, server icons, membership and permissions; configured roles, channels, embeds, welcome messages and other settings. These support commands, permission checks, customization and dashboard management.
- Messages and direct messages. Commands, interactions, message text, author details, timestamps, attachment names and links. TAGGY processes these to answer commands, display permitted channel history, relay tickets and send messages requested by authorized users. The operator's bot DM inbox stores recent conversations and can request older TAGGY DM history from Discord.
- Tickets and questionnaires. Ticket type, server, opener and staff IDs, channel ID, claim/close/reopen/delete records, timestamps, questions, answers, messages and attachments. These support help requests, bug reports and voluntary community staff applications. Closing a ticket can create a transcript in the server's configured staff logs channel.
- Verification. Discord user ID, verification status, method and timestamp. Optional Roblox verification also uses Roblox account ID, public username/display name and relevant group membership or role. Supported verification methods may process a temporary profile code or Roblox verification-experience and game-session identifiers. Existing verification records may be reused in other servers using TAGGY, subject to the receiving server's requirements.
- Moderation and security. Join events, account age, message activity, mentions, audit-log events, involved user/channel IDs, reasons, outcomes and timestamps. These support raid, spam, destructive-action and honeypot detection, automatic restrictions, alerts, and review of dashboard actions. Spam detection briefly processes message content and hashes in memory. Honeypot alerts in Discord can include an excerpt of the triggering message.
- Dish washing. Discord user ID, coins, XP, washer ownership, upgrades, dish collection, chosen kitchen, active stacks, reward claims, streaks, challenges, cooldowns and menu preferences. These keep progress consistent across servers and DMs. Cleaning totals and rankings may identify players by Discord ID or mention.
- Fishing. Discord user ID, catches, inventory, coins, XP, equipment, chosen waters, records, achievements, quests, reward claims and cooldowns. These keep game progress consistent across servers and DMs and provide public game statistics and rankings.
- Other community features. Rank and team assignments, partner information, giveaway configuration, entry/winner identifiers and timing where needed. These operate the feature requested by the server or user.
- Support requests. Your email address, the contents of your request and information needed to verify and resolve it.
Do not send passwords, account login tokens, payment-card details, health information or other highly sensitive information to TAGGY or through its ticket questionnaires. Server staff should request only information relevant to the ticket.
2. Who can access it
TAGGY's operator: The operator console can access the dashboards of servers where the bot is installed and the bot's own DM inbox, including historical conversations available from Discord. The operator can view channels and take actions where the bot has the necessary Discord permissions. These privileges are separate from the operator's own member permissions in a server and are used to operate, support and secure TAGGY.
Server managers and ticket staff: Server owners, members with appropriate management permissions and designated server managers can access their server's dashboard. Individual actions require the relevant permissions. Ticket messages, answers, attachments and transcripts are available to staff with access to the ticket or logs channel, including administrators who can access those channels.
Other Discord users: Messages and game replies posted in a channel are visible to people who can access that conversation. Fishing profiles, catches, dish washing statistics and global leaderboard entries may identify players by Discord ID or mention and show game statistics.
TAGGY can access conversations with the bot and Discord channels made available to it. It cannot read your private conversations with other people. Sending a message to TAGGY for a ticket means it will be shared with that ticket's staff team.
3. Login, cookies and website requests
Dashboard login uses Discord's official authorization flow with the identify permission. TAGGY receives your Discord ID and profile identity, then checks server access through the bot. It does not request your email or your full server list for dashboard login. OAuth access and refresh tokens are not retained after identification.
The dashboard uses essential, secure, HTTP-only cookies for login and session protection. The temporary login cookie lasts up to five minutes; a session lasts up to eight hours and expires after thirty minutes of inactivity. Session information is held in the bot's memory and is cleared when the bot restarts. Signing out revokes that account's dashboard sessions.
Cloudflare and the hosting services receive normal request information, such as IP address, browser/request headers, requested URL and time. The dashboard forwards your IP address to the bot for short-lived rate limiting and abuse prevention. Providers may maintain their own service or security logs.
TAGGY's dashboard does not include advertising trackers or custom analytics cookies. Displaying Discord avatars or attachments makes requests to Discord's media services. Disabling essential cookies prevents dashboard login.
Optional Roblox OAuth verification uses Roblox's official login with openid profile. TAGGY uses the returned identity for verification and does not retain Roblox OAuth access or refresh tokens afterward. Never provide your Discord or Roblox password directly to TAGGY.
4. Service providers and international processing
We use the following services as needed for TAGGY:
- Discord for identities, permissions, commands, messages, attachments and channel/transcript storage.
- Cloudflare for website delivery, HTTPS, request protection and the dashboard proxy. Dashboard traffic passes through Cloudflare.
- bot-hosting.net for the bot backend and its saved configuration and feature records.
- GitHub for website source and hosting of the public legal pages. Private bot records are not published in this repository.
- Roblox when its account or group verification features are used.
- Google/Gmail to receive and reply to email sent to our contact address.
TAGGY is operated from Switzerland. These providers also process information internationally, including in the United States, through their infrastructure and service providers. Their linked policies explain their own processing. Where applicable law requires transfer safeguards, the relevant legal requirements apply; contact us for information about the arrangements applicable to your data.
We do not sell personal information or Discord API data, share it with advertising networks or data brokers, or use Discord message content to train AI models. We share information only as needed with service providers, as directed by users through a feature, or when required by applicable law. Access to records for support and security is limited to the purposes described here.
5. Retention
Different records have different lifetimes. There is no single thirty-day deletion rule for all TAGGY data.
| Record | How it is retained |
|---|---|
| Dashboard login | Temporary login state: up to five minutes. Sessions: up to eight hours, with thirty-minute inactivity expiry. Both are held in memory. |
| Saved bot DM inbox | The local cache is trimmed to messages from the past thirty days, up to 150 messages per conversation and 100 conversations. Trimming occurs when the inbox is read or updated; older records on disk may remain until the next successful save. Older messages may still be fetched from Discord. |
| Ticket transcripts | Transcripts posted by TAGGY in Discord are scheduled for deletion thirty days after creation. Cleanup is attempted every six hours while the bot is running and can be delayed by lost permissions, server access or service failures. |
| Tickets and answers | Ticket metadata, saved questionnaire answers and attachment links are kept while needed for ticket handling and review. Closing or deleting a channel does not automatically erase these local records. Staff channels and independently downloaded transcripts have separate lifetimes. |
| Security incidents | The bot keeps the latest 300 incidents per server, replacing older entries as new ones arrive. These records have no fixed age cutoff. Alerts and logs posted in Discord remain until deleted there. |
| Configuration, verification, fishing, dish washing and other feature state | Stored while necessary to provide the corresponding feature, or until deletion is requested or otherwise required. Game progress and verification records may apply across servers. Removing the bot or signing out does not automatically erase them. |
| Temporary checks and provider logs | Login, verification and activity checks expire according to the relevant feature; expired persisted verification challenges may remain until removed or replaced. Hosting, email and platform logs follow the provider's applicable retention rules. |
We promptly delete bot-held personal data when requested by the relevant user, when it is no longer necessary for TAGGY's stated functionality, when required by Discord or law, or when we stop operating TAGGY, except where applicable law requires retention. Any legally required retention is limited to its necessary purpose and duration.
6. Your choices and rights
To request access, correction, an export or deletion of information linked to your account, email zzzzzworks@gmail.com with your Discord user ID and the relevant server or feature. Server owners can also request deletion of their server's configuration. We may verify control of the account or server before disclosing or changing records; never send passwords or account tokens.
A deletion request can include your stored DM cache, ticket answers, verification link, security records, fishing profile and dish washing profile. We will explain any information we must retain and any records outside our control. TAGGY-held records are separate from messages stored by Discord or copies downloaded by server staff; relevant requests for those copies may also need to go to the server owner or platform.
You can stop interacting with TAGGY, sign out of the dashboard, revoke optional Discord/Roblox authorizations in those services, or ask a server owner to remove the bot. Unlinking Roblox removes the current account link, but does not by itself erase all verification history, ticket records or messages.
Depending on applicable law, you may also have rights to object to or restrict processing, receive portable data, withdraw consent for consent-based processing, and complain to a data protection authority. Withdrawing consent does not affect processing already lawfully performed. In Switzerland, the relevant authority is the Federal Data Protection and Information Commissioner.
7. Legal basis
Where a legal basis is required, we process data as necessary to provide the features you request under our Terms of Service, for legitimate interests in maintaining and securing TAGGY and supporting server communities, subject to your rights, or with consent where required. We may also process information to meet legal obligations.
Security features can automatically delete messages, apply timeouts, kick users from honeypot channels or remove manageable roles when configured rules are triggered. These rules use activity thresholds and permissions, can make mistakes, and do not make employment, credit or similar eligibility decisions. Contact the affected server's staff for review of a moderation action, or our email for concerns about TAGGY itself.
8. Security
TAGGY uses HTTPS for dashboard traffic, server-side authentication and permission checks, protected session cookies, request validation and rate limits. Bot credentials and saved private records must be kept outside public website files. No online service can guarantee complete security.
Report suspected unauthorized access to zzzzzworks@gmail.com. We investigate and take appropriate corrective steps, and notify affected people and Discord where required by applicable law or Discord's rules.
9. Age requirements
TAGGY is for people permitted to use Discord, which requires users to be at least thirteen and may require a higher age in their country. Roblox's requirements also apply when using Roblox features. We do not knowingly seek data from people below Discord's applicable minimum age. Contact us if you believe TAGGY has received such data.
10. Changes and contact
We update this policy when TAGGY's features, data practices or legal requirements change. The latest version is published here with its update date. Where required, we provide additional notice or obtain consent for material changes.
Operator: kli, Switzerland
Privacy and support: zzzzzworks@gmail.com
TAGGY is an independent service and is not operated or endorsed by Discord or Roblox. Their own terms and privacy policies also apply when you use their platforms.