A shared conversation.
People with access to the participating Discord channels can read forwarded messages. Images hosted by linker can be opened by anyone who has their link. Treat Global Chat as a public conversation.
●Replying to messages in Global Chat is temporarily unavailable. New chat messages still work.
See what linker stores, who can access it, how it is protected, and what happens when you delete your bot profile.
People with access to the participating Discord channels can read forwarded messages. Images hosted by linker can be opened by anyone who has their link. Treat Global Chat as a public conversation.
You must sign in to see your account data. Other dashboard users cannot view it. People who own or help manage a server can see its supported settings after Discord confirms their permission.
Support conversations and reports are available to the relevant linker team members. The operator also has access to the bot host and Cloudflare account for maintenance. These records are not public.
Discord and Cloudflare keep their own service records under their policies. The periods below describe linker's own feature storage.
Encryption makes stored information or traffic harder to read without the right access. It does not mean that only you can read everything.
The secure connection protects information travelling between your browser and the website. Cloudflare also protects connections to its dashboard database.
Cloudflare automatically encrypts its D1 databases. linker also encrypts Discord access and refresh tokens before saving them. Authorized operators can still access data for maintenance. Cloudflare's database security explanation ↗
linker does not add separate encryption to its local data files. Someone with access to the phone's bot folder can read them. Protection of the device and its accounts matters.
Global Chat message tracking lasts seven days. Server logs use the deletion period chosen by the server administrator, up to 90 days. Network incident, support, and service logs have separate retention.
The bot records startup, connection problems, command errors, and website update failures. Console output is also sent to a private Discord log channel. Reports and blocked-message logs can include the message text, detected blocked term, user, channel, and server. Support staff can read support conversations.
When an administrator enables /log setup, linker records message edits and deletions, member joins and leaves, and its own punishments in a private staff forum. Entries can contain user and channel IDs, cached message text, attachment links, staff, and reasons. Authorized staff with access to the forum can read them. These log contents are not uploaded to Cloudflare, another Discord server, or the console. The bot saves forum and post IDs and the deletion period locally. To let administrators configure logs on the dashboard, Cloudflare receives setup information, available forums, and enabled module names. It does not receive the log contents.
A deletion period is required because logs may preserve deleted messages and personal information. Automatic expiry reduces how long staff can access these records. Entries expire after the administrator-selected period of one minute to 90 days. Cleanup runs every five minutes while the bot is online; downtime, backlogs, or permission failures can delay deletion. Post headers and staff replies remain. Events missed while offline and uncached original text cannot be recovered.
Discord handles login, server access, commands, forwarded messages, emojis, and support conversations. Its own records may include account, device, and connection information. Discord decides its own retention under its privacy policy.
Cloudflare hosts the site, dashboard data, and temporary images. Its systems may record IP addresses, requested pages, timing, errors, and database usage for operating and protecting those services.
top.gg processes votes. GitLab handles source and deployments. Image, font, and other asset providers can receive ordinary request information when their content loads. If linker fetches a public-link preview, that website receives a request from the bot. Each provider has its own policies.
It removes personal bot profile fields, settings, statistics, and acceptance of the chat rules after the bot processes your request. It keeps active bans and mutes. It does not erase messages already on Discord, incident reports, support conversations, or your website sign-in account.
Changing what a button looks like in your browser does not grant permission. linker checks your sign-in and server permissions before accepting protected requests.
Login responses must match a short-lived request from your browser. Sensitive changes have additional checks to reject requests from other websites.
Deleting forwarded messages and applying Global Chat restrictions require linker's Moderator or Owner role. Ordinary server administrator status does not grant that network role.
Media downloads reject private network destinations and check redirects. Repeated dashboard requests are limited to reduce misuse. Free hosting still has daily limits; high traffic can affect availability.
The site uses HTTPS, protected sign-in cookies, encrypted Discord tokens, request checks, and fresh Discord permission verification. This page summarizes the implementation; the Privacy Policy and data-rights notice explain formal requests.