Using any SaaS system raises questions about data security, confidentiality or data protection regulations. We want our customers using DeltaJSON SaaS to feel secure in the knowledge we take our responsibilities seriously. The security of your data is important to us, so we’ve answered the most common key questions below.
(To be clear, when we talk about data we mean the data you process in DeltaJSON and fragments of that data in the results.)
YES. Your data is encrypted when transferred to DeltaJSON and using our REST API requires additional authorisation headers. We allow HTTPS secure connections only.
NO. Calls to DeltaJSON where results are returned after processing (synchronous calls) are not stored.
YES, but you have complete control. When DeltaJSON is used to process many datasets (asynchronous), we encrypt the stored results. This result data is deleted after 1hr, or can be deleted immediately by sending a command. We never copy or process the results data elsewhere, i.e. backups.
We want our customers to receive an exceptional experience from our systems, so we are always monitoring performance of DeltaJSON. This means we log information to improve performance and help us resolve bugs customers might experience. Transparency is the cornerstone of trust between our customers and DeltaXML, so here is the system information we log:
|Date time||When a DeltaJSON function is used, this helps us plan resources for peak traffic.|
|Processing time||How to plan and deploy our resources to maintain performance.|
|Data size||How to plan and deploy our resources to maintain performance.|
|Function||Functions (Compare / Graft / Patch) tell us which are the most popular and useful for our customers.|
|IP Address||Useful for security when combating attacks on our system or misuse.|
|Source||How customers use DeltaJSON, i.e. from the web GUI, or from within code, or perhaps from a popular application like Postman.|
If you have any questions or concerns, please get in touch.