Privacy Policy

1. Data controller

The data controller is Yann ADORNI, sole trader, SIRET 978 733 723 00040, 39 chemin de Pibrac, Villa 05, 31880 La Salvetat-Saint-Gilles, France. Contact: [email protected]. When an administrator enables a module that processes the data of members of THEIR server, they are the data controller for that server and we act as a technical processor.

2. Data collected

• Discord account: Discord ID, username, avatar, and email address where Discord provides it at sign-in;
• Server: server, channel and role IDs, member list and the configuration of the enabled modules;
• Module usage, depending on what is enabled: levels and experience, economy and inventory, tickets and their ratings, suggestions, reports, event and giveaway entries, invites, trades, published reviews, messages highlighted by the memory wall;
• Moderation: sanctions (warning, kick, ban), their reason, author and date, as well as ban appeals and any email address provided to reply to them;
• Subscription: plan, term, start and end dates, customer ID at the payment provider. No card details are received or stored by the publisher;
• Technical: error and connection logs, IP address sent by the browser with each request, needed for security and diagnostics.
• Contribution: amount, date, transaction reference at the payment provider, and — only if you were signed in — your Discord ID. The username and message you leave are published only if you explicitly tick the box provided; the amount is never published.
• Message content: the auto-moderation, custom commands, counting and per-message experience modules read the text of messages as they are posted, in order to decide whether to react. That text is not retained, except in two cases: when an auto-moderation rule triggers a sanction, the message concerned is attached to the server's moderation log; and when the memory wall republishes a message, it copies its content (see below);
• Presence status: the game or activity shown by Discord is read when a voice channel has to be named automatically after what you are playing. This information is never stored;
• Partner program waiting list: the email address you enter on the Partner page, together with your Discord identifier and username if you were signed in, and the site language. It is used only to announce the opening of the program, and is deleted on request.
• Memory wall (Community module): when a message reaches the reaction threshold set by the server administrator, Kuratos republishes a copy of it in the chosen channel. That copy reproduces the message author's username and avatar, its text, the first image it contains if any, and a link to the original. We also keep, in our database, the identifiers of the original message, of its channel and of the published copy, along with the reaction count — but no identifier of the author;

3. Purposes and legal basis

Providing and operating the Service, and managing subscriptions and billing: performance of the contract. Ensuring security, preventing fraud and abuse, keeping a server's moderation history: legitimate interest. Handling ban appeals and support: legitimate interest and performance of the contract. Keeping accounting records, donations included: legal obligation. Notifying you of the partner program opening: consent, given by entering your address and withdrawable on request. Publicly displaying the name and message of someone who contributes: consent, given by ticking the matching box and withdrawable at any time on request. No data is sold, rented, or used for advertising or profiling, and no automated decision producing legal effects is made on this basis.

4. Who has access to your data

Server administrators only access the data of THEIR server, and only what the dashboard exposes: members' Discord ID, username and avatar, activity related to the modules they have enabled, and that server's moderation history. They have access to neither your email address, nor your subscription data, nor anything from another server. The publisher has technical access, limited to maintenance, incident diagnosis and handling requests. Our processors are: Contabo GmbH (hosting, Germany), Stripe Payments Europe Ltd. (payment and billing, Ireland), Brevo (sending replies to ban appeals, France) Cloudflare (network protection and site delivery), GitHub (code repository and storage of database backups, encrypted before upload, United States) and UptimeRobot (external site monitoring and public status page; if you subscribe to alerts from that page, your email address is processed by UptimeRobot). A web page may also display a server's experience leaderboard, with the username, avatar and Discord identifier of the members listed on it. It is CLOSED BY DEFAULT: the server administrator must enable it through a setting separate from the Levels module, and it is then only reachable through a link containing an access token, which they alone distribute. That link is neither guessable nor indexed by search engines. Disabling the page deletes the token and immediately breaks links already shared. The scope displayed is the one every member of the server already sees inside it; no individual removal is provided, closing the page being the responsibility of the administrator, who is the data controller. The Service also runs on the Discord platform, which has its own privacy policy. Apart from these cases, no data is disclosed to a third party, except upon request from a competent authority.

