> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/trust-and-security/overview.md).

# Security and data protection

Myrspoven publishes its security, privacy, and compliance posture at [trust.myrspoven.com](https://trust.myrspoven.com/). The portal is the single source of truth for commitments, certifications, and documentation available on request. This page points to it.

**Procurement and legal:** the trust portal holds the formal artifacts — ISO/IEC 27001:2022 certificate and scope, subprocessor list, security overview, privacy statement, questionnaire responses.\
**Technical operations and integrators:** building connectivity is covered under [BMS integrations](https://docs.myrspoven.com/connect-your-building/bms-integrations.md#security), signing in under [myPortal](https://docs.myrspoven.com/other-interfaces/myportal.md), and incidents under [How to raise a support case](https://docs.myrspoven.com/get-help/troubleshooting.md#how-to-raise-a-support-case).

## Where to look

For formal artifacts, start at [**trust.myrspoven.com**](https://trust.myrspoven.com/). For the latest version of each document, see the portal.

The trust portal covers:

* **Certifications.** Myrspoven is certified to ISO/IEC 27001:2022. Certificate and scope are on the portal.
* **Security overview.** Protection of customer data and building connections — hosting region, encryption, access control, incident handling.
* **Privacy and data handling.** Personal data processing, retention, data subject rights, and the current product privacy statement.
* **Subprocessors.** Third parties involved in delivering the service.
* **Authentication and access controls.** Controls enforced by Myrspoven and those configurable by the customer.
* **Vulnerability disclosure.** Reporting process and response expectations.
* **Questionnaire responses.** Standard responses to common procurement questionnaires, available on request.


---

# 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.myrspoven.com/trust-and-security/overview.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.
