01 Scope
Signal Snipe is an independent browser extension for supported Axiom and Padre terminal pages. This policy describes extension version 1.0.0. Signal Snipe is not affiliated with or endorsed by Axiom, Padre, X, Telegram, or their operators.
02 Data the extension handles
Signal Snipe processes a narrow set of content already rendered in an open supported terminal tab:
- visible X-card text and short excerpts;
- public links shown in the card, including public X links and contract or launchpad links;
- bounded text and public HTTPS links from up to three directly linked public Telegram channel posts, only when the selected card contains no contract address;
- visible token-card metadata such as chain, contract address, ticker, name, section, and public image URL;
- eligible public raster images when local visual matching is enabled;
- runtime settings stored locally when present, plus explicit SNIPE, Open again, and Clear actions.
This processing parses a selected visible alert, opens an exact contract directly when present, compares contract-less alerts with visible token candidates, maintains a bounded watch only when needed, validates a supported terminal token URL, and shows local navigation history.
03 Local processing
Text, link, contract, ticker, candidate, and image-fingerprint matching runs in packaged extension code on the user's device. Signal Snipe does not upload this content to a publisher server and does not use cloud AI.
The cloned source-card DOM and live visible-candidate index are temporary. A reduced source snapshot is retained only as part of local activity history. Downloaded image bytes are discarded after decoding. Computed fingerprints may remain in a bounded in-memory cache of up to 256 entries for the lifetime of the extension service worker; image bytes and fingerprints are not written to persistent storage.
04 Local storage and retention
Signal Snipe uses chrome.storage.local for:
- settings: enabled state, ask-only mode, visual-matching preference, active-watch limit, watch-window length, and emergency-stop state;
- activity history: up to 100 records containing time, supported platform, status, public source URL when present, a reduced source snapshot, visible-candidate count, watch-end time when applicable, matched chain and contract address, ticker, token name, match reasons, and the validated terminal URL for a completed transition.
The reduced snapshot can contain parsed contracts, tickers, up to three allowlisted public image URLs, and an excerpt of up to 240 characters. The extension does not use sync storage. History remains on the device until the user clicks Clear, clears extension data, or uninstalls the extension.
05 Network requests
The content script runs only on https://axiom.trade/* and https://trade.padre.gg/*. Signal Snipe has no publisher-operated API or analytics endpoint.
When a selected card has no contract but directly links to a public Telegram channel post, a SNIPE click may fetch up to three unique posts only from https://t.me or https://telegram.me. Private invites, bot/start links, channel indexes without a numeric post ID, and arbitrary website origins are rejected before network access. Requests omit credentials, use no-referrer, time out after three seconds, and accept only bounded HTML responses whose final URL remains an allowed public Telegram post. Executable markup is discarded. Successful results remain only in a bounded in-memory cache for the service-worker lifetime.
When a selected Axiom alert contains an exact Solana contract, packaged code sends that public contract address to https://api2.axiom.trade/search-v5 to obtain the corresponding Axiom pair address. The request occurs only after a SNIPE click, and the response must contain an exact token-address match. The browser may attach the user's existing Axiom session. Signal Snipe does not read, expose, or store cookie or authorization values.
If local visual matching is enabled and text/link matching does not resolve a candidate, packaged code may refetch eligible public raster images only from:
- https://axiom-assets-v2.axiom-cdn.io
- https://axiomtrading-v2.axiom-cdn.io
- https://axiomtrading-eth-v2.axiom-cdn.io
- https://axiomtrading-bnb-v2.axiom-cdn.io
- https://twproxy.twproxy.workers.dev
- https://pbs.twimg.com
- https://thumbnails.padre.gg
Fingerprinting requests use HTTPS, omit credentials, and use no-referrer. Redirects are accepted only when the final URL remains allowlisted. SVG files are not fingerprinted, and accepted raster types and encoded/decoded sizes are bounded.
An allowlisted image or public Telegram host can receive ordinary network metadata such as IP address and browser user agent. No terminal cookies, authorization headers, source-page referrer, wallet data, or extension history are intentionally included. Each third-party host has its own privacy practices.
Clicking SNIPE explicitly starts the workflow. An exact contract opens through a validated terminal route without starting a candidate watch. Only alerts that remain contract-less after permitted linked-post enrichment use the bounded New/New Pairs matching window. Open again and public source/explorer links open normal browser tabs. Signal Snipe does not inspect or store general browser history.
06 Data not accessed or collected
Signal Snipe does not read or collect:
- wallet seed phrases, private keys, wallet sessions, balances, or account credentials;
- passwords, authentication-cookie values, bearer-token values, or other login material;
- payment information or transaction payloads;
- general browser history or clipboard contents;
- contacts, precise location, microphone, camera, or files.
The browser may automatically attach an existing Axiom session to the user-triggered resolver request described above, but the extension does not read or store that material. Signal Snipe does not connect wallets, sign messages, click native trading controls, submit orders, buy or sell tokens, or broadcast transactions. Opening a token page is navigation only.
07 Sharing, sale, analytics, and advertising
The publisher does not receive, sell, rent, or share locally processed content or locally stored history. Signal Snipe contains no analytics, telemetry, advertising, affiliate or referral behavior, and no remote executable code.
Signal Snipe's handling of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. User data is used only to provide the extension's disclosed, user-facing navigation workflow and is not transferred for advertising, profiling, creditworthiness, lending, or unrelated purposes.
08 User controls
Users can disable the extension through Chrome, reopen a recorded terminal page, clear local Signal Snipe navigation history, clear extension data through Chrome, or uninstall the extension.
09 Changes
If a later version changes permissions, storage, supported hosts, network behavior, or data handling, this policy will be updated before that version is published. The effective date identifies the policy for this version.
10 Contact
For privacy questions, use the publisher support channel shown on the Signal Snipe Chrome Web Store listing or visit the Support page.