Privacy Notice & Cookies
(attached to contributor agreement and also available on the website)
If you would like to be involved in the Layers of London project, or stay up to date with its progress, you will be asked to provide some personal information for our records. The statement below explains how the University will process this data.
Layers of London is a project of the Institute of Historical Research, which is part of the University of London http://www.london.ac.uk
If you sign the User Agreement, the University will collect the following data:
- Name, email address
- Any data generated throughout the course of the project relating to an individual will be used purely for reporting purposes.
If you are opting in to hear more about Layers of London and its events we will collect the following:
- Name, email address
The University processes the information for the following purposes:
- Managing your user agreement
- Co-ordinating your contributions to the Layers of London project
- Publishing your contributions on the Layers of London website and other relevant repositories
- Carry out anonymised reporting and analysis on our users to check and monitor our outcomes
- Telling you about the project and other related news and events
The University has to have a legal basis for processing your data and relies on the following approach:
- Collecting the data is necessary for the performance of your contract with us as a Layers of London user
- Where you access certain optional services – such as the mailing list - we will ask for your consent
- Your contributions to Layers of London will form part of a historic record and the University will use it for archiving purposes in the public interest, scientific or historical research purposes
The data from your user agreement will be stored for the duration of the project
- We will retain your contributions as part of the permanent record of Layers of London
- We will retain your user file for appropriate periods based on risk and necessity
- We will retain your contact details if you decide to continue to keep you informed of IHR or University news and events – you can unsubscribe at any time
The University may use an external contractor or 'data processor' to store or manage its data. It will process this data only for purposes specified by the University and will be bound by contract to meeting the University's obligations under the General Data Protection Regulation. Where data is passed outside the EEA, the University will take the relevant steps to ensure there is adequate protection in place.
Your personal data will not be passed to any other third party without your consent, except where the University is required to do so by law.
You have a number of rights under the General Data Protection Regulation, such as the right of access to your data (the 'Subject Access Right'). For more information please see the University's Data Protection page at the following link: https://london.ac.uk/about-us/how-university-run/policies/data-protection-policy
You can find out more at the University's Data Protection page at the following link: https://london.ac.uk/about-us/how-university-run/policies/data-protection-policy
What are cookies
Cookies are small text files used by a website to 'request' information from your website or mobile device browser, return the information to the website and then store the information. Cookies can be requested by any website and are placed on your device’s hard drive. Cookies allow the web application to tailor its operations to your needs, likes and dislikes by gathering and remembering information about your preferences.
You can control cookies through your browser settings. Find out more about cookies and how to manage them on the Directgov website
List of the main Layers of London Cookies
The following table explains which types of cookies we use and why we use them:
|Cloudflare cookie||_cfduid||Cookies used for security tracking on our content delivery network||For full details please visit the Cloudflare site:
|_layers_app_session||Cookies used to identify a user in the application|
Changes to this privacy notice