Privacy
Reviewed 11 September 2026
Linky is a Discord bot operated by Victor Ivanov. This policy describes the hosted Linky bot. If you run the open-source software yourself, your hosting and data-handling choices apply to that instance.
Messages and attachments
Discord sends Linky messages and metadata from channels the bot can access. Linky checks whether link fixing is enabled before processing a message for reposting. It uses message text, links, author IDs, reply references and attachment details to create a replacement with attribution. It also receives command and permission information when someone uses /help or /setup.
Message text, translated text and copied attachments are handled in the bot's memory. Discord's client library can also cache messages in memory while the bot runs. Linky does not create a separate message archive or store copied attachments as files on its host.
Replacements, copied attachments and translation files are sent back to Discord. They remain Discord messages until deleted and are subject to Discord's own storage and privacy practices. The original message is deleted only after Linky's replacement checks succeed. Sending and deleting are separate requests, so an error can leave both messages visible.
Saved server settings
Linky stores a Discord server ID and its administrator's enabled or disabled choice in a settings file so the choice survives restarts. The operator can also configure server and channel IDs for existing restricted installations.
Disabling Linky stops reposting in that server; it does not erase the saved setting. Removing the bot does not automatically erase the setting either. Contact the operator if you want stored configuration reviewed or removed.
Operational logs
The hosted bot writes operational logs to help diagnose failed replacements, permissions and connection problems. They include timestamps, server and channel IDs, original and replacement message IDs, and error details. Startup logs can include configured server and channel IDs.
Routine success logs do not include message text or attachment bodies. Some Discord errors can include details of the failed request, including message text, links or attachment data. Those details can therefore appear in error logs.
Current Docker logs rotate by size, with up to three files of about 10 MB each per container. This is not a fixed retention period in days; how long a record remains depends on logging volume and container operation. No fixed age-based expiry is configured for these logs.
Preview and translation services
Linky changes supported links to preview-service URLs: fixupx.com for X, www.instagram7.com for Instagram and tnktok.com for TikTok. Some translated media uses g.fixupx.com. Discord or your client may request these URLs to display or open a preview, and those services process the requested post URL under their own practices.
When English tweet translation is enabled, Linky sends the tweet's status ID to the FxEmbed API at api.fxtwitter.com and requests an English result. That request does not include your surrounding Discord message, Discord account ID or server ID. The API returns the post's text, author details and media references for Linky to display. The service can see the bot host's network request information.
Linky downloads attachments from the URLs provided by Discord when copying a message and uploads the copies to Discord. The bot runs on a Hostinger-hosted server. Discord, the hosting provider and preview services have their own infrastructure and privacy practices, which this policy does not replace.
Analytics
The deployed bot described by this policy does not send a separate product-analytics event stream. Operational logs and saved server settings still exist as described above. A future analytics feature will be described here when it is introduced.
This website
This website records daily page-view and invite-button counts, grouped by page and a broad source category such as Google, ChatGPT or GitHub. These counts are not unique people and do not connect a visit with a Discord installation. Linky's measurement code does not set cookies, create visitor IDs or store full referrers, IP addresses or user agents. It honors Do Not Track and Global Privacy Control.
This website is hosted on Vercel. Its measurement requests pass through Vercel to an existing collector hosted through OpenAI Sites on Cloudflare. Linky forwards only the measurement event, without browser cookies, IP addresses, user agents or full referrers. These hosting providers have their own technical request processing and logging. Linky's database uses a 90-day reporting window. Expired rows are removed on the next measurement, report or maintenance operation; an idle database may retain expired rows until that operation. No fixed hosting-log or backup expiry is claimed here.
The separate bot-event collector is implemented for a future rollout, but the hosted bot currently sends no events to it. Public rollout will update this policy to describe its pseudonymous server keys and operator controls.
Your choices and requests
An administrator with Manage Server can run /setup enabled:false to disable Linky for the entire server. Administrators can also restrict channel access or remove the bot. /help reports whether link fixing is enabled in the current channel.
For privacy questions or deletion requests, email victor.n.ivanov@gmail.com. Include the server ID and a short description of the request. The operator may need to confirm that you are authorized to make a request for that server. Do not send bot tokens or unnecessary private messages.
Deleting a stored setting does not delete messages already sent to Discord. Requests involving Discord messages, accounts or provider-held data may also need to be made through the relevant service. The operator will explain what can be removed from Linky's own systems and any limits affecting the request.
General, non-sensitive bugs can be reported in GitHub issues. Issues are public; use email for private information and security reports.
Policy changes
This page will be updated when Linky's data handling changes. The date at the top identifies the version you are reading.