Privacy Policy.

Important notice

Interim technical correction.

This page describes data flows verifiable from the product repositories and removes prior categorical claims about tracking, retention, provider visibility, and screening. It is not a complete jurisdiction-specific privacy notice. Controller identity, lawful bases, retention schedules, subprocessors, transfers, and formal request procedures require counsel review.

Section 1

Data processed.

Depending on the surface and route, uSwap systems may process:

• source and destination assets, networks, amounts, addresses, transaction hashes, quotes, fees, route legs, provider identifiers, and transaction state history;
• bridge, intent, affiliate, partner, API, support, and recovery identifiers;
• for a virtual-card route, provider customer and card identifiers, selected card product, age-confirmation status, deposit and operation references, quote and funding-cost components, card status and available-balance information;
• when an authorized card-details view is requested, sensitive card data supplied by the provider, such as a card number, expiry date, CVV, and, where supplied, PIN; and card-payment or verification data, such as merchant, amount, status, time, verification code, or approval link;
• delivery details required for a selected product, such as a Telegram username, email address, gift-card order detail, fiat destination, or provider credential;
• request metadata, IP address, user agent, timestamps, errors, logs, and abuse-prevention signals;
• website and application analytics events, persistent analytics identifiers, and browser storage; and
• partner organization and authentication data on partner-facing services.

Data requested and processed varies by the selected route. A provider or destination may require additional information under its own rules. Do not submit information that the active route does not request.

Section 2

Purposes.

Data is used to request and compare quotes, create and execute routes, detect deposits, settle or deliver outputs, present status history, reconcile provider state, issue or reload a virtual card where that product is selected, support refunds and recovery, investigate incidents, prevent abuse, operate partner and affiliate functions, provide support, and understand product reliability and usage.

Public blockchain data remains visible on the relevant networks. Transaction legs may be correlatable by providers, infrastructure operators, uSwap records, counterparties, or chain analysis. Exclusion from a uSwap public activity feed does not make a transaction anonymous or untraceable.

Section 3

Providers and screening.

Routes using NEAR Intents are subject to its automated address and transaction screening. Other providers may apply their own eligibility, sanctions, identity, and risk controls. Availability varies by route and jurisdiction.

uSwap sends providers the quote, routing, destination, delivery, and transaction information needed for their route leg. For a virtual-card route, this can include the provider customer reference, selected product, age-confirmation result, funding asset and network, amount, a refund address where required, and deposit, card, quote, and operation references. Providers and infrastructure services process data under their own terms. The repositories do not establish that every route uses the same screening, eligibility, retention, or identity process.

Section 4

Virtual-card data.

The card provider can return card state, available balance, merchant transaction history, and payment-verification information so uSwap can show the selected card and help process card controls or support requests. A transaction record can include a provider transaction identifier, merchant name, amount, fee, state, currency, and time. A payment-verification response can include a merchant, amount, verification code, or an approval link when the provider makes those available.

Sensitive card credentials are retrieved only for an authorized card-settings view and are excluded from public bridge data. The interface conceals them by default and can hide them when the view loses focus. This does not protect credentials from someone who has access to your authorized settings link, device, browser session, or a place where you reveal or save them.

Section 5

Analytics and local storage.

uSwap surfaces use browser storage, PostHog analytics, and X conversion measurement to measure product use, reliability, and advertising performance. These services can use persistent device or browser identifiers and receive page, browser, and campaign-attribution data. Sensitive transaction surfaces are configured to suppress session replay, and input masking is used where replay is enabled, but analytics events and operational records may still contain transaction-context metadata.

Browser storage can retain bridge references and settings-access information so a user can return to an existing transaction. On a shared or compromised device, someone with that local access may be able to open the related settings view. Use a private device and browser profile, do not share settings links, and clear local storage when you no longer need the shortcut. Clearing browser storage removes that local copy; it does not erase server-side transaction or provider records.

Section 6

Product and partner data.

Virtual-card, digital-product, gift-card, fiat, partner, affiliate, bot, extension, and support flows can require data beyond a destination wallet address. That data is provided to the relevant supplier, counterparty, issuer, provider, or service where necessary to fulfill or support the request. Do not submit information that the selected route does not request.

The browser extension can interact with payment-site sessions and proof data for supported flows. Its permissions, local capture, relay, and retention behavior should be evaluated from the installed extension version and the relevant payment-proof provider, not from a general claim that uSwap never processes sensitive information.

Section 7

Retention and security.

Transaction state, event history, provider references, card-related operation and support records, and operational logs may be retained after settlement where needed for recovery, reconciliation, dispute handling, security, reporting, and incident investigation. Provider and blockchain records are controlled separately. A complete field-level retention schedule is under review; no statement on this page promises immediate deletion of settled transaction records.

uSwap applies technical and operational safeguards, but no system or blockchain transaction can be guaranteed completely secure. Avoid placing secrets or unnecessary personal data in transaction destinations, support messages, or public blockchain fields.

Section 8

Requests and choices.

You can clear uSwap browser storage through your browser. For a question or request about records held by uSwap, contact support@uswap.net and include only the minimum bridge, intent, or transaction identifier needed to locate the record. A request may be limited by security, fraud-prevention, legal, provider, or record-retention requirements.

Do not send a card number, CVV, PIN, or payment-verification code through ordinary support email or public channels. Use the authorized card view for card details and contact support with the minimum non-secret reference needed to identify the issue.

Section 9

Children.

uSwap is not directed to children. The current virtual-card flow requires an affirmative confirmation that the user is at least 18. Product-specific age rules may be stricter and are controlled by the applicable provider, issuer, or jurisdiction.

Section 10

Contact.

For privacy questions, email support@uswap.net. The legal entity and formal notice address are pending counsel confirmation and will be added when verified. See the Terms of Service for service disclosures.