LEGAL

Privacy Policy

Last updated: 13 November 2026

This Privacy Policy explains what information the Verosa service at verosa.io, its Telegram mini app and bot (the "Service") collect, why, who else receives it and what choices you have. "We" and "us" mean the operators of the Service. Terms in capitals have the meaning given in the Terms of Service.

We collect as little as the Service needs. We do not ask for your name, phone number, address or identity documents.

1. What we collect

Account. Your email address, your nickname, your chosen language and your password, which we store only as a one-way hash. If you turn on two-factor authentication, we store its secret in encrypted form and your recovery codes as hashes.

Telegram. If you link Telegram to your account, we store your Telegram user ID, your username and whether the bot may message you. Telegram also passes us your name, photo and language when you open the mini app; we do not store them. We do not store the messages you write to the bot.

Sessions and devices. When you sign in and use the Service we record your IP address, your browser's user agent and a random device identifier that the website keeps in your browser, together with the times of your sessions. We use them to keep you signed in, to show you your active sessions, to warn you by email about a sign-in from a new device and for security.

Offers and Trades. The offers you publish, including their terms text; the Trades you take part in, with their amounts, prices, fees, deadlines and status; the TRON addresses you give for payouts and refunds; and the public keys and signatures of the signing keys you register.

Trade chat. The messages and files (images, PDF documents) you send in a Trade's chat. Payment details that Users exchange there, such as card or account numbers, are part of these messages. Images are passed to the other User with their metadata (such as location) removed; the original file is kept as evidence.

Reputation and moderation. Ratings and reviews you give and receive, reports you make or that concern you, disputes, appeals, restrictions and the reasons for them.

Blockchain data. Transactions on the TRON blockchain are public. We read the transactions that concern Trades, including the addresses deposits come from.

Support. What you send us when you contact support.

2. What we do not collect

  • Your private keys. The signing key used in Trades is created in your browser and stays on your device, encrypted. A backup of it, if you make one, is a file saved to your device, protected by your passphrase; we never receive it.
  • Your fiat payments. They are made directly between Users, outside the Service.
  • Identity documents.

3. Why we use it

  • to provide the Service: accounts, offers, Trades, the trade chat and notifications;
  • to secure accounts and the Service, and to prevent fraud and abuse;
  • to decide disputes (section 5);
  • to run the reputation system, levels and limits;
  • to screen blockchain addresses against sanctions and illicit activity (section 6);
  • to answer support requests;
  • to improve the Service and understand how it is used;
  • to comply with law.

4. What other Users see

Your public profile shows your nickname, level, badges, reputation score, ratings and trading statistics. It does not show your email, your addresses or your Trades' amounts. In a Trade, the other User sees your nickname, your messages and files in the trade chat, and the addresses written into the Trade's terms. Reviews you write are shown with your nickname partly hidden.

Everything recorded on the TRON blockchain, including the Trade's Escrow Contract, its addresses and amounts, is public and can be seen by anyone.

5. Staff access

Members of our staff can see account and Trade data where their role requires it. Arbiters read a Trade's chat and files, including the unmasked originals, when they decide a dispute, and staff may read a chat when they investigate fraud or a report. Every such access is recorded in a tamper-evident log.

6. Address screening

The TRON addresses used in Trades are checked against public sanctions lists and the token issuer's list of frozen addresses. The addresses that deposits are sent from are also checked with an external blockchain analytics service, which receives only the address. The results are kept with the Trade.

7. Who else receives data

We do not sell your data. We share it only with service providers that help run the Service, and only what they need:

  • hosting and storage providers, where the Service and its files are kept;
  • an email delivery service, which receives your email address and the content of the emails we send you;
  • Telegram, if you link it: your Telegram ID and the text of notifications sent to you by the bot;
  • your browser's push service (for example the one run by your browser's vendor), if you turn on push notifications: the notifications we send, encrypted so the push service cannot read them;
  • TRON network infrastructure providers, which receive the addresses and transactions of Trades in order to read the blockchain and broadcast transactions;
  • the blockchain analytics service described in section 6;
  • analytics providers, where we use them (section 9).

We may also disclose data where the law requires it, or where it is necessary to protect the rights, property or safety of Users, the Service or others.

8. Cookies and storage in your browser

The Service uses:

  • one session cookie, which keeps you signed in. It is strictly necessary and cannot be turned off while you use an account;
  • local storage for your settings (theme, language, notification sound, push prompt), a sign-in flag and the random device identifier described in section 1;
  • session storage for short-lived interface state, such as when a code was last sent;
  • IndexedDB for your encrypted signing key.

You can clear these through your browser's settings. Clearing them signs you out, and clearing the site's data deletes the signing key on that device.

9. Analytics

We may use web analytics services to understand how the Service is used and to improve it. Such services may set their own cookies or similar technologies and may receive technical information such as your IP address, device and browser details, the pages you visit and how you interact with them. They do not receive your trade chat, your payment details or your keys. Where the law requires your consent for this, we will ask for it.

10. How long we keep it

We keep account, Trade, chat, reputation and dispute data for as long as your account exists and afterwards for as long as needed to resolve disputes, prevent fraud, keep records of Trades and meet legal obligations. Session and device records are kept for security and fraud prevention. Copies of sent emails and notifications are deleted after about 30 days.

11. Your choices and rights

  • You can change your nickname and language, and turn notifications on or off by channel and topic, in your account.
  • You can sign out other sessions and revoke signing keys.
  • You can deactivate your account when you have no Trades in progress. Deactivation ends all sessions; your Trades and their records remain.
  • You can ask us for a copy of your data, its correction or its deletion by writing to support. We will do what the law and the purposes above allow; records of Trades and the information needed to prevent fraud cannot be deleted while they are needed.

12. Security

Passwords and codes are stored as hashes, two-factor secrets in encrypted form, and all traffic uses encrypted connections. No system is perfectly secure; please protect your password, your two-factor device and your signing key.

13. Children

The Service is not meant for anyone under the age of majority, and we do not knowingly collect their data.

14. Changes

We may change this Privacy Policy. The date at the top shows the latest version; material changes are announced on the Service.

15. Contact

Questions and requests about your data: support@verosa.io.