> For the complete documentation index, see [llms.txt](https://docs.wagon.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wagon.network/products/data-network-upcoming/access-and-permissions.md).

# Access & Permissions

The Wagon Data Layer is designed with privacy, ownership, and controlled access at its core. Data contributors and users interact with the network under a permission framework that prioritizes security and autonomy.

***

## 👤 Who Owns the Data?

Data submitted by businesses (e.g. operational logs, leasing metrics) remains fully owned by the original contributor. Wagon does **not** sell or expose private data — instead, it enables **permission access** via smart contracts.

***

## 🧾 How Is Access Granted?

* **Public Datasets**\
  General industry stats and anonymized aggregates are openly accessible via the Wagon platform.
* **Private Datasets**\
  Access to specific datasets requires permission from the data owner and is governed via smart contracts.

***

## 🔁 How Do Users Get Access?

* **Individual Users & Enterprises** can subscribe to access data via the Wagon platform.
* Payment and permissions are handled via WAG token transactions on-chain.
* Users may select specific datasets or request custom analytics via dashboard or API.

***

## 🛡️ Privacy & Security

* End-to-end encryption and zero-knowledge principles preserve anonymity.
* All access is logged immutably on-chain to ensure transparency and auditability.
* Smart contracts enforce terms like duration, pricing, and dataset scope.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.wagon.network/products/data-network-upcoming/access-and-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.