Hide.cash

What it is. Instant XMR-output-only swap service — send major cryptocurrencies, receive only Monero, no accounts, no KYC, no AML. Listed at Grade C because the homepage is one of the stronger single-page trust surfaces for a no-peer-reference service (live reserve counter, flat 0.5% fee, explicit no-logs language), held at the directory's default tier by total absence of peer-directory confirmation and legal pages.

Background. The operator positions Hide.cash as a privacy-first Monero swap: 'No KYC · No AML · No Trace' (operator-published, homepage masthead). The copyright footer shows '© 2025 hide.cash' — suggesting operations began in 2025. No /about page exists. No operator identity, founding date, jurisdiction, or team information is published — the service IS the surface. The support contact is `lets@hide.cash` — operator-published, single-channel. The homepage lists a live XMR reserve counter at 9,265.31 XMR (operator-published) — a rare transparency signal for a swap service at this tier, though the counter's accuracy and the reserve wallet address are not independently verifiable from the page.

What you trust.

• XMR-only output direction — by operator design, not accident. Every swap terminates in Monero; the service does not offer XMR → BTC-or-anything-else. The FAQ frames this as a deliberate privacy-architecture choice: *"Monero is the only cryptocurrency with mandatory privacy at the protocol level. Ring signatures, stealth addresses, and RingCT make all XMR transactions unlinkable and untraceable by default. Converting into XMR is the most effective single step you can take to break on-chain traceability."* (operator-published, FAQ §3). This is a meaningful alignment signal in a privacy directory — the operator's economic upside is tied to Monero, not to using XMR as one token among many on an otherwise-generic aggregator. The structural consequence: the AML-attack surface flattens (no XMR → BTC leg means no "tainted XMR" challenge mid-trade), and whatever rug-pull risk exists concentrates onto the input leg, while the output leg is what the user actually receives.
• No-KYC stance. Operator-published: 'No KYC · No AML · No Trace' (homepage masthead). 'No accounts. No identity checks. No logs.' (homepage hero). 'Zero Identity: No account. No email. No KYC. No AML checks. You are just an address to us - and even that we forget.' (homepage, Why hide.cash section). This is the most direct no-KYC language in any single-page swap service in the directory — there is no ambiguity.
• No-logs policy. Operator-published: 'No Logs Policy: Session data is purged within 24 hours. We hold no order history, IP logs, or user records - by design.' (homepage, Why hide.cash). 'No data is stored. All sessions are ephemeral.' (homepage footer). A 24-hour retention window with explicit deletion is stronger than most swap services' vague 'we don't log' claims.
• Live reserve counter. Operator-published: 'Reserve: 9,265.31 XMR' displayed on the homepage hero — a live, updating figure. This is a stronger transparency mechanism than any other Grade C swap service. It signals the operator holds a known quantity of XMR and is willing to advertise it. However, the counter is not independently cryptographically verifiable (no signed proof-of-reserves or wallet address published).
• Fee structure. Operator-published: 'Flat Fee: One simple 0.5% fee. No hidden spreads, no minimum surprises. What you see is what your XMR buys.' (homepage). 0.5% is competitive for instant-swap services. The fee is published upfront rather than embedded in the exchange rate — a positive disclosure pattern.
• XMR-only output. The service only outputs Monero — no transparent-chain assets on the receive side. Inputs accepted: BTC, ETH, SOL, BNB, USDT, USDC (operator-published, homepage coin selector). This is a structurally privacy-conscious design: all output goes through Monero's default privacy, and no transparent-chain recipient address is published by the swap.
• Non-custodial claim. Operator-published: 'Non-Custodial Flow' (homepage hero tag). The FAQ describes a hot-wallet dispatch model: 'Funds are sent from our XMR hot wallet instantly.' This is non-custodial in the sense that the service does not hold user funds long-term, but during the swap execution window, funds are in the operator's control — full non-custody would require atomic-swap technology, which this service does not use.

Operational specs.

