# HyperPrivacy Mode

ExaVault used to offer a site-wide configuration option called HyperPrivacy Mode that, once set, cannot be changed without completely rebuilding your entire site.

This capability requires an Enterprise license and is no longer offered for new accounts.

**This legacy documentation is only applicable to the few customers who still use HyperPrivacy Mode.**

## Differences Between HyperPrivacy Mode and Normal ExaVault

In a normal ExaVault installation, there is one root file system, and Users are provisioned access to that file system using Permissions. Permissions can be granted on any folder.

In HyperPrivacy Mode, each user gets their own file system, completely to themselves. The only way for one user to access the files of another user is for that user to share those files or folders explicitly.

This creates an extremely private environment for each user. Files owned by a user cannot be seen by site administrators.

## History of HyperPrivacy Mode

This setting was formerly called "NextGen", "DatabaseFs", and "Contemporary platform" at various times and in various places.

For a period of time, HyperPrivacy Mode was enabled by default when installing ExaVault.

Due to challenges associated with administering sites which use HyperPrivacy Mode, we no longer recommend that customers enable HyperPrivacy Mode.

## Determining HyperPrivacy Mode Status

If you have a left menu for both "Files" and "Shares", your ExaVault site has HyperPrivacy Mode enabled.


---

# Agent Instructions: 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://docs.exavault.com/hyperprivacy-mode.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.