Skip to content

Subprocessors

A subprocessor is a third party that HodeiShield relies on to provide part of the service, and that may in doing so process data belonging to your tenant. This page lists the subprocessors that process data on HodeiShield's behalf and how they do it. It will be updated whenever one is added or removed.

OVHcloud (hosting, database and AI inference)

Entity OVH SAS (France)
Service Hosting of the platform: application servers, database, session cache and document storage. It also runs the automation engine (n8n), which operates on HodeiShield's own infrastructure on OVHcloud and is not an external provider
Purpose Providing the service, storing your tenant's data and running AI inference (OVHcloud AI Endpoints, detailed below)
Data residency European Union: Gravelines region (France) for the application servers and document storage. The managed database is an OVHcloud service on a private network, with its node in Gravelines (measured on 3 November 2026 through the OVHcloud API); its managed backups are replicated in Gravelines and Strasbourg (France) with 2-day retention, and Hodeitek's own backup copy is in OVHcloud Object Storage in Gravelines
Data it receives All platform data. The service's technical logs may be sent to OVHcloud's logging service in the same region

AI inference: OVHcloud AI Endpoints

OVHcloud AI Endpoints is a service of the same entity and contract as the hosting above (its terms are Appendix 10 of OVHcloud's Public Cloud Special Conditions), not a separate subprocessor.

Entity OVH SAS (France), the same entity as the hosting above
Service OVHcloud AI Endpoints (OpenAI-compatible API). Through n8n, in five flows with a model: HodeiAI, virtual CISO, policy drafting (the coverage analysis does not reach the model), risk analysis of supplier scans and drafting of answers to inbound questionnaires. The classification of regulatory updates does not go through n8n: the Platform's application does it by calling OVHcloud AI Endpoints directly, and only with public texts (see below). Before sending to n8n the last HodeiAI user message, or a question from a visitor to the public Trust Center, the application passes it through a safety filter: it sends it directly to OVHcloud AI Endpoints, without going through n8n, together with the name of the supplier being consulted when there is one. The model is Qwen3Guard-Gen-8B, which OVHcloud offers in a beta phase, so OVHcloud's service level does not apply to it. According to OVHcloud, the service is hosted in Europe. The moderation applies only to the user's input. This filter is the same provider as in row 7 and not an additional one.
Purpose Generating HodeiAI and Virtual CISO responses, drafting policy text, classifying public regulatory updates, and the risk analysis produced by vendor domain scans
Data residency Gravelines (France), per OVHcloud's documentation (page last updated 3 February 2026). The contract text does not state a region
Retention at OVHcloud Under OVHcloud's AI Endpoints conditions (version of 26 August 2026) the service includes no backup or storage, even temporary (the Batch API is excepted and HodeiShield does not use it); OVHcloud has no knowledge of inputs and outputs and takes no backups of them. OVHcloud states that it keeps only the usage data needed for billing
Training Under the same conditions OVHcloud does not reuse inputs and outputs in any way. OVHcloud's website adds that data is never used to train its models (a marketing statement, not contract text)

AI inference: what purpose it covers

OVHcloud AI Endpoints processes requests for five product functions:

  • HodeiAI — the conversational security assistant, including the summaries and reports it generates and the optional rewording of answers on a public Trust Center (this rewording sends the published Trust Center content and, for a visitor who has been granted access, the restricted posture score and per-framework scores).
  • Virtual CISO — answers and recommendations about your compliance posture.
  • Policy drafting — draft compliance policy text and policy coverage analysis.
  • Regulatory updates — classification of regulatory content, always sourced from public sources (official gazettes and regulatory press feeds); never from your tenant's data.
  • Vendor risk analysis — part of the analysis produced by a domain scan.

AI inference: what data categories it can see

Depending on the function, the text you send or the context of the screen you are on, the last few messages of the conversation, and tool results carrying your tenant's vendor risk or compliance data.

AI inference: pseudonymisation, function by function

Pseudonymisation is not the same for the five functions. This is what HodeiShield does today:

Function What leaves for OVHcloud AI Endpoints
HodeiAI (chat, summaries, reports, Trust Center answers) Pseudonymised. Email addresses, phone numbers, Spanish national ID numbers (DNI/NIE), IBANs and the names of people belonging to your own tenant (users and vendor contacts) are replaced with placeholders, in the question and in the results of the tools the assistant uses. Tenant and user identifier fields are removed, and the known tenant, organisation and user identifiers are replaced.
Virtual CISO Pseudonymised, in the same way as HodeiAI.
Policy drafting and policy coverage analysis Pseudonymised, in the same way.
Regulatory updates Nothing from your tenant. The workflow reads public feeds and sends their items; no pseudonymisation is applied because no tenant data is involved.
Prior safety filter (HodeiAI and public Trust Center) Prior safety filter (direct call from the application): only the last HodeiAI user message or the public Trust Center visitor's question, pseudonymised with the same pseudonymiser as the main path, which replaces emails, phone numbers, DNI/NIE, IBAN, the names in the tenant's dictionary and the organisation's own names and internal identifiers, and does not replace the names of people outside that dictionary or postal addresses, which may go out as they are; together with the name of the supplier being consulted, if there is one. Earlier messages and tool results are not sent. OVHcloud returns a verdict; Hodeitek does not store or log the text, only the verdict.
Vendor domain scan analysis Not pseudonymised. The vendor's domain, its type, the risk score, the findings and the Shodan data go in clear, with only an irreversible automatic redaction of email addresses, phone numbers with a + prefix, IBANs and DNI/NIE (replaced by [EMAIL], [PHONE], [IBAN], [ID], not restorable). Have I Been Pwned contributes only the number of breaches. The prompt carries no user or tenant identifier. This analysis only runs if the tenant's HodeiAI switch is on.

For the pseudonymised functions, the response OVHcloud AI Endpoints returns is restored inside HodeiShield before it reaches you; the table that maps each placeholder back to its value exists only in HodeiShield's memory for the duration of the request and is never stored. Names of people who are not users or vendor contacts of your tenant are not recognised and are sent as written, as are postal addresses, identifiers of other countries and free-form identifiers. Bear in mind that the content itself (for example a vendor's name) can still describe your business.

