Privacy for the Polygon to Arbitrum direction
Where offered, Private Route is intended to reduce an obvious direct association between the Polygon sending wallet and Arbitrum receiving wallet; it does not hide either blockchain. POL is the native gas asset for Polygon. EVM 0x account address ETH is the native gas asset for Arbitrum. EVM 0x account address Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Polygon source-side visibility
Polygon exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Polygon PoS uses an EVM sidechain architecture with its own validator checkpoints and gas balance. Its token representations and bridge behavior are separate from Ethereum L1 even when wallets use the same 0x account. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Arbitrum destination-side visibility
Arbitrum exposes account history, token approvals, contract calls, logs, gas funding, amounts, and timing under its own chain identifier. Its Nitro optimistic-rollup design executes through a sequencer and posts compressed transaction data to Ethereum. L2 inclusion and Ethereum settlement are separate milestones, so a source receipt can advance before the rollup state is final on L1. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Polygon deposit role versus Arbitrum receipt role
A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Those deposit-side events remain public. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. The receipt and later activity remain public.
Two EVM histories can still be compared
Polygon and Arbitrum use separate chain identifiers, balances, contracts, transaction hashes, and gas records even when address syntax matches. Sequencer inclusion and settlement timing can add further observable milestones.
POL approval and governance-token evidence; POL approval and governance-token evidence
Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this deposit. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. The source transfer remains public. Token allowances, contract transfers, voting or utility interactions, source gas, and later wallet consolidation can remain visible for this receipt. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function. The destination receipt and later use remain public even when direct wallet association is reduced.
Cross-chain linkability limits
Private routing can reduce an obvious link between two EVM accounts, but source approvals, gas, logs, destination contract or native receipt, and later activity remain on separate chain histories. Sequencer and settlement timing can add correlation evidence. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
Verification status is separate from privacy status
The provider must support the exact L2 direction, asset contracts, amount, and region. Rollup support and privacy routing do not imply that identity verification, account, or custody requirements are absent. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
