What 1inch Can See When You Connect a Wallet: Address Screening, Metadata and Privacy Limits

Connecting a wallet to 1inch does not reveal its private key or recovery phrase, but it does reveal a public blockchain address to the interface. That address can expose balances, transaction history, token approvals and relationships with other addresses. The website can also process technical metadata such as an IP address, browser information and interaction records, while screening systems may compare wallet activity with risk databases.

Last reviewed: October 1, 2026. 1inch products, privacy terms, screening providers, regional restrictions and supported connection methods can change. Review the current Privacy Policy and interface notices for the product and legal entity you use. This independent guide is educational, does not offer legal advice and does not describe methods for bypassing sanctions or access controls.

What happens when you connect a wallet to 1inch?

A wallet connection establishes a communication session between the selected account and the 1inch interface. The dapp can learn which public address is connected, identify the selected network, query public balances and prepare requests for quotes, signatures or transactions.

Connection is not the same as signing. A website can propose an action, but a self-custody wallet should still require approval before producing a signature or broadcasting a transaction. Read each wallet prompt because permissions differ between simple connection, message signing, token approval and asset transfer.

What 1inch can see immediately

What a wallet connection does not reveal

A standard connection should not expose:

• the wallet’s private key;
• the Secret Recovery Phrase;
• a hardware wallet PIN;
• passwords for unrelated services;
• automatic authority to sign every future transaction.

If a site claiming to be 1inch asks users to type recovery words, it is not a normal connection flow. Close it and verify the official domain independently.

Public address does not mean anonymous identity

A blockchain address is pseudonymous: it is an identifier without a legal name embedded in it. The transaction graph around that address is normally public. Once the address is associated with an exchange account, ENS-style name, merchant payment, social profile or disclosed identity, past and future activity may become easier to attribute.

The same address reused across swaps, NFT activity, payroll, donations and public posts creates one connected profile. Self-custody removes a custodian from key control; it does not erase the public ledger.

Onchain data visible from a connected address

• native-asset and token balances;
• incoming and outgoing transactions;
• contract interactions and method data;
• token approvals and approved spenders;
• swap routes and settlement transactions;
• NFT ownership and transfers;
• DeFi deposits, debt and liquidity positions;
• timing, frequency and gas-spending patterns;
• links to counterparties and bridge activity.

Wallet software may display only part of this information, but analytics providers can read the underlying chain directly.

Website and device metadata

Like other online services, a dapp interface can receive data required for networking and operation. Depending on the product and consent context, this can include IP address, browser or app type, operating system, language, approximate region, timestamps, referring pages, security events and interaction logs.

This metadata is different from blockchain data. Onchain transactions are replicated across a public network; website records are processed by the service and its providers under their terms, retention practices and legal obligations.

What the 1inch Privacy Policy says

1inch’s published Privacy Policy describes processing that can include public wallet addresses, transaction and balance information, product-usage data and technical information. In limited circumstances, a product may also require due-diligence or verification information under applicable rules.

The exact controller, lawful basis, recipients, retention period and available rights can depend on location and product. Read the current policy rather than assuming every 1inch-branded interface has identical data flows.

How 1inch wallet screening works

1inch describes screening wallet addresses and product interactions against internal and third-party information. The goal is to identify links to known threats, illicit activity, sanctions exposure, stolen funds, phishing, hacks or other risk categories.

A screening result is not generated from a recovery phrase. It is based on public addresses, transaction graphs, external intelligence, lists and behavioral indicators available to the screening system.

Risk scores and transaction history

According to 1inch, its risk engine can consider wallet history, behavioral patterns and external data. A provider may distinguish direct ownership risk from indirect counterparty exposure and examine connections across multiple transaction hops.

Risk classification is probabilistic and provider-dependent. False positives, outdated labels and differing methodologies are possible. A blocked interaction should be handled through official support or review routes, without sending private keys or recovery words.

Third-party screening providers

1inch has publicly named sources and partners including TRM Labs, Etherscan, Blockaid, Hypernative, ZeroShadow and internal blocklists. Providers and purposes can change. Some focus on financial-crime risk; others identify malicious dapps, scam tokens, exploits or dangerous transactions.

Using several sources can improve detection but also means a wallet interaction may be evaluated against information maintained outside the immediate 1inch interface. Consult current policies for details about recipients and processing.

Custom blocklists and reported addresses

1inch says its internal blocklist incorporates independent databases and information supplied through ecosystem investigations. Trusted organizations or law-enforcement partners may report addresses connected with incidents.

A blocklist entry can restrict interaction with the interface or supported products; it cannot delete the address or its blockchain history. Smart contracts and frontends also have different enforcement abilities, so “the protocol,” “the website” and “the wallet” should not be treated as one identical layer.

