Trust Center

Security and compliance of our voice agents

Your calls contain sensitive data. Here is how YeldaAI hosts, protects and processes it, and the documents your security and compliance teams can request from us.

Hosting
In France, with Clever Cloud
GDPR
Article 28 processor, dedicated DPO
Certifications
ISO 27001, HDS and SecNumCloud hosting provider
Encryption
TLS-encrypted communications
Model training
YeldaAI does not train language models

Chaque jour, leurs équipes font confiance à YeldaAI

01

Data and hosting

Hosting location
Platform, databases, logs and backups hosted in France with Clever Cloud, with no transfer outside the EU. Third-party AI components are called through endpoints located in the EEA whenever the provider allows it.
Recording retention
Set with each customer according to their use case and industry framework.
Transcript retention
By default 6 months after the last conversation, 3 months for technical logs. Durations can be adjusted by contract.
Use for training
YeldaAI does not train its own language models. Generative answers rely on the document base approved by the customer (RAG).
Deletion on request
YeldaAI assists the customer, as data controller, with any request for access, rectification or erasure.
02

Security

Encryption in transit and at rest
Communications secured with HTTPS / TLS, encryption at rest through the hosting provider's mechanisms.
Access and authentication
Least privilege, separate environments, MFA for privileged access, periodic access reviews.
Logging and monitoring
Logging of access and administrative actions, continuous infrastructure monitoring.
Penetration testing
Independent re-audit conducted in 2026 for a banking customer: rated "Satisfactory", all findings fixed.
Business continuity (BCP / DRP)
Automated backups, architecture redundant across several zones, disaster recovery plan tested in 2026.
Disponibilité
99,99 %
Support
Équipe YeldaAI joignable du lundi au vendredi, de 9 h à 19 h, avec une réponse sous 1 h ouvrée.
03

Compliance

GDPR and DPO
YeldaAI acts as a processor under Article 28. DPO: Annabelle Nicolas, dpo@yelda.ai.
Data processing agreement (DPA)
Signed with each customer, with prior notice of any change of subprocessor.
AI Act
Limited-risk systems: callers are informed from the greeting that they are talking to an AI (Article 50). No prohibited or high-risk use.
Certifications
Infrastructure with Clever Cloud, ISO 27001 and HDS certified and SecNumCloud qualified. Cyber-risk insurance held by YeldaAI.
Industry requirements
Support for customers subject to DORA, NIS 2 and the French ACPR and AMF regulators: register of critical suppliers, customer audits.
04

Subprocessors

The providers that process data on behalf of YeldaAI, their role and their location.

Provider

Role

Location

Data processed

List of subprocessors available on request.
05

Documents on request

Our security documents are shared with companies evaluating YeldaAI. Let us know which ones you need and we will get back to you shortly.

Data processing agreement (DPA)
Information security policy and related policies (access, incidents, continuity, vulnerabilities)
Summary certificate of the 2026 security re-audit
Register of critical suppliers

Responsible AI use charter

AI Act summary sheet

Cyber-risk insurance certificate

Answers to your security and compliance questionnaires

Company registration extract (Kbis)

Request the documents

Thank you, your request has been received. Our team will get back to you shortly.
Something went wrong. Please try again in a few moments.
06

Frequently asked questions

A security or compliance question?
dpo@yelda.ai

Where is my call data hosted?

In France, with Clever Cloud (ISO 27001, HDS, SecNumCloud). For the most sensitive projects, we can deploy an entirely French stack, with a self-hosted Mistral model: the data never leaves the country.

Are conversations used to train AI models?

YeldaAI does not train its own language models. Answers rely on your document base (RAG), and third-party models are used under a contractual framework with a DPA.

How long are recordings kept?

By default, 6 months after the last conversation for transcripts and 3 months for technical logs. These durations can be adapted in your contract.

How is the caller informed that they are talking to an AI?

From the greeting, the assistant introduces itself as a virtual assistant, in line with Article 50 of the AI Act. The caller can ask for an agent at any time.

How does the voice agent access my information system?

Through API connectors defined with you, with permissions limited to what the use case strictly requires.

What happens in the event of a security incident?

Our Data Breach Team (DPO, technical management, executive management) qualifies the incident. You are notified without delay, and the supervisory authority within 72 hours when the GDPR requires it.

The voice AI guide for banking

Use cases, compliance and lessons learned: everything you need to know to deploy a voice agent in your institution.

Resources

Our latest articles

All articles