# Introduction

## Meet global standards for privacy and security. <a href="#meet-global-standards-for-privacy-and-security" id="meet-global-standards-for-privacy-and-security"></a>

The Open Constitution AI network is a collection of digital public goods and services. These services are deployed on our servers and housed on computing infrastructure controlled by a service provider under a shared responsibility model.

‘'Foundation’' engages market vendors to maintain computing infrastructure for the network.

The organizational tenants and any other type of E-tenant provisions these servers for their projects at different TRL levels and generic needs.

In many cases, the e-tenants may also contribute computing resources to their project through the shared responsibility model. They do so using a federated computing infrastructure model.

(1) By linking their cloud console account to the Foundation’s organisational account and accessing the network’s license manager, deployment charts, security best practices, and standards.

(2) Accounting for the contribution through the network’s intra-community token.

Therefore, the Foundation is responsible for setting up best practices for security and data privacy standards for cloud computing resources, such as network interfaces to these resources.

&#x20;

All member data and content are stored in the **different data residency zones** and privacy controls depend on:

> geo-location and tax residency of any natural person(E resident) or
>
> tax residency of any organisation (E tenant).

Project tenancies that any licensed E tenant, provisioned on third-party cloud computing servers and procured by the principal data processor entities on behalf of the Open Constitution AI network.

[Read more about the AI network’s program-specific data residency zones here.](https://openconstitution.atlassian.net/wiki/spaces/AINetworkCC/pages/222527569)

Our CDN may cache some data (HTML pages and assets) in other geographies.

Access to private content through our CDN is always validated through our application servers using a complex permissions system and protocols driven in accordance with the Open Constitution Charters, adopted by the network at any given time.

#### Third-party resources, Compliance Reports and literature review: <a href="#third-party-resources-compliance-reports-and-literature-review" id="third-party-resources-compliance-reports-and-literature-review"></a>

[AWS Cloud](https://aws.amazon.com/compliance/resources/)

[Google Cloud Compliance Resources](https://cloud.google.com/compliance?hl=en)

[Google Workspace](https://workspace.google.com/learn-more/security/security-whitepaper/page-5.html)

[Atlassian Cloud](https://www.atlassian.com/trust/data-protection)

[Cloudflare](https://www.cloudflare.com/en-gb/trust-hub/compliance-resources/)

Azure Cloud


---

# Agent Instructions: 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:

```
GET https://docs.openconstitution.us/compliance-docs/global-data-policies/service-provider-resources/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.