> For the complete documentation index, see [llms.txt](https://docs.kleva.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kleva.io/kleva-ais-products/product-philoshopy-3s.md).

# Product Philoshopy: 3S

To deliver the best possible experience and value, Kleva AI is built on three core principles:

### **Simple**

No complex sign-ups or crypto exchange registrations needed. Users can easily convert points and use financial services within the app.

The process is intuitive, allowing anyone to participate effortlessly.

### **Secure**

We apply the latest security technologies and data protection measures to safeguard user assets and personal information.

All transactions and activities are securely recorded, ensuring peace of mind at every step.

### **Sustainable**

Designed to maximize the value of users’ intangible assets.

By converting expiring points into crypto and combining them with staking, investment, and reward models, we transform passive assets into active earning opportunities.


---

# 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.kleva.io/kleva-ais-products/product-philoshopy-3s.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.