> For the complete documentation index, see [llms.txt](https://swopple.gitbook.io/swop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swopple.gitbook.io/swop/major-concepts/parent-profile.md).

# Parent Profile

A "Parent Profile" within the Swopple ecosystem represents a user's decentralized identity (DID), functioning as the cornerstone of their digital presence across the platform. This concept revolves around user autonomy and privacy, ensuring that individuals maintain full control over their personal information and how it's shared within the ecosystem.&#x20;

#### Foundation of Decentralized Identity

* **Core Identity:** The Parent Profile acts as the foundational layer of a user's identity on Swopple, analogous to a digital passport within the ecosystem. It's associated with the user's Swop.ID, encapsulating essential information, preferences, and credentials that define the user's digital persona.
* **Decentralization:** Unlike traditional online profiles managed by centralized entities, the Parent Profile is decentralized. This means it's stored on a blockchain, ensuring that the user, and only the user, has control over it. Decentralization not only enhances security and privacy but also prevents any single point of failure or unauthorized access.

#### Control Over Data Sharing

* **Selective Sharing:** Users have the flexibility to decide which pieces of their Parent Profile are shared and with whom within the Swopple ecosystem. Whether interacting with DApps, engaging in transactions, or networking, users can specify what information is relevant and necessary for each interaction, ensuring that their privacy preferences are always respected.
* **Consent-Based Interactions:** Every time a third party requests access to any part of the user's Parent Profile, consent must be explicitly granted. This mechanism puts the user in the driver's seat, allowing for a privacy-first approach to online interactions and data sharing.

#### Updateable and Portable

* **Dynamic Updates:** Users can update their Parent Profile at any time, adding new information, changing preferences, or revoking previously shared data. This ensures that the digital identity remains accurate and reflects the user's current status and preferences.
* **Ecosystem-Wide Portability:** The Parent Profile is designed to be portable across the Swopple ecosystem. This means that as users navigate different services and DApps within Swopple, their decentralized ID seamlessly integrates with each experience, providing a consistent and unified digital identity.

#### Conclusion

The Parent Profile represents a pivotal shift towards empowering users with control over their digital identities in the Swopple ecosystem. By prioritizing decentralization, privacy, and user autonomy, Swopple ensures that personal data is only shared based on explicit user consent and can be updated according to the user's evolving preferences. This approach not only enhances user security and privacy but also fosters a more trustful and user-centric digital environment.


---

# 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://swopple.gitbook.io/swop/major-concepts/parent-profile.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.
