Lucid control boundary
7. RPC, routing, wallet-related processing, and compliance checks
When Lucid or related browser surfaces need to fetch blockchain data, estimate fees, read token balances, or route requests to infrastructure providers, certain technical request data may be processed. Depending on how Lucid is configured, that can include an IP address, browser metadata, approximate region, wallet address, transaction metadata, and requested chain identifiers.
We use this processing to deliver basic functionality, reduce latency, route requests safely, troubleshoot outages, apply security controls, and comply with lawful restrictions. That can include sanctions screening, abuse-prevention logic, vendor-level safety controls, and temporary restrictions on a feature, network, or routing path.
Where configurable, advanced users may choose different infrastructure or privacy configurations when those options are made available. A different configuration can change the data path, privacy posture, and support assumptions for the relevant request.