Konverso | Trust Center
Konverso AI Trust Center
Secure, Compliant, and AI-Powered with Enterprise-Grade Data Security
See More

Compliance

Our security and governance framework is designed to meet industry standards and applicable regulations across the regions where we operate.

SOC 2 Type 2

Konverso is SOC 2 Type 2 certified, demonstrating our commitment to the highest security standards. Our measures are continuously monitored to ensure ongoing protection, with an annual independent audit conducted by Prescient Security.

Penetration Testing

Konverso performs annual penetration testing as part of its SOC 2 compliance program. These tests are conducted by an independent third party, Cacilian, to identify potential vulnerabilities and validate the effectiveness of our products.

GDPR

Konverso complies with the GDPR and ensures strong data protection through secure, EU-based data hosting, strict access controls, and full respect of data subject rights.

Health Data Hosting

Konverso is able to host customers’ health data on Microsoft Azure infrastructure certified for Health Data Hosting (HDS) in France, ensuring that sensitive data is securely managed in compliance with applicable security and regulatory requirements for privacy practices.

Status Page

Konverso provides a public Status Page with real-time information on service availability, incidents, and planned maintenance.
Access the Status Page

Customers can subscribe to receive email notifications for all updates or only selected components.

A detailed Status Page Usage Guide can be downloaded from the Resources section.

Monitoring

Continuously monitored by Secureframe

Subprocessors

We carefully select each technology partner and subprocessor to ensure they meet our security, privacy, and compliance standards.

Atlassian

Offers project management and collaboration tools, such as Jira and Confluence, used by Konverso’s teams.

Data location: EU (DE/IE)

AWS

Provides AWS Bedrock LLM endpoint.

Data location: EU (IE/FR)

Datadog

Ensures observability of Konverso’s application and infrastructure performance.

Data location: EU (DE)

Google Cloud Platform

Access to Google Workspace API.

Data location: EU (BE/NL)

HubSpot

Manages customer relationship management (CRM) and marketing automation for Konverso.

Data location: EU (DE)

Microsoft Azure

Serves as a primary cloud platform for hosting Konverso’s applications and storing data, while also providing identity and access management through Microsoft Entra ID.

Data location: EU (FR)

Mistral

Provides AI and NLP services to Konverso.

Data location: EU(FR)

OpenAI

Supplies advanced AI and language processing models integrated into Konverso’s solutions.

Data location: EU/US

Orca Security

Offers cloud security and risk management services to protect Konverso’s environments.

Data location: EU
View all

Resources

SOC 2 Type II 2025 Report

Pentest 2025 Report

Information Security Policy

Data Privacy Policy

Data Protection Policy

Securing credentials

Privacy Policy

Terms & Conditions

Microsoft Azure Health Data Hosting (HDS) Compliance

Public IPs

View all

FAQs

These questions reflect the most common topics raised during customer security and vendor risk assessments. They provide an overview of Konverso’s security posture, infrastructure, data protection practices, and compliance commitments.

