Explore tokens.
Know your footprint.

SolVortex helps you discover and swap Solana tokens. This notice explains the information handled by that interface, including token discovery, wallet features, and swap monitoring. The interface operator’s privacy contact appears below. Browsing the interface does not require a registered profile, an email address, or card details.

Connecting a wallet exposes its public address to the interface. That address and its public activity may be identifiable even without a name. Secret keys and seed phrases belong in your wallet; SolVortex does not ask for them or store them.

Entering a token symbol, name, or mint address sends a search request to our server, which queries DexScreener. A confirmed server network or TLS failure can trigger a direct browser retry to DexScreener, so that provider then receives your search, IP address, and normal request headers. Trending lists are supplied by GeckoTerminal through our server. Market results may be cached and reused across visitors; discovery is not a private message to the token issuer. Selecting a search result saves that query, token metadata, and a timestamp among your five most recent selections in local storage.

Token artwork may be requested directly from external image hosts, which then receive the usual connection details, including your IP address. Following external token or transaction links opens another website under that provider’s policy. Our discovery feature does not need optional visit analytics to function.

Wallet features use your chosen wallet provider, public address, connection state, and public balances. Requesting a swap also involves input and output mints, amounts, minimum output, slippage, fees, signed quote bindings, simulation results, transaction signatures, and confirmation status. Jupiter receives routing and quote inputs; the configured Solana RPC endpoint, including Helius where configured, handles balance, simulation, submission, and verification requests.

Live transactions require the approval flow in your wallet. A simulation can still access public mainnet information without completing a trade. A submitted transaction is published on Solana and can be examined by others; the interface cannot make that chain history private or erase it later.

Local storage holds the selected wallet provider, recent selected tokens, a wallet-specific display archive, and an operation-recovery journal. The archive keeps up to 50 swaps per wallet and 100 overall. The recovery journal also preserves pending operations and quote envelopes to reduce the risk of repeating an unresolved swap; completed records are bounded by the journal’s limits. These entries have no fixed time-based expiry and persist until replaced or cleared. Do not remove recovery data while a transaction still needs checking.

A security cookie named swap-client can be issued for up to one day where a browser identifier is needed. It is HttpOnly and supports API authentication and request limits. Vercel deployments can instead use the request IP for this protection. The analytics choice for SolVortex is a separate local entry that lasts 180 days, after which we ask again.

Shared-origin previews of SolVortex, Kurama Swap, and CapyNest reuse wallet, search, and transaction storage. Analytics permission remains separate for each brand. Deployments on different origins cannot share that browser storage.

Accept analytics allows Vercel Web Analytics to measure public-page visits and associated referrer, time, coarse location, browser, operating-system, and device information. We filter out query strings and URL fragments, limit reporting to known public routes, and do not instrument wallet activity or swaps as custom analytics events. This is cookieless analytics with a request-derived visitor hash; Vercel states that a visitor session is discarded after 24 hours. Aggregate reporting can remain longer.

Without an affirmative choice, the analytics component does not load. Reject optional declines it, and Cookie settings lets you stop future events after accepting. Changing permission cannot recall previously collected statistics. The current interface contains no advertising trackers and no mechanism for selling your discovery history.

The hosting platform processes incoming IP addresses, browser headers, request paths, and operational logs to deliver and protect the site. Security counters and result caches are held in server memory. Search cache responses are reusable for 30 seconds; expired entries can remain until eviction or a process restart. Provider logs and cached infrastructure data are governed by their settings and policies.

Where Telegram is configured, the operator receives alerts after verified live swaps confirm. Each alert includes SolVortex’s identity and source page URL, wallet address, transaction signature, input/output mints, traded amounts, and minimum output. Telegram receives the message and the configured chat can retain it. A successful-delivery cache lasts 24 hours to prevent repeat alerts; it is not a Telegram message-deletion schedule. Declining visit analytics does not disable these service-operation alerts.

Hosting, Jupiter, DexScreener, GeckoTerminal, RPC, image, and Telegram services can process information in other jurisdictions. They have their own privacy rules. Necessary trade processing supports the service you request; security processing supports abuse prevention and service reliability. Depending on applicable law, these rely on service performance and legitimate interests, while optional statistics rely on your consent.

You can disconnect your wallet, decline analytics, revisit Cookie settings, and clear this origin’s local data through browser controls. Disconnecting removes the saved wallet-provider choice but does not wipe the swap archive. Erasing browser data does not remove confirmed transactions, operator alerts, or service-provider records.

Applicable privacy law may give you access, correction, deletion, portability, restriction, and objection rights, as well as the ability to complain to a supervisory authority. Send requests to the contact below with enough detail to identify the processing involved. We may verify your request without asking for wallet secrets. The revision date identifies the current notice; material changes to optional processing will require a new consent version.