CryptoAzPrivacy Policy
How CryptoAzPRO is intended to handle account, application and technical data.
1. Scope & minimization
This policy covers the CryptoAzPRO application and related official web services. Only data necessary for product operation, security, licensing, support and legal obligations should be processed.
2. Local application data
Local data may include interface settings, selected language and scale, workspace state, drawings, cache/history and other parameters actually used by the released application.
3. Market data & providers
Market information is generally market rather than personal data. Requests to external providers may disclose network or technical information under those providers’ own policies.
4. API keys
User-supplied analytical-provider API keys must be used only for the stated data function, must not be stored as plain text in ordinary settings files, and users must be able to remove saved keys.
5. Account, subscription & devices
The website architecture uses accounts, sessions, subscriptions, licenses and device activation. The final policy must enumerate the exact account fields, technical logs and retention periods used by the production backend.
6. Payments
CryptoAzPRO is designed around USDT payment verification. The final policy must describe the actual blockchain/provider infrastructure and what transaction, wallet/network and order data are processed.
7. Support & diagnostics
Support diagnostics should not intentionally include passwords, full API keys, access tokens or other secrets. Any automatic diagnostic transmission must be disclosed.
8. Technical logs & security
Server services may process IP address, request time, client version, session information and other technical data required for networking, security and diagnostics. Exact retention periods must be set before launch.
9. Marketing preferences
Transactional account communications remain separate from optional promotional marketing. Promotional messages must respect the user’s marketing preference and unsubscribe choice.
10. Sharing, international transfers & retention
Personal data should not be sold. Third-party processing, international transfers and retention must be limited to actual operational/legal needs and described according to applicable law.
11. User rights & deletion
Depending on applicable law, users may have rights of access, correction, deletion, restriction, portability and objection. A clear account/data deletion request process must exist before launch.
12. Contact
The final version must identify the product operator and provide an official privacy contact channel.
Official contact
For CryptoAzPRO support, privacy and legal enquiries: cryptoanalyzer2026@outlook.com.