> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/help/security-and-privacy.md).

# Data security and privacy

Data security and privacy at equipme: hosting, encryption, tenant separation, GDPR and retention.

Security is a central part of how equipme is built and operated.

| Topic                   | Implementation                                                                                                                                                             |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Hosting**             | In data centers in the **EU** with an ISO 27001 certified cloud provider                                                                                                   |
| **Encryption**          | Data is encrypted at rest (AES-256) and in transit (TLS)                                                                                                                   |
| **Tenant separation**   | Each company's data is strictly separated from that of others                                                                                                              |
| **Data protection**     | GDPR-compliant; only approved subprocessors are used                                                                                                                       |
| **Uploads**             | Uploaded files are scanned for malware                                                                                                                                     |
| **Operations**          | Separate production and development environments, automated tests for each release, regular backups with tested restore, process for security incidents                    |
| **Access to documents** | Files attached to assets can only be retrieved by authorized users of your own company; there are no public links                                                          |
| **Retention**           | After the contract ends, the data is deleted after four weeks unless legal obligations prevent this                                                                        |
| **Single sign-on**      | equipme receives only basic identity data when you sign in with Microsoft (see [Integrations and SSO](/dokumentation/settings/integrations-and-sso.md#single-sign-on-sso)) |

**Your responsibility:** You are responsible for the accuracy of your company's data and control who may see what via [roles and rights](/dokumentation/settings/roles-and-permissions.md). Protect [API keys](/dokumentation/settings/integrations-and-sso.md#api-key) like passwords.

You can obtain documents such as the **technical and organizational measures (TOMs)**, as well as submit requests for information or deletion, via [support](/dokumentation/help/support.md).


---

# 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://hub.equipme.io/dokumentation/help/security-and-privacy.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.