Privacy Policy

Version Identifier: 1.0.0

Version Effective Date: 20/02/2020


This privacy notice sets out how any personal data we collect from you, or that you provide to us, will be processed by us. Please read the following carefully to understand our views and practices regarding your sensitive information and how we will deal with it. For the purposes of the Data Protection Act 2018 ('the DPA') and the EU General Data Protection Regulation (‘the GDPR’), sensitive information includes what is defined as your 'personal data'.

By visiting (the 'Website') you accept and consent to the practices described in this Privacy Policy.

In this privacy policy, we seek to abide by the letter and spirit of the guidelines laid out by the UK Information Commissioner’s Office. The guidelines can be found at the following link

Who we are

We are 'Robert Atherton Software Engineering'. A company registered in the United Kingdom. If you have any concerns about the way we use your information or any questions about this Privacy Notice, please let us know. We can be contacted via email at

What we do with your information - 'Visting the website'

All requests to the Website are handled by our SSL endpoint. Requests sent in the plain are redirected to take place over SSL. In other words, if you were to try to visit our Website via an address begining with http:// it would be automatically redirected to the same address, but over https. Only the current best practice ciphers are allowed. This means that a connection to our website with an old browser that does not support these best practices will be rejected. In these circumstances it is likely that the browser will show an error message that it has been unable to make a secure connection. It is suggested to take futher external advice about upgrading to a more modern browser if you still wish to visit the Website.

When you visit the Website (a 'request') technical data is recorded to facilitate the visit. This includes the Internet Protocol (IP) address of your machine and other information such as the browser and type of machine that is making the request. This information is obtained from the request sent from your web browser. No attempts are made to obtain any further information from your machine outside of the HTTP Protocol. This data is necessary for the ongoing operation and maintainance of the system, to enable us to understand how our Website is being used and for later fault finding in the event of an error or other investigation.

In summary, only the information that is required to enable the process of 'visiting a website' is recorded. This data is aggregated and anonymised and we have no system in place to identify individual users from this information. We do not track users across multiple visits to the Website and we do not make use of cookies. Cookies are small text files that are used to store small amounts of data about a user, such as language settings, between visits to a website. Every visit to our Website is treated as a new request from a new user.

We do not provide any of our logs to any third parties. If you are concerned about giving away this type of technical data then it is suggested to seek out advice and technology in this domain. Such a discussion is outside the scope of this policy.

What we do to ensure the security of your personal information

We treat our information and electronic security with the utmost priority. As such our approach to information security is continually reviewed and evolved to keep ahead of current and emerging risks.

We have adopted industry best practices from both technological and business process perspectives in order to make the security of your data a key part of the way we do business.

We have policies and practices in place that not only ensure our compliance under the DPA but also the GDPR.

Version Control

This policy is subject to change. When considering our usage of your data the version of the policy active at the time of the usage should be used. We retain all versions of this policy along with a list of all changes that are made to it. In order to verify the authenticity of a given copy of this policy a sha hash is generated at the time of creation and stored separately. Subsequent checks can then be made to compare this hash against the copy of the file in question.

Back to top