Privacy Policy

We do not collect any personal data, metadata, or identifying information from users. No account creation is required. No email, phone number, name, or any other personally identifiable information is requested at any point.

This website does not use cookies, browser fingerprinting, localStorage, analytics scripts, tracking pixels, or any other client-side tracking mechanism. All public-facing pages are designed to function without JavaScript and are fully compatible with Tor Browser at its highest security setting.

IP address logging is disabled across every layer of our infrastructure. This is enforced at the configuration level on all of the following components:

We are technically unable to determine the country, jurisdiction, or geographic location of any user. No component of our stack processes or transmits IP address information. There is no mechanism - even internally - to associate any exchange operation with a network identity.

The only data stored in connection with exchange operations is the minimum required to process the transaction: deposit address, destination address, refund address, amounts, and blockchain transaction identifiers.

This data is permanently and irreversibly deleted after 15 days. This is not an archival or soft-delete process. The data is destroyed at the database level and cannot be recovered, reconstructed, or produced by b1eXch or any third party after deletion has occurred. Once deleted, swap IDs can no longer be used to retrieve any order information through any interface.

Saved swap history is used solely to let users quickly return to their own swap orders from the same browser session. The saved list is stored server-side and keyed to the existing session cookie; no additional tracking cookie is created for this feature.

Sessions are ephemeral and are destroyed when the browser is closed or when the session expires. No session data is written to disk. Users may clear their session swap history at any time via the "Clear History" option.

Our infrastructure is designed with the assumption that physical compromise is a realistic threat vector. The following measures are enforced:

All essential security patches are applied promptly. The operating system is a hardened Linux distribution configured specifically for this workload with unnecessary services, modules, and packages removed.

All traffic to and from our service is encrypted using TLS 1.3 with forward secrecy. The service is accessible via both clearnet domains and a dedicated .onion address for users who prefer end-to-end Tor routing.

Our network stack enforces strict firewall rules with a default-deny policy. Outbound connections are limited exclusively to blockchain nodes and essential operational endpoints. Rate limiting and DDoS mitigation are handled at the network perimeter without logging request origins.

Blockchain node connections are distributed across multiple independent providers to avoid single points of surveillance or failure.

b1eXch is fully compatible with Tor. All public-facing pages render fully without JavaScript. No client-side scripts are required to create or monitor exchange orders.

The service is accessible via a dedicated .onion hidden service, providing end-to-end encrypted routing that prevents any network observer from determining that you are accessing this service.

We do not employ any techniques that degrade the experience of Tor users - there are no CAPTCHAs, JavaScript challenges, or browser fingerprinting checks that would distinguish Tor traffic from clearnet traffic.

We do not use any third-party analytics, advertising, tracking, or monitoring services. No data is shared with, transmitted to, or accessible by any external party.

The only external services our backend communicates with are cryptocurrency blockchain nodes and decentralized exchange protocols, strictly for the purpose of processing swap transactions. These connections do not transmit any user-identifying information.

Because of our zero-logging architecture, we are unable to provide any of the following, even if compelled to do so:

This is not a policy choice that can be reversed - it is an architectural constraint. The data does not exist in our systems and therefore cannot be produced, reconstructed, or inferred.