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

# Privacy and Data

This page explains the types of data Cryptoix may process to provide its services, how it's handled, and your responsibilities. For official legal details, please always refer to the Cryptoix Operator's official Privacy Policy.

## Data Cryptoix May Process

To offer a secure and functional payment gateway, Cryptoix may process various types of information. We aim to be transparent about what data is involved.

### Payment and Transaction Data

This includes information necessary to process your payments and manage your transactions.

* **Transaction Details:** What was purchased, the amount, currency, and payment status.
* **Payment Method Information:** Details related to the cryptocurrency used for payment, such as wallet addresses involved in the transaction.
* **Order Information:** Any details you or the merchant provide about the order or service being paid for.
* **Refunds and Support Records:** Information related to any refund requests or support interactions.

### KYC and Identity Data

For certain features and to comply with regulations, Cryptoix may require identity verification.

* **Identity Documents:** Scans or photos of your government-issued ID (e.g., passport, driver's license), if required by the operator.
* **Personal Information:** Your name, address, date of birth, and contact details provided during the verification process, if required by the operator.
* **Verification Status:** Whether your identity has been successfully verified.

### API Keys and Security Data

If you are a merchant using the Cryptoix API, specific security credentials will be generated and managed.

* **API Keys:** Secret keys generated within your merchant dashboard that allow your systems to interact with Cryptoix.
* **Account Credentials:** Your username, password (securely hashed), and any other authentication details.
* **Security Logs:** Records of login attempts and security-related events on your account.

### Third-Party Services

Cryptoix integrates with various external services to provide its full functionality. The data processed by these services is subject to their own privacy policies. These services are used only where configured by the operator.

* **Blockchain Providers:** To process cryptocurrency transactions, Cryptoix may interact with blockchain networks. This involves using public blockchain data and potentially third-party nodes or explorers.
* **Exchange Rate Providers:** Services like CoinGecko, Binance, or CryptoCompare may be used to fetch real-time cryptocurrency exchange rates.
* **Email Providers:** Used for sending important notifications, receipts, and password resets.
* **Telegram:** If configured by the operator, notifications might be sent via Telegram.
* **OAuth Providers:** If you choose to sign up or log in using services like Google, GitHub, Microsoft, Discord, or Apple, your authentication data is handled by them.
* **KYC Providers:** Services like Sumsub may be used for identity verification, processing the documents and information you submit.

## Data Retention and Deletion Requests

Retention periods depend on the operator’s configuration, legal obligations, and official privacy policy.

* **Retention Periods:** Specific retention periods vary based on the type of data and legal requirements. Transaction data, for example, is typically kept for a longer duration for auditing and compliance.
* **Deletion Requests:** If you wish to request the deletion of your personal data, please refer to the official Cryptoix Privacy Policy for instructions on how to submit such a request. Please note that certain data may be retained due to legal or operational necessities.

## Security Responsibilities

Protecting your account and data is a shared responsibility.

### Your Responsibilities

* **API Keys:** Treat your API keys with the same level of security as your passwords. Do not share them publicly, embed them in client-side code, or store them in insecure locations.
* **Wallet Addresses:** Use only the deposit/payment addresses shown by Cryptoix, and carefully verify any withdrawal destination address you enter or save before sending or requesting funds.
* **Account Credentials:** Use strong, unique passwords for your Cryptoix account. Keep your login credentials confidential. If the operator offers external account integration (e.g., via OAuth), ensure those accounts also have strong security practices.
* **Third-Party Integrations:** If you connect Cryptoix to other services, ensure those services also have strong security practices.

### Cryptoix's Responsibilities

Cryptoix includes security-related controls, but deployment configuration and operational practices are the operator’s responsibility. Review the operator’s security and privacy policies for details on how your data is protected.

***

**Disclaimer:** This information is intended as a helpful guide for end-users. For definitive legal terms and conditions regarding data processing and privacy, please consult the official Cryptoix Operator's Privacy Policy.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.cryptoix.io/privacy-and-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
