This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/dws-data-extraction/security.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Security

Security

Markdown version of this page, suitable for AI agents and automation

Nutrient DWS Data Extraction API is built with enterprise security requirements in mind.

  • Data storage and retention — For plans where data retention isn’t enabled, uploaded files aren’t written to persistent storage and are discarded after processing, and extracted content is returned in the response and isn’t retained. For plans where data retention is enabled, processing runs (inputs and outputs) are stored so you can view and manage them, and we also retain a copy to improve and develop our services, including to train our models, as described on our privacy page.
  • Encryption in transit — All API communication uses HTTPS with TLS encryption. Unencrypted HTTP requests are rejected.
  • Secure payments — Billing is handled through Paddle, a PCI-compliant payment processor.

For more information, see the Nutrient security overview (including SOC 2 Type 2 compliance) and the DWS Processor security page, which covers the shared DWS infrastructure security practices.

Also refer to the getting started guide, API overview, Data Extraction API overview, and pricing and privacy pages.