Overview
Escrow0 is an Indonesia-registered escrow coordination service built around a Telegram bot, targeting buyers and sellers who want a neutral third party to hold funds until delivery is confirmed. The operator, PT. Smart Digital Service (NIB 0904230012672), launched the platform with support for both cryptocurrency and Indonesian rupiah (IDR) settlements. Its marketing emphasizes Tor accessibility, open-source components, and peer-to-peer flexibility. However, the service carries a stark scam warning on Bitcoin Forum, where multiple users have flagged the project creator as a potential fraudster. That red flag, combined with a trust score of just 4/100 and an overall rating of 5/10, places Escrow0 firmly in the "proceed with extreme caution" column for any privacy-conscious user evaluating no-KYC marketplaces.
The core workflow is straightforward: a buyer locks funds, the seller delivers goods or services, and admins review evidence before releasing payment. Escrow0 does not function as a bank or licensed deposit institution, it merely coordinates the handoff. For crypto-native users, this model can work well when trust assumptions are low; here, those assumptions are uncomfortably high.
Privacy & KYC
Escrow0's privacy posture is weaker than its anonymous-friendly branding suggests. The platform earns a privacy score of only 6/100, driven by extensive data collection spelled out in its April 2026 privacy policy. The service gathers Telegram IDs, usernames, full names, IP-related server logs, browser activity, session data, and even wallet details or payout instructions submitted during crypto withdrawals. For IDR transactions, buyers must upload screenshot proof of payment, which admins manually review.
The KYC framework is tiered. Under the May 2026 AML/KYC policy, routine identity verification is not required for standard crypto-to-crypto deals. However, the moment a user touches Indonesian rupiah, whether depositing, withdrawing, or settling in IDR, KYC becomes mandatory. This involves submitting a government-issued document (KTP or SIM), the document number, full legal name, and a selfie holding the ID. Escrow0 also reserves the right to demand additional verification for crypto-only activity if fraud, compliance, or security concerns arise. This exception clause effectively means no crypto user is fully exempt from potential identity demands.
- KYC tier: L3, Tiered (threshold-triggered, primarily IDR-linked)
- Email required: Not specified as mandatory in crawled policies
- IP logging: Confirmed active via server logs and session tracking
- Data retention: Indefinite, tied to dispute resolution and legal compliance
Supported assets & payments
Escrow0 covers a genuinely broad spectrum of payment rails, which is one of its stronger selling points for users seeking flexibility. The platform accepts Monero (XMR), Bitcoin (BTC), Lightning Network BTC, fiat currencies, and physical cash. This mix makes it one of the few escrow services in the no-KYC directory that theoretically accommodates fully anonymous settlement via XMR or cash, provided the transaction never touches IDR rails. Lightning support is particularly notable for users wanting fast, low-fee Bitcoin transfers without on-chain footprint. However, the practical privacy benefit of these options is undermined by the platform's data-hungry backend. A Monero payment still requires submitting wallet details or payout instructions to Escrow0's system, and the Telegram bot integration means the operator permanently links deals to Telegram identities.
Security & custody
Escrow0's custody model is admin-controlled and non-custodial in name only. Users send crypto to designated escrow wallets, but these wallets are under operator control. The terms explicitly state that Escrow0 is not a licensed financial institution, and admin discretion governs all release, delay, or dispute decisions. The platform claims to use "reasonable technical and administrative measures" for security, yet provides no specifics on multi-signature arrangements, key segregation, or audit procedures. Open-source components are mentioned as a feature, but without clarity on what exactly is open-sourced, smart contracts, the Telegram bot, or merely frontend code, this claim offers limited verifiable assurance.
Tor access is available, which helps users mask their network origin, though the privacy policy confirms IP-related server logs are still collected. For dispute resolution, Escrow0 reviews message logs, screenshots, delivery evidence, and chat context. Admin decisions are made "in good faith" but come with no outcome guarantee. The Bitcoin Forum scam warning amplifies custody risk: if the operator is indeed fraudulent, locked funds may be irretrievable regardless of what the terms promise.
Who it's for, verdict
Escrow0 occupies an awkward niche. It markets itself to privacy advocates and no-KYC traders, yet its infrastructure is surveillance-friendly and its KYC policy is riddled with exceptions. The service may suit Indonesian users comfortable with ID verification who need a simple escrow for local rupiah deals, or crypto traders willing to gamble on a low-trust operator in exchange for Lightning and Monero support. For strict anonymity seekers, the combination of Telegram identity linkage, IP logging, manual screenshot review, and an unverified scam warning makes Escrow0 a poor fit.
The community sentiment is thin but telling: one user praised the service for saving money while hoping fees would drop below 0.8%. That single data point suggests functional utility for some, yet the broader signal, no organic Reddit discussions, no Trustpilot presence, and an active scam flag, points to insufficient social proof. In the no-KYC escrow space, trust is the currency Escrow0 has not earned.
