SUBPROCESSORS — ENGINORA
Version 1.0
Last updated: September 1, 2026
This page presents the main subprocessors that may process personal data on behalf of Clients in connection with the provision of Enginora.
It supplements the Enginora Data Processing Agreement (DPA).
Google Cloud / Firebase
Purpose
Technical infrastructure and authentication for Enginora.
Google Cloud is used in particular for:
- hosting the application;
- hosting the PostgreSQL database;
- associated technical services.
Firebase is used in particular for user authentication.
Main location currently used
- Application: London, United Kingdom;
- Main database: Belgium.
Other technical processing may be carried out by Google depending on the services used and their applicable terms.
Data protection
Google provides Google Cloud customers with a contractual framework relating to the processing and security of personal data, including mechanisms intended to govern international transfers where necessary.
OVHcloud
Purpose
Hosting of the n8n instance operated by I AND YOO to orchestrate certain Enginora workflows.
The n8n instance is self-hosted by I AND YOO: n8n therefore does not act as an n8n Cloud provider in this architecture.
Main location
France.
Data protection
OVHcloud provides contractual provisions and a Data Processing Agreement for the processing of data carried out on behalf of its customers.
OpenAI
Purpose
Artificial intelligence processing used in certain stages of Enginora workflows, including analysis, structuring and content generation.
Depending on the requested operation, the data transmitted may include:
- project topic and context;
- editorial instructions;
- SEO or semantic information;
- intermediate content;
- elements required to generate a Draft.
Location
Processing may be carried out on the infrastructure used by OpenAI in accordance with the terms applicable to its professional services.
Data protection
OpenAI provides a Data Processing Addendum for its professional services and API.
OpenAI also states that data used with its professional offerings and API is not used by default to train its models, unless a different configuration or consent applicable to the customer is in place.
Anthropic
Purpose
Artificial intelligence processing used in particular in certain stages of Draft generation.
The data transmitted may include in particular:
- editorial context;
- brief;
- SEO information;
- instructions;
- intermediate content required for generation.
Location
Anthropic states that it may process professional customer data in several regions and may store certain data in the United States by default, unless a specific agreement or configuration applies.
Data protection
Anthropic states that its Data Processing Addendum, including the applicable Standard Contractual Clauses, is incorporated into its commercial terms.
Perplexity
Purpose
Research and response generation used in certain Enginora workflows through the Perplexity/Sonar API.
The data transmitted may include queries derived from:
- the topic;
- the brief;
- the project context;
- research needs associated with the content.
Location
Perplexity states that the compute for its API is hosted in North America.
Data protection
Perplexity’s DPA is incorporated by reference into its API terms.
Perplexity currently states that it applies a Zero Data Retention policy to content submitted to its Chat Completions API: prompts and responses are not retained or used to train its models; only certain technical and billing metadata is retained.
CHANGES TO SUBPROCESSORS
I AND YOO may change its subprocessors when necessary for the operation, security or evolution of Enginora.
In accordance with the Enginora DPA, Clients are informed of material additions or replacements of subprocessors so that they may, where applicable, raise a reasonably substantiated objection relating to data protection.
This page constitutes the public reference list of Enginora’s main subprocessors.
OTHER SERVICE PROVIDERS
Certain service providers may also be used by I AND YOO for processing for which I AND YOO acts directly as controller, including:
- Stripe, for payments, subscriptions and billing;
- Tawk.to, for certain support functions.
These processing activities are described in the Enginora Privacy Policy and are not included in this list where they do not process Client Data on behalf of the Client.
CONTACT
For any question concerning subprocessors or the processing of personal data:
End of the Enginora Subprocessor List — Version 1.0