KYC and compliance
What we need from a partner, at which step, and how it is stored.
Why
We pay partners money, and we answer for whose traffic crosses our nodes. So we verify who receives the payouts and what the audience is — the depth of the check follows the turnover.
What we need up front
- Your name or your project's name.
- Email and Telegram.
- Country of tax residence.
- Links to the public channels that evidence the audience you claim.
That is enough to review the application and open the dashboard.
What we need as turnover grows
- An identity document, or registration documents for a company / sole proprietorship.
- A USDT-TRC20 address for payouts.
- Confirmation that you declare the income in your own jurisdiction — we do not collect declarations; the responsibility is yours.
The exact threshold at which the extended pack is requested is fixed in the partner agreement, along with the operating entity and its jurisdiction.
Storage
Documents live in encrypted object storage; access sits with the compliance owner, not with the engineering team. The retention period after termination is set out in the agreement.
Traffic we will not put on shared nodes
Gambling and adult are selectable in the application form, but that traffic damages address reputation for every other partner on the same nodes. The workable variant is running on your own nodes — see Your own nodes. Decided case by case, before signing.