Use privacy when the BTC route matters

Q: What is Redacted on Rujira?

Redacted is Rujira's privacy product. It is designed to give users an optional privacy route inside the broader ecosystem rather than forcing privacy to be the only way they interact with the stack.

Q: What does privacy mean in this product?

Here, privacy means reducing how much selected activity is publicly exposed in the product flow. It is about more control over visibility, not a promise that every part of the system becomes invisible.

Q: Is this the same as full anonymity?

No. This page is careful on purpose. Redacted is about optional, product scoped privacy. Users should not treat that as a blanket claim of total anonymity in every context.

Q: Why would a Bitcoin user want optional privacy?

Because balances, movement, and strategy can become easier to infer from a fully public trail. Optional privacy gives BTC users another way to manage that exposure without giving up wallet control.

Q: Can privacy be used across multiple Rujira products?

That is the intent. Redacted is positioned as a privacy layer that can support a broader ecosystem workflow, not only one isolated privacy action.

Q: Do I stay in control of my assets?

Yes. The page is framed around wallet based usage and self custody, so privacy is treated as something that supports user control rather than replacing it with a custodial handoff.

Q: Is this only for advanced users?

No. The whole point of the page is to make privacy understandable for normal users. You do not need to be a privacy expert to know when a less public route is useful.

Q: How is this different from privacy first chains or isolated privacy apps?

Redacted is aimed at optional privacy inside the Rujira product stack. That is different from a privacy first chain or a single purpose privacy app where the entire environment is built around privacy from the start.

Redacted gives Bitcoin users a way to add privacy where it is useful without pretending every action should disappear from view. It is a product-layer option inside the wider Rujira ecosystem, built for more control over how you move and manage BTC from your wallet.

For Bitcoin users, the point is practical control: use privacy when it fits the moment, keep it optional when it does not.

Explore Privacy

How Privacy Works

Use privacy when the BTC route matters sections

Redacted Privacy Layer

What is the Privacy Layer?

Redacted is the privacy layer inside the Rujira ecosystem. It gives users a way to transact with more discretion while still fitting inside a system designed for real market participation, clearer boundaries, and compliance-aware product flows.

Because it connects through THORChain's cross-chain reach, privacy DeFi no longer has to live inside one isolated environment. Native assets like BTC, XRP, and ETH can access private routes without giving up the interoperability that brings them into the ecosystem in the first place.

That is why the ecosystem matters. Privacy is not boxed into a single app. Once the layer is active, the wider product set can use it too, so swaps, trading, borrowing, and broader Rujira flows can all benefit from the same private execution path.

Revenue flow to stakers

Interaction between products

RUJI Collections

RUJI Launchpad

RUJI Swap

RUJI Perps

RUJI Predict

RUJI Options

TC Base Layer Pools

RUJI AMM

RUJI Trade

RUJI Money Market

Stablecoin

RUJI Liquidations

Why Redacted Privacy Layer

Why use Privacy

Privacy becomes useful when a public wallet trail says more than it should about balances, routes, and intent. Redacted gives users a way to reduce that exposure without stepping out of self-custody, losing ecosystem access, or treating privacy like a separate world reserved only for specialists.

Comparison

Where Redacted sits in the privacy landscape

This comparison focuses on product design, user path, and how each project approaches privacy inside or alongside broader DeFi activity.

Comparison table for Redacted, Railgun, Aztec, Nocturne, and Tornado Cash
Category	Redacted	Railgun	Aztec	Nocturne	Tornado Cash
Privacy model	Optional and product-scoped inside the Rujira ecosystem	Optional private wallet and transaction shielding	Privacy-first execution environment	Private account model for selected wallet activity	Isolated privacy pool flow
Wallet accessibility	Designed around normal wallet-based access inside Rujira	Wallet-based, but usually a more dedicated setup	Environment-led experience rather than a lightweight product toggle	Wallet-focused, but still a more specialized route	Simple deposit and withdrawal path, but narrow in scope
Fit with broader DeFi flows	Aimed at supporting multiple product flows in one stack	Can connect to DeFi, but still feels like a more distinct privacy route	Built around a broader private environment	More focused on private account abstraction	Mostly separated from broader product flow
Normal-user complexity	Aims for simpler adoption inside a familiar product ecosystem	More approachable than many privacy systems, but still more specialized	Higher conceptual overhead because the environment itself changes	Moderate complexity around private account setup	Simple to describe, but very narrow in what it does
Best fit	Users who want privacy as an option inside a broader self-custody workflow	Users who want a dedicated privacy wallet experience	Users who want a privacy-first execution environment	Users who want private account flows for selected activity	Users who only need a narrow privacy-pool route

