How to manage permissions for third-party sites on Phantom? (Security Settings)

Understanding Permission Models in Phantom Wallet

1. Phantom implements a granular permission system that controls how third-party dApps interact with your wallet.

2. Each site must explicitly request access to view account addresses, sign transactions, or read token balances.

3. Permissions are not granted globally — they are scoped per domain and persist only until manually revoked.

4. The wallet enforces origin-based isolation: subdomains like app.uniswap.org and trade.uniswap.org are treated as separate entities.

5. No dApp can initiate a transaction without an explicit user signature, even if full permissions are granted.

Accessing and Navigating Security Settings

1. Click the Phantom extension icon in your browser toolbar to open the popup interface.

2. Select the three-dot menu in the top-right corner and choose “Settings”.

3. Navigate to the “Security” tab where permission management tools are centralized.

4. A list of connected sites appears with toggles for “View account”, “Sign messages”, and “Approve transactions”.

5. Each toggle operates independently — disabling “Sign messages” does not affect transaction approval rights.

Revoking and Resetting Site Access

1. Within the Security tab, locate the domain you wish to manage and click the trash icon next to its entry.

2. Confirm revocation in the modal prompt — this action removes all stored permissions instantly.

3. Revoked sites lose access to previously shared address information and cannot detect wallet presence unless reconnected.

4. Phantom does not store historical connection logs or metadata about revoked domains.

5. Reconnecting requires the site to reinitiate the connection flow and request permissions anew.

Recognizing Risky Permission Patterns

1. Sites requesting “Sign messages” without clear utility — such as non-authentication interfaces — warrant scrutiny.

2. Domains with mismatched SSL certificates or inconsistent naming (e.g., “metamask-swap[.]net”) trigger internal warnings.

3. Phantom displays a red warning badge next to domains flagged by its real-time phishing detection engine.

4. Any site asking for unlimited gas approval or infinite ERC-20 allowances should be treated as high-risk.

5. Wallet-connected banners showing “Connected via Phantom” do not imply endorsement — users must verify contract addresses manually.

Frequently Asked Questions

Q: Can Phantom automatically revoke permissions after a period of inactivity?A: No. Phantom does not implement time-based auto-revocation. All permissions remain active until manually removed by the user.

Q: Does disconnecting from a site in the UI also clear cached token balances or NFT metadata?A: Disconnecting only revokes wallet interaction rights. Cached asset data may persist temporarily but is never shared with the disconnected domain.

Q: If I approve a transaction on a malicious fork of a known dApp, does Phantom recognize it as untrusted?A: Phantom validates domain ownership at connection time but does not analyze smart contract logic. Users must verify contract addresses before signing.

Q: Are permissions synchronized across devices when using Phantom’s cloud backup?A: No. Permission states are stored locally per browser profile and are not included in encrypted cloud backups.