Privacy Policy

This Privacy Policy explains what information Lula (the “Bot”) collects, how it is used, who can see it, how long it is kept and which choices you have. It applies when you add the Bot to a Discord server, use its commands, buttons or menus, or take part in a giveaway that it runs. SiLuyla Development (the “Operator”, “we”, “us”) operates the Bot and is the controller of the personal data described here (in Indonesian law, the Pengendali Data Pribadi). Please read this policy together with our Terms of Service.

In short

The Bot stores only what it needs to run giveaways: Discord IDs, giveaway settings, entries and winners.

The Bot does not read the content of messages. It only receives server structure events (the “Guilds” intent) and the interactions people send to it.

We do not sell personal data, show advertising, build advertising profiles or run analytics trackers.

Finished giveaways, together with their entries and winners, are deleted automatically 30 days after they were created.

Guild settings and saved templates are deleted automatically after 30 days of confirmed departure. Before deletion, the Bot verifies through the Discord API that it is no longer a member of the Server. If verification fails, the data is preserved.

You can leave a giveaway at any time and you can ask us to delete or give you access to your data.

Definitions

Server: a Discord server (guild) in which the Bot is installed.
Administrator: a member with the “Manage Server” or “Administrator” permission in a Server.
Manager and Creator: members holding a role that an Administrator has designated, through the Bot, to manage or create giveaways.
Host: the person or label presented as the organiser of a giveaway.
Participant: a member who enters a giveaway.
Discord: Discord Inc. and its affiliates, who operate the Discord platform and its API.

Information we collect

Information about Servers and their giveaways

When Administrators, Managers or Creators use the Bot, we store the information needed to run and display giveaways:

Server ID, channel IDs and message IDs of giveaways, and the channel chosen for log messages, if enabled.
Giveaway content written by the person configuring it: prize, description, host label, embed color, the number of winners, start and end times, and the web or Discord link of any thumbnail or image. The Bot stores the link only, never a copy of the picture.
Extra-entry rules: the IDs of the roles or members that receive extra entries, the number of extra entries, and the role name or member display name shown when the rule was created.
Server settings: whether DMs to winners and hosts and logging are on, the log channel, the entry emoji, whether the captcha is required, and the IDs of the manager and creator roles.
Saved templates (name and settings) and scheduled giveaways (start time and settings).

Information about Participants and winners

Your Discord user ID and the time you entered a giveaway.
The IDs of the roles you held when you entered. They are used only to work out extra entries and are not used for anything else.
Your Discord user ID and the time you were picked, if you win.

Information about Hosts

The Discord user ID of the person who started a giveaway is stored so that the Bot can credit the Host, send the Host a direct message when the giveaway ends (if enabled) and show who made changes in the server log (if enabled).

Temporary information kept only in memory

Captcha challenges (a short arithmetic question) and their answers, discarded after a few minutes or after use.
Open editor sessions and the Discord interaction tokens needed to update them. These are discarded when you finish, cancel or stay idle for too long, and in any case when the Bot restarts.
A cache of Server, channel and role details that Discord sends to the Bot, used to display names and check permissions.

Information from Discord when you interact with the Bot

Each time you use a command, button, menu or form, Discord sends the Bot the details of that interaction, such as your user ID, the Server and channel, your roles and permissions in the Server, and what you selected or typed. We process this to carry out your request. The Bot also checks its membership status with Discord when verifying whether configuration data belonging to a departed Server can be permanently deleted. Except as described in this policy, we do not store this information.

Images you give to the Bot

If an Administrator uses /customize to change the Bot’s profile picture or banner for the Server, the image is downloaded once, sent to Discord and then discarded. It is not kept by the Bot.

Operational logs

The software that runs the Bot writes technical logs (for example errors, giveaway IDs, Server IDs and user IDs related to a failure) to help us find and fix problems. They are kept only for as long as needed for troubleshooting.

Information we do not collect

The content of messages sent in your Server and the content of direct messages sent to you by other people.
Email addresses, real names, phone numbers, payment details, precise location, IP addresses or device identifiers of users.
Any information used for advertising, cross-site tracking or sale to data brokers.

How we use information

To create, display, update, end, reroll and delete giveaways, and to select winners at random among the recorded entries.
To apply extra entries, the captcha, and the permission levels set by Administrators.
To announce results, send direct messages to winners and Hosts when the Server has enabled them, and post events to the log channel when it is enabled.
To verify the Bot's membership in a Server before permanently deleting expired Server settings and saved templates.
To start scheduled giveaways and to apply saved templates.
To keep the Bot secure, prevent abuse and enforce the Terms of Service.
To diagnose problems, maintain and improve the Bot, and to comply with legal obligations.

Winners are chosen by a random process among the entries that exist when the giveaway ends. We do not make decisions about people based on profiling.

What other people can see

Everyone who can see the giveaway message sees the prize, the Host, the end time, the number of winners and the entry count. After the giveaway, the announced winners are mentioned in the channel.
Anyone who clicks the “Participants” button on a giveaway, as well as Managers who use the participant command, can view the participant list containing Discord mentions and entry counts. The list is displayed privately only to the user who requests it. Each user can only view their own winning probability percentage and cannot view the winning probability percentages of other participants.
Administrators and Managers of a Server can see the giveaways, templates, schedules and settings of that Server.
The Server’s log channel, if an Administrator enables it, receives messages when giveaways are created, edited, ended, rerolled or deleted. Anyone with access to that channel can read them.
Winners and Hosts may receive a direct message from the Bot with the prize, the Server name and a link to the giveaway.

