Corrections policy

1. Scope

This policy covers the record Eagle Virtual LLC ("Eagle Virtual", "we", "us") publishes — the on-chain restriction events, the figures derived from them, and the way they are described — wherever it appears: the site, the data files, the API, and the MCP server. It covers factual errors: a record that does not match the blockchain it cites, a figure that is mis-stated, or wording that makes a correct record read as something it is not. Concerns about information we hold about you as a user are dealt with under the privacy policy at /privacy; concerns about a record that concerns you personally are covered by section 6 and by the notice at /data-we-publish.

2. How to report an error

Email legal@eaglevirtual.com with the wallet address or the event you are writing about, what the page or response says, and what you believe is correct. A transaction hash is the fastest possible report: every event we publish carries one, and it is the first thing we check.

You do not need an account, and you do not need to be the holder of the wallet. Anyone may report an error.

3. What happens next, and how long it takes

We acknowledge every report within two business days. We then check the claim against the blockchain itself, not against our own copy of it, because the failure we are looking for is a difference between the two.

Within ten business days of acknowledgment we either publish the correction or write to you explaining why the record stands, with the transaction that supports it. Where a report needs more time — for example because a chain is unreachable or the facts are disputed — we tell you that within the same period, and what we are waiting on.

If the record is wrong, we correct it and publish what changed. Corrections are additions to the record, never silent edits: the event store is append-only by design, so what a page said last month stays answerable, and every corrected record shows that it was corrected and when.

If the record is right, we say so and show the transaction that proves it. If our wording made a correct record read as something it is not, the wording is a defect and we fix it.

4. What we will not do

We will not remove a correctly recorded on-chain event because it is unwelcome. The event happened on a public blockchain, the transaction is public, and the record of it is the entire point of the Service.

We will not add commentary, context, or an opinion about why an action was taken. We do not know why, and inventing a reason would be worse than the omission.

We will not characterize any wallet or person. If you are asking us to mark an address as safe, clean, or cleared, the answer is that we do not publish that kind of statement about anyone.

5. Removal under a legal order

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 stating that a record was withheld under a legal order, the date, and nothing about the event itself. The note is the only thing that replaces a withheld record; we do not substitute a "clean" answer for it.

6. If the record concerns you personally

A wallet address is not a name, but it can identify a person. If information about you appears in the record and you believe it is wrong or misattributed, the process in sections 2 and 3 applies and we will work through it with you. What we can change is our record of what a public source published; what we cannot change is what the source published. Rights under data protection law, and how we review objections, are described at /data-we-publish.

7. 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. Corrections, legal, and data requests: legal@eaglevirtual.com. Other contact routes are published at /contact.