Skip to content
TRCBeacon

TRCBeacon Acceptable Use Policy

Effective date: October 12, 2026

This Acceptable Use Policy (the "AUP") applies to everyone who uses TRCBeacon (the "Service"), provided by Rivo Labs LLC, a limited liability company organized in New Mexico, USA (File # 3308017), 1209 Mountain Road Pl NE, #10346, Albuquerque, NM 87110, USA (the "Provider", "we"). It is part of the TRCBeacon Terms of Service (the "Terms"); capitalised terms have the meaning given there. If you do not comply with this AUP, we may act as set out in Section 5.

1. Purpose

1.1. The Service is a read-only monitoring tool for public blockchain addresses. We want it used for lawful purposes: protecting your own funds, reconciling payments, managing counterparty risk and meeting your own compliance obligations. We do not allow it to be used to facilitate crime, sanctions evasion or harm to others.

2. Prohibited uses

2.1. You may not use the Service, directly or indirectly, to:

(a) launder money, conceal the origin, ownership or movement of proceeds of crime, or structure transactions to avoid reporting or detection;

(b) evade, circumvent or violate sanctions, export controls or embargoes, including by dealing with persons, entities or addresses on the OFAC SDN list or other applicable sanctions lists, or by helping others to do so;

(c) finance terrorism or proliferation, or support any person designated for such activity;

(d) commit or facilitate fraud, scams, theft, extortion, ransomware, phishing, market manipulation, or trade in illegal goods or services;

(e) operate, support or serve unlicensed gambling or any gambling business that is not licensed in each jurisdiction in which it serves players. Licensed operators may use the Service and must provide evidence of their licence on request;

(f) track, profile, stalk, harass or surveil any person in breach of applicable law, or collect personal data about individuals without a lawful basis. Monitoring of your own wallets, your customers' deposit addresses with their knowledge, and counterparties in the course of lawful business is permitted;

(g) use the Service as a source for decisions to freeze, seize, report or accuse any person without independent verification;

(h) resell, sublicense, white-label or provide the Service or its data to third parties without our prior written consent;

(i) attack, probe, overload or disrupt the Service or its infrastructure; scan it for vulnerabilities without our written permission; scrape, mirror or bulk-extract data other than through documented API endpoints; exceed API rate limits or quotas; or use automated means to create accounts;

(j) bypass or attempt to bypass any access control, plan limit, territorial restriction or identity check, including by VPN, proxy, nominee, straw person, or purchased or borrowed accounts or phone numbers;

(k) misrepresent your identity, location, ownership or the nature of your business, or provide false KYB information;

(l) use the Service in or for the benefit of a jurisdiction or person excluded under Section 4 of the Terms;

(m) infringe the rights of others, or transmit malware or unlawful content through webhooks, labels or any other field;

(n) use the Service to develop a competing product or to benchmark it for publication without our consent;

(o) break any law applicable to you or to us.

2.2. Where the use of the Service is lawful for the purpose of AML or sanctions compliance (for example, monitoring an address that is on a sanctions list in order to detect and block exposure), it is not prohibited by this Section.

3. Your responsibilities

3.1. You are responsible for all activity under your account and API keys, for the Client Data you submit, and for the lawfulness of your own business.

3.2. You must keep your registration and KYB information accurate and tell us promptly of any change in ownership, control, location or licence status that affects Section 4 of the Terms or Section 2.1(e) of this AUP.

3.3. You must cooperate with reasonable requests for information to verify compliance with this AUP and with applicable law.

4. Reporting misuse

4.1. Report suspected misuse or a security issue to [email protected] or through @trcbeaconbot (command /support). Please do not publish vulnerabilities before we have had a reasonable time to fix them.

5. Our rights and enforcement

5.1. We may monitor use of the Service for compliance with this AUP and applicable law, to the extent allowed by the Privacy Policy.

5.2. If we find or reasonably suspect a breach of this AUP, of the Terms or of applicable law, or if a competent authority or law requires it, we may, with or without notice and at our discretion:

(a) warn you or ask for information or documents;

(b) limit, suspend or disable the account, an address, an API key, a webhook or a feature;

(c) terminate the account and refuse further registration;

(d) block or reject payments and refuse refunds (a refund is not owed for a suspension or termination due to a breach);

(e) preserve data as described in Section 6, and report the matter to the competent authorities as the law requires.

5.3. Immediate disablement without refund applies to breaches of Section 4 of the Terms (territory and sanctions), including circumvention by VPN or nominees, to Sections 2.1(a) to (e) and 2.1(j) to (l) of this AUP, and where required by law or authority.

5.4. A payment that U.S. law requires us to block will be blocked, will not be refunded, and will be reported as required by law; any other payment from an ineligible person is rejected and returned (Terms, Sections 4.5 and 7.3).

5.5. Our decision to act does not waive any other right or remedy, and our failure to act is not approval of the conduct.

6. Preservation and law-enforcement requests

6.1. Preservation. When we suspect a breach, or receive a lawful request, we may retain account data, Client Data, logs, screening records and payment records beyond the usual periods, as long as needed for legal purposes, and disable deletion of them. We hold such data as controller, solely for these legal purposes (Privacy Policy, Sections 1.2 and 4.1); data that is not needed for them is deleted under the Privacy Policy.

6.2. Government requests. We respond to requests for information from courts, law enforcement, regulators and other public authorities (including OFAC and FinCEN) only if they are made by a legally valid process or are required by law, and are addressed to us at [email protected] or at our registered address. We review each request for validity, scope and jurisdiction, may object or ask to narrow requests that are overbroad, and disclose only what we are legally obliged to disclose, or what is needed to prevent imminent serious harm.

6.3. Notice. Unless the law or a court order prohibits it, or notice would put someone at risk or prejudice an investigation, we will tell the affected client of a request for their data before disclosure, so that they can object. We keep a log of requests and our responses.

6.4. Reporting obligations. We may be required to report blocked property, sanctions matches and suspicious activity to authorities and may do so without notice to you, where the law requires or permits.

6.5. We do not hold your funds or private keys, and cannot freeze, return or release your assets, except payments made to us, including payments blocked under Terms 4.5. We can disclose only what we hold: account data, Client Data, screening results, payment records and logs.

7. Changes

7.1. We may update this AUP by the procedure for changes in Section 8.3 of the Terms, except that an update needed to comply with law or to address an urgent risk takes effect immediately.

8. Contact

8.1. [email protected] · Telegram @trcbeaconbot · Rivo Labs LLC, 1209 Mountain Road Pl NE, #10346, Albuquerque, NM 87110, USA.

TRCBeacon · TRON wallet monitoring

  • Terms of Service
  • Acceptable Use
  • Privacy
  • Contact
  • Telegram bot
Rivo Labs LLC · 1209 Mountain Road Pl NE, #10346, Albuquerque, NM 87110, USA
[email protected] · [email protected] · @trcbeaconbot

Read-only service: no keys, no custody, no transfers.