Frontend, API and protocol are different layers

Geofencing and region detection

1inch states that it restricts product access in sanctioned or otherwise unsupported jurisdictions. Geofencing can use IP-derived location and other signals to decide whether an interface or service is available.

A region restriction is not a statement about who owns the private key. It is a product-access and compliance control. Users should not attempt to evade legal or contractual restrictions; consult the current terms and qualified advice if eligibility is unclear.

Why a VPN does not make a wallet anonymous

A VPN can change the IP address visible to a destination service, but it does not rewrite the public transaction history of a connected wallet. Address reuse, timing, amounts, exchange withdrawals, bridge paths and other activity can still connect transactions.

1inch also describes controls intended to detect VPN or proxy-based access where regional restrictions apply. A VPN is therefore neither a blockchain privacy tool nor an authorization to bypass service rules.

WalletConnect privacy

WalletConnect establishes an encrypted communication session between a wallet and dapp. It reduces the need to expose keys to the website, but the selected account, requested networks and transaction proposals still need to be shared for the session to work.

Review which accounts and chains are authorized, reject unexpected requests and disconnect sessions that are no longer needed. Disconnecting stops that session; it does not remove completed transactions or information already processed.

Browser-extension connection privacy

A browser wallet can expose selected accounts to an approved site and may remember that permission. Browser extensions, history, cookies and local storage create another privacy boundary around the session.

Use a dedicated browser profile where appropriate, remove unnecessary extensions and periodically review connected sites inside the wallet. A malicious extension can observe or alter far more than a normal dapp connection.

Connection, signature, approval and swap are different

Read the wallet prompt rather than judging risk by whether the button says Connect, Sign or Confirm. Structured signatures can carry significant authority.

Does disconnecting 1inch revoke token approvals?

No. Disconnecting removes the communication session between wallet and dapp. A token approval is an onchain contract state and remains until reduced, revoked, consumed or otherwise invalidated.

Review allowances separately using the current 1inch approval tools or a reputable explorer on the correct network. Confirm the token, spender and revocation transaction on the wallet display.

Does disconnecting erase data?

No. Completed blockchain transactions cannot be removed by disconnecting. The interface or providers may also retain records as described in applicable policies, security requirements and law.

Privacy rights such as access, correction or deletion may apply to some offchain personal data, subject to legal exceptions. They do not allow a service to delete records from an immutable public network.

Fusion privacy considerations

Fusion uses signed intents and third-party resolvers rather than broadcasting a conventional user swap through the public mempool in the same way as a classic swap. This can reduce exposure to front-running and sandwich attacks during execution.

MEV protection is not anonymity. The order still contains information necessary for settlement, and final onchain asset movements remain observable. Wallet screening and interface metadata are separate from mempool exposure.

Fusion+ cross-chain privacy

A cross-chain swap creates activity on at least two networks. Amounts, timing, source and destination transactions may provide linking signals even when the protocol coordinates execution through intents.

Cross-chain convenience does not erase traceability. Review both network histories, destination address and any intermediate settlement steps shown by the official interface.

Classic swaps and routing

A classic aggregated swap may route through several liquidity sources. The execution path, contract calls, token approvals and final transfers are visible onchain. Splitting a route across sources is an execution strategy, not a privacy guarantee.

Quote requests may also contain token pair, amount, chain and wallet-related parameters needed to build the transaction. Avoid assuming that “non-custodial” means no operational data is processed.

What resolvers and liquidity providers need to know

Resolvers and liquidity participants need order information sufficient to evaluate and fulfill a signed intent. This may include asset, amount, acceptable return, deadline and settlement conditions.

They do not need the user’s recovery phrase. If someone claiming to be a resolver asks for a seed phrase, private key, remote access or advance payment, stop the interaction.

Portfolio tools and watch-only addresses

Portfolio or watch-only features can monitor a public address without its signing key. This is useful for tracking, but adding several addresses to one interface can create an explicit grouping in that product’s usage context.

Watch-only access never grants the ability to spend. A scammer offering a funded watch-only wallet is not transferring ownership; without the private key, the displayed assets cannot be moved.

Separate addresses by legitimate purpose

Using one address for every activity makes public profiling easier. Separate accounts for long-term storage, routine DeFi activity, public donations or organizational operations can reduce unnecessary linkage and limit the impact of a malicious approval.

Separation must be genuine and manageable. Transfers between the addresses remain public and may connect them. Maintain lawful records for accounting and tax obligations, and do not use address separation to evade restrictions.

Operational privacy practices

