Privacy

What the world can and cannot see when you use a Final Wallet — stated at the level of what you can rely on, not how it is done. Privacy here means your affairs are yours; verifiability means anyone you choose can still check what you show them. The two are designed together.

#What an outsider sees, and does not

When you act through your wallet, what becomes visible outside is deliberately small:

• Before execution: the target chain, the deadline and the schedule. Not your wallet, not the recipient, not the amount, not the content.
• At execution: a transaction on the target chain that carries no address history back to you. The account that submits it exists for that one signature and never again; it has no past to search and leaves no thread to follow. Postings from one wallet are not linkable to each other from the outside.
• Afterwards: the receipt is yours to read, from your own wallet with your own keys. Nothing indexes your activity under your name.
• Across time: an intent can have several legs, and they can execute at different times, on different chains, in different bundles. Nothing outside ties one leg to another or to you.
• Under audit: what an auditor can see is the headers — that a valid, authorised intent was admitted and that its execution matched — never the content. Validity is proved without disclosure: the chain verifies the signatures and the proofs, not the story behind them.

#Private intents

Any intent, immediate or scheduled, can be posted privately: the content is encrypted on your device and stays encrypted until execution is authorised. Until then nobody can read it — the operator included. The wire form that hides who an intent's recipients are is in service on the test environment; the sealed content nobody can read early follows as the private option, priced on the ladder. See Intents.

#Your identity, your disclosure

A Final Identity is a certificate set you made on your own device. Nothing about you is stored with us: issuance received commitments to your keys, never the keys, and never a name. On Final Chain, when a platform or an authority needs to know something about you, you decide what to present — the attribute it needs and nothing more — and withdrawing that disclosure is leaving the group, with a small set of overrides where the law fixes an attribute. Once attested, an attribute is proved from chain state wherever you present it, so nobody has to verify you twice, and nobody holds a copy of you. See Final Identity.

Identity verification is a choice, not a condition. Nothing in the network requires you to disclose who you are. Where a platform or an authority asks, you may choose to present attested attributes — and because that saves them the cost of verifying you themselves, part of the saving comes back to you. And there will always be modules, voted for by holders, that ask for nothing at all.

#Zones with their own rules

An institution can host its own zone on Final Chain with access, privacy and permission rules tuned to its needs — its own rules for its own users, always integrated with the network rather than apart from it. Privacy for the members of a zone is a property of the zone, set by whoever hosts it.

#What privacy does not mean here

• It is not opacity: the validity of every action is proved on chain, and what you choose to prove is provable, by anyone you show it to.
• It is not secrecy from yourself: every intent has a receipt and a status you can read back.
• It is not a shield against the rules you accept: a zone or a group applies its own, and leaving is always yours.

#See also

Intents · Final Identity · Security-first architecture · Final Certificates