> 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).

# Overview

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 and outlines what the rest of the chapter covers.

**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:** this chapter covers the operational details that come up during onboarding and day-to-day use — building connectivity, myPortal access, incident handling.

## Where to look

For formal artifacts, start at [**trust.myrspoven.com**](https://trust.myrspoven.com/). The portal is kept current; this documentation site is not.

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.

## What's in this chapter

The pages in this chapter complement the trust portal with operational, customer-facing detail:

* Building connectivity from a security standpoint — outbound-only connections, scoped setpoint writes, no inbound exposure of the Building Management System (BMS).
* myPortal user access — per-user accounts, MFA, role-based permissions.
* Handling of suspected security issues.

The trust portal owns the formal posture. The pages below cover practical operation.

## Reporting a security concern

Suspected security issues affecting customer data or buildings are reported to the Myrspoven representative immediately and flagged as urgent. Vulnerability reports follow the disclosure process linked on [trust.myrspoven.com](https://trust.myrspoven.com/).


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.myrspoven.com/trust-and-security/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.