> For the complete documentation index, see [llms.txt](https://verlexy.gitbook.io/legality/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verlexy.gitbook.io/legality/privacy-policy-verlexy-bot.md).

# PRIVACY POLICY VERLEXY BOT

Last Updated: \[Beta Release Date, 17/sept/2026]

At Verlexy Bot ("We", "Our", "the Service"), we are fully committed to protecting the privacy of our users ("Users", "Players", "Creators"). This Privacy Policy outlines how we collect, store, use, and safeguard your personal information when you interact with Verlexy Bot on the Discord platform.\
\
By using our Service, you agree to the collection and use of your data in accordance with this policy.\ <br>

<h4 align="center">DATA WE COLLECT </h4>

<p align="center"><strong>We only collect the absolute minimum data required to ensure the functionality of your text RPG sessions and novel-sharing features:</strong></p>

<p align="center"><em><strong>1.1.</strong></em> <em><strong>Discord Identity Information:</strong></em><br>We detect and store your <mark style="color:$info;">Discord User ID, Username, and Guild/Server ID</mark> to identify your player profile, manage your in-game coins (Lexsi Coin), track subscription roles (Premium/VIP), and assign ownership of adventure threads. We never collect your real name, email address, or physical phone number.</p>

<p align="center"><em><strong>1.2.</strong></em> <em><strong>Adventure Chat History:</strong></em><br>We temporarily store the text of your roleplay interactions with the bot in our database. This is required to send the dialogue history to our Artificial Intelligence provider <mark style="color:$info;">(Google Gemini API)</mark> to maintain consistent memory and context during your game.</p>

<p align="center"><em><strong>1.3.</strong></em> <em><strong>Personal API Keys (BYOK Mode):</strong></em><br>If you choose to use the <em>Bring Your Own Key</em> (BYOK) feature by registering your personal Gemini API Key via the <code>/set-my-key</code> command, we will store your API Key on our server using <mark style="color:$info;">secure encryption methods</mark>.</p>

***

<h4 align="center">HOW WE USE YOUR DATA</h4>

<p align="center"><strong>We only use your data for functional purposes to provide and improve the Service:</strong></p>

<p align="center">- Connecting your active RPG sessions to the Google Gemini API to generate intelligent and immersive storytelling responses.</p>

<p align="center">- Managing your Creator Profile (Subscriptions, Likes, and Lexsi Coin balance).</p>

<p align="center">- Facilitating the export and import of your story progress via <code>/export-story</code> and <code>/import-story</code> commands.</p>

***

<h4 align="center">DATA RETENTION &#x26; AUTO-CLEANUP POLICY</h4>

<p align="center"><strong>We highly respect server efficiency and your right to be forgotten. Therefore, we enforce a strict and disciplined auto-cleanup policy on our VPS server:</strong></p>

<p align="center"><em><strong>3.1. Automated Inactivity Cleanup:</strong></em><br><em><strong>• Standard Free / Verified Creator Users:</strong></em> Active adventure threads that have been idle <mark style="color:$info;">(inactive)</mark> for <mark style="color:$info;"><strong>3 days (72 hours)</strong></mark> will be automatically and permanently deleted from our server database.</p>

<p align="center"><em><strong>• Premium / VIP Members:</strong></em> Active adventure threads that have been idle <mark style="color:$info;">(inactive)</mark> for <mark style="color:$info;"><strong>7 days (168</strong></mark> <mark style="color:$info;"><strong>hours)</strong></mark> will be automatically and permanently deleted from our server database.</p>

<p align="center"><em><strong>3.2.</strong></em> <em><strong>JSON Data Backup Assurance:</strong></em><br>Before any thread is permanently deleted from our server, Verlexy Bot will compile your entire adventure progress into a secure <code>.json</code> file (protected by <strong>HMAC-SHA256</strong> digital signature encryption) and send it directly to your Discord Direct Messages (DMs) or our secure backup channel if your DMs are closed. Once sent, <strong>your story data is 100% removed from our active server</strong> until you choose to restore it using the <code>/import-story</code> command.</p>

***

<h4 align="center">THIRD-PARTY DATA SHARING</h4>

<p align="center"><mark style="color:$danger;"><strong>We do not and will never sell, rent, or trade your personal data to third parties for marketing or advertising purposes.</strong></mark><strong> </strong><mark style="color:$info;"><strong>However, your text inputs must be processed by our AI infrastructure provider:</strong></mark></p>

<p align="center"><em><strong>4.1. Google Gemini API:</strong></em><br>Your active chat history is sent securely to the Google Gemini API to generate responses. According to Google Cloud Enterprise privacy policies, <strong>data sent through this API is private, secure, and will not be used by Google to train their public AI models.</strong></p>

***

<h4 align="center">DATA SECURITY</h4>

<p align="center"><strong>We implement industry-standard technical security measures to protect your information:</strong></p>

<p align="center">- Our Virtual Private Server (VPS) database is locked and only accessible by the main Developer.</p>

<p align="center">- Your personal API Keys (BYOK) are encrypted on our server.</p>

<p align="center">- All exported story files are signed with <em>HMAC-SHA256</em> signatures to prevent unauthorized file manipulation or cheating.</p>

***

<h4 align="center">USER RIGHTS (DATA CONTROL)</h4>

<p align="center"><strong>You retain full control over your data on Verlexy Bot:</strong><br><strong>- </strong><em><strong>Right to Delete API Key:</strong></em> You can permanently delete your personal API Key from our database at any time using the <code>/remove-my-key</code> command.</p>

<p align="center"><em><strong>-</strong></em> <em><strong>Right to Delete Active Sessions:</strong></em> You can instantly delete your active story history from our server by deleting your active adventure thread in Discord.</p>

***

<h4 align="center">CHILDREN'S PRIVACY (COPPA COMPLIANCE)</h4>

<p align="center"><em>Our Service is not directed to individuals under the age of 13. We do not knowingly collect personal data from children under 13. If we discover that a child under 13 has provided us with personal data, we will immediately delete it from our servers.</em></p>

***

<h4 align="center">CHANGES TO THIS PRIVACY POLICY</h4>

<p align="center"><em>We may update our Privacy Policy from time to time. We will notify you of any significant changes by posting an announcement in the official Verlexy Discord Server. Your continued use of the bot after such updates constitutes your acceptance of the new Privacy Policy.</em></p>

***

<p align="center"><br><strong>If you have any questions regarding your data or this Privacy Policy, please feel free to reach out to us in our official Discord Server's #<code>support</code> channel.</strong></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://verlexy.gitbook.io/legality/privacy-policy-verlexy-bot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