AI inference: retention

At OVHcloud, prompts and outputs are not stored, backed up or reused under the AI Endpoints conditions (see the table above). Inside HodeiShield, conversations, messages, tool calls, and their associated AI runs are kept for a maximum of 90 days, after which they are automatically deleted.

AI inference: customer control

A tenant administrator can turn HodeiAI off at any time, from Settings › HodeiAI. While it is off, HodeiShield makes no calls to OVHcloud AI Endpoints for that tenant; functions that have a deterministic alternative engine keep working through it. The classification of regulatory updates does not depend on that switch because it carries no tenant data.

On the free trial, HodeiAI is included but stays off until an administrator explicitly turns it on.

Cloudflare (CDN and firewall)

Entity Cloudflare, Inc. (United States)
Service DNS, content delivery network, web application firewall (WAF) and TLS encryption of all traffic; bot verification on the public Trust Center
Purpose Protecting and accelerating access to the console
Data residency To be confirmed: Cloudflare handles requests in transit and the console does not set the region. The transfer relies on the EU-U.S. Data Privacy Framework and, should it cease to apply, on the European Commission's standard contractual clauses
Data it receives Requests in transit, with the IP address and technical browser data

Resend (email)

Entity Plus Five Five, Inc. (operating as Resend), 2261 Market Street #5039, San Francisco, CA 94114 (United States), per the provider's DPA and terms of service
Service Sending the platform's emails: invitations, alerts, notices and notifications
Purpose Delivering transactional email
Data residency Sending region: eu-west-1 (Ireland), measured on 14 October 2026 through the Resend API for HodeiShield's sending domain. The provider's DPA states that its primary processing operations take place in the United States and that it may transfer personal data outside the EEA; the infrastructure behind Resend is under verification
Data it receives The recipient's email address and name and the content of the message

Microsoft 365 (support and security mailboxes)

Entity Microsoft Corporation (United States). In the EEA, Microsoft Ireland Operations Limited (Dublin, Ireland) is its data protection representative, per Microsoft's Products and Services DPA
Service Microsoft 365 (Exchange Online): the support and security mailboxes (info@ and security@)
Purpose Handling support enquiries and security communications by email; those messages can contain your organisation's data if you include it
Data residency European Union (EU Data Boundary), still to be verified on Hodeitek's tenant: the tenant's region is not recorded in this repository
Transfer basis The European Commission's standard contractual clauses built into Microsoft's DPA and Microsoft's participation in the EU-U.S. Data Privacy Framework, for access from outside the EEA
Data it receives The messages you send to those mailboxes: your email address and name, the content and any attachments

Sentry (error monitoring)

Listed for transparency: Hodeitek processes the error reports as controller and Sentry is its provider for that processing, not a sub-processor of the Customer.

Sentry receives the error reports, performance traces and technical logs of the console and of its API services (api.hodeishield.com and the MCP server), and the error reports of the endpoint agent. It is a processor acting for Hodeitek. For these error reports Hodeitek is the controller (legitimate interest, art. 6.1.f GDPR). The console is not designed to send your tenant's business data to it.

