Skip to content
HodeiShield®

What protects your data, and what we do not promise.

Your DPO and your auditor will ask where everything sits and what is certified. This page answers with the full nuance, including the US provider that is in the request path.

  • Certified to ENS (Medium), no. 34/5704/26/09103, OCA Instituto de Certificación, and to ISO/IEC 27001 · Hodeitek S.L.; the scope includes the HodeiShield SaaS service.
  • Platform security is aligned with OWASP ASVS, without certification.
Security sheet
Hosting
OVH, Gravelines (France, EU)
In the path
Cloudflare (US): DNS, CDN and TLS
Passwords
Stored with an algorithm designed to resist brute-force attacks
Multi-factor
One-time codes, passkeys and SSO; your organisation can enforce it
Secrets
Credentials and secrets stored encrypted
Isolation
Each customer sees only its own data; the database itself enforces it
Audit
Immutable audit log
Reference
Aligned with OWASP ASVS (not certified)
Technical detail
  • Passwords: Argon2id hash.
  • Multi-factor: TOTP, passkeys and SSO.
  • Secrets: AES-256-GCM encryption.
  • Isolation: forced row-level security (RLS with FORCE) in PostgreSQL.

Platform facts, with no uptime figures and no badges.

Where your data lives and who answers for it

Infrastructure and data are hosted in the EU. Cloudflare, a US company, is in the path of every request. Both are true at once.

Path of a request

  1. Your organisation

    Browser, CLI or endpoint agent

    Where the request starts

  2. Cloudflare

    DNS, CDN and TLS

    US company

  3. OVH

    Managed application hosting, database and storage

    Gravelines, France (EU)

OVH hosts the application, the database and the storage. Cloudflare handles DNS, CDN and TLS, so traffic to the platform goes through its network.

What is in the EU

The application, the database and the object storage, on OVH Gravelines. The copilot's AI is provided by Mistral AI; we do not state its processing region.

Docs · Subprocessors (opens in a new tab)

What we cannot say

We do not say that no data touches US infrastructure, or that the platform is free of US providers: Cloudflare is in the path. If that matters to your risk analysis, ask us before the demo.

How the platform is protected

Controls the console implements today, explained by what they guarantee. The exact technical names are in each «Technical detail». The reference framework is OWASP ASVS: the platform is aligned with it, not certified.

Credentials and access

Who gets in, and with what assurance.

  • Passwords are stored with an algorithm designed to resist brute-force attacks.
  • Multi-factor sign-in with one-time codes, passkeys and single sign-on (SSO).
  • Multi-factor is optional by default, and an administrator can enforce it through organisation policy.

Scope: Enforcing it is your administrator's decision: it does not come imposed.

Technical detail
  • Passwords: Argon2id hash.
  • Multi-factor: TOTP, passkeys and SSO.

Secrets and credentials stored encrypted

Integration credentials and multi-factor secrets are stored encrypted.

  • Webhook secrets are shown only once, when you create them.
Technical detail
  • Encryption: AES-256-GCM.

Isolation between organisations

Each customer sees only its own data: the database itself enforces the isolation, not just the application.

  • API, CLI and MCP tokens cover a single organisation: the one you choose when you grant access.
Technical detail
  • Every query goes through the tenant context.
  • PostgreSQL applies forced row-level security (RLS with FORCE).

Traceability

An immutable audit log of platform activity, and a record of ACT actions saying who did what.

  • The action ledger only ever adds entries, each one is linked to the previous one and they are signed in batches: anyone can check it with the public key.

Scope: Post-quantum signatures (ML-DSA-65) protect attestations and the action ledger. They do not encrypt live traffic.

Technical detail
  • An append-only action ledger, hash-chained and batch-signed with ML-DSA-65, verifiable with the public key.
  • ML-DSA-65 (FIPS 204) is a post-quantum signature.

What happens to your data when you use HodeiAI

The copilot sends content to an AI provider. These are the exact limits of that processing.

What is pseudonymised

Before sending, HodeiShield replaces the personal data it recognises with placeholders.

  • Emails, phone numbers, national IDs, IBANs and the names of your organisation's users and vendor contacts.
  • The table that maps placeholder to value exists only in memory for the duration of the request.

