# Overview

IronWeave ensures data privacy by fundamentally rethinking the traditional blockchain model, establishing each interaction as a new, self-contained and encrypted data unit, or *block*.&#x20;

Unlike monolithic blockchains, which expose transaction details and are scannable and thereby making all data visible to anyone, IronWeave's Shared-Block Architecture ensures that each block is encrypted with a unique set of keys, accessible only to the participants involved in that specific interaction.&#x20;

This architectural approach means that, outside of the direct participants, no one even knows the interaction exists or occurred. Such fundamental privacy on a per-interaction level prevents surveillance and brute-force attacks common on scannable public ledgers, even those using privacy-enhancing techniques like ZK Proofs or FHE.&#x20;

The architectural shift from a single, central chain to an unlimited number of independent, interconnected chains, allowing parallel block creation and individualized encryption on a per-block level, delivers inherent privacy and unparalleled security for any type of data, from financial transactions and medical records to AI data exchanges.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ironweave.io/privacy/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
