Privacy Policy & Data Protection

Last Updated: 1st October 2018

1.0 User Privacy and Data Protection

Bourne Abbey Primary Academy hold four core beliefs with regard to the manner in which we treat your data.

• User privacy and data protection are human rights
  • We have a duty of care to the people within our data
  • Data is a liability, it should only be collected and processed when absolutely necessary
  • We will never sell, rent or otherwise distribute or make public your personal information

2.0 Relevant legislation

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:

• UK Data Protection Act 1988 (DPA)
  • EU Data Protection Directive 1995 (DPD)
  • EU General Data Protection Regulation 2018 (GDPR)
  • UK Data Protection Act 2018

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

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

3.1 Google Analytics Usage

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. Disabling cookies on your internet browser will stop GA from tracking any part of your visit to pages within this website. You can view our complete cookies policy here – Abbey Academies Trust Cookie Policy

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. 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 and email links

Should you choose to contact us using the consultation form; none of the data that you supply will be stored by this website or passed to / be processed by any of the third-party data processors defined in section 6.0. Instead the data 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.

4.0 How We Store Your Personal Data

As detailed in section 3.2 above, if you submit a comment to a blog post published on this website some personal information will be stored within this website’s database. This is currently the only occasion 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 Our Website Server

This website is hosted by Go Daddy within the UK.

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

6.0 Our Third-Party Processors

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. Both of these third parties are based in the USA and are EU-U.S Privacy Shield compliant.

7.0 Data Breaches & Our Reporting Process

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: Abbey Academies Trust

We are registered with the Information Commissioners Office www.ico.org.uk

Our address is:
Bourne Abbey C of E Primary School,

Abbey Road,

Bourne,

PE10 9EP

You can contact Abbey Academies Trust with any questions on Data Protection or the use of your “Personal Data” through our company Data Protection Officer Duncan Pickering on mailto:BAP.enquiries@abbeyacademies.co.uk

9.0 Changes To Our Privacy Policy

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 change log.