# Examples

In each case, the Protocol provides a public record of the agreement and the user’s permission, while the data itself remains off-chain and is delivered by the service provider.

#### Example 1: Website

A website asks users to opt in to specific data uses, records each opt-in on the blockchain, and rewards users for participating.

**How it works**

* The website publishes an **agreement** that states the permitted purposes and references the governing terms.
* A user opts in, creating an on-chain **proof of permission** tied to that agreement. The permission can be ongoing or time-limited, and it can be revoked when allowed by the agreement.
* The website stores and manages the user’s data off-chain. When the data is used or shared, the website checks the on-chain permission status to confirm it is active.
* The website rewards the user under its reward program, using the on-chain permission record as the auditable basis for the reward.

**What this provides**

* A clear record of what the user authorized and when.
* A defensible permission trail for audits and partner reviews.
* A shared source of truth for permission status without relying only on internal logs.

***

#### Example 2: Data Marketplace

A marketplace connects users with third-party brands. Brands publish offers and terms, users choose what to share, and each permission is recorded on-chain.

**How it works**

* Brands publish offers with defined purposes and referenced terms. Each offer is anchored as an on-chain **agreement**.
* Users opt in by data product, which may include surveys, AI chats they choose to share, paid brand lead forms, linked public content, clickstream, browsing signals, and other user-generated data.
* Each opt-in creates an on-chain **proof of permission** tied to the specific brand agreement, with a visible status over time.
* The marketplace or designated service providers package and deliver the approved data off-chain, and can require that permission remains active before providing access.
* Users are rewarded under the marketplace’s commercial model, with the on-chain permission record supporting transparency and auditability.

**What this provides**

* Brands receive permissioned data tied to stated purposes and referenced terms.
* Users can view and manage permissions across many brands in one place.
* The marketplace can demonstrate it brokered permissioned access using a public, tamper-evident record.


---

# 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.permission.ai/permission-protocol/concepts/examples.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.
