Privacy Policy

What we collect

When you use the Discord bot or dashboard, Dubtrackr may store:

• Discord user, server, channel, role, and message identifiers;
• your Discord display name and avatar URL;
• OAuth session records;
• server configuration, feature events, moderation records, and audit entries;
• music history and playlists;
• support or privacy requests you submit.

Enabled game modules may store Epic/Fortnite account identifiers, public profile data, provider snapshots, tracking membership, and generated summaries. We also process basic operational logs such as timestamps, errors, and request metadata needed to secure and run the service.

Other modules a server switches on may store more about that server and its members. Module data lists what each one keeps and for how long.

How we use data

• Provide the modules and dashboard selected by each Discord server.
• Authenticate users, enforce server permissions, and prevent cross-server access.
• Poll enabled providers, generate server-specific results, and maintain service reliability.
• Investigate abuse, respond to support and privacy requests, and keep a security audit trail.

Sources and processors

Data comes from Discord, server administrators and members, enabled game providers, and services users ask the bot to access.

Dubtrackr relies on Discord for bot and OAuth services, Cloudflare for public edge delivery and tunneling, Fortnite-API for enabled game features, and YouTube or media sources selected by users for music. Those providers apply their own policies.

Module data

Every module below starts switched off in every server. It stores nothing for a server until an administrator of that server switches it on or sets it up, and what it stores belongs to that server alone.

• Birthdays: the month and day a member saves, the year only if they add it, and who saved it. A record of each celebration is kept for the current and the previous year. A member’s birthday is deleted when they leave the server.
• Economy: each member’s wallet and bank balances, daily streak and cooldown times, and the shop items they own. The transaction ledger keeps 90 days, and at most the newest 50,000 entries per server; chat rewards are not recorded one by one.
• Giveaways: who entered each giveaway and with how many entries, the winners, and the prize and description a giveaway manager typed. The last 50 finished giveaways are kept per server, with their entries for rerolls.
• Suggestions: each suggestion’s text and author, each member’s up or down vote, and staff decisions and notes. They are kept until an administrator deletes them.
• AFK Status: a member’s away reason, when they went away, how often they were mentioned, and the nickname to put back. It is deleted when they return, leave the server, or an administrator clears it.
• Counting: the current count and record, who counted last, and each member’s correct counts, mistakes and highest number.
• Auto Moderation: one entry per hit: the member, channel, rule, action, a short detail such as “7 mentions (limit 5)”, and any moderation case number. Message text is never stored. Hits are deleted after 30 days, and at most 5,000 are kept per server.
• Verification & Anti-Raid: each verification attempt (member, result, method and a short detail), deleted after 30 days, and anti-raid events (join counts, what Dubtrackr did, and the channel permissions it will restore), the last 50 per server. A lockdown that has not been lifted is kept until it is.
• Member Subscriptions: when a member joins or leaves a subscription tier, kept for 365 days.
• Link in Bio: each person's Discord account ID, saved profile and links, public page handle, publication state and click records containing only a link slug and UTC timestamp. Click records do not contain visitor IP addresses, device information, referrers or visitor account identifiers. The published page uses no analytics cookies or third-party tracking scripts. A person's page stays with their account when they leave a server. They can download their page data, avatar and aggregate click counts, or delete the page and stored click records from their personal workspace. Discord membership checks determine whether a paid server includes Premium page features for them. Free analytics show the last 28 days. Premium shows lifetime totals, a 30-day trend and aggregate CSV exports. Preserved community pages remain server-owned and follow server data deletion.
• Social Alerts: each alert’s settings (the account followed, the channel, the ping role and the message), the items already seen (the newest 1,000 per alert), and a history of the posts it made (the newest 200 per alert).
• Temporary Roles: each timed role (member, role, end time, who gave it and the reason), and the newest 200 that have ended per server.
• Server Logs: only its settings; it stores no message content. To show what an edited or deleted message said, it remembers up to 2,000 recent messages per server in memory, for at most 24 hours, and it posts log entries, which can include that text, into the log channels the server’s administrators chose.

Auto Responder triggers, sticky messages, subscription tiers and other text an administrator writes are kept as that server’s configuration. All module data is part of the server’s data: when a server removes Dubtrackr or schedules deletion, it is purged with the rest, on the schedule under Retention and deletion.

Retention and deletion

Removing Dubtrackr immediately stops that server’s background processing and starts a 30-day retention window so an accidental removal can be reversed. Reinstalling during that window cancels the pending purge and requires onboarding validation again.

A server administrator may schedule deletion in Admin > Data & Privacy. Processing pauses immediately, and the request can be cancelled for seven days. After that, the server-owned configuration, links, events, moderation, music, audit, and generated data are purged automatically.

A minimal guild identifier and deletion ledger are retained for up to 90 days to document and prevent duplicate processing. Shared provider snapshots that are not specific to one Discord server may remain as cache; Discord claims and server presentation fields are unlinked when no server still uses them.

OAuth sessions expire after at most 30 days. Operational logs and support or privacy request records are kept only as long as needed for security, response, and legal obligations. Use the support and privacy request form to request access to or deletion of personal data. Some records may be retained where required for safety, fraud prevention, disputes, or law.

Security and access

Dashboard authorization intersects current Discord membership and permissions with servers where Dubtrackr is installed. Sensitive configuration is not published. No system can promise absolute security; report concerns through Support.

Children and changes

Dubtrackr is for people permitted to use Discord under Discord’s rules and applicable law. We may update this policy as the product changes; the effective date above will change when material revisions are published.

Contact

Submit a tracked request through dubtrackr.win/support. Sign-in verifies the Discord account connected to the request.