> For the complete documentation index, see [llms.txt](https://whitepaper.kindredlabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.kindredlabs.ai/overview/introduction/breathe-life-into-ai/personalized-ai-from-assistance-to-companionship/privacy-security-and-ethical-design.md).

# Privacy, Security, and Ethical Design

With AI deeply embedded in our lives, privacy and ethical design are paramount. Kindred tackles these concerns by prioritizing user control, data security, and emotional well-being.

**Key Principles of Ethical AI at Kindred**:

* **Decentralized Memory**: Personal data is decentralized and encrypted, ensuring privacy and user security.
* **User Control**: Users have full control over their AI agents, including data deletion, customization, and memory resets.
* **Emotional Integrity**: AI responses are designed to support user well-being, not manipulate emotions or influence decisions.

These safeguards ensure that Kindred’s AI agents act as trusted allies, supporting users without compromising privacy, security, or ethical integrity.


---

# 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:

```
GET https://whitepaper.kindredlabs.ai/overview/introduction/breathe-life-into-ai/personalized-ai-from-assistance-to-companionship/privacy-security-and-ethical-design.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.