Privacy Policy

1. Who we are and what this policy covers

Exylia Link (the "Service") links Minecraft accounts to Discord accounts for Minecraft servers and networks. It is made of the dashboard and public link pages at link.exylia.net, the plugin gateway at link-gateway.exylia.net, the ExyliaLink server plugin (the "Plugin") and the Exylia Link Discord bot (the "Bot"). 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 everyone who signs in with Discord on link.exylia.net ("Users": network owners and staff on the dashboard, and players who link their account on a network's link page) and for visitors of our websites. Sections 2 and 4 to 12 describe that processing.
• As processor, for the players and Discord members of each network that uses the Service. The owner of each network (the "Customer") decides to link its players' accounts and what to do with the links, and is the controller of that data; we process it only on the Customer's instructions under our Data Processing Agreement. Section 3 describes that data in full, so that players and Customers can see it.

If you are a player and want to exercise your rights over your link on a network, contact that network first: it decides what is collected and why. If you write to us instead, we will pass your request on to the network and help it answer.

2. Data about Users who sign in

We collect only what the Service needs to work:

• Discord account: when you sign in with Discord we receive your Discord user ID, your display name and the address of your avatar, and we keep them in your account. We request the scopes "identify" and "guilds". We never receive your email address, your password or your messages.
• Your Discord servers: the "guilds" scope lets us read the list of Discord servers you are in, with each server's name, icon and your permissions there. We use it only to show the servers you own or manage when you create a network or add a server to it, and we store only the servers you add (their ID and name). To do this we keep the Discord access token of your sign-in, encrypted with AES-256-GCM, together with your login session; it is used for nothing else and is deleted with the session.
• Login sessions: a random session token, stored on our side only as a hash, with its creation and expiry dates. We do not store your IP address or browser with the session.
• Network data, if you run a network: the networks you create or join, your role and permissions, the invitations you create or accept, the settings, reward rules, webhooks and API keys you configure, and a log of the actions you take in each network (the audit log). For each API key we record when it was last used and the IP address of the system that used it.
• Communications: the messages you send us by email and our replies.
• Technical data: when you visit our sites, 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 an external error-monitoring service.
• Usage analytics, only if you accept them in the cookie banner: Google Analytics and Microsoft Clarity receive the pages you visit (URL path and title), the referring page, your device, browser and operating system, your screen size, an approximate location that they derive from your IP address, and your clicks and scrolls. Clarity also records sessions and heatmaps; all text inside the dashboard panels is masked, so recordings never show network, player or Discord data. Page addresses and titles may include the name of a network. If you reject or ignore the banner, none of this is collected.

We do not run advertising, we do not use your data for advertising profiles, and we do not sell or rent personal data.

3. Player and Discord member data processed for Customers

For each network, the Service processes the following on the Customer's behalf:

• Minecraft identity and presence: the Minecraft UUID and username of each player who joins a server of the network, as reported by the Plugin; whether the player is online and on which server or proxy; when the player was first and last seen and on which server; and the player's LuckPerms groups (primary first). The Plugin does not send players' IP addresses, chat or commands to the Service.
• Links: which Minecraft UUID is linked to which Discord user ID, how the link was made (code in game, code in Discord, the web link page, an import or by staff), when it was made and removed, who removed it, and the Discord username known when it was made, which the Plugin can show in game. Removed links are kept as history, which enforces the network's relink waiting time and lets staff see past links.
• Linking codes: short single-use codes bound either to a player's UUID and username or to a Discord user ID and username. They are valid for 2 to 60 minutes, as the network chooses (10 by default).
• Discord bot interactions: when someone uses the Bot's /link, /unlink or /whois commands or its buttons in a server of the network, the Bot receives that person's Discord user ID, username, permissions and the options they typed. When someone sends the Bot a direct message, the Bot reads its text only to find a linking code in it; the message is not stored. To decide which network a code sent by direct message belongs to, the Bot may check whether the sender is a member of the network's Discord servers.
• Discord sync and rewards, only where the Customer turns them on: the Bot receives events when members join a server of the network or when their roles or Server Boost change, and once a day reads the member list of those servers. From each member's Discord user ID, username, nickname, roles and boost start date it computes, in memory, which roles and nickname the member should have (for example a "verified" role, a role per LuckPerms group, or a nickname built from the Minecraft name) and which rewards apply. It stores none of the member data it reads: it writes only the result, which is the role or nickname change made in Discord, the rewards granted and a per-run summary with counts and up to 100 Discord user IDs it could not update, with the reason.
• Rewards: when a reward rule fires (first link, a Server Boost, a role), a record of the grant with the player's UUID, Minecraft username, Discord user ID, the server commands to run, the server it ran on and its delivery status.
• Imports: links imported from DiscordSRV through the Plugin or from a CSV file uploaded by staff (pairs of Minecraft UUID and Discord user ID), with the totals of each import and up to 100 pairs that could not be imported.
• Audit log: who linked or unlinked which account and how, including the Minecraft UUID and Discord user ID involved and the Discord user ID of the person who acted.

We do not call Mojang or Microsoft services: Minecraft usernames and UUIDs come only from the network's servers, which receive them from Minecraft's own login. Except for linking codes and the internal queue (section 7), the data in this section is kept while the network exists, unless the Customer has it erased sooner.

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

• To provide the Service you signed up for: sign-in, networks, permissions, linking your accounts and the features you or the network 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 linking attempts, error diagnosis and backups. Basis: our legitimate interest in running a secure service (GDPR art. 6.1.f).
• 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).
• To measure and improve the Service with usage analytics and session recordings (Google Analytics and Microsoft Clarity), 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.
• Player and Discord member data: we process it only to provide the Customer with the linking, sync and reward features it configures. The Customer is responsible for having a legal basis (usually the player's own request to link, and its legitimate interest in running and moderating its community) and for informing its players and members.

We do not make decisions that produce legal or similarly significant effects on anyone solely by automated means. Roles, nicknames, rewards and in-game requirements follow rules that the Customer sets and can change at any time.

5. Cookies and local storage

The Service uses cookies that are strictly necessary for it to work or that remember choices you made, and, only if you accept them, analytics cookies. There are no advertising cookies. Nothing other than the strictly necessary and preference cookies is set before you choose in the cookie banner, and Accept and Reject are equally easy.

• exylia_consent: remembers whether you accepted or rejected analytics cookies, for every Exylia site (*.exylia.net). 180 days. Strictly necessary.
• __Host-elk_session: keeps you signed in. 30 days, renewed while you use the Service. Strictly necessary.
• __Host-elk_oauth: protects the Discord sign-in against forgery. 10 minutes. Strictly necessary.
• elk_reveal: shows a newly created secret (for example an API key) once, on the page that created it. 2 minutes. Strictly necessary.
• NEXT_LOCALE: the language you chose, shared with the other Exylia sites. 1 year. Preference.
• elk_rail and elk_adv: remember whether the sidebar and its advanced section are collapsed. 1 year. Preference.
• The theme (light or dark) and some folded sections are kept in your browser's local storage and never leave your device.

Analytics cookies, set only if you accept them:

• _ga and _ga_<id> (Google Analytics, Google LLC): distinguish visitors and sessions to count visits. 2 years.
• _clck and CLID (Microsoft Clarity, Microsoft Corporation): identify the browser across visits for usage statistics and recordings. 1 year.
• _clsk (Microsoft Clarity): groups the pages of one session in a recording. 1 day.
• MUID (Microsoft): identifies the browser for Microsoft's services used by Clarity. 1 year.

Google Analytics runs with advertising storage, ad user data and ad personalisation denied and without Google Signals; Clarity runs with advertising storage denied. You can change or withdraw your choice at any time with the "Cookies" link in the footer of every page; withdrawing deletes these cookies and reloads the page without the analytics scripts. Your choice applies to every Exylia site.

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

6. Who receives the data

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

• Cloudflare, Inc. (United States; global network): DNS, TLS and network protection. All traffic to link.exylia.net and link-gateway.exylia.net, including the connections of the Plugin, passes through Cloudflare.
• Discord Inc. (United States): sign-in with Discord, and the Bot, which works inside Discord: its replies, role and nickname changes happen on Discord's platform.
• Google LLC (United States): Google Analytics, only if you accept analytics cookies.
• Microsoft Corporation (United States): Microsoft Clarity, only if you accept analytics cookies.

Customers decide who else receives the data of their network: their staff see it according to the permissions the Customer grants them; the network's Minecraft servers receive the links of their players (for example to show the linked Discord name or run reward commands); and the Customer can share identities with other tools through API keys, webhooks it points at addresses of its choice, or by connecting other Exylia services (Exylia Tickets, Staff or Analytics) through Exylia Connect. Each of those receives only what the Customer enables, and the Customer can revoke it at any time.

We may disclose data when required by law or by a court or competent authority, and to defend our legal rights.

7. 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. An account that still owns a network cannot be deleted until the network is handed to someone else or deleted.
• Login sessions and the Discord access token kept with them: deleted once the session expires (30 days without use). Signing out ends the session at once; its record is deleted on the date it would have expired.
• Linking codes, network-linking codes and Exylia Connect codes: deleted one day after they expire.
• Internal event queue: processed events are deleted after 30 days; finished background jobs are deleted when they complete. Webhook delivery logs keep the last 50 deliveries of each webhook.
• Players, links (including removed links), reward grants, imports, sync summaries, invitations and the audit log: while the network exists. Removing a Discord server from a network deletes its sync history. A Customer can have a player's data erased, or its whole network deleted, by writing to [email protected]; we do so within 30 days.
• Technical logs: up to 90 days.
• Usage analytics: Google Analytics keeps its data for 14 months; Clarity keeps session recordings for 30 days.
• 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.

8. International transfers

Our servers are in Chile, and the providers in section 6 are 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.

9. Security

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

• Encryption in transit (HTTPS/TLS) for all traffic to our domains, including the Plugin's connections.
• Session, invitation, API and server tokens and network secrets stored only as hashes; Discord access tokens and webhook signing secrets encrypted with AES-256-GCM.
• Discord sign-in through OAuth with PKCE and a signed, single-use state.
• Linking codes that are short-lived, single use and rate limited per Discord account, per player and per server.
• Strict separation of each Customer's data by network, and role-based permissions within each network.
• Signed webhooks and protection against webhooks pointed at internal 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.

10. 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 (for analytics cookies, with the "Cookies" link in the footer). 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.

Players can remove their own link at any time with /unlink in Discord or on the network's link page, where the network allows it, or by asking the network's staff. To exercise any other right, write to [email protected] from a channel that lets us confirm your identity (we may ask you to confirm through your Discord account). 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.

11. Minors

To create or run a network you must be at least 18 years old or of legal age where you live. To sign in with Discord at all you must meet Discord's own minimum age, which is at least 13 and higher in some countries.

Many Minecraft players are minors. The Service does not ask for or record anyone's age, keeps only what linking needs, and never uses player data for advertising or profiling. Customers whose communities are aimed at minors must assess their obligations, including parental consent where the law requires it.

12. 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].