Binance data from 2023 emerges in Russian terrorism case

Those procedures explain how disclosure is supposed to work. The public record does not establish which Binance legal entity controlled Belenkiy's account, which law compelled the production, or whether he received notice.

A blockchain records transfers under addresses rather than passport names. That pseudonymity can be powerful until an address touches a centralized exchange. An exchange's know-your-customer file supplies the missing key. It can connect a wallet or deposit address to a name, phone number, address, document image, and device data. Internal transaction records can add the route between an on-chain transfer and an exchange account. Once the identity file and public ledger are joined, investigators can reconstruct activity that occurred years earlier.

Governments required centralized exchanges to collect more identifying data to deter money laundering, sanctions evasion and fraud. The same system produces a durable archive that can be used in tax cases, political investigations, or prosecutions under national security laws.

The permanence works in both directions. A blockchain can preserve evidence of criminal finance. It can also preserve a lawful donation that a government later classifies as criminal. The ledger cannot tell those uses apart. The legal system that attaches a name and offense to the transfer does that.

Belenkiy's case is especially sensitive because Russian authorities classify Azov as a terrorist organization and treat related support accordingly. A donation framed elsewhere as assistance to Ukraine can carry a radically different legal meaning inside Russia. Binance's role was to provide records, not to make that classification.

Belenkiy's Bulgarian residence permit adds an unresolved European issue. A residence card alone cannot establish that he was a customer of an EU Binance entity or that the General Data Protection Regulation governed the disclosure. Reuters could not determine his registration entity. The available facts offer no basis for alleging that Binance violated EU law.

If an EU entity controlled the account, GDPR rules would still require a legal basis and safeguards for sending personal data outside the bloc. The European Commission's guidance on international transfers explains that European protections can follow the data. Companies need an adequacy decision, approved safeguards, or a valid derogation.

Nor does GDPR create an unconditional right to erase an old exchange account. The Commission's explanation of individual rights says erasure can be refused when processing is required by law or needed for legal claims. Its example is a bank that must retain former customer details for 10 years even when the customer asks for deletion.

That distinction leaves users with two very different forms of control. Moving coins to self-custody removes the exchange from future custody and can limit new account records. Closing an account may stop future use. Neither action erases transactions already written to a public chain or records an intermediary must legally keep.

Binance's Russian exit was real at the level it announced: it sold the business and wound down local service. Belenkiy's prosecution exposes the extra layer carried by former customers. Companies leave markets on a corporate timetable. Personal data leaves, if it leaves at all, on a legal one.