Security
Nutrient DWS Processor API is designed to keep your data safe. We do this by following security best practices and not storing more data than is absolutely required. This guide is also intended to support enterprise security, audit, SOC 2, and compliance reviews for teams evaluating how uploaded document data is handled.
If you need to return from this trust review to product or implementation context, continue to getting started for API key setup and a first request, the REST API reference for endpoint details, the Processor API overview, Processor API pricing for credits and commercial review, or the privacy guide for the adjacent data-handling view.
More specifically, we implement the following to keep your data safe:
- No input files are persistently stored on our infrastructure. As soon as a build request finishes, any files submitted by you are cleaned up as soon as possible. The same goes for the resulting PDF, which is deleted as soon as you download it. In addition, no metadata from your input files — beyond the MIME type and page count — is stored.
- All communication between your application and Nutrient needs to use HTTPS to ensure your data is encrypted when it’s sent to us. Additionally, all data we do collect (your account data, performance-related metrics of requests, history of purchases) is stored in an encrypted database to further reduce the risk of any data leaks. For more details on the data we do collect, read our privacy policy.
- All payments are handled by Paddle(opens in a new tab), which is responsible for payment processing and collection of data related to payment processing. Nutrient DWS Processor API never has direct access to any of your payment data.