> For the complete documentation index, see [llms.txt](https://docs.mindnetwork.xyz/mind-lake-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindnetwork.xyz/mind-lake-sdk/glossary.md).

# Glossary

## Encryption & Permission

Contrary to conventional centralized databases that utilize role-based access control, Mind Lake does not directly manage user access control. Instead, permission management is accomplished through client-side encryption. Users with the capability to decrypt the data possess the necessary permissions while everyone else, including Mind Lake itself, is unable to access the encrypted information. All unencrypted data within Mind Lake is accessible to any user.

When a user in Mind Lake wishes to share encrypted data with another user, they must grant decryption permissions to the recipient. With these permissions, the recipient can then decrypt the shared data using a specific key associated with their account.

{% hint style="warning" %}
If you choose not to encrypt the data while inserting to Mind Lake, it will be accessible to any user.
{% endhint %}

## Secure Key Storage

<figure><img src="/files/8vVwYTU31cr9QqU0yhxj" alt=""><figcaption><p>Diagram of Key Storage Process</p></figcaption></figure>


---

# 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.mindnetwork.xyz/mind-lake-sdk/glossary.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.