> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/help-center-es/general-faq/nuestro-almacenamiento-y-subencargados-del-tratamiento.md).

# Nuestro almacenamiento y subencargados del tratamiento

Consulta nuestros subencargados y proveedores de almacenamiento

Actualmente almacenamos datos utilizando nuestros subencargados del tratamiento Cloudflare R2 (para unidades Active) y Wasabi (para unidades Vault). Ambos son proveedores de almacenamiento verificados, compatibles con S3, que siguen los protocolos de seguridad más estrictos (incluidas las políticas de cifrado AES-256 en reposo y SOC 2 Tipo II).

Tus datos se transportan y protegen con HTTPS y nadie del equipo de Shade ve nunca tus datos. Para obtener más información sobre subencargados adicionales, consulta nuestro [centro de confianza](https://trust.shade.inc).

Para impulsar las funciones de IA, parte de tu contenido también es procesado por los siguientes subencargados:

* **Google Cloud (Gemini en Vertex AI)** - Metadatos, etiquetado y análisis de IA de imágenes, video y documentos
* **AssemblyAI** - Transcripción de audio y video

Tus datos tampoco se usan nunca para entrenar ninguna de nuestras IA (consulta nuestra [Política de datos](https://shade.inc/data-usage-policy-and-ai)).

Por último, metadatos como etiquetas, EXIF y y embeddings de IA se almacenan en nuestra base de datos Postgres alojada por Google Cloud.


---

# 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://academy.shade.inc/help-center/help-center-es/general-faq/nuestro-almacenamiento-y-subencargados-del-tratamiento.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.