> For the complete documentation index, see [llms.txt](https://docs.cryptolegacy.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptolegacy.app/execution-scenarios/chapter-1-privacy-how-cryptolegacy-shields-you-from-coercion.md).

# Chapter 1 – Privacy: How CryptoLegacy Shields You from Coercion

Privacy-by-design prevents coercion by hiding asset information until execution conditions are met.

Imagine Bob, traveling abroad, suddenly detained without explanation. Authorities seize his laptop and phone, leaving him unable to access or control his crypto assets. Pressure shifts to his family, where past tensions — sibling rivalries, unresolved conflicts — become leverage.

With multisig wallets, Bob’s family must urgently coordinate signatures. In doing so, his full balances are immediately exposed. Under pressure and uncertainty, conflicts escalate, increasing the risk of coercion and manipulation.

With shared mnemonics, the situation is even more direct: beneficiaries instantly gain visibility into Bob’s entire holdings, concentrating both power and pressure at the worst possible moment.

Traditional legal approaches offer little relief. They are slow, jurisdiction-bound, and ineffective in situations involving immediate on-chain control — especially across borders.

CryptoLegacy approaches the problem differently, by reducing leverage created through premature disclosure:

* **Trusted Guardians:**\
  Guardians are selected in advance and operate under predefined thresholds. They do not access funds or control assets. Their role is limited to confirming owner unavailability according to on-chain rules, enabling execution without discretionary decisions.
* **Encrypted Asset Data:**\
  Information about wallets and assets is encrypted per role and remains inaccessible until predefined conditions are met. Neither guardians nor beneficiaries have visibility into balances or asset structure before execution is permitted.
* **Gradual Beneficiary Access:**\
  Once assets are transferred into the CryptoLegacy contract, beneficiaries can claim only what the predefined schedule allows. This staged access limits sudden concentration of control and reduces external pressure.
* **Hidden Recovery Mechanism:**\
  Recovery addresses are stored as cryptographic hashes and remain unlinkable until used. They provide a predefined recovery path for remaining contract-held assets if circumstances change, without exposing control paths in advance.

By separating visibility from authority, CryptoLegacy limits the leverage that third parties can exert during moments of uncertainty.

Bob’s family can act within predefined boundaries, without exposing full balances, concentrating power, or escalating pressure — exactly when restraint matters most.

**Your keys. Your crypto. Your privacy.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cryptolegacy.app/execution-scenarios/chapter-1-privacy-how-cryptolegacy-shields-you-from-coercion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
