Avius software is developed by Avius Ltd in the UK, no part of it is outsourced or subcontracted.
The Avius servers have been built and are maintained by Avius Ltd.
The Avius software have been developed by Avius Ltd in the UK and uses standard industry software such as Qlik, Microsoft, Mongo etc.
Avius uses some commodity third party components to provide support for hardware scanners, data parsing, data storage etc.
Written comments in Avius solutions responses may be processed by WebPurify and Google Translation APIs depending on customer preference to aid in filtering out profanity and translating comments into different languages. The comments are not sent with any additional survey response data and Avius Ltd does not provide a way to identify the customer or site.
Avius survey devices encrypts each response it stores in a way that means even the device cannot decrypt it, it can only be decrypted after being sent to our systems. Therefore, if the device is physically stolen or compromised none of the response data can be read. The encryption we use meets or exceeds the current NIST recommendations.
Avius survey devices are locked down to deter theft and prevent unauthorised modification.
Devices that are reported stolen can often be remotely locked and tracked.
Data transferred to and from the Avius servers is via HTTPS and is TLS/SSL encrypted. Passwords are passed through a strong one-way hashing algorithm and the original password information is not stored.
The data is stored on dedicated servers in a well-established tier 2, UK based data centre, where bio-metric credentials are required to gain access to the building.
Avius survey devices connect to the internet using either Wi-Fi or Cellular connectivity. The internet connection is used to connect to our servers which are hosted in a data centre in the United Kingdom and to the device manufacturer’s notification, application and operating system update services.
Each Avius device once setup can operate without internet connectivity by storing completed survey responses locally on the device. This is limited only by the storage space available on the device.
Whilst operating offline, the Avius device will not receive updates to the survey, theme, Avius application or device operating system.
Once an Avius device is set-up and running, the most frequent traffic will be survey responses. These will occur whenever a customer completes a survey on the device.
Health checks run every 30 minutes (this is customizable) for the device to report its status to Avius support. Occasionally the Avius application will be updated to add new functionality or resolve issues.
When requested by the customer, their survey or theme will be updated and these changes will be pushed to the Avius device.
Avius devices may also receive operating system updates from the device manufacturer designed to maintain the performance and security of the underlying platform. The application may leverage new functionality provided by these updates from time-to-time, this will require the customer to run the device manufacturer’s update.
|Data||Frequency||Average file size|
|Survey result||On completion of a survey||2.11KB|
|Survey update||When the device is initially set-up and when changes are requested by the customer||416KB|
|Theme update||When the device is initially set-up and when changes are requested by the customer||5MB|
|Avius Surveys application health||30 by default (adjustable from 10 minutes - 4 hours)||2-3KB (approx. 1MB per week)|
|Meraki ( mobile device management)||On demand as required to manage the iPad environment||Approx. 2MB per week|
|Avius Surveys application update||When Avius release a new version of the application - typically every 2 months||10MB|
|Device manufacturer OS/firmware update||When Apple, Google or Microsoft release an update||5MB - 1GB|
Avius data is stored on resilient storage and replicated between multiple servers in the data centre. A nightly backup of the data is stored in the data centre and an encrypted weekly backup is stored offsite.