1. Data we process

• email for recovery and notifications;
• AR wallet number and internal account identifier;
• IP address, session and device information, and sign-in events;
• history of transfers, exchanges, P2P and Merchant transactions;
• 2FA settings, security-check statuses and service logs;
• messages and attachments that the user submits to support or a P2P dispute.

2. How data is used

• authorization, access recovery and account protection;
• execution and audit of financial transactions;
• prevention of replayed requests, fraud and abuse;
• delivery of webhooks and system notifications;
• review of support tickets and P2P disputes;
• error diagnostics and system integrity monitoring.

3. Password, PIN and 2FA

Passwords and financial PINs are stored as cryptographic hashes where supported by the relevant mechanism. 2FA secrets and system keys are protected separately. Support staff must never ask for a user password, financial PIN or current 2FA code.

4. Cookies and sessions

The service uses technical cookies for authorization, session protection, interface settings and antifraud controls. They are not intended for selling advertising profiles to third parties.

5. External services

Certain features may use external infrastructure providers, email, Telegram, currency-rate sources and merchant integrations. Only data required for the relevant operation or notification is transmitted.

6. Storage and protection

Financial and security logs may be retained longer than ordinary interface data because they are required for investigations, recovery and audits. Access to service directories, configuration, backups and keys is restricted on the server.

7. Requests

To request clarification, correction or deletion of data that can be removed without compromising financial and security audit requirements, create a ticket through the support center.