Directional comparison of project design and user experience, not a live feature audit.

Activation

Turn privacy on when it matters

Privacy should feel usable, not mysterious.

You do not need to become a privacy specialist before Redacted becomes useful. The practical path is simple: decide when a public trail is unnecessary, move into a more private route for that part of the flow, then carry on with the rest of your activity.

That makes privacy feel like a tool for control instead of a separate identity. It is there when you want more discretion around balances, movement, or strategy, and it stays optional when you do not.

Start with a private balance

Move into a more private route when you want less public visibility around a specific asset position or transfer.

Bring that privacy into the wider flow

Use privacy as part of a broader Rujira workflow instead of treating it like a one-step detour that goes nowhere else.

Explore Privacy

See Bitcoin product flows

Redacted visual representing privacy support for Bitcoin users on Rujira

Private and Compliant

Private and compliant can live in the same system

Serious users do not need privacy framed as a rejection of legitimacy. The stronger model is controlled discretion inside an ecosystem that still values clarity, accountability, and real-world usability.

Global coordination with cleaner exposure

For Bitcoin users, that means a privacy route should feel calm and deliberate. It should reduce unnecessary visibility around balances, transfers, and strategy without turning the broader product experience into something theatrical or adversarial.

The point is not to pretend public context disappears. It is to make sensitive flows less immediately legible while still operating inside a stack designed for real markets, normal self-custody habits, and more credible participation.

Designed for globally coordinated flows

BTC activity can move across wallets, venues, and regions quickly. Privacy works better when it supports that reality instead of isolating users in a narrow side path.

Controlled disclosure instead of total opacity

The useful promise is reduced exposure where it matters, paired with clearer expectations about what privacy helps with and where visible context still exists.

A calmer posture for meaningful size

The experience should feel trustworthy for users managing real positions: less noise, more discretion, and a stronger sense that privacy belongs inside a mature product stack.

Interactive globe representing private, globally coordinated, compliance-aware Bitcoin activity on Rujira

Privacy explained

The goal is to make privacy understandable enough that users can choose it intentionally.

Why it matters

Onchain activity leaves a visible trail

Wallet activity can say a lot about a user even when addresses are public by design. Privacy matters because some flows reveal more information than they need to.

What gets protected

Privacy is about reducing unnecessary exposure

In this product context, privacy means making selected balances, movements, or flow details less publicly obvious than they would be in a fully open path.

Optional use

It is optional, not all-or-nothing

Redacted is not asking users to make every action private. It is there for the moments where a public trail feels unnecessary or strategically unhelpful.

Across products

Privacy can support more than one workflow

The point is not only private transfers. Privacy can fit before or during trading, balance management, collateral movement, and other product flows across the Rujira stack.

What it does not do

Privacy is not the same as absolute invisibility

This page is about product-scoped privacy, not blanket anonymity claims. Users should understand what a privacy route helps with, and also where public context still exists.

You Are Ready

You now understand when privacy can make sense on Rujira.

That gives you a clearer next step: use privacy more intentionally, keep custody of your assets, and explore the live product when you want more control over how a flow appears.

Explore privacy

What is Redacted on Rujira?

What does privacy mean in this product?

Is this the same as full anonymity?

Why would a Bitcoin user want optional privacy?

Can privacy be used across multiple Rujira products?

Do I stay in control of my assets?

Is this only for advanced users?

How is this different from privacy-first chains or isolated privacy apps?