> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/other-resources/vault-privacy-for-administrators-and-users.md).

# Vault privacy for administrators and users

Vault privacy for administrators and users explains why corporate vaults allow administrative access and how Devolutions Cloud offers full privacy.

The connection and password management solutions provided by Devolutions (Remote Desktop Manager, Devolutions Server, and Devolutions Cloud) offer a robust system that empowers administrators with complete and secure control over user vault management. However, it is natural for some customers to have concerns regarding the potential access to their "private" vaults by a malicious administrator. It is crucial to clarify the intended purpose of these "private" or "user" vaults, as they are primarily designed for personal corporate usage rather than personal private usage.

The distinction lies in the fact that these vaults are created within the context of a corporate environment, where administrators need to ensure continuous access to critical information stored within them. This necessity arises from various scenarios such as managing incidents, addressing employee terminations, and other operational requirements. By maintaining administrative access to these vaults, organizations can effectively safeguard against potential disruptions and ensure the smooth functioning of their operations.

While administrators do possess the ability to access these vaults, it is important to emphasize that this access is granted within the framework of their administrative responsibilities, and they are logged normally for visibility and traceability. Devolutions recognize the importance of privacy and understand that users may require an additional layer of security for their personal information. To address this concern and provide users with absolute privacy, Devolutions offers Devolutions Cloud for free to individual users.

Devolutions Cloud is specifically designed to cater to the individual needs of users who seek heightened privacy and control over their personal data. This solution ensures that personal information remains entirely private, without any administrative access or intervention. Users can securely store and manage their sensitive data within their personal vaults, maintaining complete ownership and exclusive control over their information.

By recommending Devolutions Cloud for users seeking absolute privacy, Devolutions acknowledges the importance of differentiating between the corporate and personal usage of their connection and password management solution. This approach provides a comprehensive suite of options, catering to both the administrative requirements of organizations and the individual privacy needs of users, thereby offering a well-rounded and versatile solution for diverse user scenarios.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/resources/other-resources/vault-privacy-for-administrators-and-users.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