Scope: Names of people who are neither users nor vendor contacts of your organisation are not recognised and are sent as written. The content itself (a vendor's name, for example) can still describe your business. This applies to HodeiAI and the virtual CISO. The risk analysis of supplier scans does not pseudonymise: it sends the supplier's domain and the findings. That call is only made if HodeiAI is switched on for your organisation.

How long it is kept and who controls it

Conversations are kept for 90 days at most and then deleted automatically.

  • An administrator can switch HodeiAI off; while it is off, no calls to Mistral AI are made for that organisation.
  • It never acts without your explicit confirmation.

Scope: It queries your organisation's live data through tools; it is not a RAG system.

Certifications: ENS and ISO/IEC 27001, with HodeiShield in scope

We say it plainly so nobody has to guess in the audit.

Hodeitek S.L., the company

What we do not claim

  • Neither certifying your compliance nor CPSTICHodeiShield measures your posture, it does not certify your compliance, and it is not listed in the CPSTIC catalogue, which is a different thing. Its security is aligned with OWASP ASVS, without certification.

ECSO “Cybersecurity Made in Europe” label

Hodeitek holds the label, which expresses a self-declared European origin. It is not equivalent to a certification. Hodeitek also appears in the INCIBE catalogue, which is a listing and not an accreditation.

What is not guaranteed

What someone might take for granted and should not.

  1. That no data goes through the US

    Cloudflare, a US company, handles DNS, CDN and TLS in the request path.

  2. That we certify your compliance

    Hodeitek S.L.'s ISO/IEC 27001 and ENS Medium certifications include HodeiShield in their scope, but HodeiShield does not certify your organisation's compliance. Alignment with OWASP ASVS is not a certification.

  3. That multi-factor is switched on

    It is optional by default. Your organisation's policy turns it on or enforces it.

  4. That an attestation proves compliance

    It proves the integrity, origin and time of what was signed. It does not prove it is true, and there is no public transparency log. Signing keys are kept as platform secrets, not in a hardware security module (HSM).

  5. That HodeiAI never sees personal data

    It pseudonymises what it recognises, and what it does not recognise is sent as written.

  6. Availability figures

    We publish no SLA and no availability metrics on this site.

Responsible disclosure

If you think you have found a vulnerability, write to us before making it public.

security@hodeitek.com

This is Hodeitek's channel for security issues. We do not offer encrypted email.

  1. Report it privately: through GitHub private vulnerability reporting on the public repository of the product concerned (hodeishield-cli or hodeishield-attest-verifier), or by email to security@hodeitek.com. The website, the console and the agent have no public repository, so for them use email.
  2. Include the affected URL, tenant or product and version, the steps to reproduce it, the impact you see and a way to reach you. Never include a real API key or token.
  3. We acknowledge receipt, keep you informed during the analysis and agree the publication date with you.

In scope

  • hodeishield.com and www.hodeishield.com.
  • app.hodeishield.com, only if you take part in the beta and inside your own tenant or workspace.
  • The HodeiShield agent. It has no public repository: report by email.
  • The command-line tool (hodeishield-cli), in its public repository.
  • The attestation verifier (hodeishield-attest-verifier), in its public repository.

Out of scope

  • Denial of service and load testing.
  • Social engineering and physical attacks.
  • Third-party services (Cloudflare, Turnstile, analytics tags).
  • Automated scanner output without demonstrated impact.
  • Missing headers without a possible exploit.
  • Form spam.

Rules

  • Use only your own accounts.
  • Do not access, modify or keep other people's data.
  • If you see exposed data, stop at the first instance and tell us.
  • Do not degrade the service or harm its users.
  • We will not take legal action over good-faith research that follows this policy.

Response times and fix targets

Acknowledgement and first assessment in business days; every other period in calendar days. Fix targets are for shipping a fixed release, counted from the first assessment. These are the times we work to, not an SLA.

Acknowledgement
3 business days
First assessment
10 business days
Status updates
At least every 14 days
Fix target, critical
7 days
Fix target, high
30 days
Fix target, medium
90 days
Fix target, low
The next release
Coordinated disclosure
90 days from your report; we may publish earlier if the vulnerability is being actively exploited

We do not pay bounties. With your permission, we credit you publicly.

Trust: where each document lives

An index of what you can ask for or check before you sign. Each link goes to the text in force, not to a summary.

Certifications

Hodeitek S.L. is certified to ISO/IEC 27001 and to the ENS, Medium category (certificate no. 34/5704/26/09103), with the HodeiShield SaaS service in scope. What we do not certify is in the same section.

Subprocessors

The published lists are those of the two notices above, and each describes the scope of its own document. The subprocessor annex for beta participants is under review and will be published together with the data processing agreement (DPA).

Trust Center

HodeiShield has no public trust portal of its own. Trust Center is a console feature that lets each customer publish its own, and it is managed from the console once signed in.

DPO and audit questions

The ones that come up most, with the answer that survives a review.

Does data leave the EU?

The application, the database and the storage are on OVH Gravelines (France). Cloudflare, a US company, handles DNS, CDN and TLS in the request path, so we cannot promise that no data touches US infrastructure.

Does HodeiShield hold ISO 27001 or ENS certification?

Yes. Hodeitek S.L. holds ISO/IEC 27001 and ENS Medium category certifications (ENS certificate no. 34/5704/26/09103, issued by OCA Instituto de Certificación), whose scope includes the HodeiShield SaaS service. That does not certify your organisation's compliance, and the CPSTIC catalogue is a different thing that we do not claim.

What does “aligned with OWASP ASVS” mean?

That the platform's security controls were designed with ASVS as the reference. It is not a certification and no third party issues it.

Does HodeiAI send personal data to a third party?

It sends content to Mistral AI. Before that it pseudonymises the personal data it recognises (emails, phone numbers, IDs, IBANs and the names of your users and contacts), but not what it does not recognise. The risk analysis of supplier scans does not pseudonymise: it sends the supplier's domain and the findings. An administrator can switch it off.

How do I report a vulnerability?

Write to security@hodeitek.com with the affected URL or tenant, the steps to reproduce it, the impact and a way to reach you. Scope, rules and indicative timelines are in the responsible disclosure section of this page.

Go over these points with your DPO

If your risk analysis needs more detail, we cover it in the demo with whoever you choose.

A working conversation, no commitment.