Privacy and Data Policy

The controller of personal data is Anton Elizarov, identified on the Legal information page. For privacy questions or rights requests, email [email protected].

• item, options, order number and value, currency, network, and payment status;
• Telegram user and chat identifiers, bot state, delivery file identifier, and support-routing metadata;
• technical request data, including IP address and User-Agent, needed for abuse prevention, logs, and Cloudflare Turnstile.

VERIFIED WALLET does not ask for a third-party wallet password, seed phrase, or private key in support.

• contract performance and pre-contract steps: order creation, payment, digital fulfilment, and support;
• legitimate interests: site protection, abuse prevention, fault diagnosis, and defence of claims;
• compliance with applicable law and responses to competent authorities;
• consent only where expressly requested and withdrawable for the future.

Data is not sold or used for advertising mail or solely automated decisions with legal or similarly significant effects.

The language cookie and localStorage preference may last up to 12 months. Protected current-order data lasts no more than 24 hours. These mechanisms are necessary for language, security, and checkout state.

Advertising cookies, cross-site tracking, and user behavioural profiles are not used.

• the origin-server hosting provider contracted by the operator for hosting and technical operation;
• Cloudflare for protection and Turnstile;
• CryptAPI and the selected blockchain network for creating and checking a cryptocurrency payment;
• Telegram when the user selects that channel or sends a request;
• professional advisers and public authorities where required by law or necessary to defend a claim.

A public blockchain creates a record that VERIFIED WALLET cannot erase or alter.

• working data for an unpaid order is deleted approximately 60 minutes after creation; if a payment was created, deletion waits until the active payment window expires;
• paid-order working data is deleted approximately 24 hours after payment confirmation;
• registration data created before the personal account was retired is retained for: while the account is used and afterwards only as needed for legal obligations, dispute resolution, or deletion after a verified request;
• Telegram bot state and previously created support requests are kept only as needed for delivery, security, and operator replies; support requests are retained for: for the time needed to reply, resolve a dispute, and meet applicable legal obligations;
• where legal acceptance was separately recorded, its version and time are retained for: for the duration of the contract and afterwards as needed to prove acceptance, comply with mandatory law, or defend claims;
• minimal financial records may be retained longer for mandatory accounting, disputes, and defence of claims.

Where provided by law, a user may request access, correction, erasure, restriction, and portability, object to processing, or withdraw consent. Reasonable identity verification may be required before fulfilling a request.

A complaint may be sent to the President of the Personal Data Protection Office of Poland (Prezes Urzędu Ochrony Danych Osobowych) or another competent authority.

VERIFIED WALLET limits the data collected, encrypts connections, and restricts access. Some providers may process data in other countries; legally recognised transfer mechanisms are used where required. No transmission or storage method can eliminate every risk.

The server creates daily aggregate counters for public-page views and confirmed order and payment stages. Only bounded categories are used: UTC date, locale, coarse source, page type, product slug, payment method, and event type.

The measurement store does not contain cookies, session, customer, order, or payment-attempt identifiers, IP addresses, User-Agent, full Referer, or query strings. No third-party analytics or browser fingerprinting is used. View counts are directional because requests may repeat and bots are not identified; order and payment transitions are counted only after successful server operations. Daily aggregates are deleted after 400 days.