Data processing

Privacy policy

This page describes how Voicey collects, uses and retains data necessary for Discord authentication, the dashboard and moderation functions.

General principles

The logic presented on the site rests on a simple principle: collect only the data necessary for the bot's operation, for authenticating authorized individuals, for managing Discord servers, and for providing the moderation tools described in the documentation.

Voicey is not presented as a general surveillance tool. The processing described here falls within a framework of voice management, useful traceability, and moderation assistance, in accordance with the site's public pages and usage guidelines.

Data that may be processed

Depending on the features used, the service may process data from Discord, including technical identifiers, usernames, server names, administration or moderation roles, guild configuration information, and elements necessary to access the dashboard.

The service may also process data related to temporary voice channels, voice ban history, record restrictions, message or archive links, and, when the corresponding feature is used, recordings published in Discord.

Discord authentication

Access to the dashboard relies on authentication via Discord. For this purpose, session data and information related to the connected Discord account are processed to identify the person, maintain their session, and determine whether they can access a server's dashboard.

These processes aim to secure access to private pages and reserve sensitive tools for individuals with the necessary rights.

Processing purposes

Data is processed to enable dashboard login, display accessible servers, manage guild settings, review moderation elements, use the documentation, and operate the features publicly described on the site.

When a recording is triggered, the stated purpose on the site remains supporting a legitimate moderation action, and not casual, curiosity, or general surveillance use.

Recordings and storage

In line with the public pages, recordings are published in Discord, in the log channel of the relevant server, with an archive intended for use via the dashboard.

The site presents this architecture as a data sovereignty logic tied to the Discord space of the user's server. Recordings are not intended to be stored as a centralized library for purposes unrelated to server moderation.

Data access

The site and documentation indicate that the dashboard is reserved for authorized moderators and administrators of the server. Sensitive information is therefore not intended for public or general access by community members.

Administrators and moderation teams using Voicey remain responsible for the usage framework on their server, for informing members, and for complying with the rules they impose locally.

Cookies and sessions

The operation of authentication and the dashboard may involve the use of technical session mechanisms, essential for login, maintaining the authenticated state, and securing access to private pages.

No separate public commitment to advertising tracking or marketing profiling is presented on the site within the currently published pages.

Third-party services

The service relies on third-party platforms, notably Discord for identity, servers, messages and the publication of moderation-related elements, as well as GitHub Pages for hosting the public site.

Processing carried out by these third-party services also falls under their own policies, terms and technical obligations.

Rights and requests

Any request related to data processed via the site, dashboard access, or the publicly presented usage framework can be addressed via the project's public contact point indicated on the site, namely the Discord support server.

Requests must be assessed in light of the site's role, the nature of the data, the dashboard's security constraints, as well as the third-party services involved in Voicey's overall operation.

Policy updates

This policy may evolve to reflect changes made to Roicey, Voicey, the dashboard, moderation features, or third-party services used by the project.