Privacy policy · Updated August 5, 2026
Focused data. One clear purpose.
BRO-ker Extension processes limited channel activity to detect supported contract addresses in channels you enable and, if you connect, sync that activity with your BRO-KER account.
Our single purpose
BRO-ker Extension watches user-enabled Telegram Web and Discord channels for supported contract-address-like text and optionally syncs relevant activity to the user’s BRO-KER account.
Watching is local by default. Connecting a BRO-KER account is optional for local watching and required for account sync and connected features.
Data the extension may process
- Newly displayed message text on supported Telegram Web or Discord pages, only after you enable watching for that channel. Existing visible history is treated as a baseline.
- Supported contract-address-like strings, their selected network, and detection timestamps.
- Channel title or key and page origin or path used for per-channel settings and Activity.
- Extension settings, enabled channel settings, recent Activity, and session presence stored in Chrome extension storage.
- Public wallet metadata returned by a connected BRO-KER account, such as wallet ID, network, public address, short address, and label.
- Telegram account identifier and username returned by Telegram login and the BRO-KER service.
How data is used
- Detect supported contract addresses in channels selected by the user.
- Keep recent detections locally and show them in Activity.
- Sync supported detections and settings with the user’s BRO-KER account after connection.
- Show connection, channel, network, wallet, and capability status.
- Apply BRO-KER safety checks before any available server-side auto-buy action.
- Provide safe diagnostics designed to exclude secrets.
Data the extension does not collect
The extension does not read clipboard contents. An explicit copy button may write selected safe text to the clipboard when you choose it.
Local storage, sharing, and retention
Local storage
Settings, enabled channels, recent Activity, and connection state can be stored in Chrome extension storage on your browser.
Sharing
Detection and settings data stays local while you are not connected. A bounded local retry queue may temporarily keep normalized detection summaries while sync is unavailable; Activity shows queued and dropped counts. After connection, supported data is sent only to the official BRO-KER extension service. BRO-KER does not sell extension data, use it for unrelated advertising, or share browsing data with advertising networks.
Retention
Local settings and recent Activity remain until you clear Activity, reset settings, log out, remove the extension, or clear Chrome extension data. Backend retention follows BRO-KER server policy for extension sessions, settings, and detection or Activity records.
Your controls
- Use local watching without connecting an account.
- Enable, pause, reset, or remove individual channels.
- Select one explicit network for each watched channel.
- Keep auto-buy off or disable it per channel.
- Clear local Activity.
- Log out from the current browser session.
- Revoke all extension sessions connected to your Telegram account.
- Remove the extension and its local Chrome data.
Security
BRO-ker Extension uses Manifest V3, keeps extension-executed code packaged locally, stores its connection token only in extension storage, keeps that token out of content scripts, and redacts sensitive values from diagnostics.
Wallet signing and trade execution remain server-side. Browser-provided price, liquidity, market-cap, and projected-spend values are not trusted for live decisions.
Contact
For privacy or extension questions, use the official support page or contact the BRO-KER Support Bot on Telegram.