# 6.1 User Data Principles

VIBE treats user data as a **user-held asset**, not a platform-owned resource.\
Data exists to serve the individual first, the system second.

#### Default Position

```plsql
User Data → User Control
Platform Access → Permissioned
```

Data is not collected for speculation, resale or opaque analytics.\
If data is not needed for a feature to function, it is not required.

#### **Minimal by Design**

VIBE follows a reduction-first approach:

* Collect only what enables the feature
* Store only what must persist
* Expose only what the user allows

No hidden aggregation, no background profiling.

#### **Clarity Over Complexity**

Instead of long privacy explanations, VIBE focuses on simple rules:

* Users know what exists
* Users know where it is used
* Users can choose whether to participate

Data is not abstracted away from the user experience.

#### **Why This Matters**

Wellness data carries context and sensitivity.\
Control is not a feature, it is the baseline.


---

# 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://vibe-6.gitbook.io/vibe-docs/6.-data-and-user-control/6.1-user-data-principles.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.