1. Controller and contact
NapoSky is responsible for processing by the official instance. The public contact is the repository’s GitHub issues. For a personal request, open an issue without sensitive data to arrange a private exchange, or contact the 11e Discord administration. Do not post your identifier, private messages, tokens or data exports in a public issue.
2. Data processed and purposes
The bot receives Discord identifiers for the server, members, roles, channels and interactions. It checks roles and permissions to respond to authorised actions. It stores associations between games, channels, roles and messages it manages, together with notification subscription preferences.
Game proposals include the author’s identifier, the submitted name and link, language, dates, status and administrative responses. Events retain their name, description, associated game, Discord resources and creation or closure state.
Temporary sessions and quota timestamps support private navigation and abuse prevention. Audit and operation records contain the action, target, actor identifiers where needed and dates required to recover interrupted operations.
To assess game activity, Nexus observes human-message timestamps and channel and thread metadata without storing conversation text. It does not request the privileged message content intent, record voice conversations or track game presence.
3. Why we process data
Data needed for requested features is processed to provide the service. Permission checks, abuse prevention, security and operation recovery serve the legitimate interest of running a reliable community service. Notifications are optional and can be disabled by removing the relevant role or using Nexus.
Data is not sold, used for advertising or used to train an artificial intelligence model. Archiving is based on activity in game spaces, without individual member profiling.
4. Retention
Open requests expire after 30 days without an update. Closed requests are kept for 30 days after closure. Audit entries, terminal operations and old rate-limit timestamps are cleaned after 30 days. Sessions are removed at expiry.
Unresolved operations, catalogue associations, import receipts and data needed to operate games and events remain while necessary. Subscription preferences follow Discord roles; manual removals and server departures are taken into account during reconciliation. Legacy records without lifecycle dates have a 30-day transition period from retention activation.
Channel histories remain on Discord under server and Discord rules. Archiving a game or event does not delete its messages. Backups and technical logs may retain copies; their rotation depends on hosting. NapoSky can explain remaining copies when handling a request; we do not promise instant deletion from every backup.
5. Recipients and external services
The operator and authorised administrators access data needed for management and support. Exchanges and publications use Discord under its own Privacy Policy.
The bot queries RAWG to search titles and retrieve game details and images. The searched game name is sent to RAWG without adding a Discord member identifier. Images are retrieved from artwork providers. The bot runs on the operator’s infrastructure.
This static website is served by GitHub Pages. Images and fonts are hosted with the site; no Discord or video embed loads automatically. The site adds no cookies, local storage or analytics. GitHub may process connection data, including IP addresses, to serve and secure the site. Following a link to Discord, GitHub or another service opens an environment governed by its own policy. These providers may process data outside your country under their respective safeguards.
6. Your rights and security
Subject to applicable law, you may request access, correction, deletion, restriction, objection and, where applicable, portability by contacting NapoSky. Identity verification is limited to what is necessary. Legal exceptions or unresolved operations will be explained if retention remains necessary.
Disabling notifications does not automatically delete a proposal or audit entry. Leaving the server does not erase messages you posted there; these are also managed by Discord and the server administration.
You may complain to the CNIL or your competent supervisory authority. Access to the bot and its data is restricted to authorised people; application logs filter secrets, request bodies and raw error messages. If a data breach occurs, required notifications will be made to affected people and authorities.
7. Policy changes
The date on this page identifies its version. Changes are preserved in the public repository history. Material changes in processing will be communicated to members through appropriate community channels.