> For the complete documentation index, see [llms.txt](https://zendius-jsc.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zendius-jsc.gitbook.io/docs/support/user-data-deletion-instructions.md).

# User Data Deletion Instructions

**Last Updated: September 30, 2026**

Zendius respects your privacy and provides users with the ability to request the deletion of personal data associated with our games and services.

If you have used **Facebook Login** to access a game or service operated by Zendius, you may request deletion of your account and associated data by following the instructions below.

### How to Request Data Deletion

To request deletion of your data, please contact Zendius support using the official support email provided in the game, application, or service you are using.

Please use the subject:

**Data Deletion Request**

In your request, please provide the following information:

* The name of the game or application you are using.
* Your in-game User ID, if available.
* The email address associated with your account, if applicable.
* A statement confirming that you would like Zendius to delete your account and associated personal data.

Please do not send your Facebook password or any other account password.

### What Happens After Your Request

After receiving your request, Zendius may ask for additional information to verify that you are the owner of the account.

Once your request has been verified, we will delete or anonymize personal data associated with your account that is stored and controlled by Zendius, except where retention is required for legal, regulatory, security, fraud-prevention, accounting, or other legitimate compliance purposes.

Data stored in backups may remain temporarily until those backups are overwritten or expire according to our standard retention procedures.

### Facebook Login Data

If you signed in using Facebook Login, Zendius may receive certain information from Facebook depending on the permissions you granted, such as:

* Facebook User ID
* Name
* Email address, if permission was granted
* Profile information made available through the permissions granted to our application

When your verified deletion request is processed, data received from Facebook and stored by Zendius will also be deleted or anonymized where applicable.

Please note that deleting data stored by Zendius does not delete your Facebook account or data independently stored and controlled by Meta. You can manage your Facebook account and connected applications through your Facebook settings.

### Removing the App from Facebook

You may also remove access to our application from your Facebook account:

1. Log in to Facebook.
2. Open **Settings & Privacy** → **Settings**.
3. Go to **Apps and Websites**.
4. Find the relevant Zendius game or application.
5. Select the application and choose **Remove**.

Removing the application from Facebook stops future access through Facebook Login, subject to Facebook's platform behavior. If you also want data stored by Zendius to be deleted, please submit a data deletion request using the instructions above.

### Contact

If you have any questions about data deletion or privacy, please contact:

**Zendius JSC**\
Hanoi, Vietnam\
**Email:** <zendius.studio@gmail.com>


---

# 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://zendius-jsc.gitbook.io/docs/support/user-data-deletion-instructions.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.