Privacy Policy
Relay only collects information needed to run the bot, dashboard, licensing and support features.
Information Relay stores
Relay may store your Discord account ID, username, avatar, email address if Discord provides it during login, servers you connect, Relay configuration, usage analytics, license status and payment status. If a server uses Captcha verification, Relay processes connection and basic browser interaction information to complete the check. Relay stores the IP address as a server-scoped keyed fingerprint rather than a readable IP address, together with limited device/browser fingerprints so optional alt protection can compare later accounts on that server. If a server owner enables ticket transcripts, Relay also stores the text content and basic author/time information from closed Relay ticket channels. Attachments and images are not stored in transcripts.
How the information is used
The information is used to sign you in, connect Relay to your Discord servers, save your settings, provide bot features, prevent abuse, manage trials and licenses, and support the service.
Payments
Payments are processed by Stripe. Relay does not store your full card number or card security code.
Sharing
Relay may share the minimum information needed with service providers such as Discord, Stripe and hosting providers so the service can operate. Relay does not sell personal information.
Retention and deletion
Server configuration is normally kept while your Relay access is active. Ticket transcripts use a rolling limit of the newest 300 transcripts per server, so older transcripts are removed as new ones are saved. After an expiring license ends, server data may be kept for up to 30 days so it can be restored if you renew. Some account, trial and license records may be retained longer to prevent repeated trials, maintain billing history and protect Relay from abuse.
You can use the account controls in Relay to remove your account data where available.
Changes
This policy may be updated when Relay changes. The current version published on this page applies to use of the service.