No-KYC aggregator claims: interface access and business onboarding differ

Read a “no KYC” claim as a statement about a particular product flow. It does not establish that every service with the same brand has identical onboarding, that every asset is available, or that the transaction is private.

Retail trading and developer access differ

1inch Business onboarding documents identity or business verification for specified account and subscription actions. That is a commercial API relationship. It should not be generalized into a claim that every retail 1inch swap requires the same process, nor ignored because the underlying protocol is decentralized.

The wallet may show several exchange types

Trezor Suite’s current guide separates CEX and DEX offers. It describes DEX use without personal-information submission, while centralized providers may request verification, including in some refund situations.

That difference is relevant before choosing an offer. A simple initial deposit process does not prove that a centralized provider can never request information later. Read the selected provider’s conditions instead of treating the hardware wallet as the exchange service.

Availability is another separate question

The 1inch RWA announcement restricts that asset product by jurisdiction and issuer eligibility. An ordinary wallet connection does not remove those product conditions. This example concerns RWA access, not all tokens on the same chain.

Finally, a public transaction can reveal addresses, token movements and amounts even if a swap screen never asks for a passport. Avoid substituting “anonymous” for “no account creation.” They answer different questions.

For selection, record four separate facts: whether an account is needed, whether identity verification is requested, whether the user and asset are eligible, and what information becomes visible through the transaction. A precise answer to those questions is more useful than a blanket no-KYC label.