How to remove a connected site from MetaMask? (Privacy Settings)

Accessing Connected Sites in MetaMask

1. Open the MetaMask extension in your browser or launch the mobile app.

2. Tap or click the account icon located in the top-right corner to open the account menu.

3. Select Settings from the dropdown or navigation options.

4. Scroll down and choose Privacy & Security — this section governs data sharing, site permissions, and connection history.

5. Locate and tap Connected Sites, which displays a list of all dApps and websites granted access to your wallet address and network information.

Identifying Active Connections

1. Each entry shows the domain name, last connected timestamp, and permission level granted (e.g., address exposure, network switching).

2. Some entries may include a lock icon indicating persistent access across sessions, while others show temporary session-only status.

3. Domains with multiple subdomains—like app.uniswap.org and info.uniswap.org—appear as separate entries even if hosted under the same root.

4. Third-party analytics integrations embedded within dApps may register as distinct connections, especially when they load external scripts that trigger wallet detection.

5. No confirmation dialog appears when a site auto-connects during page load; the only visible indicator is its presence in this list after interaction.

Revoking Site Permissions

1. Tap or hover over the target domain to reveal an action menu or trash icon.

2. Click Disconnect — this immediately removes read access to your public address and prevents future network-switching prompts from that origin.

3. MetaMask does not delete cached transaction history or saved custom RPC endpoints associated with the domain unless manually cleared elsewhere.

4. Disconnection does not affect any on-chain activity already executed through that interface; it only severs real-time wallet interaction capability.

5. If the site uses injected provider patterns common in Ethereum-compatible chains, reconnection requires explicit user approval via signature request or connect button click.

Preventing Unwanted Reconnections

1. Disable Auto-lock in Settings > Security to avoid unintentional re-authentication after timeout-based lockouts.

2. Use Network Restrictions to block specific RPC endpoints tied to known tracking domains or analytics-heavy infrastructure providers.

3. Install browser extensions like uBlock Origin with Ethereum-specific filter lists to intercept wallet-detection scripts before they execute.

4. Avoid clicking “Connect Wallet” buttons on unverified landing pages—even static documentation sites sometimes embed live wallet connectors for demo purposes.

5. Clear site data manually for suspicious domains via browser developer tools before reconnecting, ensuring no residual localStorage keys persist.

Frequently Asked Questions

Q: Does disconnecting a site remove previously signed messages or transactions?A: No. Disconnection only revokes current session access. All on-chain actions remain immutable and publicly verifiable.

Q: Can a disconnected site reconnect without my knowledge?A: Only if you explicitly interact with its UI again—no background reconnection occurs. MetaMask enforces strict user-initiated permission flow.

Q: Why do some domains reappear after disconnection?A: They may be loaded via iframe embedding from another trusted dApp or share domain roots with whitelisted services using wildcard permission rules.

Q: Is there a way to bulk disconnect all sites at once?A: MetaMask does not offer native bulk removal. Each domain must be disconnected individually through the Connected Sites interface.