Privacy Policy

Who is responsible?

The controller is l'équipe d'Elythera. Contact: contact@elythera.com.

Discord, Mojang and Microsoft, and Twitch also process some of your data for their own services, under their own responsibility: their privacy policies then apply. When a page of the site makes your browser load an image hosted elsewhere (avatars from Discord's CDN, IGDB covers, images in some articles), your IP address is sent to its host: we are responsible for this loading, based on our legitimate interest in displaying the site; what that host then does with this data is its sole responsibility.

In short

• No payments, no advertising, no third-party audience measurement tools. We do not sell your data.
• Much of what you do on the server is visible to other members (levels, leaderboards, announcements, profile): that is how a community works. The site's showcase, for its part, is public.
• The bot reads the content of messages on the Elythera server to make its features work, without keeping ordinary messages: see “What our Discord applications receive”.
• The moderation and administration team has access to a lot of data to protect the community. Its actions on the site are logged.
• Several categories of data do not yet have a maximum retention period, and few are erased when you leave the server. We say so section by section. “No maximum period to date” means: kept as long as the feature exists, until you request its erasure or the team deletes it. These periods are being set.
• Legal bases (Article 6 GDPR): performance of the terms of service you accept (6.1.b), our legitimate interest in running and protecting the community (6.1.f), your consent when it is requested (6.1.a, and Article 82 of the French Data Protection Act, the loi Informatique et Libertés, for reading your browser).

What our Discord applications receive

• The “Elythera” bot is only present on the Elythera server. It receives the content of the messages posted in the channels it has access to and of the direct messages sent to it.
• For most messages, it only extracts transient information from them, without keeping the text: the length (XP bonus), quest counting (messages, images, counting channels), sudoku moves played in a channel, hunt draws, and the messages of the DiscordL, Disboard and EPIC RPG bots (bumps, votes, EPIC RPG helper). These ordinary messages are not recorded.
• It copies the content only for: tickets, the forum, the threads of the team's report forum, the Creative Park, or Parc Créatif (images and captions from creative channels), direct messages addressed to the bot, the chat of personal voice channels (when they close), the hall of fame, messages reported with /signaler-msg (sent to the team) and, if the team turns it on, excerpts of deleted or edited messages in its log channel.
• It also receives the member list and its changes (roles, nickname, boost, tag), voice states, reactions, invites and bans. It never receives presences (online status, current activity).
• The “Elythera Partenaire” (Elythera Partner) application only receives, in partner servers, the member list, their departures and their bans: never message content, direct messages, voice states or presences.

Where the data comes from

Most data comes from you or from what you do in the services. Other data comes from elsewhere:

• Discord: your ID, your name, your avatar, your nickname on the server, your roles, your booster status, whether you display the server tag, your voice states, your bans, and your account's creation date, deduced from your ID.
• Other members and the team: reports, moderation files and notes, a birthday recorded by an administrator, a mention of your account in another member's verification.
• Third-party bots whose public messages our bot reads: DiscordL and Disboard (bumps, votes), EPIC RPG (EPIC RPG helper).
• Mojang: your UUID, your username and your skin, when you associate your Minecraft account.
• Partner servers, through the “Elythera Partenaire” application: your presence on their server, your departure and your ban.
• Twitch: the live status of your channel (title, game, thumbnail), if you have declared it.
• At verification: the network category of your IP address, taken from public lists (Tor exits, VPNs, hosting providers) and, if the option is on, from proxycheck.io.

What is mandatory and what is not

• No data is required by law.
• Your Discord ID is needed to log in to the dashboard and to use the features tied to your account; without it, only the showcase and the public pages are accessible (or, if the team enables this option, an email account with limited features).
• At verification, your IP address is needed. Reading your browser is optional: if you decline it, your verification waits, in active mode, for a team member's decision.
• The following are optional: your birthday, your Twitch link, your Minecraft account, your game library, your email address and your application answers.

Logging in to the site and web account

• Data: your Discord ID, your username, your nickname and your avatar's address (the only permission requested from Discord is “identify”); your server membership, any ban and your team status, read from Discord; your session (secret identifier, dates, login method); the log of your logins (date, display name, browser used, no IP address). With email login: your email address, your password as a hash (never in clear text), your second factors (secret key of your authenticator app, passkeys), your backup codes (as a hash) and the links sent by email.
• Why: logging you in, reserving the dashboard for members, securing your account, curbing abuse, notifying you of security changes.
• Legal basis: performance of the terms of service; legitimate interest for the login log and security.
• Retention: session: 7 days, deleted when you log out; links sent by email valid for 24 hours (address verification) or 1 hour (forgotten password), then deleted automatically; IP address used for rate limits: in memory only and briefly, never written to the database for this purpose; login log, email address and factors: no maximum period to date.
• Who sees it: you; administrators (your email address and your service address, with which they can search for your account; your sessions in abbreviated form, your latest logins, whether a password or factors exist, never their value; a password or backup codes that an administrator sets for you are shown to them once); the team's log channel on Discord receives a notice for each login to the site through Discord, if the team keeps this log active.
• The token that Discord hands over at login is used only once and is not kept. Emails are sent through the sending server chosen by the team.

Signing in to the team's services

• Data: depending on the permissions you accept on the consent screen, your Discord ID, your name, your nickname, your avatar, your verified email address, your service address if the team has assigned you one, and your roles; access codes and tokens (as a hash); your consent, service by service.
• Why: opening the team's internal services to you, with rights modelled on your Discord roles.
• Legal basis: performance of the terms of service.
• Retention: access renews as long as the service uses it, each refresh token being valid for 30 days; it is revoked if you leave the server, are banned or lose the required role, if your account is disabled or if you change your password; codes and tokens are deleted shortly after they expire; your consent: no maximum period to date, and there is no button yet to withdraw it (ask via contact@elythera.com).
• Who sees it: the service you sign in to (some services declared trusted by the team skip the consent screen); administrators; the team's log channel receives a notice for each sign-in to a service.

Newcomer verification

Summary; the verification notice (dsc.elythera.com/verification/infos) gives the details.

• Data: your Discord ID and username; your IP address, judged on the spot (VPN, Tor, hosting provider) and then kept only as a one-way code; only with your consent, a “device” cookie and technical characteristics of your browser reduced to a code; the ID of another account signed in to Discord or to the site in the same browser (for the site, only with your consent); the date and result of each verification, similarities with other accounts, the team's decision and its author; your verification status (verified, under review, refused).
• Why: spotting alt accounts and banned people coming back. This data is used only for verification.
• Legal basis: legitimate interest for the IP address and the comparison; consent for reading the browser and the cookie. You can decline: nothing is then read from your browser; in active mode, you stay in quarantine (limited access to the server) until a team member decides.
• Retention: IP address code: 30 days; cookie, browser code and verification history: 180 days; attempt refused for VPN: 30 days; if a ban is linked to the account, the cookie and browser codes are kept until 24 months after their creation; a refusal by the team is kept for 24 months after the decision, with the IDs of the linked accounts: if your account is cited in another member's refusal, this mention stays until that refusal expires, even after your own data has been erased (legitimate grounds: preventing an alt from lifting its own refusal); your verification status stays recorded as long as you are a member; everything is erased 30 days after you leave the server, unless a review is in progress, or there is a refusal or a ban.
• Who sees it: the moderation team sees the result and, when in doubt, the accounts that resemble yours and the type of similarity, never your address or your characteristics; the team's log channel keeps the “vérifié” (verified) mention and the author of an approval; proxycheck.io receives your IP address only if the team turns on this option, which the notice shows live.
• Your tools: the “🔎 My data” button in the verification channel, to view your data, withdraw your consent or erase your data.

Levels, quests, seasons and rewarded activity

• Data: your XP and your level; the log of your earnings, one line per rewarded message or minute of voice, quest, game, bump, vote or team correction, with the date and time (the text of your messages is not in it); your quests and their progress, fed by your actions (messages, reactions, voice, games, purchases…); your bumps and votes (ID, Discord tag, date); your achievements; the end-of-season archives (full leaderboard, quests, bumps, votes).
• Why: making progression, rewards and leaderboards work, keeping the history of seasons, spotting cheating.
• Legal basis: performance of the terms of service; legitimate interest for the leaderboards and the archives.
• Retention: levels, season quests, bumps and votes are reset at each new season, after archiving; daily and weekly quests are replaced every day and every Monday; earnings log and season archives: no maximum period to date. Nothing is erased when you leave the server.
• Who sees it: any member can display your level and your profile (/level, /profil, as a public reply), your quests (/quests) and your bumps (/bumps); the Discord and dashboard leaderboards show the members present; season archives are visible to logged-in members and through /archives; you, the latest lines of your earnings log; the team, all the details.

What is publicly visible

• The site's showcase, without logging in: the season's top members by level, bumps and votes, with nickname and avatar. The avatar's address, hosted by Discord, contains your Discord ID. The “Public showcase leaderboard” setting, on by default, lets you opt out; it only applies to the showcase.
• Announcements on Discord: level-ups (the announcement is posted with or without a mention, depending on your “Level-up mentions” setting), birthdays and, when the team turns them on, the welcome message (with a mention, when you get the welcome role), announcements of your public games and of your ElyRPG assaults (nickname, and avatar for ElyRPG), the weekly recap, the year in review (named podiums), live alerts, end of hunt and hall of fame. Private games or games reserved for one opponent are not announced. There is no setting to stay out of these announcements. The date of your welcome is kept until you leave the server.
• Profile (/profil): any member can display yours, as a public reply: nickname, avatar, level, XP, rank, date you joined the server, boost date, showcased badges, economy figures, Discord ID, and your verified Minecraft username if you have made it visible. When you display your own /profil, your verified Minecraft username always appears, and that reply is visible to the whole channel.
• Other public pages of the site: public Creative Park works (image, caption, nickname), authors of news posts, nicknames of the players in a game on its invitation page (for anyone who has the link), Agario high scores, game sessions published as events.
• Legal basis: legitimate interest in running the community. To object to what has no setting, contact us (contact@elythera.com).

Economy, hunt, badges, Astre, tag and birthdays

• Data: your virtual wallet and your purchases; your hunt items and their log (with the name of the channel where you got them); your badges and profile backgrounds (date, origin); your Astre pass (expiry, origin, author), your custom role (name, colour) and any ban from Astre perks, with its reason; your booster status, read from Discord; whether you display the server tag; your birthday (day, month, optional year).
• Why: making the virtual economy, events, distinctions and the Astre and tag perks work; announcing birthdays.
• Legal basis: performance of the terms of service; for your birthday, your consent when you enter it yourself, which you can withdraw, and our legitimate interest when a team member records it for you (birthdays carried over from former bots), with the same right to remove it.
• Retention: Astre pass deleted after its expiry; server tag display erased as soon as you stop displaying it or leave the server; birthday kept until you remove it; the rest (wallet, purchases, hunt log, badges, backgrounds, custom role): no maximum period to date, even after you leave.
• Who sees it: your birthday is announced publicly on the server, with your age if the year is known, and any member sees the date and the upcoming age in /anniversaire; an administrator can also record your birthday, year included: you are not notified, but you can remove it; your showcased badges, your custom role and your booster status (on /profil) are visible to everyone; the team sees the rest.
• Your tools: /anniversaire retirer or the site's button; hide or reorder your badges; choose your background; edit or delete your custom role.

Twitch streamers

• Data: the link and ID of your Twitch channel, if you declare it; your activity conditions over the period (messages, voice minutes, level); the alerts posted and their number; any block by the team.
• Why: announcing your streams when the feature is active.
• Legal basis: performance of your request.
• Retention: if you clear your link, the row stays in the database, without the link, so that a block cannot be bypassed; alerts: no maximum period to date.
• Who sees it: the whole server sees the alert (mention, stream title, game, thumbnail, link); Twitch receives your channel ID when the bot checks whether you are live; the team sees the list and your activity conditions.

Voice and personal voice channels

• Data: your voice sessions (channel, arrival time) and your voice time per day, counted in all channels (except the AFK channel, depending on the setting), even when you are alone or muted; the team can turn this counting off, but rewarded time is then still recorded; your arrivals, departures and voice channel changes, recorded in the team's log channel (on by default, the team can turn it off). For personal voice channels: your channel (named after your nickname), its settings, your banned and promoted members, “doorbell” requests, your passes and tickets, and the channel's text chat, archived when it closes (authors, messages, attachment links).
• Why: rewarding voice activity, feeding statistics (streamer conditions, year in review), making personal voice channels work, moderating.
• Legal basis: performance of the terms of service; legitimate interest for statistics and moderation.
• Retention: session erased when you leave voice; voice time per day: no maximum period to date; archive of a personal voice channel's chat: deleted once older than 90 days, when the team views the list of archives; doorbell requests: 30 days, purged when the bot starts; log channel messages: not erased by the bot.
• Who sees it: your year in review shows your voice hours, and the team can publish the members who spend the most time in voice; chat archives: administrators; the log channel: the team; your personal voice channel's panel, visible to the server, shows its owner and its promoted members.

Games

• Data: your games (opponents, moves, result, dates), your tournaments and the leaderboards; your progress and possessions in the Clicker, Agario and ElyRPG; the log of your actions in ElyRPG; your sudoku statistics; your game library and your matchmaking sessions. In Agario: your name, your avatar and your nickname colour (which reveals Astre or team status, adjustable), your friends, your chat messages, your death card, your reports, and your IP address (in memory, written to the database only in case of a ban). In the Clicker: a profile of your clicking rhythm, for anti-cheat.
• Why: making the games and their leaderboards work, preventing cheating, moderating.
• Legal basis: performance of the terms of service; legitimate interest for anti-cheat and moderation.
• Retention: Agario chat: 30 days; ElyRPG log: 7 days; Clicker anti-cheat log: only the latest events; Agario reports: in memory, until restart; games, progress, statistics, library, friends, bans, death card: no maximum period to date (can be reset by the team).
• Who sees it: other players see what the game displays (name, avatar, scores); Agario high scores are public, and the data served by the site contains the Discord ID of ranked members; your approved death card is shown to your victims, guests included, and its address contains your Discord ID; the Agario chat history can be read by anyone who has access to the game, guests included, without your ID; any member can view your game library, and owning a game can earn you a mention in the announcement of a session of that game; a tournament's champion and the ElyRPG leaderboard on Discord are public; the team sees the rest, including the IP address of Agario players for administrators who have presented their second factor.
• Agario guests: without an account, you can play if the team allows it. Your nickname is kept in your browser; during the game, it is visible to other players and spectators, and can appear on the current high-score board, kept in memory until restart. Your IP address is used, in memory, to limit the number of guests; it is only written to the database in case of a ban, with no expiry. Nothing else is recorded in your name in the database.
• Game search: the text you search for is sent to IGDB (a Twitch service), without your ID.
• EPIC RPG helper (beta): the bot reads the public messages of the EPIC RPG bot to know your inventory, keeps it in memory and replies by mentioning you.

Forum, Creative Park and news

• Data: for the forum, your topics and messages (text, title, attachments, date), your ID, your nickname and your avatar, including for what you write directly in the Discord forum channel, with the original version of an edited message and the content of a deleted message, and any ban from the forum; for the Creative Park, your images, their caption, your nickname, the chosen visibility and the “likes”, including your Discord reactions on a work; for news posts, the name of their author.
• Why: linking the site's forum to Discord's, displaying works, moderating.
• Legal basis: performance of the terms of service; legitimate interest for moderation records.
• Retention: no maximum period to date. A message deleted on Discord stays in the database as a moderation record. A work leaves the gallery when its message or its channel is deleted on Discord, or when its image is removed from the message: its image and its reduced thumbnail are then erased, but its votes stay on our servers. A deletion made while the bot is offline is not seen: the work stays until you ask for it to be removed.
• Who sees it: for the forum, logged-in members and the Discord forum channel; for deletion and edit records, the moderation team only; for works, according to their visibility (public = the whole internet); your vote is only shown to you, only the totals are public.
• Files: Creative Park images and their thumbnails follow the same rules as the lists, even for someone who knows their exact address: a private or hidden work is only served to its author and to the team, a “members” work only to logged-in members.

Direct messages with the bot

• Data: every direct message you send to the bot (text, names and links of attachments, date) and those the team sends you through the bot, with their author. The team can also import the history of your private conversation with the bot, the bot's messages included, without you seeing it. The messages you exchange with other members are not covered: the bot has no access to them.
• The bot does not warn you, when you write to it, that your message is recorded: every message sent to the bot is kept and can be read by administrators.
• Why: moderation and prevention; giving anyone who writes to the bot someone to talk to.
• Legal basis: legitimate interest (community safety, answering requests). You can object to the retention of your messages: contact us (contact@elythera.com).
• Retention: kept with no time limit. An administrator can delete a conversation.
• Who sees them: administrators.
• Your “Bot direct messages” setting turns off event messages, but also those about votes, badges, backgrounds, the hunt, Astre and compensations, game invitations and reminders, the ticket closing notice and the messages of partner events. Sanction messages, those concerning a ban appeal, the identity borrowing notice and the messages the team writes to you are sent to you regardless of this setting.
• Site bell notifications: messages from the team, erased once older than 30 days, when the next notification is sent.

Moderation, tickets and reports

• Data: warnings, sanctions and their reasons; the team's internal notes, never shown to the member; the team's files on a member (report forum threads, messages and images); reports (/signaler, /signaler-msg, Agario reports); tickets (number, subject, category, messages, images, attachments, full history); exclusions (tickets, forum, gallery, personal voice channels, matchmaking, Astre, Agario); the ban register and appeal files (your message, your screenshots, the replies, the decision); alt-account marking and progress transfers; access to the adults-only channel. In the team's log channel on Discord: arrivals (with the invite code and the person who created it), departures, warnings and sanctions issued with the bot or from the site and, if the team turns them on, bans made directly on Discord, role and nickname changes, excerpts of deleted or edited messages.
• Why: protecting the community, enforcing the rules, providing support, making it possible to challenge a decision.
• Legal basis: legitimate interest; performance of the terms of service for tickets and appeals.
• Retention: a ban's register entry until the ban is lifted; the rest (warnings, sanctions, notes, files, tickets and their history, appeals, exclusions, markings): no maximum period to date, even after you leave; messages posted in the team's channels on Discord are not erased by the bot; Discord's audit log, which keeps sanctions with the moderator's ID, follows Discord's rules.
• Who sees it: the moderation team, according to rank, and administrators; media from tickets, reports and appeals can only be viewed after a second factor has been presented. You: the number of your active warnings on your profile, sanction direct messages, your tickets and their history (downloadable), your latest appeal file, without the names of team members.

Team access and identity borrowing

• Administrators have a record for each member that gathers their data: progress, sanctions, tickets, birthday, last login, wallet, roles, games, badges…
• Changes made by the team from the site, and some reads of personal data, are recorded in an audit log (author, action, target, summary of the request, which may contain a reason, a note or an email address). Administrators can view it; it is kept with no maximum period to date.
• Identity borrowing: an administrator can open a session in your name. Read-only mode: 30 minutes; they see the site as you do and can open, under your identity, the team's services you have access to, without being able to post, spend, touch your account's security, administer or moderate (opening a game page can only create your starting data). You are notified by direct message if your account is linked to Discord and your direct messages are open, and by email if your address is verified and email sending is set up; otherwise, you may not be. Full mode: for up to 7 days, the administrator can act in your place, with your administration or moderation rights if you have any, including changing your account's security and using the team's services opened under your identity, and you are not notified. Each borrowing is recorded (who, for whom, when, for how long), entered in the login log and announced in the team's log channel, with no maximum retention period to date.
• Legal basis: legitimate interest (support, security, team accountability).

Events, Minecraft, launcher and cosmetics

• Data: your event sign-ups (status, date, Minecraft username, application answers); your associated Minecraft identity (UUID, username, skin, chosen visibility); the launcher link (token hash, dates, launcher version) and what is handed to the launcher (ID, name, avatar, access roles, Minecraft identity); the cosmetics you own and wear; your application to the team with /candidater (nickname, age, motivation, experience).
• Why: organising events, giving you access to the Minecraft servers and then removing it, preventing a Minecraft account from being claimed by someone else, opening the launcher's restricted profiles, displaying your cosmetics, recruiting the team.
• Legal basis: performance of the terms of service; legitimate interest for team applications and for keeping a banned person's Minecraft identity, so that they cannot attach it to another account.
• Retention: Minecraft identity, until you unlink it or leave the server of your own accord (kept in case of a ban), the texture file of your skin possibly remaining on our servers; launcher link, 30 days, renewable, revoked at the first check after you leave or are banned, its record then remaining in the database; sign-ups for Elythera events, cosmetics and team applications: no maximum period to date; partner events: see “Partner events”.
• Who sees it: the team; your verified Minecraft username only appears on the /profil that other members display if you choose the “Visible to members on /profil” visibility (private by default), but it always appears when you display your own /profil, a reply visible to the channel; the event's Minecraft server receives your username, and sometimes your UUID or your Discord ID, in whitelist commands; Mojang receives your UUID and your username to verify your account; servers equipped with the mod receive the cosmetics you wear, attached to your UUID, without a Discord ID; team applications are posted in a team channel; an external application form belongs to its publisher.
• Your tools: unlink your Minecraft account (site or launcher) and choose its visibility; undo the launcher link from the launcher itself; unregister from an event.

Partner events

• When you sign up for a partner's event, its managers see your Discord ID, your display name (which may be the one you use on the Elythera server), your status, your dates, your Minecraft username, whether it is verified, the way you signed up, your application answers, and whether you are a member of Elythera, of the partner or of both; the log channel of its Discord mentions you; its Minecraft server receives the whitelist commands.
• The partner's management log, which its managers can read, keeps their actions, with the ID of the person concerned, the username entered when adding someone and the reason for an exclusion.
• The “Elythera Partenaire” application reads, in partner servers, the member list, departures and bans, never message content.
• Retention periods: guest session: 72 hours; application answers: erased 90 days after the end of the event; sign-ups: 180 days after the end; guest record: 180 days after the last check; exclusion: 24 months at most; management log: 365 days. Messages already posted in the partner's Discord are up to the partner.
• Legal basis: performance of your sign-up request; legitimate interest for the management log and exclusions.
• The details are in the notice shown in the partner's zone. Guest: your tools (stop direct messages, erase your data) are in the “My data” section of that zone. Elythera member: your dashboard settings, or contact@elythera.com.

Technical logs and backups

• Program logs (Discord IDs, nicknames, actions, errors): 30 days.
• Full backup of the database every day: the 7 most recent are kept, so data that has been erased can survive a few days in a backup.
• A full copy of the database is also made before each update that modifies it: the program erases it after 30 days.
• The first season's archives contain full copies of the database as it was then, kept with no maximum period to date.
• Also remaining in the database, unused and never purged: the sign-ups of the old Minecraft events system (Discord ID, Minecraft username); a working copy of an old voice sessions database (Discord IDs) may also remain on disk.
• The front-end web server and the hosting platform may keep their own logs and backups, which may contain your IP address.
• Visit counters: only totals per day and per page type, with no identifier or IP address.
• Legal basis: legitimate interest (security, service continuity).

Who receives your data

• The Elythera team, according to each member's role (moderation by rank, administration, founder).
• Discord Inc.: everything the bot posts, sends or edits on Discord (messages, announcements, team logs, direct messages, roles), and logging in to the site.
• The hosting of the site, the bot and the database, and, if the team uses one, a PostgreSQL or MariaDB database server.
• When the feature is used: Twitch (streamers' channel IDs); IGDB, a Twitch service (game search texts); Mojang and Microsoft (Minecraft account verification, skin); proxycheck.io (IP address at verification, only if the option is enabled); the email sending server chosen by the team (address and content of emails).
• Partners, for their own events, and the events' Minecraft servers.
• The team's services you sign in to with Elythera.
• The authorities, if the law requires us to disclose data to them.
• DiscordL and Disboard receive nothing from Elythera: the bot reads their public messages to credit your bumps and your votes.
• Resources loaded by your browser: Discord's CDN (avatars, emojis), images.igdb.com (covers), external images in some articles, GitHub if you download the launcher. These services receive your IP address.
• We neither sell nor rent your data.

Transfers outside the European Union

Several recipients are established outside the European Union, notably in the United States: Discord, Twitch (and IGDB), GitHub, Microsoft (and Mojang). Your data is therefore transferred to them; each of them describes in its privacy policy the safeguards it applies to these transfers. Partners and their members may be in any country: if a partner's managers are outside the European Union, sending them your sign-up data is necessary for your sign-up to its event (Article 49(1)(b) GDPR). To find out the country of our other providers (hosting, email, proxycheck.io), contact us (contact@elythera.com).

Cookies and storage in your browser

The site uses no advertising or audience measurement cookies. The cookies below are necessary for the services to work and do not require your consent, except the verification “device” cookie, set only if you accept.

• elythera_session: your login to the site (7 days; 72 hours for a partner's guest).
• elythera_oauth: secures the round trip through Discord when you log in (10 minutes).
• elythera_form: protects the web account forms (email login, sign-up, forgotten password, second factor) (30 minutes).
• __Host-elythera_verif: ties your verification link to this browser (20 minutes).
• __Host-elythera_appareil: recognition of your device for verification, only with your consent (180 days); removed when you withdraw your consent or erase your data.
• elythera_agario: your Agario player token, until the browser is closed.
• elythera_retour and elythera_emprunt: used only during an identity borrowing by the team; the second one displays the borrowing banner.

Local storage (localStorage): preferences that you choose yourself and that stay in your browser until you clear them: theme (appearance), language (elythera_lang), game sounds (gameSfxMuted), Clicker (ckAutoclick, ckSrvTopOpen), Corolle (elythera_corolle_daltonien, elythera_corolle_aide), Agario (elythera_agar_touches, elythera_agar_prefs, elythera_agar_mode, and elythera_agar_nom for a guest's nickname), the team's embed editor (elythera_emb_ouverts, elythera_emb_apercu). elythera_emprunt_recharge (session storage) is only used during a borrowing.

The site can be installed as an app: its service worker caches nothing.

Reading your device: the verification page only reads your browser's technical characteristics if you click “Accept and verify me”.

Third-party resources: the site's fonts (Quicksand, Nunito) are served by the site itself, without going through Google; your browser does, however, load avatars and emojis from Discord's CDN, game covers from images.igdb.com and, in some articles, images hosted elsewhere. These services then receive your IP address and technical information about your browser. The verification pages load no third-party resources.

Security

• Between your browser and our front-end server, the connection is encrypted (HTTPS).
• Session cookies cannot be accessed by the page's JavaScript, are not sent with form submissions or embedded requests triggered by other sites (SameSite=Lax), and your browser only sends them over an encrypted connection (HTTPS).
• Passwords and backup codes are stored as a hash (scrypt); so are the links sent by email and the tokens of the team's services (SHA-256). The token that Discord hands over at login is not kept.
• A second factor is available to everyone (authenticator app, passkey); the team must have presented it less than 60 minutes ago to use its powers on the site, unless this requirement has been switched off in an emergency. On Discord, the team's commands depend on each member's roles.
• Verification codes are computed with a secret key kept outside the database; verification keeps no IP address in clear text.
• Rate limits against abuse and password guessing; audit log of the team's actions; moderation media restricted and subject to the second factor; daily backup.

No protection is perfect. In the event of a personal data breach presenting a risk, we notify the CNIL and, if the risk is high, the data subjects, as required by the GDPR.

Your rights and how to exercise them

You have the right to access your data, to have it rectified or erased, to object to processing based on legitimate interest, to request its restriction or portability, to withdraw your consent, and to give instructions on what happens to your data after your death. The tools that exist today:

• Access: your dashboard (profile, latest lines of your XP log, latest purchases, achievements, badges, birthday, Minecraft account, account security); “🔎 My data” for verification; if you are a partner's guest, the “My data” section of its zone; the history of your tickets, downloadable. For the rest: contact@elythera.com.
• Rectification: the dashboard settings (language, preferences, email address, password), your birthday, your Twitch link, your game library, your Minecraft account. For the rest: contact@elythera.com.
• Erasure: remove your birthday, unlink your Minecraft account, remove games from your library, delete a message on Discord (a work then leaves the gallery), “Erase my verification data” for verification and, for a guest, “Erase my data” in the partner zone. Elythera member signed up with a partner: go through contact@elythera.com. There is no button yet to delete your account or your progress: ask via contact@elythera.com.
• Objection: the “Public showcase leaderboard” and “Bot direct messages” settings, the visibility of your works and of your Minecraft account, declining to have your browser read at verification. The “Level-up mentions” setting only removes the notification: your name is still announced. To stop appearing in announcements, and for the rest: contact@elythera.com.
• Withdrawal of consent: “Withdraw my consent” in “🔎 My data” for verification; removing your birthday.
• Restriction and portability: there is no automatic export; request them via contact@elythera.com.

The team must reply within one month, which can be extended by two months if the request is complex. It may ask you to confirm that the request really comes from your Discord account, for example by making it from a ticket; never attach an ID document.

Some data may be kept despite an erasure request, on legitimate grounds and for as long as necessary: an ongoing ban or exclusion and what relates to it (including your Minecraft identity and your verification codes), an alt-account marking, the mention of your account in another member's verification refusal, moderation records, and backups until they are rotated.

If you believe that your rights are not being respected, you can lodge a complaint with the CNIL, the French data protection authority (cnil.fr).

Automated decisions

Some decisions are made without human intervention. We consider that they do not produce legal effects concerning you and do not significantly affect you within the meaning of Article 22 GDPR, because they concern access to a community server or to a mini-game. You can always ask for a review by a person, express your point of view and contest the decision (ticket or contact@elythera.com).

• Verification, VPN refusal (active mode): your IP address appears in public lists of Tor exits, VPNs or hosting providers, or proxycheck.io classifies it as such if the option is on. You can try again without a VPN, Tor or relay, or ask for a review by the team. This refusal suspends itself if too many recent attempts are refused: a person then decides.
• Verification, recent account (active mode): your Discord account is less than 7 days old, according to the date read from your ID; access opens by itself on the announced date.
• Verification, quarantine (active mode): strong similarity with another account or with a banned account, declining to have your browser read, contesting a VPN refusal, or the VPN refusal being suspended; you then wait for a person's decision.
• Clicker, if the team turns on detection: more than 45 minutes of clicking without a break of at least 10 seconds, or machine-like regularity over a long series of clicks, can freeze your earnings or only alert the team, depending on its setting; spending 10 minutes in total close to the maximum rate alerts the team. Holding the click as allowed by the official perk is not counted as cheating. A Clicker suspension is always decided by the team.
• Rate limits and game caps apply automatically.

Minors

• The services are intended for people who have reached the minimum age required by Discord in their country.
• At verification, agreeing to have your browser read requires being 15 or older, or having a parent's consent; otherwise, choose verification by the team.
• If you are a minor, do not enter your year of birth for your birthday: your age would be announced publicly.
• The adults-only channel requires the “majeur” (adult) role.
• A parent or legal guardian can exercise their child's rights via contact@elythera.com.

Changes

We update this policy when a feature changes. The date at the top of the page shows the version in force; a significant change is announced on the Discord server.

Contact

Questions about your data, exercising your rights: contact@elythera.com. Supervisory authority: the CNIL, the French data protection authority (cnil.fr).