# Privacy Policy

### Privacy Policy

#### Introduction

At Zaro, we respect your privacy and the importance of protecting your data. This Privacy Policy explains our privacy practices for the activities listed below. In line with your rights, we explain how we collect, store, access, and otherwise process information related to individuals. In this Policy, **Personal Data** means any information that, by itself or when combined with other available information, can identify an individual.

This Policy applies to the Zaro website, API, and scripts. It does not apply to third-party applications, websites, products, services, or platforms that may be reached through links we provide. Those sites are owned and operated independently, and they follow their own privacy and data collection practices. Any personal data you provide to those sites is governed by that third party's own privacy policy. We are not liable for the actions or policies of those independent sites, and we are not responsible for their content or privacy practices.

This Policy applies when you interact with us in any of the following ways:

* Use our application and services as an authorized user
* Visit any of our websites that link to Terms of Service
* Run a script protected by Zaro

#### Data we collect

We collect information about you in different ways. For example, we collect information you provide when you register, fill out a form, or use our application or services. Data we collect may include:

#### For script users:

If you are running a script protected with Zaro, this section applies to you. We collect the following data:

* IP addresses *(required as part of access control. Many similar services do this.)* This information is not directly shared with the script owner. They can only see your country, not your full IP.
* Timestamps *(the time when you executed the script)*
* This information is delivered to the script owner if they enable webhook log delivery.
* HWID and User-Agent headers *(do not contain sensitive information)*
* HWID is a hash of device properties. It does not contain sensitive information. It is used only as part of access control because it is usually unique per device.
* Discord ID, This information is collected to support the 2-step verification process.
* ❌ In-game stats and similar data are not collected.
* These are not collected or required by Zaro.
* However, if the script developer added their own webhook logger inside their script, we would not know.

#### For developers:

If you own a Zaro key or use the Zaro dashboard, this section applies to you.

* IP addresses, timestamps, and data you provide when adding users
* Email address and Discord ID *(for login)*
* Any data you submit through input fields on the website or API *(for example script names, webhooks, and user notes)*, except the script upload button
* ⚠️ Scripts uploaded by you are automatically deleted from our systems after obfuscation.

#### Service providers and other third parties

We use third-party service providers for obfuscation and webhook log delivery and ads etc. These providers may operate locally or outside your region. We share data with them. The data we disclose includes:

* IP address and HWID header of your users *(for webhook log delivery)*. IP is only sent if an anti-tamper measure is triggered.
* Webhook log delivery is optional and can be disabled by the script owner.
* This information is sent to the **DISCORD.COM** API for webhook log delivery.
* Script files you upload *(for obfuscation)*

#### How to Delete Data

Currently for now you can't delete any data such as discord id and login deatils and to unlink your discord account, For this you must contact us on discord&#x20;

#### Cookie Policy

Like most websites, we use cookies to collect information. Cookies are small files stored by a website on your computer or mobile device. They are commonly used to help websites function properly.

By visiting our website, you consent to the use of cookies. Cookies may include favicons, API keys, and user details. You can remove cookies in your browser settings or by logging out of your account.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zaroguard.com/privacy-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
