# Private Spaces

#### 1. Control of Private Spaces.

Some accounts, such as paid accounts, may have private spaces, which allow the User to control access to Content.

#### 2. Confidentiality of Private Spaces.

GitBook considers the contents of private spaces to be confidential to you. GitBook will protect the contents of private spaces from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.

#### 3. Access.

GitBook employees may only access the content of your private spaces in the following situations:

* With your consent and knowledge, for support reasons. If GitBook accesses a private spaces for support reasons, we will only do so with the owner’s consent and knowledge.
* When access is required for security reasons.

You may choose to enable additional access to your private spaces. For example:

* You may enable various GitBook services or features that require additional rights to Your Content in private spaces. These rights may vary depending on the service or feature, but GitBook will continue to treat your private space Content as confidential. If those services or features require rights in addition to those we need to provide the GitBook Service, we will provide an explanation of those rights.
* You may also grant a third-party application authorization to use, access, and disclose the contents of your private spaces. Your use of third-party applications is at your sole risk; GitBook is not liable for disclosures to third parties that you authorize to access a private space.

#### 4. Exclusions.

If we have reason to believe the contents of a private space are in violation of the law or of our Terms of Service, we have the right to access, review, and remove them. Additionally, we may be[ compelled by law](https://policies.gitbook.com/privacy-and-security/statement#how-we-respond-to-compelled-disclosure) to disclose the contents of your private spaces.


---

# 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://gitbook.com/docs/policies/policies/trademark-policy-1.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.