Privacy Policy

1.0 Our core beliefs regarding user privacy and data protection

2.0 Relevant legislation

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.

3.0 Personal information that this website collects and why we collect it

This website collects and uses personal information for the following reasons:

3.1 Site visitation tracking

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 analytics.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.

3.2 Our blog

Should you choose to add a comment to any posts that we have published on our blog, the name and email address you enter with your comment will be saved to this website’s database, along with your computer’s IP address and the time and date that you submitted the comment. This information is only used to identify you as a contributor to the comment section of the respective blog post and is not passed on to any of the third party data processors detailed below. Only your name will be shown on the public-facing website although if the supplied email address is linked to a Gravatar account, your Gravatar photo will also be displayed.

Your comment and it’s associated personal data will remain on this site until we see fit to either 1. remove the comment or 2. remove the blog post. Should you wish to have the comment and it’s associated personal data deleted, please email us here using the email address that you commented with.

If you are under 16 years of age you MUST obtain parental consent before posting a comment on our blog.

NOTE: You should avoid entering personally identifiable information to the actual comment field of any blog post comments that you submit on this website.

3.3 Contact forms

Should you choose to contact us using any of the contact forms within this website, the information that you submit will be collated into an email and sent to us over the Simple Mail Transfer Protocol (SMTP). 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. The data will also be saved to this website’s internal database purely for the purposes of backup. Once we have received and responded to your contact form enquiry, all of the form submission data is deleted from this website’s database.

4.0 How we store your personal information

As detailed in above, if you submit a comment to a blog post published on this website or if you submit a contact form some personal information will be stored within this website’s database. These are currently 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 build on (WordPress). 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.

5.0 About this website’s server

This website is hosted by United Hosting within a UK data centre located just outside London.

Some of the data centre’s more notable security features are as follows:

Full details of United Hosting’s data centre can be found here.

All traffic (transferral of files) between this website and your browser is encrypted and delivered over HTTPS.

6.0 Our third-party data processors

We use two third parties to process personal data on our behalf. These third parties have been carefully chosen and comply with the legislation set out in section 2.0 of this privacy policy. Both of these third parties are based in the USA and are EU-U.S Privacy Shield compliant.

7.0 Data breaches

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.

8.0 Data controller

The data controller of this website is: Jacobs Allen limited, a UK Private limited Company with company number: 7916295

Whose registered office is:
59 Abbeygate Street
Bury St Edmunds
Suffolk
IP33 1LB

9.0 Data Protection Officer

Name: Sheila Burke
Title: Director
Telephone: 01284 704260
Email: ask@jacobsallen.co.uk

10.0 Changes to this privacy policy

This privacy policy may change from time to time inline 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 change log below.

10.1 Change log

21/06/2017