Privacy Policy

Privacy Policy.

Interim disclosure of transaction, provider, operational, and analytics data. Final entity, retention, and jurisdiction-specific language remains subject to qualified-counsel review.

Last updated August 5, 2026

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;
  • 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.

Standard crypto use does not require creation of a uSwap consumer account or direct submission of government identity documents to uSwap. A selected provider or destination may require additional information under its own rules.

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, 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. 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

Analytics and local storage.

uSwap surfaces use browser storage and PostHog analytics to measure product use and reliability. Configuration can include automatic interaction capture and persistent device or browser identifiers. 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 so a user can return to an existing transaction. Clearing browser storage removes that local copy; it does not erase server-side transaction or provider records.

Section 5

Product and partner data.

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, 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 6

Retention and security.

Transaction state, event history, provider references, 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 7

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.

Section 8

Children.

uSwap is not directed to children. Product-specific age rules may be stricter and are controlled by the applicable provider, issuer, or jurisdiction.

Section 9

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.