Privacy Policy

Remote Inject Bridge Chrome Extension · Last updated: March 2026

What data we collect

Remote Inject Bridge does not collect, transmit, or store any personal information. Specifically:

• No browsing history — the extension reads only the background color of the active tab to adjust the popup theme. No page content, URLs, or history are sent anywhere.
• No wallet keys or seed phrases — the extension never has access to private keys. It only forwards JSON-RPC requests between the DApp and your mobile wallet.
• No analytics or telemetry — no usage data is collected or sent to any server.

Local storage

The extension uses Chrome's storage API to save two items locally on your device:

• Your relay server URL (default: remote-inject.awesometools.dev)
• The current session ID, so you don't need to re-scan the QR code on every visit

This data never leaves your device except as part of the normal connection to your chosen relay server.

Relay server communication

When the bridge is active, the extension connects to a relay server via Server-Sent Events (SSE). The relay server:

• Forwards JSON-RPC messages between the DApp and your mobile wallet
• Does not log or store transaction content
• Can be self-hosted — see github.com/atshelchin/remote-inject

Permissions

• storage — saves relay server URL and session ID locally
• tabs — reads the active tab's background color to match the popup theme
• sidePanel — enables the side panel UI mode
• offscreen — maintains the background SSE connection while you browse other tabs

Third-party services

By default the extension connects to remote-inject.awesometools.dev, a relay server operated by the developer. You can switch to a self-hosted relay server at any time in the extension settings. The relay server's own privacy policy applies when you use it.

Open source

The full source code is available at github.com/atshelchin/remote-inject for independent review.

Contact

Questions? Open an issue at github.com/atshelchin/remote-inject/issues.