• Fee. 0.5% flat fee, no hidden spreads (operator-published, homepage). No minimum or maximum order size stated.
• Supported inputs. BTC, ETH, SOL, BNB, USDT, USDC (operator-published, homepage coin selector dropdown). Six input chains covering the major liquid markets. Output: Monero only.
• Settlement time. Operator-published: 'Most orders complete in under 20 minutes after the required confirmations on the source chain.' (homepage, Why hide.cash). Time varies by chain — BTC requires more confirmations than SOL.
• Order mechanics. One-time deposit addresses are generated per session. Orders are valid for 60 minutes (operator-published, order-creation modal). A refund address can be optionally provided. Session IDs appear ephemeral (e.g., 'Exchange SESSION: SX-95DB9AF2').
• Tor mirror. None — no onion address published and no `Onion-Location` header detected. Clearnet-only. A Tor-accessible swap would be a meaningful privacy upgrade for a service called 'Hide.'
• Contact / support. Email: `lets@hide.cash`. No additional public channel beyond the operator X handle below. Public channel: `@hidedotcash` on X (operator-controlled per the homepage's social link).
• Legal surface. Minimal — no /privacy, /terms, /tos, /aml, /about, or /contact page exists at any standard path. The homepage IS the legal surface: the privacy claims, no-logs policy, and fee structure are all published inline on the single page. There is no standalone ToS or privacy policy at any discoverable path.

Operator philosophy. The operator has built a deliberately minimalist single-page swap service. Every trust claim lives on one page — no subpages, no knowledgebase, no blog, no about. The design is opinionated: XMR-only output, no accounts, ephemeral sessions, flat fee, live reserve counter. The branding ('Hide.cash,' the single-mailbox support address, the 2025 copyright) reads as a small-team or solo-dev project that chose to publish the service as the surface rather than build a company around it. The absence of an /about page is consistent with this posture — there is no operator to find.

Grade rationale. Listed at Grade C — the directory's default tier for services with no verifiable external trust signals. The homepage publishes unusually strong and specific privacy claims (no KYC, no AML, no logs, 24h session purge, flat 0.5% fee, live reserve counter) — a stronger single-page trust surface than most C-grade listings. However: (1) no peer-directory lists hide.cash (verified against kycnot.me and monerica.com); (2) the service has no separate legal pages — the entire legal surface is embedded in the homepage marketing copy; (3) no Tor mirror; (4) the service has been operating for under a year (copyright shows 2025; no public history before then) with no review record on any independent platform. Grade C reflects that the homepage claims are structurally credible and the XMR-only output design is privacy-conscious, but there is no external corroboration whatsoever. Path to B-: publish the reserve wallet address or a Monero view-key so the live `~9,265 XMR` counter can be reconciled against the chain — currently it is a signaling claim, not auditable proof. Add a second public contact channel (PGP-signed email or matrix/simplex handle in addition to `lets@hide.cash`) and accumulate ≥6 months of operating-since on-platform without a withheld-funds incident.

Useful when:

• fill after curator test trade: does a BTC → XMR swap complete within the advertised 20-minute window? Is the 0.5% fee accurate against the XMR received?
• fill from test trade: does the reserve counter update in real-time after your swap? Does the figure plausibly change, or is it static?

Caveats.

• The live reserve counter (9,265.31 XMR) is displayed but not cryptographically verifiable — no signed proof-of-reserves, no wallet address, and no independent audit mechanism exists. The counter could be a static design element or a manually updated figure rather than a programmatic reflection of wallet balance. This matters: the reserve counter is the single strongest trust signal on the page, and if it's cosmetic, the service's trust surface collapses to the operator's word.
• No peer-directory currently lists hide.cash (verified against kycnot.me and monerica.com). A handful of general privacy-resource indexes mention the name in passing, but there are no service-specific reviews from any independent reviewer as of fold-time.- Support is single-channel — `lets@hide.cash` is the only email contact, and the operator X handle has 15 followers as of fold-time. If that mailbox is compromised or the operator's domain registration lapses, users have no fallback channel.