> For the complete documentation index, see [llms.txt](https://docs.autopilotmonitor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autopilotmonitor.com/trust-and-security/data-flows.md). # Data Flows & External Services Where data actually travels when you use Autopilot Monitor — what the service stores, what it only reads from, and which connections exist because you configured them. ## Data Flows and External Services **Last reviewed: 6 September 2026 · Next review: 2 March 2027.** A technical map of every outbound connection Autopilot Monitor makes, grouped by what actually happens to your data. Read the groups carefully — they are not equivalent, and most of them carry no customer data at all. {% hint style="info" %} This page describes the architecture. The **data processing agreement** is the authoritative document for the contractual side — which parties are engaged, on what terms, and how changes are handled. It is available on request; see the [Security & Privacy FAQ](/trust-and-security/security-faq.md#can-i-get-a-data-processing-agreement-dpa--avv). {% endhint %} ### 1. Where your data is stored | Service | Role | Data | Location | | ------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | **Microsoft Azure** | The platform itself — compute, storage, real-time messaging, container hosting, operational telemetry | All customer data: sessions, events, configuration, audit logs, backups, and any hosted diagnostics | **Germany West Central** (portal front-end static assets: West Europe) | That is the whole of it as far as the product is concerned: nothing in the platform is wired to copy telemetry to an analytics platform, a CRM, an error tracker, or an AI provider. Every other connection on this page is a message about the service, public reference data read inbound, a lookup in your own tenant, or a destination you configure. Access by the people operating the service — for support, incident handling, and platform analysis — takes place under the platform roles described in the [Security & Privacy FAQ](/trust-and-security/security-faq.md#identity-and-access) and the terms of the data processing agreement. ### 2. Messages the service sends Used to deliver messages *about* the service. **Neither carries enrollment telemetry.** | Service | When it is used | What it receives | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Mailchimp Transactional (Mandrill)** | Onboarding and offboarding only — the welcome message sent when a tenant is activated, and the farewell message sent after a tenant is offboarded | The recipient administrator's email address and the tenant's domain name. Open and click tracking is disabled | | **Telegram** | Operator alerting, so incidents get noticed and acted on quickly | Platform health signals: event type, severity, a short message, and the tenant ID an event relates to. No device data, no enrollment telemetry, no personal data | Telegram is **operator-only infrastructure**, not a tenant feature — it cannot be configured or used by customers. It is listed here because it exists in the open-source code and you would find it anyway; it is how the people running the service learn that something is wrong. Autopilot Monitor does **not** route notification alerts through an email provider. There is no other mail service in the product. ### 3. Data the service reads in — nothing goes out Public reference data is pulled *from* these sources to enrich your view. **Nothing about your environment is sent to them.** Your software inventory is never uploaded for lookup; matching happens inside the backend against a cached copy of the public data. | Source | Purpose | | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **National Vulnerability Database (NVD)**, NIST | CVE and CPE records for vulnerability correlation. This product uses the NVD API but is not endorsed or certified by the NVD. | | **CISA Known Exploited Vulnerabilities (KEV) Catalog** | Which vulnerabilities are actively exploited in the wild. | | **Microsoft Security Response Center (MSRC)** | Microsoft-specific vulnerability details. | | **Exploit Prediction Scoring System (EPSS)**, FIRST.org | The likelihood that a known vulnerability is exploited in the wild. This lookup is the one that carries a query: the public CVE identifiers held in the shared, tenant-agnostic reference cache — never a device, a tenant, or an inventory. | ### 4. Lookups inside your own tenant The service queries **Microsoft Graph in your tenant**, using the permissions granted at onboarding, to verify that a device reporting telemetry really is a registered Autopilot device of yours, and to resolve friendly names for scripts and applications. This reads your own directory; it discloses nothing to anyone else. See [Optional Graph Permissions](/reference/optional-graph-permissions.md) for what is required and what is optional. ### 5. Destinations you choose These connections exist **only because someone configured them**. They point at systems you nominate, and you can remove them at any time. | Destination | When it applies | What is sent | | ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Your own Azure storage account** | Diagnostics upload with the default `CustomerSas` destination | The diagnostics package — agent logs and state, IME logs, session info, RealmJoin logs when that watcher is enabled, plus the additional log paths your administrators configure. This is the default: the payload never reaches our infrastructure. | | **Microsoft Teams, Slack, Discord, or a generic webhook endpoint** | Notification channels you configure | Alert payloads — session, device, and finding details. Webhook targets pass an SSRF guard before any request is made. | | **Your AI assistant** | If a user connects an AI client through the [MCP integration](/integrations/ai-integration-mcp.md) | Whatever that assistant queries. The platform itself makes no AI calls; this transfer is initiated by your user, to your vendor, under your agreement with them. MCP access is limited to accounts that hold a role in your tenant — people, or a service principal your admin added as a read-only member and consented to in Entra; individual accounts can be blocked, and MCP can be switched off for your whole organization on request. | | **IP geolocation service** (`ipinfo.io`, fallback `ifconfig.co`) | Geolocation, a tenant setting that is **on by default** | The device's outbound connection reaches the service, which returns approximate location. The session stores country, region, city, and approximate coordinates; the outbound IP is stored separately as a diagnostic event. Disable geolocation to stop this entirely — see the [Security & Privacy FAQ](/trust-and-security/security-faq.md#is-the-devices-ip-address-stored). | {% hint style="info" %} To eliminate group 5 entirely: leave diagnostics upload off or on `CustomerSas`, configure no notification channels, connect no AI assistant through MCP, and switch off geolocation. The service is fully functional with all of them disabled — only Geographic Performance goes dark, because it has nothing to plot. {% endhint %} ## Citations * [Security & Privacy FAQ](/trust-and-security/security-faq.md) — data residency, isolation, encryption, retention, and contracting. * [Network Endpoints](/reference/network-endpoints.md) — the outbound hosts to allow on firewalls and proxies. * [Notifications](/integrations/notifications.md) — configuring notification channels. * [Diagnostics & Log Collection](/troubleshooting-and-support/diagnostics-and-log-collection.md) — diagnostics upload modes. --- # 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.autopilotmonitor.com/trust-and-security/data-flows.md?ask=&goal= ``` `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.