On privacy,
and what we keep.

Knoww is a product that helps you discover and interact with prediction markets (including markets provided by third parties) and related information. The Web App may connect to blockchain wallets, display data associated with public blockchain addresses, and provide trading- and comment-related features that rely on third-party market providers.

The Extension enhances supported social websites by detecting topics in on-screen content and surfacing potentially relevant markets. Depending on your settings and the feature being used, the Extension may process page content locally, store local relevance/personalization data, send excerpts of content to Knoww for AI-assisted matching, and make network requests to market data providers to retrieve results.

Information you provide

• Wallet information: if you connect a wallet in the Web App or Extension, we and our wallet connectivity providers may receive your public wallet address and related connection metadata. When usage analytics is enabled, Knoww may use that address to recognize your wallet across the Web App and Extension and provide a more personal experience.
• Comments and other submitted content: if you post a comment or otherwise submit content through Knoww, we process the content you submit and the wallet-authentication data needed to send it to the relevant provider.
• Support communications: if you contact us, you may provide your email address and the contents of your message.

Information collected automatically

• Usage and device data: standard log data such as IP address, browser type, pages viewed, and timestamps may be processed by our hosting, infrastructure, analytics, and wallet connectivity providers.
• Personalized experience and diagnostics: the Web App may capture feature-usage events, your connected public wallet address, wallet-related action metadata, market identifiers/titles, and client error or exception diagnostics through analytics tooling when enabled in our deployment configuration. We use this information to remember the connected wallet across Knoww, tailor the experience, and understand whether features work as intended.
• Local app state, cookies, and similar technologies: the Web App stores certain preferences, wallet connection state, and session state in your browser (see “Storage, Cookies & Similar Technologies”).

Information processed by the Extension

• On-page text content from supported sites may be read and processed to extract keywords and topics for market discovery. This is used to determine what market data queries to run.
• Unsupported-site prompt: to show the support request prompt automatically, the Extension has host access on HTTP and HTTPS pages. On unsupported sites, this lightweight prompt reads only the current hostname. It does not inspect page text, links, forms, or the full page address.
• Extension settings and local preference data (for example enabled platforms/sources, learned click/ignore preferences, local caches, and similar state) are stored using Chrome extension storage and related browser storage.
• Extension session and trading state: if you use wallet-connected extension features, the Extension may store short-lived extension session tokens and trading-related credentials/state in extension storage for the current browser session.
• Extension usage analytics: usage analytics is enabled by default and can be turned off in Extension settings. While enabled, we may collect your connected public wallet address and events such as extension startup, supported-site detection, market card impressions and clicks, trading panel opens, settings changes, platform name, and host. We use this information to give you a more personal experience across Knoww and understand whether features work as intended. These events do not include page addresses or raw page text.
• Website support requests: if you select “Request support for this website,” the Extension sends the normalized domain shown in the request screen and an anonymous installation identifier. It does not send the page address or page contents with that request.
• AI-assisted matching inputs: if AI-assisted matching is enabled in the Extension, normalized or truncated excerpts of page text and market titles/tags may be sent to Knoww APIs so we can extract topics or validate market relevance.

• Provide the product: operate the Web App, show markets, support comments, and enable wallet-based features.
• Improve and debug: diagnose issues, monitor errors, protect against abuse, and improve reliability and performance.
• Provide a more personal experience: recognize a connected wallet across the Web App and Extension, understand which features and supported sites are used, and tailor the experience based on those interactions.
• Match markets to content: analyze text, extract topics, rank candidates, and validate relevance so the Extension can show more useful market suggestions.
• Personalize results: if personalization is enabled in the Extension, learn from your clicks and ignores to adjust future ranking locally on your device.
• Communicate: respond to support requests and important updates.

We do not sell your personal information. We may share information in the following circumstances:

• Market, trading, and blockchain providers: Knoww queries third-party services (for example, Polymarket, Kalshi, bridge providers, RPC providers, and related infrastructure) to fetch market information, support trading, route deposits, fetch comments, and read public blockchain data. Requests may include search terms, wallet addresses, signatures, transaction details, or standard network metadata as needed for the feature you use.
• Wallet connectivity providers: the Web App integrates with wallet connection tooling (for example, Reown / WalletConnect and wallet applications). These services may process connection metadata according to their own policies.
• Analytics providers: Knoww uses analytics tooling (currently including PostHog) to provide a more personal experience, understand feature usage, and diagnose client errors. When usage analytics is enabled, these tools may receive your connected public wallet address and related interaction metadata from the Web App or Extension.
• AI providers: if AI-assisted matching is enabled in the Extension, excerpts of page text and market metadata may be processed by Knoww and AI providers acting on our behalf (currently via OpenRouter and underlying model providers) to extract topics or validate relevance.
• Infrastructure providers: hosting, caching, networking, and security providers may process standard logs and request metadata to deliver the service.
• Legal and safety: if required by law or to protect users, the public, or our rights.

Supported sites

The Extension supports a broader set of sites than only X, LinkedIn, and Reddit. Current supported platforms include major social sites, forums, developer communities, and crypto/news properties such as X/Twitter, LinkedIn, Reddit, Quora, Hacker News, Stack Overflow / Stack Exchange, Product Hunt, Slashdot, supported Lemmy and Mastodon instances, Threads, Bluesky, Discord, Farcaster, CoinMarketCap, Paragraph, CoinDesk, Cointelegraph, Decrypt, The Block, Blockworks, Bankless, Bitcoin Magazine, BeInCrypto, Unchained, and CryptoPanic. The list may change over time, and the Extension settings are the best source for the latest supported platforms.

