This privacy statement tells you what personal information we collect and how it is used when dealing with you particularly with regard to this website.
- We do not store any personal information of yours online.
- We take every precaution to protect your privacy when dealing with you.
- When you contact us via the form on this website, no data from the form is kept or stored online. All data is sent to us by e-mail.
- We never pass any of your personal information to a third party unless you explicitly consent to it in each case.
Cookies are small text files passed to your computer by websites that you visit. They are usually stored by your web-browser software and have an expiry date after which the browser will destroy them. They are widely used in order to make websites work, or work more efficiently, as well as to provide information to website owners.
- We do not store any personal information in cookies for websites visitors
- Users who log into this site are passed a single cookie to enable them to use the administration functions. This contains no tracking information whatsoever.
- We do not pass cookies to any other user of this website, neither do we track your usage or visit to this website.
- A single cookie called DYNSRV is set at the start of your visit. This is set to be destroyed by your browser when you close it. This cookie is set by something called a load balancer which helps keep the site running and cannot be avoided. It is destroyed when your session and contains no personal data whatsoever.
- We do not embed third party content, including advertising, on our websites and certainly nothing that requires cookies.
- This website is in accordance with the EU cookie directive of 2011 and GDPR 2018.
We occasionally link to selected external sites and this statement does not cover those websites. You are advised to refer to their own privacy statements for further details.
If you find anything on this website that you think conflicts with this statement, please let us know and we will do our best to resolve the issue.
Page last updated: 21 February 2019