5. Transfers outside the European Union

Data is hosted within the European Union. GitHub (encrypted backups), Cloudflare (delivery) and UptimeRobot (monitoring) are established in the United States or carry out technical processing there; such transfers are covered by the European Commission's standard contractual clauses or by an adequacy decision. Discord, which operates the platform the Service runs on, is established in the United States: any data passing through Discord falls under its own policy.

6. Retention periods

A server's data is retained while the bot is present on it. Removing the bot does not delete that data today: it only marks the server as inactive, and the data stays in the database until a deletion is requested. This is a gap we are fixing, and in the meantime you can have your own data deleted immediately from the My data page or by writing to us. By category: moderation sanctions (warnings, kicks, bans) are kept with no time limit, for server security and under the legitimate interest of its administrator; handled reports are deleted after 30 days; technical error logs after 30 days at most; ban appeals are deleted once handled; login sessions expire after 7 days; copies published by the memory wall are kept for as long as the republished message keeps enough reactions — as soon as the count falls back below the threshold, the copy and its record are deleted automatically, as they are when all reactions are removed at once; deleting the original message always deletes the copy, purges included, and even if the server administrator has since disabled the module; deleting the memory wall configuration erases all of its records; accounting records are kept for 10 years, in accordance with article L123-22 of the French Commercial Code. If an account is deleted, the donor’s name and message are erased and immediately disappear from the public thanks; only the accounting record — amount, date, transaction reference — is kept, without identity, under the same obligation.

7. Security

Traffic to the site and the interface is encrypted (HTTPS). The database is not exposed to the internet, secrets are not stored in the code, sessions rely on a signed token held in a cookie that scripts cannot read, and backups kept off the server are encrypted. As no system is infallible, any data breach presenting a risk would be notified to the supervisory authority and, where applicable, to the individuals concerned, within the time limits set by the GDPR.

8. Your rights

You have the right to access, rectify, erase, restrict, object to and port your data. You can exercise these rights yourself and immediately, without writing to us, from the My data page: it lets you download all of your data in a readable file, and permanently delete your account. Your username and avatar are rectified from Discord: they are resynchronised at each sign-in. After deletion, only the following remain: the moderation history concerning you on servers where the bot is present — kept on the compelling legitimate grounds of server security (articles 17.1(c) and 21.1 GDPR) —, the accounting records, kept for ten years by the publisher and by the payment provider under a legal obligation, and a pseudonymised identifier if you had used the free trial, to prevent account deletion from being used to obtain a new one. That identifier is a SHA-256 hash of your Discord identifier combined with a secret key: it cannot lead back to you, only recognise an identifier already known. It is currently kept with no time limit, as the lock would otherwise lose its purpose; we will review that duration. You may also write to us at [email protected], and lodge a complaint with the competent supervisory authority, in France the CNIL.

9. Minors

The Service is not intended for people below the minimum age required by Discord in their country of residence. No data is knowingly collected below that age; were such collection brought to our attention, the data would be deleted without delay.

10. Cookies

The site sets exactly two cookies, both strictly necessary: an authentication cookie (nexus_token), which keeps the session after signing in with Discord, and a language cookie (NEXT_LOCALE), stored only when the visitor chooses their own language. No advertising cookies, no analytics, no third-party trackers, no local storage. As these cookies are strictly necessary for the service expressly requested, they are exempt from prior consent under article 82 of the French Data Protection Act and the ePrivacy Directive: no consent banner is therefore displayed. The payment page, hosted by Stripe, falls under Stripe's privacy policy.

11. Changes

This policy may change; the version that applies is the one published on this page, whose update date appears at the top. Any substantial change is announced on the Service.