Giveaway data is separated by Server: the Bot never shows one Server’s giveaways, settings or templates to another Server.

Legal bases (where data protection law requires them)

Where data protection laws apply, such as the GDPR or Indonesia’s Personal Data Protection Law (Law No. 27 of 2022, “UU PDP”), we process personal data because (a) it is necessary to provide the Bot to the Servers and people who use it, which is our legitimate interest and, for Administrators, part of the service they request; (b) it is necessary to keep the Bot secure and prevent abuse, which is our legitimate interest; (c) we must comply with a legal obligation; or (d) you have given consent, for example by entering a giveaway. You may object to processing based on legitimate interests as described in section 9.

We do not sell or rent personal data. We share it only in these situations:

With Discord, because the Bot works through the Discord platform. Discord handles messages, mentions and interactions under its own Privacy Policy (discord.com/privacy).
With our hosting provider, which stores the database and runs the Bot on our behalf, under appropriate confidentiality and security terms.
When required by law, such as a valid court order, or to protect the rights, safety and property of people, Servers, the Operator or the public.
In a business transfer, such as a merger or the transfer of the Bot to a new operator, in which case this policy continues to apply to the transferred data until updated notice is given.

Storage, location and security

Data is stored in a database on infrastructure operated by us or our hosting provider. We protect it with measures that include keeping the Bot’s access token secret, limiting administrative access, using encrypted connections to Discord, and keeping the software up to date. No system is perfectly secure, so we cannot guarantee absolute security. If we become aware of a breach affecting your personal data, we will notify the people and authorities required by applicable law within the time it requires.

How long we keep data

We keep data only as long as it is needed for the purposes above, as follows.

Data	Kept until
Active giveaway (settings, entries, role IDs at entry)	The giveaway ends, or it is deleted by a Manager, whichever comes first.
Finished giveaway, its entries and winners	Deleted automatically 30 days after the giveaway was created. Deleting a giveaway removes it and its entries immediately.
An individual entry	You press “Leave giveaway”, the giveaway is deleted, or the automatic deletion above happens.
Templates	A Manager deletes them, or we remove them on request.
Scheduled giveaways	The giveaway starts, a Manager deletes the schedule, or we remove it on request.
Server settings (roles, emoji, DM and log options)	A Server changes or resets them, or we remove them on request. If the Bot leaves or is removed from a Server, its settings and saved templates are retained for at least 30 days. After that period, we verify the Bot's membership through the Discord API before deleting them. If the Bot is still a member, the settings are restored. If verification fails, the data is preserved until verification can be completed.
In-memory data (captchas, editor sessions, caches)	A few minutes after last use, and always when the Bot restarts.
Operational logs	Only as long as needed for troubleshooting.
Backups, if any	Overwritten in the normal backup cycle after deletion from the live database.

Your rights and choices

Controls you have in Discord

Participants: press “Leave giveaway” to remove your entry. You can also choose not to enter.
Administrators and Managers: delete giveaways, templates and schedules; turn DMs and logging off with the Bot’s commands; change or clear manager and creator roles; remove the Bot from the Server at any time.
Anyone: turn off direct messages from server members in Discord’s privacy settings. The Bot then cannot message you, and will not retry.

Requests to us

Depending on where you live, you may have the right to access the personal data we hold about you, correct it, have it deleted, restrict or object to its processing, receive it in a portable format, and withdraw consent at any time. This includes the rights of data subjects under the UU PDP. California residents may also ask what categories of personal information we collect and disclose; we do not sell or share personal information for cross-context behavioral advertising. To make a request, contact us at [email protected] or through https://discord.gg/WMts5cSauh. To find your data we need your Discord user ID and, where relevant, the Server. We may need to verify that the request comes from the account holder. We will respond within the time required by applicable law and, where the law sets no period, within 30 days. We will not charge a fee unless requests are clearly excessive. If you are unhappy with our response, you may complain to your local data protection authority.

Children

The Bot is available only to people who meet Discord’s minimum age requirement, which is at least 13 years or older where local law sets a higher age. It is not directed at children under that age and we do not knowingly collect their data. If you believe a child has provided personal data to the Bot, contact us and we will delete it. Hosts are responsible for ensuring that their giveaways are appropriate for the age of their audience.

International transfers

Discord and our hosting provider may process data in countries other than your own. Where we transfer personal data out of the EEA, the UK, Indonesia or other regions with transfer restrictions, we rely on appropriate safeguards required by the law that applies.

Third-party services

The Bot runs on Discord. Links in giveaways, such as a prize page or an image, lead to services we do not control. Their privacy practices are their own, and we encourage you to read their policies before you provide information to them.

Changes to this policy

We may update this policy from time to time, for example when the Bot gains new features. We will change the effective date above and, for significant changes, announce them in the support server or through the Bot before they take effect. Continued use of the Bot after a change means you accept the updated policy.

Contact

SiLuyla Development
Email: [email protected]
Support: https://discord.gg/WMts5cSauh

Appendix A. Permissions the Bot requests and why

The Bot asks for the following when it is invited. Server Administrators can change permissions at any time in Discord.

Permission or scope	Why it is needed
applications.commands	Lets people use the Bot’s slash commands.
View Channel, Send Messages, Send Messages in Threads, Use External Emojis, Embed Links	Post, edit and delete the giveaway message and the result announcement in the channel chosen for a giveaway.
Read Message History	Locate and update the Bot’s own giveaway message.
Change Nickname	Only used by the /customize command, to change the Bot’s own nickname in your Server.
Guilds Intent	Receive Server, channel and role information so the Bot can show names and check access. The Bot does not request the Message Content, Server Members or Presence intents.