Privacy Policy
Information about the data collected by the Rilum application.
This Privacy Policy describes how RILUM collects, uses, and protects your personal data when you use our Discord bot and website services. By using our services, you agree to the collection and use of information in accordance with this policy.
- Bot
- Rilum#2692 (ID: 1418038523491258378) on the Discord platform.
- Service
- The website available at https://rilum.me/.
- Discord
- An application owned by Discord Inc.
- User
- Any person using the Bot or the Service.
- GDPR
- Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.
1. Service
We process the following data necessary for the functioning of the Service:
- List of Discord servers where the User is present;
- User's username, identifier (ID), and link to the profile picture;
- Date of the last login to the Service.
This data is deleted after 3 months from the last login or upon logout from the Service. The processing of this data is justified according to Art. 6(1)(f) of the GDPR and arises from the necessity of processing data for user identification.
2. Bot
When you use the Bot, we process data from your Discord account, such as nickname, ID, and avatar. Processing of this data is justified based on your consent (Art. 6(1)(a) of the GDPR). Your data will be stored for a period of two years from the date of submission.
3. Chat
When contacting through chat (support, commands that send messages to us), we process the information provided in the message content. Processing of this data is justified based on your consent (Art. 6(1)(a) of the GDPR) and is aimed at providing you with support. Messages and related logs are stored for 2 years from the start of the conversation.
4. Other Data
The Administrator also collects and processes other technically necessary information to provide services, such as data about servers where the Bot was added or configuration values set by users. According to Art. 4(1) and Recital 26 of the GDPR, these do not always constitute personal data and therefore are not detailed here; consent is not collected for their processing where legally not required.
The Service uses Cookies stored on the User's device. Some cookies (required cookies) are necessary for the proper functioning of the Service and may be stored automatically (without the User's consent). These include files responsible for saving user session data. The legal basis is Art. 5(3) of Directive 2002/58/EC on privacy and electronic communications and Recital 66 of Directive 2009/136/EC. Other cookies (functional and analytical) are stored only after the User's consent expressed by clicking the appropriate button in the consent window displayed after loading the Service. The User can also manage cookies via browser settings.
Each User has the right to:
- access their personal data (Article 15 GDPR);
- request the deletion of their personal data (Article 17 GDPR);
- object to the processing of their personal data when processed for the purposes of the legitimate interests pursued by the Controller (Article 21 GDPR);
- request restriction of processing of their personal data (Article 18 GDPR);
- withdraw consent to the processing of their personal data if processing is based on consent (Article 7 GDPR);
- data portability (Article 20 GDPR);
- rectification of their personal data (Article 16 GDPR);
- file a complaint with the supervisory authority (e.g. President of the Personal Data Protection Office in Poland, UODO).
To exercise these rights, please contact the Administrator (details below). Note that fulfillment of these rights may be subject to conditions provided by applicable law.
Contact with support team is possible by email: [email protected] or on the support server: Discord Server.
This Privacy Policy may be updated. The current version is available at the Service URL. Changes will be published on the Service and become effective on the date indicated in the updated document.
Version: 1.0
Effective date: October 20, 2025
If anything is unclear, please reach out via the contact method you usually use with RILUM. We're here to help.