Last Updated: November 10, 2026
This Privacy Policy describes how your personal information is collected, used, and shared when you visit or use Flexslot.gg or the Flexslot-Riftbound Discord card bot.
When you use our website, we may collect the following information:
We use the information we collect to:
We do not sell your personal information. We may share your information with third parties under the following circumstances:
For more information about how these services handle your data, please refer to:
You may access, update, or delete your personal information at any time through your Account Settings. If you have any questions about your data or your rights, please contact us at George@flexslot.gg.
The bot receives message text in Discord channels it can access. It checks for marked card references and sends the extracted lookup terms and optional set codes to Flexslot's card API, hosted on Railway. The lookup request does not include the complete conversation, your Discord username, or your server name as separate fields. Discord identifiers let the bot reply in the original channel and respond to interactions.
The bot does not keep a message-history cache or a card-query cache. Active navigation buttons hold lookup terms, card results, and reply identifiers in memory until the view times out after 15 minutes without interaction or the bot restarts. Server identifiers, bracket preferences, and Scryfall detection results remain in memory until the bot leaves the server or restarts.
Hosting services process request metadata, including IP addresses, request paths, response status, and timing. Current lookup logs omit query text, Discord usernames, and server names. Historical logs can contain these fields. Our Railway Pro plan provides 30 days of accessible log history; this is not a guarantee of permanent deletion after 30 days. Log access uses Railway's project and workspace permissions.
We do not use Discord message content to train machine learning or AI models. The bot has no per-user opt-out setting. Server administrators can restrict the channels the bot can view or remove the bot to stop it receiving messages in that server. Bot replies remain on Discord under Discord's retention and deletion controls.
For access or deletion requests concerning bot data, email George@flexslot.gg. Include the relevant Discord identifiers and approximate dates so we can locate records. Website account deletion does not delete Discord messages. We assess requests against the records and deletion controls available, including those of our hosting provider.
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
For any questions about this Privacy Policy, please contact us at George@flexslot.gg.
Last Updated: November 10, 2026
This Privacy Policy describes how your personal information is collected, used, and shared when you visit or use Flexslot.gg or the Flexslot-Riftbound Discord card bot.
When you use our website, we may collect the following information:
We use the information we collect to:
We do not sell your personal information. We may share your information with third parties under the following circumstances:
For more information about how these services handle your data, please refer to:
You may access, update, or delete your personal information at any time through your Account Settings. If you have any questions about your data or your rights, please contact us at George@flexslot.gg.
The bot receives message text in Discord channels it can access. It checks for marked card references and sends the extracted lookup terms and optional set codes to Flexslot's card API, hosted on Railway. The lookup request does not include the complete conversation, your Discord username, or your server name as separate fields. Discord identifiers let the bot reply in the original channel and respond to interactions.
The bot does not keep a message-history cache or a card-query cache. Active navigation buttons hold lookup terms, card results, and reply identifiers in memory until the view times out after 15 minutes without interaction or the bot restarts. Server identifiers, bracket preferences, and Scryfall detection results remain in memory until the bot leaves the server or restarts.
Hosting services process request metadata, including IP addresses, request paths, response status, and timing. Current lookup logs omit query text, Discord usernames, and server names. Historical logs can contain these fields. Our Railway Pro plan provides 30 days of accessible log history; this is not a guarantee of permanent deletion after 30 days. Log access uses Railway's project and workspace permissions.
We do not use Discord message content to train machine learning or AI models. The bot has no per-user opt-out setting. Server administrators can restrict the channels the bot can view or remove the bot to stop it receiving messages in that server. Bot replies remain on Discord under Discord's retention and deletion controls.
For access or deletion requests concerning bot data, email George@flexslot.gg. Include the relevant Discord identifiers and approximate dates so we can locate records. Website account deletion does not delete Discord messages. We assess requests against the records and deletion controls available, including those of our hosting provider.
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
For any questions about this Privacy Policy, please contact us at George@flexslot.gg.