These answers focus on the technical aspects of Jetty. For further answers, please contact our team directly.

A: Well beyond the typical standards for username & password, the data is stored on an encrypted database cluster. It is effectively unavailable from outside Amazon Web Services (AWS), which we are using for the hosting of the Jetty Tools. We have set rules to limit outside access to our 4 IP addresses world wide. As for services we use within AWS, they also require rules to allow access to the data because by default, they are denied access. The web server, on which the code is run, only accepts HTTPS-requests on a specific port. Then it is directed to the API, which is used to serve data to clients. This type of request cannot affect the file system that the code resides on. It is not possible to access the server using SSH or FTP without additional steps being taken to configure the servers by the administrator. When updating the code, it is automatically fetched from a 2-factor authenticated, private Gitrepository on Github over HTTPS. No code can be directly deployed to or edited on the server. The Github repository is only accessible by the development team at Swace Digital. Any updates to the code must be approved by a senior developer before being accepted into the code that is eventually deployed to the server.