This is Lublox's privacy policy, which should detail the data stored and how it is used or shared. This page is supposed to be updated, but might not.

The Lublox services are hosted at Hetzner (in Germany), and some requests goes through Cloudflare for proxying. Saves are sometimes uploaded to GitHub. The data files now are encrypted.
The website owner can access the stored data and log incoming data for various reasons such as testing, helping, and applying the terms of service. Whoever has access to these are supposed to not share informations that the user(s) didn't consent to share.
There may be automated ways to delete some data, but if not, you can ask the website owner (Lulu5239) using any way you find, such as the requests page (almost not read), an e-mail to deletion@lublox.xyz (if Gmail doesn't consider it as spam), or through social medias.

Accounts
Various informations are saved based on how you use the Lublox services. The informations that always are saved are the account username, the used IP addresses, and the valid cookies to use the account.
Login to see which informations are stored on your Lublox account.
Some data about Lublox accounts are displayed on your profile, you can look at others' profiles to see. Private data about users is not being sold.

The Discord bot (Grand robot)
Users using the bot's slash commands gets a sort of account automatically created, to save informations (such as settings and cooldowns for the /cooldowns) without having to create a Lublox account. Something similar also exists for servers, to save for example the gaming channels, the users who used the /no_ping command, and the list of gaming channels and their settings.
Messages may be read by the bot (like in gaming channels) but should not be stored after being processed. Processing messages can refer to detecting if it is a command (the prefix is ::) and seeing if it is another bot's response to a command then updating the user's cooldowns.
Lublox has a service named Discord Bot View which can be used to view Discord as a bot. When the bot gets verified, the website developer will make an update so viewing Discord as the bot Grand robot hides the servers that didn't enable the human intelligence feature (with the command /settings hi) with the exception of servers where the managers seemed to appreciate the bot talking, and the big Discord Bots server; you can use the command to disable it. This service only saves the token of bots when they are entered by a website administrator, else they are deleted 30 minutes after the token has been entered (or when pressing the "Stop using token" button).
Bots can use a variant of the page https://discord.lublox.xyz/onlinify? as interaction endpoint API. That feature does not log anything (except for a secret command with the auto-complete that only logs the interaction, only usable by the website administrator). Entering :id; in the option of the /ping command (usually created when using the "Replace slash commands" button in Discord Bot View) may leak the time of the last ephemeral posted by the bot in the channel.
If you want the bot to ignore your messages (except when server settings, such as the voting channels feature, forces something for the channel), type/use the command /autocomplete_test text::ignore true; . If you want to delete some data you've given through Discord, send ::delete, select an option, press the button, and do it again for each thing you want to delete.
When kicking the bot out of a server, it takes between one and two days for the data related to that server (at least the server ID, possibly settings) to be deleted.
There is a Discord server from which you can contact the developer.
Various bots (such as NetherBot, GDC game (copy) and Online detector) are fragments of Grand robot, they are hosted at the same place with the same data. These bots doesn't read messages, you will need to use Grand robot's ::delete command to delete data.

This privacy policy (and the Terms of service) can be updated without notification, you may check for updates.