2. Data Required for Service Operation

GuardPay processes a minimal volume of data necessary exclusively for providing the stated functions: delivery of notifications via Telegram, matching deal parties, and displaying statuses. We do not collect data for advertising or third-party analytical purposes.

We never request or store private keys, seed phrases, or wallet passwords.

Your account. When you sign in with Google we receive and store your email address and the name from your Google account — nothing else. The address lets us recognise you on another device, send you an invoice and warn you when a paid month is ending. If you register with a password, we store the name or nickname you gave, your email and the password — only as an irreversible hash: not even we can read the password itself. We do not send emails yet, so an email given at registration is confirmed only by signing in with Google to the same address. If you set a label for your referral link, it is stored in the account too; the label is visible to anyone you send the link to.

Stolen funds tracing. When you open a case on /stolen you give us the receiving address, the hash of your transfer and, optionally, your own address and a description of what happened. We store them together with the money trail we build and the case log, plus your device fingerprint and IP address to tell the case owner from a stranger, and your Telegram ID if you connect alerts. No wallet connection is needed; we never ask for private keys. The description goes into the platform letter and the statement generated on your request. The trail and log of a closed case are deleted after 180 days; the case record itself remains.

2.1. Cookies and Analytics on the Website

The split is simple: strictly necessary items always work, everything else runs only with your permission and is off by default. Silence is not permission: until you press Accept, no optional tracker is loaded.

• Strictly necessary (no consent). Interface language. Protection of wallet screening against bulk scraping: a session token and free-quota accounting. Without these the service you came for does not work.
• Visit analytics (with consent). A gp_s cookie lasting 12 months plus browser characteristics — screen, timezone, language, graphics adapter, platform. Taken together these characteristics can recognise a device between visits; we use them to understand which pages are used.
• Session recording (with consent). The third-party service Microsoft Clarity records cursor movement, clicks and page scrolling. It is a separate category and is enabled separately from analytics.

You can change or withdraw consent at any time — withdrawal erases both the choice and the gp_s file:

Open cookie settings

The full list — what exactly is stored on your device, who places it and for how long — is in the cookie declaration.

3. Disclosure of Data to Third Parties

GuardPay does not sell or disclose personal data to third parties for commercial purposes. The operation of the service is based on the infrastructure of the public TRON blockchain, to which any network participant has access.

4. Government Requests

Blockchain data (transactions, addresses, amounts) is publicly available without any request by its very nature. With respect to other data, GuardPay acts in accordance with applicable law.

5. Policy Changes

GuardPay reserves the right to update this policy. The current version is always available at this address. Continued use of the service following publication of changes constitutes acceptance thereof.

6. Contact

For questions related to data: