Rubicon for FOMO Privacy Policy

Effective date: 4 October 2026
Contact: 147pty@gmail.com

This policy describes Rubicon for FOMO version 0.5.10. The extension adds token and trader research to supported FOMO pages. It does not sign or submit trades, hold funds, or request wallet seed phrases or FOMO login credentials.

Information the extension handles

• Page context and content: the current supported FOMO URL, token chain and contract address, trader handles and identifiers, visible follower/following information, and relevant displayed transaction or position information. Opening a native FOMO position can create a temporary sample of its currently visible activity rows.
• Research results: public market and pool data, plus provider-reported wallets, profiles, ranks, positions, recent-buy alerts and trading activity requested through the tools.
• Your inputs: token/trader notes, your follower-threshold preference and an optional FOMOAPI key entered in Settings.
• Optional diagnostics: a rejected recent-buy response can produce fixed reason codes and limited field-type/count information. This diagnostic excludes raw response records, trader identities, token addresses, request URLs and API keys. It is copied only when you choose Copy diagnostics and is not automatically uploaded.

The extension does not read Chrome's full browsing-history database or browser cookies. It has no inbox, chat, location or behavior-analytics feature and does not keep click, scroll or keystroke logs.

Requests to other services

Public market context can load automatically for the current supported token and visible discovery cards. Requests send the relevant chain and contract address to Dexscreener at api.dexscreener.com.

Volume-history and buyer-volume research can request a selected pool and time window from GeckoTerminal at api.geckoterminal.com.

After you connect your key and initiate the relevant research action, requests to FOMOAPI at api.fomoapi.io can include a trader identifier, token/chain, time window or pagination cursor. The key is sent in an authorization header to FOMOAPI. A buyer check can request a bounded batch of follower profiles. An intentional P&L hover on an eligible non-native position can initiate a position lookup; reading native FOMO position activity does not initiate that provider lookup.

These API requests use HTTPS and omit browser cookies and credentials other than the FOMOAPI key described above. The key is not sent to Dexscreener or GeckoTerminal. Providers receive ordinary connection information, including the connecting IP address, and handle requests under their own policies. Rubicon for FOMO does not control their retention practices.

Opening an external research link makes a normal browser visit to the selected site, such as FOMO, FomoScan, Dexscreener, Solscan, X or Bubblemaps. Its URL can contain the relevant trader, wallet, token or pool identifier. Displaying a link does not itself fetch that external page.

Storage and retention

Notes and preferences are stored in Chrome extension local storage on this device. Saving an empty note removes that note. Preferences remain until changed or the extension is removed. Notes appear inside the extension's on-page interface; the extension does not upload them to a Rubicon server.

Your FOMOAPI key stays in extension session memory by default. Chrome clears that storage when the browser restarts or the extension is disabled, reloaded or updated. If you explicitly choose to keep the key on this device, it is saved in Chrome extension local storage. The current extension does not add its own encryption to that persistent key. Remove key in Settings deletes both session and local copies and invalidates associated research caches. The key is not returned to the FOMO page or repopulated into the Settings input.

Research caches stay in extension/page memory. Public market, minute-history and recent-alert results can be reused for about one minute; profile/rank results for about two minutes. These are reuse limits, not exact deletion schedules. Displayed results can remain until refreshed or the page context closes or changes.

Buying-habit continuation can retain normalized pages and cursor information in extension session storage so a requested scan survives background-worker suspension. A scan is usable for ten minutes and bounded to ten pages. Expired records are removed during subsequent access or cleanup; session-storage resets also clear them. This is not continuous background trade tracking.

Chrome storage access is restricted to trusted extension contexts. The extension does not use Chrome Sync.

Purpose and Limited Use commitments

Information is used for the disclosed token/trader research functions, saved preferences and notes, and troubleshooting you request. Transfers to the named API providers support those functions.

The extension contains no advertising or analytics SDK and sends no research data to a Rubicon telemetry or collection endpoint. We do not sell extension user data or use or transfer it for unrelated purposes, personalized advertising, creditworthiness or lending decisions. These commitments describe data use; they are not a statement that Chrome has approved the extension.

Your choices and contact

Public features work without a FOMOAPI connection. You can remove the key, delete individual notes, change preferences, revoke optional FOMOAPI access in Chrome, or uninstall the extension. Revoking access stops provider requests; use Remove key to delete a stored key. Uninstalling clears extension local storage.

Wallet and diagnostic Copy actions write the selected output to your clipboard only after you act. If you email 147pty@gmail.com, you choose what information to share. Your message and attachments pass through the email service and can be used to respond to your request. Do not include API keys, passwords or seed phrases. Contact this address for privacy questions or requests concerning information you voluntarily sent; this policy does not promise a fixed email-deletion schedule.