This website is designed to comply with the following national and international legislation with regards to data protection and user privacy:
This site’s compliance with the above legislation, all of which are stringent in nature, means that this site is likely compliant with the data protection and user privacy legislation set out by many other countries and territories as well. If you are unsure about whether this site is compliant with your own country of residences’ specific data protection and user privacy legislation you should contact our data protection officer (details of whom can be found in section 8.0) for clarification.
This website collects and uses personal information for the following reasons:
Site visitation tracking
Like most websites, this site uses Google Analytics (GA) to track user interaction. I use this data to determine the number of people using my site, to better understand how they find and use my web pages and to see their journey through the website.
Although GA records data such as your geographical location, device, internet browser and operating system, none of this information personally identifies you to us. GA also records your computer’s IP address which could be used to personally identify you but Google do not grant me access to this. I consider Google to be a third party data processor (see section 5.0 below).
GA makes use of cookies, details of which can be found on Google’s developer guides. FYI my website uses the gtag.js implementation of GA.
Disabling cookies on your internet browser will stop GA from tracking any part of your visit to pages within this website.
In addition to Google Analytics, this website may collect* information (held in the public domain) attributed to the IP address of the computer or device that is being used to access it. The information is supplied to me from Whoisvisiting.com. Whoisvisiting.com is a service offered by Whoisdata Limited. The Whoisvisiting system does not use your IP address to identify you, the individual, in any way. No cookies are used by the Whoisvisiting system.
* The Whoisvisiting system will only lookup information when a static IP address is being used. Differences between a static and dynamic IP address. More information about how Whoisvisiting uses IP addresses.
Should you choose to submit a form on my website, such as a contact us form, the data you’ve submitted, including your name, telephone number and email address where applicable will be collated into an email and sent to me over the Simple Mail Transfer Protocol (SMTP). In addition a record of your submission will be stored on my website’s database, which is only accessible by authorised members of the site owners’ team and is maintained by my 3rd party processor Webflow. For more information about Webflow please visit their privacy policy here.
This website is hosted by Webflow, one of my third party data processors. They in turn use both Amazon Cloudfront and the Fastly Content Delivery Network to distribute copies of the website around the world. The reason for the distributed nature is to ensure speed and reliability of the website globally.
Full details of Webflow’s hosting can be found here.
All traffic (transferral of files) between this website and your browser is encrypted and delivered over HTTPS.
I use a number of third parties to process personal data on my behalf. These third parties have been carefully chosen and all of them comply with the legislation set out in section 2.0.
I will report any unlawful data breach of this website’s database or the database(s) of any of my third party data processors to any and all relevant persons and authorities within 72 hours of the breach if it is apparent that personal data stored in an identifiable manner has been stolen.
The data controller of this website is: Elliot Hyams
Mr Elliot Hyams
This privacy policy may change from time to time in line with legislation or industry developments. I will not explicitly inform our clients or website users of these changes. Instead, I recommend that you check this page occasionally for any policy changes. Specific policy changes and updates are mentioned in the changelog below.