Vanderbilt solutions and products enable customers to manage and process personal data in such a way as to meet GDPR requirements. This guide is intended to help and support our customers in assessing their own readiness in meeting their responsibilities and obligations towards the new regulations.
Data protection is a fundamental right whereby everyone has the right to the protection of personal data concerning him or her. The General Data Protection Regulation (GDPR) is applicable from 25th May 2018 and is designed to give individuals more control over their personal data. There is one set of rules for the whole of the EU, which can be complemented in some areas by national legislation.
The GDPR imposes obligations on businesses or organizations that collect, use and process personal data. At the center of GDPR is the requirement for organizations and businesses to be fully transparent about how they are using and protecting personal data, and to be able to demonstrate accountability for their data processing activities. Such data must be processed fairly for specified purposes and on the basis of the consent of the person concerned or some other legitimate basis laid down by law.
While Vanderbilt offers customers flexible and intuitive product functionality to facilitate compliance with the new regulations, the Vanderbilt organization does not collect, control, use or process personal data which exists within Vanderbilt on-premises products. Therefore, it is the role and responsibility of the controller and processor of personal data to ensure that obligations stated in GDPR are complied with.
If you are in any doubt or are unsure about the identity of the data controller and/or data processor, in any case, you should consult your legal adviser.
The term “personal data” means any information relating to a living person who is identified or identifiable.
A person is identifiable if they can be identified directly or indirectly using an “identifier”. The GDPR gives examples of identifiers, including names, identification numbers, and location data. A person may also be identifiable by reference to factors which are specific to their identity, such as physical, genetic or cultural factors.
Personal data that has been de-identified, encrypted or pseudonymized but, can be used to re-identify a person remains personal data and falls within the scope of GDPR. If personal data has been rendered anonymous in such a way that the individual is no longer identifiable, then this is not considered personal data. For data to be truly anonymized, the anonymization must be irreversible.
The law protects personal data regardless of the technology or method used for processing that data – it applies to both automated and manual processing. It also doesn’t matter how the personal data is stored – in an IT system, through video surveillance, or on paper; in all cases, personal data is subject to the protection requirements set out in the GDPR.
Processing covers a wide range of operations performed on personal data, including by manual or automated means. It includes the collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction of personal data.
The General Data Protection Regulation (GDPR) applies to the processing of personal data wholly or partly by automated means as well as to non-automated processing, if it is part of a structured filing system.
A data controller is an individual or the legal person who controls and is responsible for the keeping and use of personal information on a computer or in structured manual files. Being a data controller carries with its legal responsibilities, so you should be quite clear if these responsibilities apply to you or your organization.
If you or your organization controls and is responsible for the personal data which it holds i.e. decides what personal information is going to be kept and to which use the information will be put, then you or your organization is a data controller.
Examples of cases where the data controller is an individual include general practitioners, pharmacists, politicians and sole traders, where these individuals keep personal information about their patients, clients, constituents etc.
If you or your organization holds the personal data, but some other individual or organization decides and is responsible for what happens to the data, then that other individual or organization is the data controller, and you or your organization is a "data processor".
Examples of data processors include payroll companies, accountants, and market research companies, all of which could hold or process personal information on behalf of someone else.
In order to legally process personal data, organizations and businesses must identify and document the legal basis for doing so from the start. Some of the legal ways to process data include:
- Consent of the individual: Consent is appropriate if individuals are offered real choice and control over how their data is used.
- Vital interests: Processing is necessary to protect the vital interests of the individual, e.g. if it’s necessary to protect someone’s life.
- Compliance that has a legal obligation: Data can be processed if, for example, it is required by EU law for a particular purpose.
- A contract with the individual: Processing is necessary for the performance of a contract with an individual, e.g. to supply goods or services that have been requested
If you are in any doubt, as to whether you have acquired sufficient consent to process personal data, you should consult your legal adviser.
If you hold or process (enter, edit, maintain) personal data (data processor) on behalf of your customer (data controller) you will require a data processing contract. We would recommend obtaining legal advice to best ensure the contract addresses appropriate security and other data protection safeguards. As part, we would advise customers to have a checklist regarding data handling and the handover of the security system.
It is clear the law is changing to GDPR and this needs to be factored into security system planning. Areas need be identified and addressed that may cause compliance problems under the GDPR. Under GDPR individuals have the right to be given clear information relating to the use of their data.
The first practical step is to identify your role and responsibility with respect to GDPR. Are you a data controller or data processor or both? If you are in any doubt or are unsure about the identity of the data controller and/or data processor, in any case, you should consult your legal adviser.
The second step is to become accountable. Consider all the personal data you are handling when working with the security system and examine it under the following headings:
- What personal data is stored?
- What is the legal basis on which processing of personal data is based?
- Where is the data stored?
- How is the data protected?
- How long is the data retained?
- What is the policy for handling individual data access requests?
- What is the process if someone asks to be removed from the system?
- Who has access to the data?
- Is personal data transferred outside the EEA?
bright blue / lite blue & GDPR
The following information outlines the Vanderbilt bright blue / lite blue v5.x system functionality in relation to GDPR compliancy.
What personal data is stored?
The only required personal data for a cardholder record in bright/lite blue is Last Name and Encoded Badge ID, though additional data is likely collected. First Name and Middle Initial are optional. User definable fields could be used for entering various personal data as defined by the end user (customer).
What is the legal basis on which processing of personal data is based?
The legal basis on which the personal data is obtained and processed is defined by the end user’s policies and procedures.
Where is the data stored?
The data is entered and owned by end user and is stored locally on the controller, or in backups and archives that can be saved elsewhere and managed by the end user. The system does not allow for duplicate encoded IDs.
How is the data protected?
The bright/lite blue system requires a password protected login to access the database.
Access permissions can be restricted to 3 levels, whereby database rights can be granted as per role for Administrator, Manager, and Operator.
Vanderbilt does not have access to customer data unless given specific permission and remote access for technical support.
How long is the data retained?
The Database Utility in bright/lite blue automatically saves 5 backups (1 per day) to the controller. Backups are FIFO and can be downloaded and saved elsewhere by user if desired. In addition to backups, archives are also stored on the board. For every 1M transactions/log events, an archive is created and stored. Max archive files that can be stored is 12.
Cardholder records and the associated personal data can be ‘deleted’ (i.e. flagged for deletion / hidden) from the software immediately, however cardholder data is not fully not deleted until their last associated transaction (log event) is purged. Transactions are purged after the database hits 1 million transactions (and then it is purged back to 500,000). Archives (up to 12) are FIFO are the length of storage is dependent on the size of- and activity on the system.
What is the policy for handling individual data access requests?
There are pre-defined Cardholder, Access and Audit reports that can be run and printed and/or exported in CSV and viewing in structured formats such as Excel and PDF.
What is the process if someone asks to be removed from the system?
Cardholder records with associated personal data can be deleted within the software. Backup database copies would also need to be deleted unless more than 5 days have elapsed (whereby the 5 daily backups would already be overwritten). Archives and can be removed/deleted by contacting Vanderbilt Technical Support.
Personal data in any backup saved elsewhere (off controller) would need to be deleted manually by end user.
Who has access to the data?
These details are defined and driven as per the corporate policies specific to and set by each end user. bright/lite blue allows the deletion of cardholder personal data from the database. Data copies are managed completely by the end user once saved elsewhere (off controller).
Is personal data transferred outside the EEA?
Any transfer of data would be managed and initiated by the end user.