This privacy policy explains how personal data is processed when using Relai, referred to below as the "App". We process personal data in accordance with the General Data Protection Regulation (GDPR).

Responsible

Niklas Mueller
Johann-Sebastian-Bach-Str. 23
34134 Kassel
Germany
Email: info@diszy.com

Hosting

The App and its backend are hosted by Contabo GmbH, Welfenstraße 22, 81541 Munich, Germany. Contabo acts as a processor under Art. 28 GDPR. Hosting is necessary to provide the service and maintain its secure and reliable operation (Art. 6(1)(b) and Art. 6(1)(f) GDPR).

Data processed by Relai

When an administrator configures Relai, the App stores the Discord server ID, the channel IDs for up to two source-to-destination relay pairs, the enabled state, the administrator's Discord ID, and—if selected—the filtered source author's Discord ID. This configuration is needed to route messages and can be viewed, changed, paused, or deleted by server administrators using the Relai commands.

When a message is considered for relay or explicitly submitted with /relai post, Relai processes:

• the Discord ID of the source author;
• the source message text and the original Discord message link;
• the Discord server, source channel, and destination channel IDs required for routing;
• image attachments and filenames when images are forwarded unchanged;
• a hash of the Discord ID and the associated shared Diszy credit balance, spending, and transaction records.

The source author's username and avatar URL may be processed transiently to label the translated post and prefill the Diszy credit checkout page. Relai does not create a persistent archive of source message text or image files. Messages and attachments remain stored by Discord according to the server's and Discord's settings. Operational logs may contain message IDs, status information, and error details, but are not intended to contain message text.

Purpose and legal basis

Message, routing, and attachment data are processed to provide the requested translation relay (Art. 6(1)(b) GDPR). Discord identifiers, billing data, and limited operational logs are processed to administer shared credits, prevent misuse, diagnose failures, and operate the App securely (Art. 6(1)(b) and Art. 6(1)(f) GDPR).

Storage and deletion

Relai does not persistently store source message content or copied image files in its own application database. Per-server routing configuration remains stored until an administrator runs /relai reset or the App is removed from the server. Discord IDs, their hashes, credit balances, spending, and transaction records remain stored while the shared Diszy account is used and as required for contractual, accounting, fraud-prevention, and legal-retention purposes. You may request access, correction, or deletion by contacting info@diszy.com; statutory retention obligations may limit immediate deletion of transaction records.

Processing by Google Gemini

Source message text that is not a native Discord reply is sent to the Gemini API provided by Google for a combined standalone-message evaluation, automatic language detection, and translation. Conversational messages classified for skipping are not posted and do not consume the user's credits. Text submitted with the explicit /relai post command bypasses the standalone-message evaluation. Images are not sent to Gemini by Relai. Google receives the text and technical request metadata needed to return the decision and, when applicable, translation. This processing is required to provide Relai's core service (Art. 6(1)(b) GDPR).

For paid Gemini API services, Google states that prompts and responses are not used to improve its products. Google may retain prompts and responses for a limited period for abuse monitoring unless applicable zero-data-retention controls are in place. Details are available in the Gemini API Additional Terms and Gemini API data-retention documentation.

Processing by Discord

Relai operates on Discord and receives and posts messages through Discord's platform. Discord independently processes account, message, server, and attachment data under its own privacy policy. Removing Relai or revoking its permissions stops future relays, but does not automatically delete messages already stored in Discord channels.

Your rights

Subject to the GDPR, you may have rights of access, rectification, erasure, restriction, data portability, and objection. You may also lodge a complaint with a competent supervisory authority. To exercise your rights regarding data controlled by the App operator, contact info@diszy.com.

By adding the Discord App Relai, application ID 1536622881411309590 ("Relai"), to a Discord server, you understand and agree that:

• Configured relay: Relai reads new messages only in up to two source channels selected by a server administrator. The administrator may restrict both relays to one source author or allow all non-bot authors. Each source has its own configured English destination.
• Authorization: The server operator is responsible for having the necessary permission to relay the source author's messages and images into the destination channel and for informing affected server members.
• AI processing and filtering: Native Discord replies are ignored locally. Other message text is sent to the Google Gemini API for a combined standalone-message evaluation, automatic language detection, and translation. Conversational messages may be skipped, and automated classification can be incorrect. The configured author can explicitly publish with /relai post. Images are forwarded through Discord unchanged and are not sent to Gemini for text recognition or translation.
• Translation limitations: Automated translations can contain errors. Relai does not provide financial, investment, legal, medical, or other professional advice. Users must verify information before relying on it.
• Unified credits: Relayed text consumes the source message author's shared Diszy credits. The current request cost is displayed beneath the translated post. Conversational messages skipped by the evaluator and image-only relays do not consume user credits. When available credits are exhausted, that source author must top up to continue using AI translation.
• Content responsibility: Users must not use Relai to process or redistribute unlawful, infringing, confidential, harmful, or otherwise unauthorized content.
• Availability: Relai is provided without a guarantee of uninterrupted or error-free availability. Discord, Google, hosting, or network outages may delay or prevent translations.
• Stopping the service: Administrators can pause Relai, delete its server configuration, remove it from the server, or revoke its channel permissions. Relai does not backfill messages or synchronize later edits and deletions.

More information about Relai is available at https://diszy.com/bots/relai/.

Relai runs automatically after a server owner or administrator completes setup.

Admin setup commands

Command	What it does
/relai setup	Add or update exactly one source-to-English channel pair. Run the command separately for the optional second pair. Rerunning it for an existing source updates only that source's destination and leaves the other pair unchanged. The optional author filter is shared by both pairs.
/relai post	Explicitly translate and publish text and up to three images from the current configured source channel. This is available to the configured source author and bypasses automatic conversational filtering.
/relai status	Show the current routing, author filter, and enabled state.
/relai test	Post a permission test in every configured destination channel.
/relai enable	Resume translations without changing the setup.
/relai disable	Pause translations while retaining the setup.
/relai reset	Delete this server's stored Relai configuration.

The setup, status, test, enable, disable, and reset commands require the Discord Manage Server permission. The post command is reserved for the configured source author when an author filter is set.

How it works

1. A server administrator runs /relai setup source:#source target:#english author:@person once for each independent channel pair, up to two times.
2. For example, configure #chat-de → #chat-en, then run setup again for #trading-talk-de → #trading-talk-en. Neither setup replaces or crosses into the other route.
3. Native Discord replies are ignored. Other new text is evaluated and translated in one AI request only when it is a self-contained post that makes sense without prior conversation.
4. Conversational answers, acknowledgements, and context-dependent fragments are skipped. Skipped messages are not posted and do not consume user credits.
5. Each translated post identifies the original author and links back to the original Discord message.
6. The configured author can use /relai post in either source channel to explicitly publish content that should bypass the evaluator.

Supported content

• Automatic language detection for German, Spanish, French, Arabic, CJK languages, mixed-language messages, and other languages supported by Gemini.
• Already-English text is preserved.
• Trading terminology, Markdown, links, mentions, emojis, timestamps, numbers, and code are protected during translation.
• Images are re-uploaded unchanged with their original filenames. Text inside images is not translated.
• Image-only native replies are ignored; other image-only posts bypass AI and are relayed directly.
• Only future messages are relayed; edits, deletions, and historical messages are not synchronized.

Credits

Text translations use the shared Diszy credit balance of the person who wrote the source message. The credit cost appears beneath each translated response. If the balance is depleted, Relai displays the existing Diszy top-up link. Image-only relays do not use AI and do not consume credits.