Exyliacommunity

Exylia Community

Privacy Policy

Last updated: November 4, 2026

How Exylia Community handles the data of the people who use the dashboard and of the Discord users who join, leave or boost servers that use the bot. We do not sell data or show ads, and analytics run only if you accept them.

1. Who we are and what this policy covers

Exylia Community (the "Service") is a set of free community tools for Discord servers (announcements, welcome, leave and boost messages and related features), made of the Exylia Community Discord bot (and the custom bots Customers connect to it), the dashboard at community.exylia.net and the programming interfaces that connect it with other Exylia apps. It is operated by Cristobal Aranda, a natural person domiciled in Chile ("we", "us"). Contact: [email protected].

We handle personal data in two different roles:

  • As controller, for the people who sign in to the dashboard ("Users": server owners and their team) and for visitors of our website. Section 2 and sections 5 to 13 describe that processing.
  • As processor, for the Discord users the bot handles in a server that uses it ("Members": people who join, leave or boost the server, and people the Customer mentions in the messages it designs). The owner of each workspace (the "Customer") decides to use the bot in its server and is the controller of that data; we process it only on the Customer's instructions under our Data Processing Agreement. Sections 3 and 4 describe it in full so Members and Customers can see exactly what happens.

If you are a Member and want to exercise your rights over data a server holds about you, contact that server first: it decides what is kept and for how long. If you write to us instead, we will pass your request on to the server and help it answer.

2. Data about Users of the dashboard

We collect only what the Service needs to work:

  • Discord account: when you sign in with Discord we request the "identify" and "guilds" scopes. We store your Discord user ID, your username and the address of your avatar. We never receive your email address or your password. The "guilds" scope gives us the list of servers you are in and your permissions there; we read it only to show the servers you can manage when you add one, and we do not store the list.
  • Login sessions: a random session token, stored on our side only as a SHA-256 hash, with its creation and expiry dates, and the Discord access token of that login, encrypted with AES-256-GCM, so we can list your servers when you add one. We do not store your IP address or browser with the session.
  • Workspace data: the workspaces you create or join, your role and permissions, the invitations you create or accept, what you configure (servers, announcements, welcome, leave and boost messages, templates, integrations) and what you write and upload in the dashboard (texts, links and images of your messages). Changes you make are recorded in the workspace's audit log with your account.
  • Usage counts: for members of a workspace, how many times per day each section of the dashboard was opened (for example "announcements" or "settings"), used to understand which parts of the Service are used. These counts do not record the pages' content or your clicks.
  • Analytics, only if you accept them in the cookie banner: Google Analytics and Microsoft Clarity measure how the site and the dashboard are used, as described in section 6.
  • API usage: for each API key, the number of requests per day, when it was last used and the IP address of the last request.
  • Communications: the messages you send us by email and our replies.
  • Technical data: when you visit our site, our network provider and our servers process your IP address, browser user agent and the requested URL to deliver the page, protect the Service against abuse and diagnose errors.

We do not use the dashboard to profile you, we do not run advertising on it, and we do not sell or rent personal data.

3. Discord data processed for Customers

The bot connects to Discord with the Guilds gateway intent and, where the Customer's application has been granted them, the privileged Server Members intent (to see members joining, leaving and boosting) and the Message Content intent. It does not use the Presence intent: it never sees your online status or activity. The bot does not store or process the messages members write in the server's channels. What the bot does with what it receives:

  • Member events: when someone joins, leaves or boosts a server where the Customer turned the matching message on, the bot receives the member's Discord user ID, username, display name, avatar address and the server's member count, and uses them to fill the Customer's message (for example a welcome with the member's name).
  • Direct messages: if the Customer enables a welcome DM, the bot sends the newcomer that message. The bot does not store replies to it.
  • Messages the bot posts: the text, images, links and buttons the Customer designs, the channel and message IDs of what was posted, its schedule and state (draft, scheduled, posted, failed), and who in the Customer's team created or last edited it. The files themselves are those the Customer links or uploads in the dashboard.

Roles on join: if the Customer sets roles to give on join, the bot assigns them to the newcomer through Discord.

Customers must not put sensitive data (health, political opinions, religion, sexual orientation and the like), passwords or payment card data into the messages they design.

4. Messages and designs