What the Extension does with page content

• The Extension reads visible content (such as post text) to extract keywords/topics and match relevant markets.
• If AI-assisted matching is enabled, the Extension may send normalized or truncated text excerpts and market metadata to Knoww APIs for topic extraction and relevance validation.
• The Extension uses those extracted keywords/tags to query market data APIs (e.g., Polymarket and Kalshi) and display results on the page.
• The Extension stores user settings using Chrome’s storage permission, and may keep local preference data and local embeddings on-device to improve relevance ranking.
• While usage analytics is enabled, the Extension sends events used to provide a more personal experience and understand feature usage. These events may include your connected public wallet address, host, platform, and feature interaction metadata, but not page addresses or raw page text.

Data sent to Knoww

The Extension may communicate with knoww.app to support AI-assisted matching, extension authentication, analytics ingestion (if enabled), explicit website support requests, trading-related features, and other Extension-backed functionality. Depending on the feature, this may include wallet address, signed authentication messages, short-lived session tokens, content excerpts, market metadata, and product interaction metadata.

The Web App uses browser storage and cookies to keep the app usable and remember your preferences. Examples include:

• Theme and accent preferences stored in localStorage.
• Trading onboarding completion stored in localStorage (per wallet address).
• Trading session state stored in localStorage (with expiration).
• API credentials and read-only API keys stored in localStorage with expiration and cleared when you disconnect or reset trading credentials.
• Recent searches, last-viewed markets, alert preferences, and UI state stored in browser storage to support search, notifications, and interface preferences.
• Wallet connection state stored in cookies and related storage used by the wallet connection stack.

The Extension also stores settings in chrome.storage.sync, local preferences and some analytics queue/state in chrome.storage.local, short-lived auth/trading state in chrome.storage.session, and local embeddings / caches in browser storage such as IndexedDB.

Third parties (such as wallet connectivity, analytics, and hosting providers) may use their own cookies or similar technologies as part of providing their services.

We use reasonable safeguards designed to protect information. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

We retain information only for as long as needed for the purposes described in this policy, unless a longer retention period is required or permitted by law. Some data is stored locally in your browser or extension and remains until it is cleared or expires; some session data is cleared when the browser session ends; and some server-side logs, caches, and analytics records may be retained for a limited period as needed to operate, secure, and improve the service.

• Disconnect your wallet: you can disconnect in the Web App and/or in your wallet provider.
• Disable the Extension: you can disable or uninstall the Extension at any time in Chrome.
• Disable usage analytics: you can turn off usage analytics in the Extension settings at any time.
• Disable AI-assisted matching: you can turn off AI-assisted matching in the Extension settings, which stops those AI requests from the Extension.
• Control local storage: you can clear site data (local/session storage/cookies) in your browser settings and clear Extension data in Chrome.
• Request help: contact us to ask questions about this policy or your information.

Knoww is not intended for children or for people who are not legally permitted to use prediction market or trading-related products in their jurisdiction. We do not knowingly collect personal information from children.

We may update this policy from time to time. If we make material changes, we will update the “Last updated” date and may provide additional notice as appropriate.

Knoww MCP connects compatible AI assistants to prediction market data. Google sign-in identifies the person approving a connection. The following details apply specifically to Google user data and the MCP service.

Google data we access and use

We request the openid and email permissions. Google provides an account identifier, email address, and verified-email status in a signed identity token. We verify these claims to authenticate you, associate your approved MCP connections with your account, enforce usage limits, and prevent unauthorized access. These permissions do not provide access to Gmail messages, Drive files, Calendar, or contacts.

We discard your email address and Google tokens after verification. We retain your Google account identifier in authorization records and use an identifier derived from it for access control and usage limits. We also store a separate random identifier for each Google account and MCP client pair.

Sharing and disclosure

Google processes the sign-in request. Cloudflare hosts the MCP service and stores its authorization records on our behalf. Your chosen MCP client receives Knoww authorization tokens and the market data you request. We do not send it your Google email address or Google tokens.

When MCP analytics is enabled, PostHog receives a hashed identifier derived from your MCP identity, along with usage and diagnostic events such as tool names, client type, request status, and timing. These events help us understand usage and diagnose failures. They do not include your Google email address, raw Google account identifier, Google tokens, or the contents of your tool requests.

We do not sell Google user data or use it for advertising or training AI models. We disclose it only to operate these features, comply with legal obligations, or protect users and the service. Knoww's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable.

How we protect this data

We use HTTPS for Google sign-in and production MCP connections. We verify Google's signed identity tokens and use one-time authorization transactions, state and nonce checks, and PKCE to protect the sign-in flow. MCP permissions restrict the actions a connected client can perform. Google tokens are processed on the server and are not given to MCP clients.

Retention and deletion

Sign-in transactions expire after five minutes and are removed when consumed or expired. Knoww access tokens last up to one hour; refresh tokens have a 30-day lifetime and rotate when used. Token expiry does not delete all account data. The separate account-to-client identifier has no automatic expiry. Authorization records and usage records support your connections, usage limits, and service diagnostics.

To request deletion of your MCP identity, authorization records, and associated usage data, email contact@knoww.app. We may need to verify your identity before processing a request. Records required for legal obligations or security may be retained as needed for those purposes.

You can remove Knoww MCP from your assistant and revoke its Google connection in your Google Account connections. Revoking Google access does not automatically revoke existing Knoww tokens or delete Knoww's stored records. Contact us to request removal of those records and connections.

If you have questions or requests about this Privacy Policy, contact us at contact@knoww.app.