1. What this policy covers
This policy covers the PolyEnhancer browser extension and its accompanying website. PolyEnhancer adds market context, analytics, trader watchlists, comment controls, Bonds filters and wallet-signed trading to Polymarket. A separate PolyEnhancer account is not required.
The current extension performs its calculations in your browser and requests the external data needed for its features. It does not send your settings, watchlists or trading credentials to a PolyEnhancer-operated backend. We do not sell personal data, use it for targeted advertising, or transfer it for purposes unrelated to the features described here.
2. Information the extension handles
Market pages and public data
On Polymarket pages, the extension reads the current market, selected outcome, visible prices, order-form inputs and relevant page content to display its panels and support trading. Comment filters process loaded comment text and account names in your browser. Market identifiers, token identifiers, public wallet addresses and tracked public account identifiers are sent to the relevant data services to retrieve market details, order books, public positions, activity, holder PnL, public posts and price feeds.
Public posts and trader information come from public data sources. The extension does not request access to your private social-media messages, passwords, general browsing history or unrelated websites.
Settings and saved traders
Your enhancement preferences, border preference, Bonds filters and named presets, comment-filter text and account filters, and saved trader wallet addresses, names and groups are stored in the extension’s local browser storage. These preferences are not uploaded to a PolyEnhancer account or synchronized by the extension across devices.
Wallet connections and trading
If you enable trading, the extension asks your selected wallet provider, such as MetaMask, Rabby or Phantom, for the account address, network information and the authentication or order signatures needed for that action. The provider may ask you to approve connecting, switching to Polygon, adding Polygon’s network configuration, signing in or signing an individual order. PolyEnhancer never asks you for your wallet’s private key or recovery phrase.
Wallet addresses, authentication signatures, CLOB API credentials, selected market and order details, and signed orders are processed to authenticate with Polymarket, estimate fees, verify permissions and submit the orders you approve. Credentials stay in the extension worker and browser-session storage and are supplied to Polymarket when required; they are not exposed to the website or uploaded to a PolyEnhancer server. Submitted orders include the public PolyEnhancer builder code for attribution and the disclosed app fee.
3. Services that receive requests
The current extension communicates with these services as needed:
- Polymarket — polymarket.com, gamma-api.polymarket.com, data-api.polymarket.com and clob.polymarket.com provide market information, public account and trading data, regional trading availability, authentication and order execution.
- Polymarket XTracker — xtracker.polymarket.com provides public account tracking, post counts and post content.
- Binance — data-api.binance.vision and data-stream.binance.vision provide historical and streaming market prices.
- Polymarket crypto feeds — polymarket.com/api/crypto and ws-live-data.polymarket.com provide supported reference prices, including Chainlink-sourced price data.
- Your wallet provider — handles wallet connections, account access and signatures. If Polygon needs to be added, the extension supplies network configuration using polygon.drpc.org as the RPC endpoint and polygonscan.com as the block explorer. Your wallet’s network requests are governed by its settings and privacy practices.
External services receive the request parameters needed for the feature and ordinary connection information, such as your IP address and request time. Their own policies govern their processing and retention. Public-data requests omit browser account cookies where implemented; trading requests use the authentication needed to execute your approved action.
If you open an original post, a Polymarket profile or another external link, that destination also receives the information normally sent by your browser. Blockchain transactions and public wallet activity can be publicly visible and cannot be deleted by PolyEnhancer.
4. Why browser permissions are needed
- Storage saves preferences, watchlists and filters locally, and keeps temporary session data for public-data caching and trading.
- Scripting lets the extension communicate with the wallet provider on a supported Polymarket page for account connection and signatures.
- Site access allows the extension to add its features to Polymarket and request data from the specific services listed above. The extension does not request access to all websites.
5. Storage, retention and deletion
Local settings, saved traders and filters remain in your browser until you change or delete them, clear the extension’s data or uninstall the extension. Temporary public-data caches remain in memory or browser-session storage and expire or clear with their cache or session lifecycle.
Trading credentials are scoped to the connected tab and document. Disconnect removes those locally stored credentials; closing the tab also triggers credential cleanup, and browser-session storage clears when the browser session ends. Disconnect does not delete your Polymarket account or reverse an order. A local record of an uncertain submission may remain until you check the order and acknowledge its status, or the browser session ends.
Removing local data does not delete public market records, blockchain records or information retained by an external service. Requests concerning records held by Polymarket, your wallet provider or another service should also be directed to that service.
6. This website and support messages
The current website does not include advertising trackers, analytics scripts, account registration or nonessential cookies. Its product illustrations use sample data and do not connect to your wallet.
The service hosting the website receives information needed to deliver pages, such as your IP address, requested URL, browser information and request time. Any hosting logs follow that provider’s retention settings. If you email us, we receive your email address and the contents of your message and use them to respond and handle your request. Support correspondence is retained only as needed for that purpose and applicable recordkeeping obligations.
7. Your choices
You can edit saved traders, filters and preferences using the extension. Wallet connection and each order signature require your approval. You can decline wallet prompts or disconnect the trading connection.
The popup’s enhancement and border switches control display features. They do not turn off the builder trading panel, its routing or its fees. To stop the extension from running altogether, disable or remove it in your browser’s extension settings.
For privacy questions or requests to access, correct or delete information you have sent us directly, contact info@polyenhancer.com. Most extension preferences are held only on your device and can be managed there.
8. Security and limited use
The extension uses HTTPS and secure WebSocket connections for its external API traffic. Trading credentials are kept in the extension context rather than the webpage, and orders require wallet signatures. No method of storage or transmission can guarantee absolute security.
PolyEnhancer uses information received through Chrome APIs only to provide and support the features described in this policy. Its use and transfer of that information adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. We do not use this information for advertising, data brokerage or assessing creditworthiness.
9. Changes and contact
We will update this page when our data practices change and revise the date above. Material changes that require an additional notice or consent will be communicated through the relevant website, extension or store interface.
For questions about this policy or PolyEnhancer’s data practices, email info@polyenhancer.com.