English
Reivyx

Privacy Policy

How Reivyx collects, stores, and uses information.

Effective date: August 28, 2026

1. What This Policy Covers

This Privacy Policy explains what information Reivyx may collect, store, and process while operating in Discord servers and providing dashboard features.

2. Information We May Collect

Depending on which systems a server enables, Reivyx may collect and store the following types of information:

3. Why We Use This Information

We use this information to operate the bot, provide server-management features, run verification and ticketing, send welcome messages, manage roles, protect servers from abuse, provide moderation tools, create transcripts, manage leveling and achievements, handle bug and problem reports, display dashboard statistics, and keep audit records for staff accountability.

4. Dashboard Login

When Discord login is enabled, the dashboard uses Discord OAuth and a secure HttpOnly cookie to identify authorized server owners and staff, select a language and server, and protect sensitive actions. Session data is stored in Redis or the configured session store and normally expires within 12 hours.

5. Who Can Access the Data

Data may be accessible to the server owner and authorized server staff, to the Reivyx team when required for support or security, and to infrastructure providers needed to operate the service. Access may occur through Discord, the dashboard, logs, ticket transcripts, and database storage. We do not sell user data.

6. Third-Party Services

The bot depends on Discord and may use third-party infrastructure such as Railway, Redis, and a database provider. Data may pass through or be stored by these services as needed to operate the service. When a server administrator enables media scanning and configures a provider, images, GIFs, stickers, or extracted frames may be sent to OpenAI Moderation and/or Sightengine for safety classification; the bot does not record or send audio. AutoMod continues to apply local rules for text, links, doxing, and dangerous files; flagged message content and metadata may be stored in a moderation event. Public information pages may be crawled and cached by search engines such as Google.

7. Optional Secure Browser Verification

When a server administrator enables secure browser verification, the verification page requests explicit consent before processing a random first-party browser token, coarse browser and device characteristics, and a shortened network prefix. Reivyx converts these values into server-specific HMAC digests before storage. This feature does not store raw IP addresses or raw browser characteristics. The purpose is to detect possible ban evasion and protect participating Discord servers. A match is a risk signal and is not technical proof that two Discord accounts belong to the same person. Server administrators may configure alert, quarantine, kick, or ban actions and should provide an appeal or manual-review process.

8. Data Retention

Data is retained for as long as needed to operate the server, maintain bot systems, handle tickets and reports, investigate abuse, preserve audit history, and keep server configuration. Website sessions normally expire within 12 hours. Secure-verification digests follow the administrator’s configured period, up to 365 days. Player-file event details follow the configured security-event period; summary counters remain until an authorized deletion request or deletion of the server data. Ticket transcripts, problem reports, logs, blacklist entries, level data, and configuration data may remain until deleted by authorized staff or until the bot data is reset.

9. Data Access or Deletion Requests

You may request access to or deletion of information related to you by opening a ticket in the official Reivyx support server or contacting the staff of the server where the bot was used. Some information may be retained when required for moderation, abuse prevention, security, or server records.

10. Security

We work to protect data by limiting dashboard access, keeping secrets in private configuration variables, isolating data between servers, and restricting staff tools. No system is perfectly secure, and we cannot guarantee absolute security.

11. Changes to This Policy

This policy may be updated when bot systems or service requirements change. The latest version will be available on this page.

12. Contact

For privacy questions or data-related requests, contact the Reivyx team through the official support server and open a support ticket.