Data we publish

1. Summary

Eagle Virtual LLC ("Eagle Virtual", "we", "us") publishes and cites public blockchain facts: the control actions that the companies issuing stablecoins and similar tokens record on-chain — blacklist additions and removals, freezes, seizures, and releases — and sanctions listings that a company has written to a blockchain contract. Every record carries the transaction and block that wrote it.

A record reflects what the cited on-chain source recorded. It is not an accusation, finding, or determination by Eagle Virtual about any person. If a record concerns you and you believe it is wrong or misattributed, section 9 explains how to reach us and what we can and cannot do.

2. Why we publish this notice

The events we publish can relate to identifiable people — most directly, the holder of a restricted wallet address. Because we obtain this data from public sources rather than from the people it concerns, data protection laws (including Article 14 of the EU GDPR and Brazil’s LGPD) require us to state publicly what we process, where it comes from, the basis on which we process it, and how people can exercise their rights. Where informing each person individually would be impossible or disproportionate, this page is our public notice.

3. What we publish

On-chain issuer control events. We decode and publish the enforcement events token issuers record on public blockchains — blacklist additions and removals, freezes, seizures, releases, and similar control actions affecting specific addresses. These are facts recorded permanently on public networks by the companies themselves; we cite the on-chain transaction evidence for each one. Where an event moved a balance, we publish the amount as the chain recorded it; where the event itself named no amount and we measured the balance at the block, the record says so.

On-chain sanctions listings. Where a company publishes a sanctions list to a blockchain contract, we record those entries as the on-chain facts they are — a company’s rendering of a list, written to the chain with its own lag — each with the transaction and block that wrote it. We do not reproduce government sanctions lists themselves, and no answer on this site is a government-list screening result.

Aggregates. We publish statistics derived from the record — counts by month, coin, chain, and company — that identify no one.

Where it appears. The record appears on the site’s public pages, in signed-in account views, in the data files the site publishes, over the API on paid plans, and through our MCP server for AI assistants. The coins, chains and event types covered are stated at /what-we-check.

4. What we do not publish, and the limits we place on the record

We do not publish our customers’ identities, saved address lists, or account activity.

We do not publish names, identities, or labels for addresses; we do not cluster addresses to individuals or infer who controls a wallet; and we do not assign risk scores, bands, or opinions to any person or address. Our records reproduce what a cited public source recorded, with its citation.

We limit how the record can be enumerated. Listing surfaces — recent-event feeds, per-coin and per-chain lists, the published data files, and the MCP server’s listing tool — carry only events from the most recent six months; older events remain reachable by looking up a specific address directly. We do not publish the full set of restricted addresses as a download, and we do not permit it to be harvested wholesale.

5. Where the data comes from

Every record is read from a public blockchain: from the contract events the issuing company emitted, and, for measured amounts, from the balance the chain recorded at the relevant block. We obtain nothing from the people the records may concern, and we do not buy, license, or combine third-party data about individuals.

6. Legal bases for publishing

Where data protection law applies, we rely on legitimate interests (GDPR Article 6(1)(f); LGPD Article 7 IX and Article 10): the interests of Eagle Virtual, its customers, and the public in being able to check whether a stablecoin balance has been frozen, seized, or blacklisted before funds move, and in a transparent, dated account of actions taken on public infrastructure. We balance those interests against the rights of the people concerned; the balance is strongly informed by the fact that every record we publish was already made public — recorded on a public blockchain by the company that took the action — and by the limits in section 4.

We also rely on the freedom to receive and impart publicly available information, and on the public interest in the transparency of permanent public blockchain records.

We do not use this data to market to, profile, or make automated decisions about the people it concerns.

7. What a record means — and does not mean

A record means the cited transaction happened on-chain. It is not an allegation, finding, or opinion by Eagle Virtual about any person, and it is not legal, financial, or compliance advice.

Answers carry coverage and freshness states. A wallet with nothing recorded against it has nothing recorded against it on the coins and chains we check, as of the date shown — that is all it means. "Can’t vouch right now" and "not yet checked" mean exactly that: they are unknowns, not findings.

Sources change: companies release addresses and reverse actions. Our record keeps the full history — an event and its later reversal are both shown, dated, so a wallet that was frozen and then unfrozen reads as exactly that.

8. How the record is licensed

The facts in the record are public and we claim no ownership of them. Our records and figures may be quoted, cited, and republished with attribution to Eagle Virtual and a link to the page the record cites, under the Creative Commons Attribution 4.0 license, carrying the date of publication. Machine-readable terms for automated use are published at /license.xml: they permit search, AI indexing and AI input with attribution, and do not permit use of the record to train AI models. The record may not be presented as a judgment about a person. The full terms are at /terms.

9. Your rights and our review process — including non-customers

You do not need to be a customer to contact us about data that concerns you. Depending on your jurisdiction, you may have rights to access, correct, object to, restrict, or request erasure of personal data, and to complain to your supervisory authority.

Email legal@eaglevirtual.com with the subject line "Data subject request". Include the specific record or page concerned, what you believe is wrong, your relationship to the data (for example, that you control the address), and your country of residence. We may need to verify your control of an address before acting. We respond within one month, or any shorter period applicable law requires.

What we will do: correct our errors promptly where we mis-decoded or inaccurately reproduced an on-chain record; re-check the source and propagate reversals; review objections individually, with the balancing assessment the law requires; and restrict processing while we review, where the law requires it. The factual-error route, with its position on removal stated in full, is the corrections policy at /corrections.

What we generally cannot do: remove an accurate record of a transaction that exists on a public blockchain. We do not remove a correctly recorded event voluntarily. If a court or an authority with jurisdiction orders one removed, we comply and leave a dated note in its place.

10. Who we are and how to contact us

Eagle Virtual LLC, a Florida limited liability company, 8586 Potter Park Dr, Sarasota, FL 34238, United States. For anything in this notice, write to legal@eaglevirtual.com; other contact routes are published at /contact. Our privacy policy, which covers information about you as a user of the service rather than the public record, is at /privacy.