Security

DWS Viewer API is designed to keep your data safe. We follow security best practices, and we don't store more data than is absolutely required.

Infrastructure

DWS Viewer API is deployed on AWS. When creating your application, you have a choice to host it in one of these regions:

• eu-central-1 (Frankfurt)
• us-west-2 (Oregon)

Data Encryption

All data is encrypted, both in transit and at rest:

• We store data in encrypted databases and encrypted S3 buckets.
• All communication between your application and DWS Viewer API needs to use HTTPS to ensure your data is encrypted when it’s sent to us.

Network

There are three ways DWS Viewer API can be accessed:

1. 1
   Your backend uses the API. This API is protected by an API key.
2. 2
   You backend uses the API to generate session tokens, which ensure that the holder of such a token is allowed to access a given document. It then passes them to your client apps using Nutrient for Web or DWS Viewer API's programmatic API. Your apps then pass it to DWS Viewer API to prove they have access to the document in question.
3. 3
   We provide a dashboard, which gives access to all documents uploaded to DWS Viewer API. The dashboard is protected with a username and password.