• Connect only the account needed for the current task.
• Use verified 1inch domains and official applications.
• Review wallet sessions and disconnect those no longer used.
• Remove unnecessary token approvals separately.
• Avoid publishing addresses tied to private holdings.
• Do not reuse a transaction-history address without verifying its source.
• Keep recovery words offline and out of browsers and cloud notes.
• Use dedicated accounts for experimental dapps and limited balances.
• Review cookie and privacy settings available in the interface.
• Export records needed for legitimate tax and accounting duties.

Privacy versus security

Privacy limits who can connect activity to a person or broader profile. Security limits unauthorized control or loss. A wallet can be secure while its complete history is public, and an address can be hard to attribute while its private key is poorly protected.

1inch screening and transaction warnings are security and compliance controls that may require analyzing public activity. Users must weigh the visibility created by those protections against their personal privacy needs and product eligibility.

Responding to a blocked or flagged wallet

1. Do not follow support links sent in unsolicited messages.
2. Record the exact public address, network, time and error message.
3. Check official 1inch status, help and support channels.
4. Provide public transaction hashes only when relevant.
5. Never provide a private key, recovery phrase or authentication code.
6. Ask what review or appeal process is currently available.
7. Preserve lawful source-of-funds documentation where appropriate.

Do not pay a third party promising to “clean” an address or remove an immutable transaction history.

Common privacy misunderstandings

• “Connecting gives 1inch my private key.” A standard connection shares a public account, not signing secrets.
• “Self-custody is anonymous.” Key ownership and transaction visibility are different questions.
• “Disconnect deletes my history.” Onchain records and previously processed data remain.
• “Revoking a session revokes approvals.” Allowances require a separate onchain action.
• “A VPN hides the wallet.” It does not alter the transaction graph and may be restricted.
• “Fusion makes swaps private.” MEV-resistant execution is not anonymity.
• “A watch-only wallet owns the funds.” It can view an address but cannot sign for it.
• “A new address erases all links.” Public transfers and common usage can reconnect addresses.
• “Non-custodial means no data collection.” It means the service does not hold the user’s signing keys.

1inch privacy checklist

• The official 1inch domain or application has been verified.
• Only the necessary wallet account and network are connected.
• The address has not been unnecessarily linked to a public identity.
• Message signatures and approvals are read before confirmation.
• Old WalletConnect and browser-wallet sessions are removed.
• Unused allowances are reviewed and revoked separately.
• Public blockchain history is assumed to be permanent.
• Technical metadata and screening are understood as separate from key custody.
• Current Privacy Policy and regional terms have been checked.
• No recovery phrase or private key is shared with a dapp or support agent.

Frequently asked questions

Can 1inch see my wallet balance?

Yes. Once a public address is known, its supported onchain balances can generally be queried by 1inch or anyone else using blockchain data.

Can 1inch access my private key?

A normal wallet connection does not disclose the private key or recovery phrase. The wallet signs only after user authorization.

Does 1inch track wallet addresses?

1inch says it screens connected and interacting addresses using internal systems and third-party risk information. Its Privacy Policy also describes processing public blockchain and usage data.

Why does 1inch screen my wallet?

The stated purposes include detecting security threats, stolen funds, fraud, sanctions exposure and other financial-crime or compliance risks.

Does disconnecting my wallet remove its transaction history?

No. Disconnecting ends the dapp session. Confirmed transactions remain permanently visible on the relevant public blockchain.

Does disconnecting revoke token approvals?

No. Approvals are onchain permissions and must be reviewed or revoked through a separate transaction.

Is 1inch Fusion private?

Fusion is designed to reduce conventional public-mempool exposure and MEV risks. It does not make the connected address or final settlement anonymous.

Does WalletConnect hide my address from 1inch?

No. WalletConnect secures session communication, but the dapp still needs the selected public account and transaction information to operate.

Can a VPN hide my blockchain activity?

No. It may change the network IP presented to a site, but public addresses and onchain transactions remain visible and linkable.

Can 1inch delete my onchain data?

No. Privacy requests may apply to qualifying offchain personal data, but 1inch cannot erase transactions replicated on a public blockchain.

Final perspective

Connecting a wallet to 1inch preserves self-custody because signing secrets stay with the wallet. It does not create anonymity. The selected address exposes a public financial history, and the interface can process the technical and security information needed to provide, protect and restrict its products.

Meaningful privacy begins with understanding each layer: browser metadata, wallet sessions, address screening, signed permissions and permanent blockchain records. Limit unnecessary exposure, maintain separate security controls and use the service only within applicable terms and law.

Official sources

• 1inch — User protection, wallet screening and geofencing
• 1inch — Security and deterrent measures
• 1inch Privacy Policy
• 1inch official blog