> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/geodin-desktop/es/administracion/data-privacy-and-ownership.md).

# Privacidad y propiedad de datos

## Privacidad y propiedad de los datos

GeoDin no accede a los datos de los clientes; la propiedad de los datos y la privacidad son principios fundamentales.

El cliente controla dónde se almacenan los datos (localmente, en un servidor local o en la nube) y quién tiene acceso.

Los datos introducidos en GeoDin no son visibles para la empresa matriz ni para otros clientes; la plataforma funciona de forma independiente.

GeoDin no anonimiza ni vende datos de los clientes.

Los acuerdos de NDA están disponibles para los clientes que necesitan compartir datos confidenciales del proyecto durante la configuración o el desarrollo de la API; se proporcionan plantillas de NDA estándar, o los clientes pueden usar las suyas propias.

Los clientes pueden ejecutar GeoDin en un entorno corporativo restringido sin acceso a Internet: la telemetría en tiempo de ejecución o la transferencia de archivos desde el personal de GeoDin a la red del cliente quedan bloqueadas en esas configuraciones.


---

# 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://docs.geodin.com/geodin-desktop/es/administracion/data-privacy-and-ownership.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.