Entity Functional Software, Inc. (Sentry)
Service Sentry (error monitoring)
Purpose Diagnosing technical errors of the console and of the endpoint agent
Data residency Console: European Union (EU) data region, per the configured ingest host (*.ingest.de.sentry.io). Endpoint agent: the same EU (Frankfurt) Sentry organisation, measured on the published agent releases 2.12.2, 2.12.3 and 2.15.0 (the DSN is baked in when each agent version is built). Only the agent service binary reports
Role Sentry is a processor for Hodeitek. Hodeitek is the controller of the error reports of the console and of the endpoint agent
Retention 90 days
Data it receives Error reports, traces and technical logs from the console, configured not to attach user information, cookies, request headers or request bodies, and with e-mail addresses, IP addresses, tokens and query-string values in free text, URLs and logs rewritten before they leave. Logs are filtered through an allow-list of technical fields (they carry the identifier of the affected tenant and the country of the connection). Session replays are only recorded when an error occurs and mask all text and inputs; pages that carry an access token are excluded. These controls reduce what is sent but do not guarantee that no personal data can ever appear in an error report. Sentry also sees the address of the connection that sends the reports. The endpoint agent's reports are on by default in the beta, carry the error message and stack trace, the agent version, the operating system and architecture, with no user information attached, and can be switched off on each machine (see the privacy notice)
Not sent by design Content of your workspace: vendors, evidence, risks or conversations. The free text of an error message is cleaned of known patterns (e-mail addresses, tokens, IP addresses), which cannot catch every case

Public security sources and logo service

To analyse the exposure of your vendors, HodeiShield's automation engine queries these external services. They receive identifiers of the thing being analysed, not user accounts. For none of them is the processing region set by HodeiShield, and it is not yet recorded in the provider's documentation we hold: residency under verification in every case.

Service Used for What it receives
Shodan (api.shodan.io) Vendor domain scan (also the public domain scan) The vendor's domain and the IP addresses it resolves to
Have I Been Pwned (haveibeenpwned.com) Vendor domain scan (also the public domain scan) The vendor's domain
OSV.dev (api.osv.dev) Matching the components of uploaded SBOMs against known vulnerabilities The package identifier (purl) of each component: name, version and ecosystem, without the tenant that uploaded it
NVD (services.nvd.nist.gov) Looking up CVEs for software assets The CPE name of the asset's software product (vendor, product, version), without the tenant
FIRST EPSS (api.first.org) Getting the exploitation probability of each CVE The CVE identifiers
Logo.dev (img.logo.dev) Fetching the logo of a vendor The vendor's domain

A vendor's domain can still describe your business.

Aiven (sub-processor of OVHcloud: managed PostgreSQL)

Hodeitek does not contract Aiven directly: it is a sub-processor of OVHcloud, which uses it for the managed PostgreSQL service.

Entity Aiven Oy, Helsinki, 2795743-5
Service The managed PostgreSQL service that OVHcloud offers is administered by Aiven. This is how it appears in production: its administrative role and an internal database belong to Aiven
Purpose Running the database that stores your tenant's data
Data residency European Union: node in Gravelines (France); managed backups in Gravelines and Strasbourg (France) with 2-day retention (measured on 3 November 2026 through the OVHcloud API). The database is reached over OVHcloud's private network
Data it receives The data stored in the database. The roles HodeiShield uses to read and write it are its own; Aiven's access to the stored content is under verification

UptimeRobot (public status page)

Entity UptimeRobot s. r. o., Bratislava (Slovakia)
Service The public status page (status.hodeishield.com), its incident and maintenance notices, and the availability checks of Hodeitek's public addresses
Purpose Publishing service status and sending notices to those who subscribe
Data residency European Union as the main location, with secondary processing in the United States under the European Commission's standard contractual clauses (Decision (EU) 2021/914), per its data processing agreement (version 2.2 of 28 August 2026). The agreement does not invoke the Data Privacy Framework
Data it receives The IP address and usage logs of visitors to the status page and, if you subscribe to its notices, your email address, which UptimeRobot stores and uses to send them; Hodeitek cannot see it. It receives no data from the console

Stripe and Holded (only if you buy online)

These two providers do not process your tenant's data and are not sub-processors of the Customer: they are listed for transparency. They are processors for Hodeitek, which handles billing as controller, for charging and invoicing the subscription when you buy AI Governance or Essentials online (see Buy online).

Stripe Holded
Purpose Card payment and subscription management Issuing the legal invoice, registered in TicketBAI
Data it receives Legal name, tax ID, billing email, registered address and payment data (you enter the card on Stripe; HodeiShield never sees it) Legal name, tax ID, billing email, registered address and the invoice lines
Data it does not receive Nothing from your workspace: vendors, evidence, risks, conversations or users The same

Scope of this page

This page covers hosting and database, CDN and firewall, platform email, support email, AI inference (part of OVHcloud), the public status page (UptimeRobot), the public security sources and the logo service. Error monitoring (Sentry) and the payment and invoicing providers (Stripe and Holded) are listed above for transparency: they are Hodeitek's providers for processing it does as controller, not sub-processors of the Customer. The same applies to the cloud and identity providers to which the Customer connects an evidence connector (Microsoft and, when available, Google and Amazon Web Services): they are the Customer's own providers, and the Customer grants the read authorisation at them (clause 3.6 of the data processing agreement); Hodeitek reads only what that authorisation allows. Where a statement reads "under verification" or "to be confirmed", HodeiShield does not set it and cannot yet back it with a document from the provider; it will be updated when it can.