Konverso is hosted on Microsoft Azure cloud infrastructure, primarily located in France (Azure France Central region). This ensures that customer data remains within the European Union and benefits from Azure’s high security and compliance standards. Azure infrastructure used by Konverso is certified under internationally recognized frameworks such as ISO 27001 and HDS (Health Data Hosting). Backup data is geographically replicated within France (e.g., France Central and France South) to ensure resilience and business continuity.
Konverso implements a defense-in-depth security approach to protect customer data. All data transmitted between users, systems, and APIs is encrypted using TLS 1.2 or higher, while data stored in databases and storage systems is encrypted using AES-256. Access to the platform is controlled through strong authentication mechanisms, including SSO and multi-factor authentication (MFA). Strict access controls, environment segregation, monitoring, and centralized logging further ensure the confidentiality, integrity, and availability of customer data.
Yes. Konverso undergoes an annual SOC 2 Type II audit conducted by an independent third-party auditor (Prescient Security). This certification evaluates the effectiveness of Konverso’s security, availability, and confidentiality controls over time. The audit verifies that internal processes, infrastructure protections, and operational practices meet recognized industry standards.
Yes. Konverso conducts annual penetration tests performed by an independent cybersecurity firm (Cacilian). These tests evaluate the platform’s resistance to real-world attack scenarios and identify potential vulnerabilities. Any findings are documented, prioritized, and remediated as part of Konverso’s continuous security improvement process.
Konverso maintains clear disaster recovery objectives to ensure service continuity. The Recovery Time Objective (RTO) is 2 hours, meaning that services can be restored within two hours in the event of a major incident. The Recovery Point Objective (RPO) is 24 hours, defining the maximum acceptable data loss window. These objectives are supported by automated backups, geographic replication across Azure regions in France, and regularly tested disaster recovery procedures.
Yes. Konverso fully complies with the General Data Protection Regulation (GDPR). Konverso includes GDPR-compliant Data Processing Agreements (DPAs) in its contracts. The platform processes only the data necessary to deliver the service and implements strict security controls to protect personal data. Data subject rights such as access, rectification, and deletion are supported through formal procedures managed by Konverso’s Data Protection Officer (DPO), Amédée Potier.
No. Customer data is strictly isolated within each client environment and is not reused across customers. Konverso does not use client data to train shared AI models. When AI models are fine-tuned for a specific customer, the training data remains confined to that customer’s dedicated environment. Additional anonymization or pseudonymization options can also be implemented upon request.
Konverso retains system and application logs for up to one year (12 months). Logs are centralized, encrypted, and accessible only to authorized security personnel in read-only mode. This retention period supports security monitoring, incident investigation, and compliance requirements while ensuring traceability of system activities.
Customers can contact Konverso through several support channels, including a secure ticketing portal and dedicated support email. Standard support hours are Monday to Friday from 9:00 AM to 6:00 PM (CET). In addition, the platform is continuously monitored 24/7/365, and on-call technical teams are available to respond to critical incidents affecting service availability or security.

Monitoring

Security

Encryption at Rest
Service data is encrypted-at-rest.
Access Control
Personnel are required to use strong, complex passwords and a second form of authentication to access sensitive systems, networks, and information.
Network & Infrastructure Security
A Network Security Policy identifies the requirements for protecting information and systems within and across networks.
Vulnerability & Penetration Testing
A 3rd party is engaged to conduct a network and application penetration test of the production environment at least annually. Critical and high-risk findings are tracked through resolution.
Encryption in Transit
Service data transmitted over the internet is encrypted-in-transit.

Resilience

Business Continuity & Disaster Recovery
Business Continuity and Disaster Recovery Policy governs required processes for restoring the service or supporting infrastructure after suffering a disaster or disruption.
Incident Response
Identified incidents are documented, tracked, and analyzed according to the Incident Response Plan.
Testing & Improvements
The Incident Response Plan is periodically tested via tabletop exercises or equivalents. When necessary, Management makes changes to the Incident Response Plan based on the test results.

Privacy & Data Protection

Data Lifecycle
A Data Retention and Disposal Policy specifies how customer data is to be retained and disposed of based on compliance requirements and contractual obligations.
Data Classification
A Data Classification Policy details the security and handling protocols for sensitive data.
Vendor Oversight
Vendor SOC 2 reports (or equivalent) are collected and reviewed on at least an annual basis.

People & Governance

Risk Management
A Risk Assessment and Treatment Policy governs the process for conducting risk assessments to account for threats, vulnerabilities, likelihood, and impact with respect to assets, team members, customers, vendors, suppliers, and partners. Risk tolerance and strategies are also defined in the policy.
Code of Conduct & Ethics
A Code of Conduct outlines ethical expectations, behavior standards, and ramifications of noncompliance.

Transparency

System Description
Descriptions of the company's services and systems are available to both internal personnel and external users.
Terms of Service
Terms of Service or the equivalent are published or shared to external users.
Reporting Channels
A confidential reporting channel is made available to internal personnel and external parties to report security and other identified concerns.
Security Commitments
Security commitments and expectations are communicated to both internal personnel and external users via the company's website.

Operations & Reliability

Monitoring & Alerts
System tools monitors for uptime and availability based on predetermined criteria.
High Availability
The system is configured for high availability to support continuous availability, when applicable.
Backup Validation
Backed-up data is restored to a non-production environment at least annually to validate the integrity of backups.
Segregation of Environments
Development, staging, and production environments are segregated.