Everything the Customer designs in the dashboard is stored with its workspace so the bot can post, edit and delete it. In particular:

  • Drafts and posted messages are kept as the Customer wrote them, with the variables (such as the member's name) the Customer used. When a message is posted the bot fills the variables with Discord data described in section 3.
  • Scheduled messages are posted by a background job at the chosen time. Failed jobs are retried and their last error is kept for up to 30 days so the Customer can see it.
  • We do not read your messages to profile members or to train any model, and no language model or automated decision-making is applied to them.

The preview in the dashboard is drawn in your browser from the same message data the bot sends; it does not contact Discord.

5. Why we use the data and on what legal basis

  • To provide the Service you signed up for: sign-in, workspaces, permissions and the features you use. Basis: performance of a contract (GDPR art. 6.1.b) and, in Chile, the contractual relationship and your consent given when you sign in (Law 19.628, arts. 4 and 20).
  • To keep the Service secure and working: preventing abuse, rate limiting, error diagnosis, the audit log and backups. Basis: our legitimate interest in running a secure service (GDPR art. 6.1.f).
  • To understand which parts of the dashboard are used and improve them (the daily usage counts). Basis: our legitimate interest in improving the Service; the counts identify no one outside our platform administration and are never used for advertising.
  • To measure how the site and the dashboard are used and improve them with Google Analytics and Microsoft Clarity (usage statistics, session recordings and heatmaps), only if you accept them. Basis: your consent (GDPR art. 6.1.a; in Chile, your consent under Law 19.628 and Law 21.719), which you can withdraw at any time from the "Cookies" link in the footer without affecting the processing before it.
  • To answer your requests and communicate changes to these terms. Basis: performance of a contract and legitimate interest.
  • To comply with legal obligations and respond to lawful requests from authorities. Basis: legal obligation (GDPR art. 6.1.c).
  • Member data: we process it only to provide the Customer with its community tools. The Customer is responsible for having a legal basis (usually its legitimate interest in welcoming and informing its community, or consent where required) and for informing its Members.

6. Cookies and local storage

The site uses cookies that are strictly necessary for it to work or that remember choices you made and, only if you accept them in the cookie banner, analytics cookies from Google Analytics and Microsoft Clarity. There are no advertising cookies. Nothing is loaded and no analytics cookie is set until you choose.

  • exylia_consent: remembers whether you accepted or rejected analytics, for every Exylia site (it is set on .exylia.net). 180 days. Strictly necessary.
  • __Host-ext_session: keeps you signed in. 30 days, renewed while you use the dashboard. Strictly necessary.
  • __Host-ext_oauth: protects the Discord sign-in against forgery. 10 minutes. Strictly necessary.
  • __Host-ext_connect: protects the connection of another Exylia app to your workspace. 10 minutes. Strictly necessary.
  • NEXT_LOCALE: the language you chose. 1 year. Preference.
  • ext_rail, ext_adv and ext_notice: remember the sidebar state, the open "Advanced" section and dismissed announcements. 1 year. Preference.
  • The theme (light or dark) is kept in your browser's local storage and never leaves your device.

Analytics cookies, set only if you accept them:

  • _ga and _ga_<id> (Google Analytics 4, Google LLC): tell visits and visitors apart. 2 years.
  • _clck (1 year), _clsk (1 day), CLID (1 year) and MUID (1 year) (Microsoft Clarity, Microsoft Corporation): tell visits and visitors apart and join the pages of one session.

If you accept, Google and Microsoft receive the pages you visit (the URL path and the page title), the page you came from, your device, browser and operating system, your screen size, an approximate location they derive from your IP address, and your clicks and scrolls. Clarity also records sessions and builds heatmaps, with the text inside the dashboard masked, so recordings do not show message designs or workspace content. Page addresses and titles may include workspace or server names and Discord user IDs. Analytics never load on invitation links, because their address works as a password. Google Analytics runs with advertising features and Google Signals off (advertising storage, advertising user data and ad personalisation denied). Google Analytics data is kept for 14 months and Clarity recordings for 30 days.

You can change your choice at any time with the "Cookies" link in the footer. Rejecting after accepting deletes the analytics cookies and reloads the page. The choice applies to every Exylia site.

Discord avatars, server icons and some attachments are loaded by your browser directly from Discord's servers (cdn.discordapp.com), which receive your IP address when they do.

7. Who receives the data

We run the Service and its database on our own servers. We share personal data only with the providers needed to run it, each bound by its own data protection terms:

  • Discord Inc. (United States): the bot works inside Discord, so everything it posts also lives on Discord under its own privacy policy; sign-in with Discord.
  • Cloudflare, Inc. (United States; global network): DNS, TLS and network protection. All traffic to community.exylia.net passes through Cloudflare.
  • Google LLC (United States), only if you accept analytics: Google Analytics 4 measures visits to the site and the dashboard. It receives the data described in section 6.
  • Microsoft Corporation (United States), only if you accept analytics: Microsoft Clarity records sessions and heatmaps, with the dashboard's text masked. It receives the data described in section 6.

We may disclose data when required by law or by a court or competent authority, and to defend our legal rights. Customer team members see the data of their own workspace according to the permissions the Customer grants them. Customers can also connect other Exylia apps to their workspace; those apps receive only what the Customer approves in the connection and are the Customer's responsibility.

8. How long we keep data

  • User account: until you ask us to delete it by writing to [email protected]; we do so within 30 days. Accounts that own a workspace are deleted together with it or after it is handed to someone else.
  • Login sessions and the Discord access token stored with them: until they expire (30 days without use); expired sessions are deleted every day. Signing out revokes the session at once.
  • Workspace and Member data (announcements, greeting messages, templates, their designs and posting history, audit log, usage counts): while the workspace exists. There is no automatic expiry: removing the bot from the server stops all new processing but does not erase what was stored. When a workspace is deleted, everything listed here is deleted with it.
  • Workspaces never used (the bot never joined, no posted messages, nobody but the owner) are deleted automatically a week after they were created.
  • Failed background tasks: 30 days.
  • Records of actions taken by our platform administrators (for example suspending or deleting a workspace) are kept for accountability, including after the workspace is gone.
  • Analytics, only if you accepted them: Google Analytics data for 14 months and Clarity recordings for 30 days, in Google's and Microsoft's systems; the cookies for the periods listed in section 6.
  • Emails with us: as long as needed to handle the matter and for up to 2 years afterwards, unless the law requires longer.

Backup copies, where they exist, are rotated and overwritten within 30 days, so deleted data disappears from them within that period.

9. International transfers

Our servers are in Chile, and the providers in section 7 are in the United States. Discord itself processes all messages in the United States. When data from the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (incorporated in our Data Processing Agreement for Customers) and on our providers' own safeguards, such as the EU-U.S. Data Privacy Framework or their Standard Contractual Clauses. Google LLC and Microsoft Corporation, which receive analytics data only with your consent, are certified under the EU-U.S. Data Privacy Framework.

10. Security

We protect data with measures appropriate to the risk, including:

  • Encryption in transit (HTTPS/TLS) for all traffic to our site and between the bot and Discord.
  • Secrets (custom bot tokens, Discord access tokens, connected-app keys) encrypted with AES-256-GCM under keys derived per workspace or purpose.
  • Session, invitation and API key tokens stored only as hashes; sign-in through Discord OAuth with PKCE.
  • A database not exposed to the internet and reachable only from the Service's own containers.
  • Strict separation of each Customer's data by workspace, role-based permissions within each workspace, and an audit log of changes.
  • Connections to other apps configured by Customers are blocked from reaching private network addresses.

No system is completely secure. If a personal data breach occurs, we will notify affected Customers without undue delay, and the competent authority and affected people where the law requires it.

11. Your rights

Depending on where you live, you have the right to access your data, rectify it, erase it, restrict or object to its processing, receive it in a portable format and withdraw any consent you gave, without affecting earlier processing. In Chile, Law 19.628 grants the rights of access, rectification, cancellation and blocking, and from Law 21.719 taking effect also objection, portability and the right not to be subject to automated decisions.

To exercise them, write to [email protected] from a channel that lets us confirm your identity (we may ask you to confirm through your Discord account). Members should address the server first, as explained in section 1. We will answer without undue delay and within the time the applicable law allows (under the GDPR, one month, extendable where necessary).

You can complain to a data protection authority: in the European Union, the authority of your country of residence or work; in Chile, the Personal Data Protection Agency created by Law 21.719 once it is operating, or the courts under Law 19.628. We would appreciate the chance to resolve your concern first.

12. Minors

The dashboard is intended for people who are at least 18 years old or of legal age where they live.

Many Discord communities include minors. The bot does not ask for or record anyone's age, and we never use Member data for advertising or profiling. Customers whose servers are aimed at minors must assess their obligations, including parental consent where the law requires it.

13. Changes and contact

We will update this policy when the Service or the law changes, and show the date of the latest version at the top. If a change materially affects how we use personal data, we will announce it in the dashboard at least 30 days before it applies.

Questions or requests: [email protected].