Legal
Subprocessors
Who takes part in processing the data our customers keep in GMAO CLOUD, for what purpose, where, and under what contract.
Última actualización: November 17, 2026
1. What this page covers
The data a customer enters into GMAO CLOUD is theirs: the customer is the controller and GMAO CLOUD acts as processor. To provide the service we use providers who, depending on the case, may access that data. They are the subprocessors listed here.
The list reflects real data flows, not an inventory of every tool we use as a company. Tools used only for our own corporate activity (for example, our commercial contracts and proposals) are not subprocessors as long as they do not process personal data on a customer’s behalf. If that changed, we would add them here.
2. Providers involved in the service
| Provider | Purpose | Where data is processed | Contract and safeguards |
|---|---|---|---|
| OVHcloud | Production hosting and service infrastructure. | France (EU). | Provider data processing agreement and subprocessor list: ovhcloud.com/es-es/terms-and-conditions/contracts/ |
| Amazon Web Services (AWS) | Storage (S3) of files uploaded by the customer and compressed database backups. | Paris and Madrid (EU). | AWS DPA: aws.amazon.com/compliance/eu-data-protection/ |
| Asana, Inc. | Support, project and incident management, where they contain personal data processed on the customer’s behalf. | United States by default; EU residency only with a plan or arrangement that allows it. | Asana DPA (effective September 1, 2026), covering the EU–US Data Privacy Framework and, where applicable, standard contractual clauses: asana.com/terms/data-processing |
| OpenAI (API) | Customer-support chatbot. It may receive questions typed by the user, which could contain personal data. | As per the provider’s terms; may involve processing outside the European Economic Area. | OpenAI commercial DPA (effective January 1, 2026): openai.com/es-ES/policies/data-processing-addendum/. We use the API with optional call logging disabled; that is not a provider guarantee of zero data retention. |
| Anthropic (API) | First-line (L1) handling of support incidents. It may receive incident messages, which could contain personal data. | As per the provider’s terms; may involve processing outside the European Economic Area. | Anthropic commercial terms and DPA: anthropic.com/legal. The API retains inputs and outputs for up to 30 days, subject to contractual or legal exceptions. |
| Fathom (Fathom Video) | Recording, transcription and summarisation of meetings, only when recording is authorised and the meeting involves data processed on the customer’s behalf. | United States. | Fathom DPA: fathom.video/dpa |
3. Artificial intelligence
AI takes part in two support flows: the chatbot and first-line incident handling. Those two providers may receive the text the user types.
- We do not use customer data to train AI models.
- Automated support channels process what the user types; we do not deliberately enrich it with personal data taken from the customer’s databases.
- We apply data minimisation and tell users that AI tools are involved.
- We do not claim that either service offers zero data retention without specific confirmation of its scope.
- Technical development and diagnostic access to databases is read-only and is forbidden from querying personal data.
The AI features that work with customer data inside the product (GMAO-IA credits) are governed by what is agreed in each contract.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
4. International transfers
Primary data and backup storage is in the European Union (OVHcloud in France and AWS S3 in Paris and Madrid). Storing in the EU does not by itself rule out a provider accessing from outside to give support, and that is assessed separately.
When processing involves transferring data outside the European Economic Area (for example, with Asana, Fathom and the AI providers), it only happens under a valid GDPR Chapter V safeguard: an adequacy decision, such as the EU–US Data Privacy Framework, or standard contractual clauses, with whatever supplementary measures are needed.
5. Security measures
Per-customer database segregation, encrypted communications (HTTPS/TLS and SSH), encrypted backups, access controls, and internal continuity and recovery procedures.
6. Changes to the list
We keep this list up to date. When we add or replace a subprocessor that affects a customer’s service, we notify them at least 15 days in advance, except in justified urgent cases, so they can object on data protection grounds.
Each subprocessor is bound by contract to substantially equivalent data protection obligations, and GMAO CLOUD remains liable to the customer for their performance.
7. Contact
To request our data processing agreement, ask about this list, or object to a change, write to hola@gmao.cloud. Incidents and support are handled through the usual service channels.