Security Policy

Last updated October 26, 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.

Trust Center

Our Trust Center is the reference for our security and compliance program: security controls, list of sub-processors, policies, and the status of our SOC 2 audit. Reports can be requested from the Trust Center.

Infrastructure & Hosting

Carbone Cloud is hosted in France, by OVHcloud and Scaleway. The full list of providers is published in the Trust Center.

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. We also apply the recommendations of the Guide d'hygiène informatique ("IT hygiene guide") published by ANSSI, the French National Cybersecurity Agency.

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.

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.

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:

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.