> For the complete documentation index, see [llms.txt](https://support.airspacelink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.airspacelink.com/configuration-guides/sub-processors-subsidiaries-and-support.md).

# Sub-Processors, Subsidiaries & Support

At Airspace Link, we rely on carefully selected sub‑processors to support the delivery, security, and performance of our platform. Each sub‑processor undergoes a thorough privacy and security review, and we maintain contractual safeguards to ensure they process personal data in alignment with our regulatory and contractual obligations. Airspace Link continuously monitors its sub‑processors to ensure they uphold the same high standards of confidentiality, integrity, and data protection that our customers expect from us.

AirHub**®** Portal Sub-processors

<table data-full-width="true"><thead><tr><th>Name</th><th>Applicable Services</th><th>Type of Service</th><th>Data Shared</th><th>Sub-processor hosting regions</th><th data-hidden data-type="content-ref">Additional Information</th></tr></thead><tbody><tr><td>Chekr</td><td>AirHub<strong>®</strong> Portal</td><td>Background checks for staff</td><td>Information to process background checks</td><td>US</td><td><a href="https://checkr.com/legal/privacy-policy">https://checkr.com/legal/privacy-policy</a></td></tr><tr><td>Azure</td><td>AirHub<strong>®</strong> Portal</td><td>Platform hosting</td><td>Platform for the product</td><td>US</td><td><a href="https://www.microsoft.com/en-us/privacy/privacystatement">https://www.microsoft.com/en-us/privacy/privacystatement</a></td></tr><tr><td>Auth0</td><td>AirHub<strong>®</strong> Portal</td><td>Authentication Identity platform</td><td>Users credentials and authentication</td><td>US</td><td><a href="https://www.okta.com/legal/privacy-policy/">https://www.okta.com/legal/privacy-policy/</a></td></tr><tr><td>Maxio</td><td>AirHub<strong>®</strong> Portal</td><td>E-Commerce, financial and accounting</td><td>Product purchasing transactions</td><td>US</td><td><a href="https://www.maxio.com/privacy-policy">https://www.maxio.com/privacy-policy</a></td></tr><tr><td>M365</td><td>AirHub<strong>®</strong> Portal</td><td>Data hosting; email; productivity tools</td><td>Customer and general business emails</td><td>US</td><td><a href="https://www.microsoft.com/en-us/privacy/privacystatement">https://www.microsoft.com/en-us/privacy/privacystatement</a></td></tr><tr><td>PostHog</td><td>AirHub<strong>®</strong> Portal</td><td>Product analytics intelligence platform</td><td>Tracks user behavior, analyzes product usage</td><td>US</td><td><a href="https://posthog.com/handbook/company/security">https://posthog.com/handbook/company/security</a></td></tr></tbody></table>


---

# 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://support.airspacelink.com/configuration-guides/sub-processors-subsidiaries-and-support.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.