Privatly
Demo

Connect a wallet

You sign in your own wallet. Nothing about it leaves your browser.

Connecting only proves the wallet is yours. It does not log you in and it approves nothing on its own.

TRADESTOCKSLIQUIDITYPAYMENTS0x741...91AETHTradeSwapNVDAAAPLEquity buyPoolLP positionFeesUSDCPaymentAgent

One address.

Privacy without the friction.

Privacy did not disappear because people stopped caring. It disappeared because going private became too complicated, too technical and too slow, so convenience won. Privatly removes the tradeoff. You choose what you want. It works out how to reveal less.

You should not need to understand privacy to have it.

$PRIVATLYcopyexplorer
Know before you sign

See exactly what a transaction reveals.

Before anything is signed, Privatly separates what the chain will record from what somebody might conclude from it. The first list is fact. The second is labelled as inference, with its reasoning attached, because telling you your accounts are linked when they are only correlated would be telling you something false about your own money.

One account, many identities

Personal, Trading, Business, Savings.

Each one is a separate address on the chain, derived from your signature rather than stored anywhere. No second seed phrase, no second browser profile, no second extension. Switching between them takes one click and the active one is always on screen.

Set the rules once

Stop deciding in the middle of every transaction.

Never fund Savings straight from your wallet. Use Trading for apps you have not used before. Tell me before two of my accounts become publicly related. The rules are applied before anything is signed, and a rule that blocks cannot be overridden by an app.

See what stayed private

A receipt for every transaction.

Not the word private on a green tick. A line for each dimension with a plain answer: main wallet kept out, broadcaster separated, amount private, balance private. Every answer comes from the path that actually ran, so it cannot claim more than it delivered.

One private identity

Sign in as you. Execute as a context.

A passkey, a hardware wallet or a wallet you already control holds the signing authority. Google and Apple sign you in and nothing more: an identity provider that can move funds is a custodian with extra steps.

Account mesh

One account. Many isolated contexts.

Trading, equities, liquidity, yield, payments and each automation get their own smart account. You never manage them by hand. The mesh routes the action to the right one and tells you when it could not.

Private execution

The plan shows what the chain will see.

Before anything is signed: which context executes, whether your primary account is touched, whether an address is reused, whether a relay is available, and the exact list of facts that become public.

Private equities

Tokenized equities, held in their own context.

Where an asset carries jurisdiction or eligibility rules, Privatly respects them. Privacy architecture proves eligibility. It is not a route around it.

Automations

An agent that can only do one thing.

Every automation runs in its own context on a scoped, expiring session key, inside a policy of allowlists and caps. What it can do and what it cannot are shown side by side, and you can pause or revoke it without a counterparty.

Selective disclosure

Reveal the fact. Not the history.

Eligible: yes. Above the collateral threshold: yes. Without exposing the balance, the accounts or the record behind it. Where no proving backend is connected, Privatly says so rather than implying one.

Privacy health

Seven dimensions. No mystery score.

Address reuse, public identity linkage, cross-context linkability, primary wallet exposure, relay coverage, public approvals, shielded balances. Each one shows how it was calculated, so you can disagree with it.

Business and treasury

Operating, payroll, vendors, treasury.

A company sees one consolidated treasury. The chain does not receive the entire internal financial structure from one reusable address.

Self-custody

Your wallet. Your keys. Your financial graph.

Privatly never asks for a seed phrase or a private key, and there is no field in the data model to hold one. Recovery is yours to configure, and deliberately slow.

What works today
  • Your accounts, worked out from one signature and read from the chain
  • What you hold and what it is worth, priced from the pools themselves
  • What each holding cost you, read at the block it arrived
  • Every payment in and out, from the chain rather than from our records
  • Seven privacy measurements, each showing how it was calculated
  • A picture of what publicly links your accounts to each other
  • Every app you have given permission to spend, and every one you cancelled
  • Funding routes, ranked by how much each one gives away about you
  • Swapping from one of your accounts, at the pool's own price, with a minimum the router enforces
  • A signed claim about what one account holds, which anyone can check against the chain without trusting us
  • Providing liquidity from an account, across the whole price range, with the fees it has earned shown as the protocol would actually pay them
  • Standing instructions with limits a contract refuses to exceed: what may be spent, how much at once, how much ever, how often, and the date it stops
  • Checking somebody else's signed claim against the chain, with no account and no wallet
What is not built yet
  • Automations running while you are away. You can set one up, switch enforcement on for an account, and run it, all with the limits enforced by a contract. What is missing is somebody to submit a run at three in the morning: this app has no server, and a submitter can change nothing about a run, so this is a gap in convenience rather than in safety.
  • Shielded balances. The integration reads the pool and verifies it; producing a spend needs a prover, note synchronisation and encrypted backup, none of which are connected.
  • Hiding which account a fact is about. You can sign a claim about one account and anyone can check it against the chain, and doing that without revealing that account needs a proving system nothing on this chain provides.

The section above describes the product. This one says how much of it you can use right now, because a feature list cannot tell you that and finding out after signing in is the wrong time.

What Privatly reduces
  • Unnecessary public address reuse
  • Cross-activity linkage between unrelated things you do
  • Direct linkage between your signer and the transaction broadcaster
  • Public aggregation of your whole portfolio from one address
  • Standing approvals nobody is using any more
What it does not prevent
  • Advanced heuristic analysis of public chain data
  • Disclosure by a counterparty you transacted with
  • Data that a protocol publishes by design
  • A compromised device, browser or endpoint
  • Legal disclosure requirements
  • Restrictions attached to the underlying asset or protocol

Every privacy claim in this product maps to something the implementation actually does. Where it cannot deliver a mode, it falls back and says so in the plan, before you sign.

Reveal what is required. Not everything you own.

Privatly · Private by default