Who runs flanker
flanker is an independent project operated by Malik Shahzain, a developer based in Pakistan. In this policy, “flanker”, “we”, “us” and “our” refer to Malik Shahzain and the flanker service.
This policy covers the flanker Discord bot, the dashboard at flanker.wtf and related support services. Discord operates its own platform under its own Privacy Policy.
Data we handle
flanker only needs data connected to the features a server or member uses. Depending on those features, this can include:
- Discord account and server data: user, server, channel, role and message IDs; usernames and display names; avatars; membership; roles; permissions; channel details; and server settings.
- Custom status: when a server uses a vanity role or giveaway status requirement, flanker can compare the current custom status with the configured keyword. Presence data is held in memory and is not saved to the database.
- Commands and configuration: commands sent to flanker, server prefixes, moderation settings, security rules, welcome messages, ticket panels, application forms, notification subscriptions and other saved configuration.
- Security and moderation records: audit-log activity, security events, filter and honeypot catches, moderation cases, warnings, staff notes, jail records, saved jail roles, hardbans and captcha state.
- Community records: levels, XP, invite counts, reaction counts, message counts, voice time, streaks, suggestions, giveaway entries, ticket records, application submissions and answers, accepted friendships, gifts and their notes, and social block preferences.
- Message content in specific features: recent deleted or edited messages for snipe, filtered or honeypot messages, ticket transcripts, application answers, reminders, notes, confessions, saved messages and owner-enabled backups.
- Personal settings: birthdays, time zones, AFK status, reminders, last-seen information, name history, personal prefixes, Last.fm usernames and authorized session keys, voice-scrobbling preferences, Spotify authorization tokens and Fortnite watch lists.
- Dashboard data: your Discord ID, name, avatar, current server list, a signed session identifier, encrypted Discord access and refresh tokens, a short-lived OAuth state value, and a login record (your ID, name, avatar, first and last login, and how many times you logged in).
- Technical data: basic request, error and security logs that may include an IP address, browser information and timestamps when needed to operate or protect the service.
Friendships and gift collections follow your account across servers. Requests and gift notes are posted publicly in the channel where they are sent. Knowme host choices are private during setup, then revealed as each round finishes. Quiz choices stay in memory for at most ten minutes or until the game ends or the bot restarts.
When a server owner connects a Minecraft SMP, flanker receives player names, chat messages and announced advancements for delivery to the selected Discord channels. Pending events expire after one minute, and batch identifiers are retained for up to 24 hours to prevent replay. Connection settings and hashed pairing credentials remain until disconnected. The plugin stores its own connection credential locally; it never receives flanker's Discord bot token.
Last.fm authorization happens on Last.fm. Flanker never requests your Last.fm password. Linked usernames and listening statistics can be requested in shared servers. Authorized session keys enable actions such as loving a track; voice scrobbling is separately optional and starts off for new authorizations. Use lastfm logout to delete your link and session and cancel pending approval. Brief API caches expire within one minute. Voice-scrobbling listening estimates stay in memory for the current track and exclude paused or deafened samples.
flanker tracks whether someone is in voice and how long they stay. It does not record or store voice audio.
Server backups are off by default. If a server owner enables them, a backup can include roles, channels, emojis, the latest 100 messages in each text channel and message files up to 8 MB.
How data is used
We use this data to:
- respond to commands and show the dashboard;
- detect raids, nukes, spam and other abuse;
- apply moderation actions and keep an audit trail for server staff;
- run features that a member or server administrator has chosen to use;
- show server activity, levels and leaderboards;
- maintain sessions, prevent misuse, diagnose failures and improve reliability;
- meet legal obligations and protect users, flanker and Discord.
We do not sell personal data, provide it to data brokers, use it for targeted advertising or train machine-learning models on Discord message content.
Server controls
A server owner or authorized administrator chooses which flanker modules are enabled and where their output is posted. That choice can cause flanker to process information about members of that server. Server staff are responsible for using those controls lawfully and for telling their members about server-specific logging or moderation practices where required.
Some results are posted back to Discord, including moderation logs, ticket transcripts, application reviews and security alerts. Once posted, those messages are also controlled by Discord and the server administrators who can access that channel.
How long data is kept
Retention depends on the feature. Current default periods are:
| Data | Normal retention |
|---|---|
| OAuth login state | Up to 10 minutes |
| Dashboard sessions and encrypted Discord OAuth tokens | Up to 7 days |
| Dashboard login record | Until you ask us to delete it |
| Filter catch records | Up to 30 days |
| Security events, honeypot catches and stored reaction-message metadata | Up to 90 days |
| Daily server-level command, button, menu and feature usage totals. No message content or user IDs. | Up to 90 days |
| Message, reaction, voice and VoiceMaster activity statistics | Up to 400 days |
| Snipe content | Held in memory until overwritten, cleared or the bot restarts |
| Discord presence and custom status | Held in memory until updated, the member goes offline or the bot restarts |
| Friendships, accepted gifts and social blocks | Until removed with the relevant command or through a deletion request |
| Pending friendship requests and gifts | Expire after 10 minutes and 24 hours respectively, then are automatically removed |
| Gift sending limits | Three days |
| Knowme quiz choices | Held in memory for up to 10 minutes, until the game ends or the bot restarts |
| Owner-enabled backups | Until replaced or the owner disables backups and deletes the backup data |
| Configuration, cases, tickets, applications and personal feature data | Until removed, no longer needed, or the relevant feature or server data is deleted |
Aggregated statistics may remain after direct identifiers are removed. Messages and transcripts already posted to Discord follow the retention and deletion controls of Discord and the server where they were posted. Ticket transcripts are also stored by flanker so they can be read on flanker.wtf by the ticket's opener, the people who wrote in it and the server's ticket staff (after signing in with Discord), together with copies of images posted in the ticket. They are deleted automatically after one year.
Where data is handled
flanker is operated from Pakistan. Its production bot, dashboard and database run in the United States. Discord and connected third-party services may process data in other countries. This means data can be transferred across national borders when the service is used.
Security
We use access checks, signed dashboard sessions, short retention periods for sensitive event data, restricted database access and other technical safeguards suited to the service. No online system is completely secure, so we cannot promise that unauthorized access or data loss will never happen.
If a security incident is likely to affect users, we will investigate it and provide notice where required.
Your choices and deletion requests
You can ask what personal data flanker holds about you, ask for a correction, object to certain processing or request deletion. Contact us at [email protected] or through discord.gg/yRyTAHmvxJ. We may ask you to verify control of the relevant Discord account before acting on a request.
We will remove data controlled by flanker when reasonably possible. We may retain limited records when they are needed for server security, abuse prevention, legal compliance or the rights of other users. Moderation cases, security records and ticket records created for a server may also be controlled by that server's administrators.
Some features have their own removal commands, such as removing a birthday, time zone, name history, reminder or linked account. Server owners can disable modules, clear their configuration, remove flanker from the server and disable backups. Removing flanker does not automatically delete messages it already posted in Discord.
Age requirements
You must meet Discord's minimum age for your country to use flanker. Discord states that users must be at least 13, and some countries require a higher age. If a parent or guardian believes a child's data was handled improperly, they can contact us for review and deletion.
Changes to this policy
We may update this policy when flanker's features, providers or legal obligations change. The date at the top shows the latest revision. Material changes may also be announced through the support server or the dashboard.
Contact
Privacy questions and requests can be sent to [email protected] or raised in the support server at discord.gg/yRyTAHmvxJ.