---
source: https://carbone.io/company/security-policy.html
title: "Carbone Security Policy"
description: "Security Policy | Carbone Open Source Report and Document Generator"
generated_at: "2026-07-10"
---

# Security Policy

Last updated July 9, 2026

CarboneIO SAS takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations.

While the discovery of new vulnerabilities is rare, we also recommend always using the latest versions of CarboneJS to ensure your application remains as secure as possible.

## Infrastructure & Hosting

Our Cloud infrastructure is hosted in France by [OVHcloud](https://www.ovhcloud.com/en/compliance/), a cloud provider certified ISO/IEC 27001, 27017 and 27018, and qualified [SecNumCloud](https://www.ovhcloud.com/en/compliance/secnumcloud/) by [ANSSI](https://cyber.gouv.fr) — the French National Cybersecurity Agency — on parts of its offering.

## Secure Development

Security is considered at every stage of our development process rather than treated as an afterthought — from architecture and code review to how we manage and deploy our services. This "privacy and security first" approach guides how we build and maintain Carbone.

## Security Audits

We conduct security audits of our infrastructure and services on an annual basis, to proactively identify and address potential vulnerabilities.

## Data Handling

### On-Premise / Self-Hosted deployments

When Carbone runs on-premise, in your own infrastructure (Docker, Kubernetes, VM, or any cloud environment you control), CarboneIO has **no access whatsoever** to your templates, your data, or your generated documents. Everything stays within your environment, under your control.

### Carbone Cloud

On Carbone Cloud, only your **templates** are stored, so they can be reused across render calls. We do not store or log the data (JSON payload) you submit for rendering, nor the documents generated from it, beyond what is strictly necessary to complete the document generation process and deliver the result back to you.

## Certifications

We have not pursued formal security certifications such as ISO 27001 or SOC 2 for CarboneIO. Given the cost and organizational complexity these represent relative to the size of our team, we have chosen to prioritize concrete security measures over the certification process itself, for now — this is a decision we regularly revisit as we grow.

In the meantime, we apply the security recommendations from [ANSSI](https://cyber.gouv.fr)'s [Guide d'hygiène informatique](https://messervices.cyber.gouv.fr/guides/guide-dhygiene-informatique) ("IT hygiene guide"), a reference set of 42 security best-practice measures for information systems published by the French National Cybersecurity Agency.

## Reporting a Vulnerability

**Please do not report security vulnerabilities through public GitHub issues.**

If you believe you have found a security issue in `Carbonejs`, `Carbone Studio`, `Carbone Render` or anything related to the Carbone ecosystem, please responsibly disclose by contacting us at `support@carbone.io`. Even when you are not 100% certain that it is actually a security issue. Typically, you will receive an answer within a day or even within a few hours. If possible, encrypt your message with our [PGP key](/pgp-key.md).

When a vulnerability is reported, it immediately becomes our top concern, with a full-time contributor dropping everything to work on it. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

-   Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
-   Full paths of source file(s) related to the manifestation of the issue
-   The location of the affected source code (tag/branch/commit or direct URL)
-   Any special configuration required to reproduce the issue
-   Step-by-step instructions to reproduce the issue
-   Proof-of-concept or exploit code (if possible)
-   Impact of the issue, including how an attacker might exploit the issue

Thank you for improving the security of Carbone and its ecosystem. Your efforts and responsible disclosure are greatly appreciated and will be acknowledged.

The vulnerability reporting process described above also lives alongside the [Carbone source code](https://github.com/carboneio/carbone/blob/master/SECURITY.md).

## Related topics

- [Terms of service](/company/terms-of-service.md)
- [Privacy Policy](/company/privacy-policy.md)
- [Legal notice](/company/legal-notices.md)
- [Cookie policy](/company/cookies-policy.md)