Along with our business and internal computer systems, 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 9.0) for clarification.
This website collects and uses personal information for the following reasons:
Like most websites, this site uses Google Analytics (GA) to track user interaction. We use this data to determine the number of people using our site, to better understand how they find and use our 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 us access to this. We consider Google to be a third party data processor (see section 6.0 below).
GA makes use of cookies, details of which can be found on Google’s developer guides. FYI our 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 us 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 our 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 us over the Simple Mail Transfer Protocol (SMTP). In addition a record of your submission will be stored on our website’s database, which is only accessible by authorised members of the MVEST team and is maintained by our 3rd party processor Webflow. For more information about Webflow please visit their privacy policy here.
In various places of this website there is the option to click to email or click to call. In both of these cases upon clicking a link our website will not record or store any of the information you subsequently submit. These links will prompt your device to launch either the default call or email app in use.
Emails sent and received by us use Simple Mail Transfer Protocol (SMTP), this service is provided to us by one of our third party processors Microsoft, on their Office 365 platform, for more information about Microsoft as a data processor see section 6.0.
Our SMTP servers are protected by TLS (sometimes known as SSL) meaning that the email content is encrypted using SHA-2, 256-bit cryptography before being sent across the internet. The email content is then decrypted by our local computers and devices.
As detailed in section 3.3, if you submit a form on the website, some personal information will be stored within this website’s database. This is the only occasions where personal data will be stored on this website. This data is currently stored in an identifiable fashion; a limitation of the content management system that this website is built on (Webflow). However, whilst identifiable, the information is only accessible to those with the necessary system privileges.
In the near future we aim to change the storage of this data to a pseudonymous fashion meaning that the data would require additional processing using a separately stored ‘key’ before it could be used to identify an individual.
Pseudonymisation is a recent requirement of the GDPR which many web application developers are currently working to fully implement. We are committed to keeping it as a high priority and will implement it on this website as soon as we are able to.
This website is hosted by Webflow, one of our 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.
We use a number of third parties to process personal data on our behalf. These third parties have been carefully chosen and all of them comply with the legislation set out in section 2.0.
We will report any unlawful data breach of this website’s database or the database(s) of any of our 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: MVEST Ltd, a UK Private limited Company with company number: 115460213
Whose registered office is:
1 Boulter Lane, Southwick, Hampshire, PO17 6HH
Mr Steve Munday
Director
Email: steve@mvest.co.uk
This privacy policy may change from time to time in line with legislation or industry developments. We will not explicitly inform our clients or website users of these changes. Instead, we recommend that you check this page occasionally for any policy changes. Specific policy changes and updates are mentioned in the changelog below.