GDPR

Data Protection Policy DATAEGG

1. 

Introduction 

  • 1.1.  Background to the General Data Protection Regulation (‘GDPR’)
    The General Data Protection Regulation 2016 replaces the EU Data Protection Directive of 1995 and supersedes the laws of individual Member States that were developed in compliance with the Data Protection Directive 95/46/EC. Its purpose is to protect the “rights and freedoms” of natural persons (i.e. living individuals) and to ensure that personal data is not processed without their knowledge, and, wherever possible, that it is processed with their consent.
  • 1.2.  Definitions used by the organisation (drawn from the GDPR)
    Material scope (Article 2) the GDPR applies to the processing of personal data wholly or partly by automated means (i.e. by computer) and to the processing other than by automated means of personal data (i.e. paper records) that form part of a filing system or are intended to form part of a filing system.
    Territorial scope (Article 3) the GDPR will apply to all controllers that are established in the EU (European Union) who process the personal data of data subjects, in the context of that establishment. It will also apply to controllers outside of the EU that process personal data in order to offer goods and services, or monitor the behaviour of data subjects who are resident in the EU.
  • 1.3.  Article 4 definitions
    Establishment the main establishment of the controller in the EU will be the place in which the controller makes the main decisions as to the purpose and means of its data processing activities. The main establishment of a processor in the EU will be its administrative centre. If a controller is based outside the EU, it will have to appoint a representative in the jurisdiction in which the controller operates to act on behalf of the controller and deal with supervisory authorities.
    Personal data – any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

 

Special categories of personal data – personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade-union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation. 

Data controller – the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law. 

Data subject – any living individual who is the subject of personal data held by an organisation. 

Processing – any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. 

Profiling is any form of automated processing of personal data intended to evaluate certain personal aspects relating to a natural person, or to analyse or predict that person’s performance at work, economic situation, location, health, personal preferences, reliability, or behaviour. This definition is linked to the right of the data subject to object to profiling and a right to be informed about the existence of profiling, of measures based on profiling and the envisaged effects of profiling on the individual. 

Personal data breach a breach of security leading to the accidental, or unlawful, destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed. There is an obligation on the controller to report personal data breaches to the supervisory authority and where the breach is likely to adversely affect the personal data or privacy of the data subject. 

Data subject consent means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data. 

Child the GDPR defines a child as anyone under the age of 16 years [A1] old, although this may be lowered to 13 by Member State law. The processing of personal data of a child is only lawful if parental or custodian consent has been obtained. The controller shall make reasonable efforts to verify in such cases that consent is given or authorised by the holder of parental responsibility over the child. 

Third party – a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data. 

Filing system – any structured set of personal data which are accessible according to specific criteria, whether centralised, decentralised or dispersed on a functional or geographical basis. 

2. Policy statement 

  • 2.1.  The management of DataEgg Ltd, located at xxxxxx, Thomastown, Ireland are committed to compliance with all relevant EU and Member State laws in respect of personal data, and the protection of the “rights and freedoms” of individuals whose information DataEgg Ltd collects and processes in accordance with the General Data Protection Regulation (GDPR).
  • 2.2.  Compliance with the GDPR is described by this policy and other relevant policies such as the Information Security Policy, along with connected processes and procedures.
  • 2.3.  The GDPR and this policy apply to all of DataEgg Ltd’s personal data processing functions, including those performed on customers’, clients’, employees’, suppliers’ and partners’ personal data, and any other personal data the organisation processes from any source.
  • 2.4.  DataEgg Ltd has established objectives for data protection and privacy.
  • 2.5.  Data Protection Officer (DPO) is responsible for reviewing the register of
    processing annually in the light of any changes to DataEgg Ltd’s activities (as determined by changes to the data inventory register and the management review) and to any additional requirements identified by means of data protection impact assessments. This register [A4] needs to be available on the supervisory authority’s request.
  • 2.6.  This policy applies to all Staff and interested parties of DataEgg Ltd such as outsourced suppliers. Any breach of the GDPR or this PIMS will be dealt with under DataEgg Ltd’s disciplinary policy and may also be a criminal offence, in which case the matter will be reported as soon as possible to the appropriate authorities.
  • 2.7.  Partners and any third parties working with or for DataEgg Ltd, and who have or may have access to personal data, will be expected to have read, understood and to comply with this policy. No third party may access personal data held by DataEgg Ltd without having first entered into a data confidentiality agreement, which imposes on the third party obligations no less onerous than those to which DataEgg Ltd is committed, and which gives DataEgg Ltd the right to audit compliance with the agreement. 

Responsibilities and roles under the General Data Protection Regulation 

  • 3.1.  DataEgg Ltd is a data controller and data processor under the GDPR.
  • 3.2.  Management and all those in managerial or supervisory roles throughout
    DataEgg Ltd are responsible for developing and encouraging good information handling practices within DataEgg Ltd; responsibilities are set out in individual job descriptions.
  • 3.3.  Data Protection Officer (DPO), a role specified in the GDPR, should be a member of the senior management team, is accountable to Board of Directors of DataEgg Ltd for the management of personal data within DataEgg Ltd and for ensuring that compliance with data protection legislation and good practice can be demonstrated. This accountability includes: 
    • 3.3.1.  development and implementation of the GDPR as required by this policy; and
    • 3.3.2.  security and risk management in relation to compliance with the policy.
  • 3.4.  Data Protection Officer (DPO), who Management considers to be suitably
    qualified and experienced, has been appointed to take responsibility for DataEgg Ltd’s compliance with this policy on a day-to-day basis and, in particular, has direct responsibility for ensuring that DataEgg Ltd complies with the GDPR, as do Manager’s in respect of data processing that takes place within their area of responsibility.
  • 3.5.  The Data Protection Officer (DPO) have specific responsibilities in respect of procedures such as the Subject Access Request Procedure and are the first point of call for Staff seeking clarification on any aspect of data protection compliance.
  • 3.6.  Compliance with data protection legislation is the responsibility of all Staff of DataEgg Ltd who process personal data.
  • 3.7.  Staff of DataEgg Ltd are responsible for ensuring that any personal data about them and supplied by them to DataEgg Ltd is accurate and up-to-date.

Data protection principles 

All processing of personal data must be conducted in accordance with the data protection principles as set out in Article 5 of the GDPR. DataEgg Ltd’s policies and procedures are designed to ensure compliance with the principles. 

4.1. Personal data must be processed lawfully, fairly and transparently
Lawful – identify a lawful basis before you can process personal data. These are often referred to as the “conditions for processing”, for example consent. 

Fairly – in order for processing to be fair, the data controller has to make certain information available to the data subjects as practicable. This applies whether the personal data was obtained directly from the data subjects or from other sources. 

The GDPR has increased requirements about what information should be available to data subjects, which is covered in the ‘Transparency’ requirement. 

Transparently – the GDPR includes rules on giving privacy information to data subjects in Articles 12, 13 and 14. These are detailed and specific, placing an emphasis on making privacy notices understandable and accessible. Information must be communicated to the data subject in an intelligible form using clear and plain language. 

The specific information that must be provided to the data subject must, as a minimum, include: 

  • 4.1.1.  the identity and the contact details of the controller and, if any, of the controller’s representative;
  • 4.1.2.  the contact details of the Data Protection Officer (DPO);
  • 4.1.3.  the purposes of the processing for which the personal data are
    intended as well as the legal basis for the processing;
  • 4.1.4.  the period for which the personal data will be stored;
  • 4.1.5.  the existence of the rights to request access, rectification, erasure or
    to object to the processing, and the conditions (or lack of) relating to exercising these rights, such as whether the lawfulness of previous processing will be affected;
  • 4.1.6.  the categories of personal data concerned;
  • 4.1.7.  the recipients or categories of recipients of the personal data, where
    applicable;
  • 4.1.8.  where applicable, that the controller intends to transfer personal data
    to a recipient in a third country and the level of protection afforded to
    the data;
  • 4.1.9.  any further information necessary to guarantee fair processing.
  • 4.2.  Personal data can only be collected for specific, explicit and legitimate purposes
    Data obtained for specified purposes must not be used for a purpose that differs from those formally notified to the supervisory authority as part of DataEgg Ltd’s GDPR register of processing.
  • 4.3.  Personal data must be adequate, relevant and limited to what is necessary for processing

4.3.1. The Data Protection Officer (DPO) is responsible for ensuring that DataEgg Ltd does not collect information that is not strictly necessary for the purpose for which it is obtained. 

 

  • 4.3.2.  All data collection forms (electronic or paper-based), including data collection requirements in new information systems, must be include a fair processing statement or link to privacy statement.
  • 4.3.3.  The Data Protection Officer (DPO) will ensure that, on an annual basis all data collection methods are reviewed by internal audit to ensure that collected data continues to be adequate, relevant and not excessive.

Personal data must be accurate and kept up to date with every effort to erase or rectify without delay 

  • 4.4.1.  Data that is stored by the data controller must be reviewed and updated as necessary. No data should be kept unless it is reasonable to assume that it is accurate.
  • 4.4.2.  The Data Protection Officer (DPO) is responsible for ensuring that all staff are trained in the importance of collecting accurate data and maintaining it.
  • 4.4.3.  It is also the responsibility of the data subject to ensure that data held by DataEgg Ltd is accurate and up to date. Completion of a registration or application form by a data subject will include a statement that the data contained therein is accurate at the date of submission.
  • 4.4.4.  Staff/customers should be required to notify DataEgg Ltd of any changes in circumstance to enable personal records to be updated accordingly. It is the responsibility of DataEgg Ltd to ensure that any notification regarding change of circumstances is recorded and acted upon.
  • 4.4.5.  The Data Protection Officer (DPO) is responsible for ensuring that appropriate procedures and policies are in place to keep personal data accurate and up to date, taking into account the volume of data collected, the speed with which it might change and any other relevant factors.
  • 4.4.6.  On at least an annual basis, the Data Protection Officer (DPO) will review the retention dates of all the personal data processed by DataEggLtd, by reference to the data inventory, and will identify any data that is no longer required in the context of the registered purpose. This data will be securely deleted/destroyed.
  • 4.4.7.  The Data Protection Officer (DPO) is responsible for responding to requests for rectification from data subjects within one month. This can be extended to a further two months for complex requests. If DataEgg Ltd decides not to comply with the request, the Data Protection Officer (DPO) must respond to the data subject to explain its reasoning and inform them of their right to complain to the supervisory authority and seek judicial remedy.
  • 4.4.8.  The Data Protection Officer (DPO) is responsible for making appropriate arrangements that, where third-party organisations may have been passed inaccurate or out-of-date personal data, to inform them that the information is inaccurate and/or out of date and is not to be used to inform decisions about the individuals concerned; and for passing any correction to the personal data to the third party where this is required. 

Personal data must be kept in a form such that the data subject can be identified only as long as is necessary for processing. 

  • 4.5.1.  Where personal data is retained beyond the processing date, it will be minimised/encrypted/pseudonymised in order to protect the identity of the data subject in the event of a data breach..
  • 4.5.2.  The Data Protection Officer (DPO) must specifically approve any data retention that exceeds the retention periods, and must ensure that the justification is clearly identified and in line with the requirements of the data protection legislation. This approval must be written.

Personal data must be processed in a manner that ensures the appropriate security 

The Data Protection Officer (DPO) will carry out a risk assessment taking into account all the circumstances of DataEgg Ltd’s controlling or processing operations. 

In determining appropriateness, the Data Protection Officer (DPO) should also consider the extent of possible damage or loss that might be caused to individuals (e.g. staff or customers) if a security breach occurs, the effect of any security breach on DataEgg Ltd itself, and any likely reputational damage including the possible loss of customer trust. 

When assessing appropriate technical measures, the Data Protection Officer (DPO) will consider the following: 

  • ●  Password protection;
  • ●  Automatic locking of idle terminals;
  • ●  Removal of access rights for USB and other memory media;
  • ●  Virus checking software and firewalls;
  • ●  Role-based access rights including those assigned to temporary staff;
  • ●  Encryption of devices that leave the organisations premises such as
    laptops;
  • ●  Security of local and wide area networks;
  • ●  Privacy enhancing technologies such as pseudonymisation and
    anonymisation;
  • ●  Identifying appropriate international security standards relevant to
    DataEgg Ltd.

 

When assessing appropriate organisational measures the Data Protection Officer (DPO) will consider the following: 

The appropriate training levels throughout DataEgg Ltd;
Measures that consider the reliability of employees (such as references etc.); 

  • ●  The inclusion of data protection in employment contracts;
  • ●  Identification of disciplinary action measures for data breaches;
  • ●  Monitoring of staff for compliance with relevant security standards;
  • ●  Physical access controls to electronic and paper based records;
  • ●  Adoption of a clear desk policy;
  • ●  Storing of paper based data in lockable fireproof cabinets;
  • ●  Restricting the use of portable electronic devices outside of the
    workplace;
  • ●  Restricting the use of employee’s own personal devices [A18] being
    used in the workplace;
  • ●  Adopting clear rules about passwords;
  • ●  Making regular backups of personal data and storing the media
    off-site;
  • ●  The imposition of contractual obligations on the importing
    organisations to take appropriate security measures when transferring data outside the EEA.
    These controls have been selected on the basis of identified risks to personal data, and the potential for damage or distress to individuals whose data is being processed.

4.7. The controller must be able to demonstrate compliance with the GDPR’s other principles (accountability) 

The GDPR includes provisions that promote accountability and governance. These complement the GDPR’s transparency requirements. The accountability principle in Article 5(2) requires you to demonstrate that you comply with the principles and states explicitly that this is your responsibility. 

The [A20] DataEgg Ltd will demonstrate compliance with the data protection principles by implementing data protection policies, adhering to codes of conduct, implementing technical and organisational measures, as well as adopting techniques such as data protection by design, DPIAs, breach notification procedures and incident response plans. 

 

5. Data subjects’ rights
5.1. Data subjects have the following rights regarding data processing, and the 

data that is recorded about them: 

 

  • 5.1.1.  To make subject access requests regarding the nature of information held and to whom it has been disclosed.
  • 5.1.2.  To prevent processing likely to cause damage or distress.
  • 5.1.3.  To prevent processing for purposes of direct marketing.
  • 5.1.4.  To be informed about the mechanics of automated decision-taking
    process that will significantly affect them.
  • 5.1.5.  To not have significant decisions that will affect them taken solely
    by automated process.
  • 5.1.6.  To sue for compensation if they suffer damage by any
    contravention of the GDPR.
  • 5.1.7.  To take action to rectify, block, erased, including the right to be
    forgotten, or destroy inaccurate data.
  • 5.1.8.  To request the supervisory authority to assess whether any
    provision of the GDPR has been contravened.
  • 5.1.9.  To have personal data provided to them in a structured, commonly
    used and machine-readable format, and the right to have that data
    transmitted to another controller.
  • 5.1.10.  To object to any automated profiling that is occurring without
    consent.

DataEgg Ltd ensures that data subjects may exercise these rights: 

  • 5.2.1.  Data subjects may make data access requests and DataEgg Ltd will ensure that its response to the data access request complies with the requirements of the GDPR.
  • 5.2.2.  Data subjects have the right to complain to DataEgg Ltd related to the processing of their personal data, the handling of a request from a data subject and appeals from a data subject on how complaints have been handled.

6. Consent 

  • 6.1.  DataEgg Ltd understands ‘consent’ to mean that it has been explicitly and freely given, and a specific, informed and unambiguous indication of the data subject’s wishes that, by statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. The data subject can withdraw their consent at any time.
  • 6.2.  DataEgg Ltd understands ‘consent’ to mean that the data subject has been fully informed of the intended processing and has signified their agreement, while in a fit state of mind to do so and without pressure being exerted upon them. Consent obtained under duress or on the basis of misleading information will not be a valid basis for processing.
  • 6.3.  There must be some active communication between the parties to demonstrate active consent. Consent cannot be inferred from non-response to a communication. The Controller must be able to demonstrate that consent was obtained for the processing operation.
  • 6.4.  In most instances, consent to process personal and sensitive data is obtained routinely by DataEgg Ltd using standard consent documents e.g. when a new client signs a contract, or during induction for participants on programmes.
  • 6.5.  Where DataEgg Ltd provides online services to children, parental or custodial authorisation must be obtained or have been obtained by the school. This requirement applies to children under the age of 13.
  1. Security of data 
    • 7.1.  All Staff are responsible for ensuring that any personal data that DataEgg Ltd holds and for which they are responsible, is kept securely and is not under any conditions disclosed to any third party unless that third party has been specifically authorised by DataEgg Ltd to receive that information and has entered into an agreement.
    • 7.2.  All personal data should be accessible only to those who need to use it. All personal data should be treated with the highest security and must be kept: 
      • ●  in a lockable room with controlled access; and/or
      • ●  in a locked drawer or filing cabinet; and/or
      • ●  if computerised, password protected in line with corporate
        requirements); and/or
      • ●  stored on (removable) computer media which are encrypted in line
        with Secure Disposal of Storage Media.
    • 7.3.  Care must be taken to ensure that computer screens and terminals are not
      visible except to authorised Staff of DataEgg Ltd.
    • 7.4.  Manual records may not be left where they can be accessed by unauthorised
      personnel and may not be removed from business premises without explicit authorisation. As soon as manual records are no longer required for day-to-day client support, they must be removed from secure archiving.
    • 7.5.  Manual records that have reached their retention date are to be shredded and disposed. Hard drives of redundant PCs are to be removed and immediately destroyed before disposal.
    • 7.6.  Processing of personal data ‘off-site’ presents a potentially greater risk of loss, theft or damage to personal data. Staff must be specifically authorised to process data off-site
  2. Disclosure of data 
    • 8.1.  DataEgg Ltd must ensure that personal data is not disclosed to unauthorised third parties which includes family members, friends, government bodies, and in certain circumstances, the Police. All Staff should exercise caution when asked to disclose personal data held on another individual to a third party. It is important to bear in mind whether or not disclosure of the information is relevant to, and necessary for, the conduct of DataEgg Ltd’s business.
    • 8.2.  All requests to provide data for one of these reasons must be supported by appropriate paperwork and all such disclosures must be specifically authorised by the Data Protection Officer (DPO).

 

  1. Retention and disposal of data 
    • 9.1.  DataEgg Ltd shall not keep personal data in a form that permits identification of data subjects for longer a period than is necessary, in relation to the purpose(s) for which the data was originally collected.
    • 9.2.  DataEgg Ltd may store data for longer periods if the personal data will be processed solely for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes, subject to the implementation of appropriate technical and organisational measures to safeguard the rights and freedoms of the data subject.
    • 9.3.  Personal data must be disposed of securely in accordance with the sixth principle of the GDPR – processed in an appropriate manner to maintain security, thereby protecting the “rights and freedoms” of data subjects.
  2. Data transfers

10.1. All exports of data from within the European Economic Area (EEA) to non-European Economic Area countries (referred to in the GDPR as ‘third countries’) are unlawful unless there is an appropriate “level of protection for the fundamental rights of the data subjects”. 

The transfer of personal data outside of the EEA is prohibited unless one or more of the specified safeguards, or exceptions, apply: 

  • 10.1.1.  An adequacy decision
    The European Commission can and does assess third countries, a territory and/or specific sectors within third countries to assess whether there is an appropriate level of protection for the rights and freedoms of natural persons. In these instances no authorisation is required.
    Countries that are members of the European Economic Area (EEA) but not of the EU are accepted as having met the conditions for an adequacy decision.
    A list of countries that currently satisfy the adequacy requirements of the Commission are published in the Official Journal of the European Union. http://ec.europa.eu/justice/data-protection/international-transfers/adeq uacy/index_en.htm
  • 10.1.2.  Privacy Shield
    DataEgg Ltd wishes to transfer personal data from the EU to an organisation in the United States it should check that the organisation is signed up with the Privacy Shield framework at the U.S. Department of Commerce. The obligation applying to companies under the Privacy Shield are contained in the “Privacy Principles”. The US DOC is responsible for managing and administering the Privacy Shield and ensuring that companies live up to their commitments. In order to be able to certify, companies must have a privacy policy in line with the Privacy Principles e.g. use, store and further transfer the personal data according to a strong set of data protection rules and safeguards. The protection given to the personal data applies regardless of whether the personal data is related to an EU resident or not. Organisations must renew their “membership” to the Privacy Shield on an annual basis. If they do not, they can no longer receive and use personal data from the EU under that framework. 

Assessment of adequacy by the data controller

In making an assessment of adequacy, the Irish based exporting controller should take account of the following factors: 

  • ●  the nature of the information being transferred;
  • ●  the country or territory of the origin, and final destination, of the
    information;
  • ●  how the information will be used and for how long;
  • ●  the laws and practices of the country of the transferee,
    including relevant codes of practice and international
    obligations; and
  • ●  the security measures that are to be taken as regards the data
    in the overseas location.
  • 10.1.3.  Binding corporate rules
    DataEgg Ltd may adopt approved binding corporate rules for the transfer of data outside the EU. This requires submission to the relevant supervisory authority for approval of the rules that DataEgg Ltd is seeking to rely upon.
  • 10.1.4.  Model contract clauses
    DataEgg Ltd may adopt approved model contract clauses for the transfer of data outside of the EEA. If DataEgg Ltd adopts the model contract clauses approved by the relevant supervisory authority there is an automatic recognition of adequacy.
  • 10.1.5.  Exceptions
    In the absence of an adequacy decision, Privacy Shield membership, binding corporate rules and/or model contract clauses, a transfer of personal data to a third country or international organisation shall only take place on one of the following conditions: 
    • ●  the data subject has explicitly consented to the proposed transfer, after having been informed of the possible risks of such transfers for the data subject due to the absence of an adequacy decision and appropriate safeguards;
    • ●  the transfer is necessary for the performance of a contract between the data subject and the controller or the implementation of pre-contractual measures taken at the data subject’s request; 
  • ●  the transfer is necessary for the conclusion or performance of
    a contract concluded in the interest of the data subject
    between the controller and another natural or legal person;
  • ●  the transfer is necessary for important reasons of public
    interest;
  • ●  the transfer is necessary for the establishment, exercise or
    defence of legal claims; and/or
  • ●  the transfer is necessary in order to protect the vital interests
    of the data subject or of other persons, where the data subject is physically or legally incapable of giving consent.
    Information asset register/data inventory
  • 11.1.  DataEgg Ltd has established a data inventory and data flow process as part of its approach to address risks and opportunities throughout its GDPR compliance project. DataEgg Ltd’s data inventory and data flow determines: 
    • ●  business processes that use personal data;
    • ●  source of personal data;
    • ●  volume of data subjects;
    • ●  description of each item of personal data;
    • ●  processing activity;
    • ●  maintains the inventory of data categories of personal data processed;
    • ●  documents the purpose(s) for which each category of personal data is
      used;
    • ●  recipients, and potential recipients, of the personal data;
    • ●  the role of the Organisation Name throughout the data flow;
    • ●  key systems and repositories;
    • ●  any data transfers; and
    • ●  all retention and disposal requirements.
  • 11.2.  DataEgg Ltd is aware of any risks associated with the processing of particular types of personal data. 
    • 11.2.1.  DataEgg Ltd assesses the level of risk to individuals associated with the processing of their personal data. Data protection impact assessments (DPIAs) are carried out in relation to the processing of personal data by DataEgg Ltd, and in relation to processing undertaken by other organisations on behalf of DataEgg Ltd.
    • 11.2.2.  DataEgg Ltd shall manage any risks identified by the risk assessment in order to reduce the likelihood of a non-conformance with this policy.
    • 11.2.3.  Where a type of processing, in particular using new technologies and taking into account the nature, scope, context and purposes of the processing is likely to result in a high risk to the rights and freedoms of natural persons, DataEgg Ltd shall, prior to the processing, carry out a DPIA of the impact of the envisaged processing operations on the protection of personal data. A single DPIA may address a set of similar processing operations that present similar high risks. 
  • 11.2.4.  Where, as a result of a DPIA it is clear that DataEgg Ltd is about to commence processing of personal data that could cause damage and/or distress to the data subjects, the decision as to whether or not DataEgg Ltd may proceed must be escalated for review to the Data Protection Officer (DPO).
  • 11.2.5.  The Data Protection Officer (DPO) shall, if there are significant concerns, either as to the potential damage or distress, or the quantity of data concerned, escalate the matter to the supervisory authority.

Copyright © 2018 DataEgg Ltd. All rights reserved.

Privacy Policy

Privacy Policy DataEgg

 

Updated: 19th July 2018 

 

  1. At DataEgg, we take privacy very seriously. We’ve updated our privacy policy ( Policy ) to ensure that we communicate to You, in the clearest way possible, how we treat personal information. We encourage You to read this Policy carefully. It will help You make informed decisions about sharing Your personal information with us. All data subjects whose personal data is collected, in line with the requirements of the GDPR.
  2. DataEgg is a provider of online platforms, mobile apps and APIs that are simple, smart, and secure and gives business and individuals the opportunity to visualise data in augmented reality.
    The Service involves the storage of Data about companies or individuals. That Data can include personal information. “Personal information” is information about an identifiable individual, and may include information such as the individual’s name, email address and what school they’re attached to.
  3. DataEgg may collect personal information directly from You when You: 
    • ●  register to use the Service,
    • ●  use the Service,
    • ●  have your data in a business Management Information System,
    • ●  are included in a business integration,
    • ●  contact the DataEgg support team, and
    • ●  visit our Website. 

    • You can always choose not to provide Your personal information to DataEgg, but it may mean that we are unable to provide You with the Service.
  4. Responsibility 
    • 3.1.  The Data Protection Officer (DPO) is responsible for ensuring that this notice is made available to data subjects prior to DataEgg Ltd collecting/processing their personal data.
    • 3.2.  All Employees of DataEgg Ltd who interact with data subjects are responsible for ensuring that this notice is drawn to the data subject’s attention and their consent to the processing of their data is secured.

 

4. Privacy notice

4.1. Who are we? 

DataEgg are a company that helps companies visualise their data 

Our DPO and data protection representatives can be contacted directly here: 

  • ●  Email: dpo@dataegg.net
  • ●  Tel: 0863179000
  • The type of data we collect from you includes:

Personal Data Type Source 

First name Sign-up page

Last name Sign-up page 

Email address Sign-up page

Phone number Sign-up page 

 

The personal data we collect will be used for the following purposes: 

 

  • ●  Allowing you to access DataEgg
  • ●  Allowing you to access software purchased directly or by the partner.
    Our legal basis for processing for the personal data include ‘consent’ (the individual has given clear consent for you to process their personal data for a specific purpose) and ‘contract’ (the processing is necessary for a contract you have with the individual, or because they have asked you to take specific steps before entering into a contract).

4.2. Consent 

By consenting to this privacy notice you are giving us permission to process your personal data specifically for the purposes identified. Consent is required for DataEgg Ltd to process both types of personal data, but it must be explicitly given. Where we are asking you for sensitive personal data we will always tell you why and how the information will be used. You may withdraw consent at any time. 

 

4.3. Retention period 

DataEgg Ltd will process personal data for as long as required by our jv partner, their approved third parties and any direct services provided to individuals. DataEgg will only store the personal data for the retention period in line with the requirements of GDPR. 

4.4. Your rights as a data subject 

At any point while we are in possession of or processing your personal data, you, the data subject, have the following rights: 

 

● ● ● ● ● ● ● ● 

Right of access – you have the right to request a copy of the information that we hold about you.
Right of rectification – you have a right to correct data that we hold about you that is inaccurate or incomplete.
Right to be forgotten – in certain circumstances you can ask for the data we hold about you to be erased from our records.
Right to restriction of processing – where certain conditions apply to have a right to restrict the processing.
Right of portability – you have the right to have the data we hold about you transferred to another organisation.
Right to object – you have the right to object to certain types of processing such as direct marketing.
Right to object to automated processing, including profiling – you also have the right to be subject to the legal effects of automated processing or profiling.
Right to judicial review: in the event that Organisation Name refuses your request under rights of access, we will provide you with a reason as to why. You have the right to complain as outlined in clause 3.6 below. 

All of
involved in the processing of your personal data. 

the above requests will be forwarded on should there be a third party 

4.5. Complaints 

In the event that you wish to make a complaint about how your personal data is being processed by DataEgg Ltd (or third parties as described), or how your complaint has been handled, you have the right to lodge a complaint directly with the supervisory authority and DataEgg Ltd’s data protection DPO. 

 

5. Online privacy statement 

Personal data 

Under the EU’s General Data Protection Regulation (GDPR) personal data is defined as: 

“any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person”. 

How we use your information 

This privacy notice tells you how we, DataEgg Ltd, will collect and use your personal data for [outline further information on services and activities that you collect personal data, for example: cookies, profiling, complaints, subscriptions, etc.)] 

Why does DataEgg Ltd need to collect and store personal data? 

DataEgg collects Your personal information so that we can provide You with the Service and any related services You may request. In doing so, DataEgg may use the personal information we have collected from You for purposes related to the Services including to: 

  • ●  verify Your identity,
  • ●  administer the Service,
  • ●  notify You of new or changed services offered in relation to the Service,
  • ●  carry out marketing or training relating to the Service,
  • ●  assist with the resolution of technical support issues or other issues relating to
    the Service,
  • ●  comply with laws and regulations in applicable jurisdictions, and
  • ●  communicate with You.
    By using the Service, You consent to Your personal information being collected, held and used in this way and for any other use You authorise.In any event, we are committed to ensuring that the information we collect and use is appropriate for this purpose, and does not constitute an invasion of your privacy.
  • Will DataEgg Ltd share my personal data with anyone else?
    We may pass your personal data on to third-party service providers contracted to DataEgg Ltd in the course of dealing with you. Any third parties that we may share your data with are obliged to keep your details securely, and to use them only to fulfil the service they provide you on our behalf or on behalf of a school. When they no longer need your data to fulfil this service, they will dispose of the details in line with DataEgg Ltd’s procedures. If we wish to pass your sensitive personal data onto a third party we will only do so once we have obtained your consent, unless we are legally required to do otherwise.

 

How will DataEgg Ltd use the personal data it collects about me? 

DataEgg Ltd will process (collect, store and use) the information you provide in a manner compatible with the EU’s General Data Protection Regulation (GDPR). We will endeavour to keep your information accurate and up to date, and not keep it for longer than is necessary. DataEgg Ltd is required to retain information in accordance with the law, such as information needed for income tax and audit purposes. How long certain kinds of personal data should be kept may also be governed by specific business-sector requirements and agreed practices. Personal data may be held in addition to these periods depending on individual business needs. 

Under what circumstances will DataEgg Ltd contact me? 

Our aim is not to be intrusive, and we undertake not to ask irrelevant or unnecessary questions. Moreover, the information you provide will be subject to rigorous measures and procedures to minimise the risk of unauthorised access or disclosure. 

DataEgg can aggregate Your non-personally identifiable data 

By using the Service, You agree that DataEgg can access, aggregate and use non-personally identifiable data DataEgg has collected from You. This data will in no way identify You or any other individual. 

DataEgg may use this aggregated non-personally identifiable data to: 

  • ●  assist us to better understand how our customers are using the Service,
  • ●  provide our customers with further information regarding the uses and
    benefits of the Service,
  • ●  enhance school productivity, including by creating useful school insights from
    that aggregated data and allowing You to benchmark Your schools
    performance against that aggregated data, and
  • ●  otherwise to improve the Service.
  • Can I find out the personal data that the organisation holds about me?
    DataEgg Ltd at your request, can confirm what information we hold about you and how it is processed. If DataEgg Ltd does hold personal data about you, you can request the following information:
  • ●  Identity and the contact details of the person or organisation that has determined how and why to process your data. In some cases, this will be a representative in the EU.
  • ●  Contact details of the data protection officer, where applicable.
  • ●  The purpose of the processing as well as the legal basis for processing.
  • ●  If the processing is based on the legitimate interests of DataEgg Ltd or a third
    party, information about those interests.
  • ●  The categories of personal data collected, stored and processed.
  • ●  Recipient(s) or categories of recipients that the data is/will be disclosed to.
  • ●  If we intend to transfer the personal data to a third country or international organisation, information about how we ensure this is done securely. The EU has approved sending personal data to some countries because they meet a minimum standard of data protection. In other cases, we will ensure there are specific measures in place to secure your information.
  • ●  How long the data will be stored.
  • ●  Details of your rights to correct, erase, restrict or object to such processing.
  • ●  Information about your right to withdraw consent at any time.
  • ●  How to lodge a complaint with the supervisory authority.
  • ●  Whether the provision of personal data is a statutory or contractual
    requirement, or a requirement necessary to enter into a contract, as well as whether you are obliged to provide the personal data and the possible consequences of failing to provide such data.
  • ●  The source of personal data if it wasn’t collected directly from you.
  • ●  Any details and information of automated decision making, such as profiling,
    and any meaningful information about the logic involved, as well as the significance and expected consequences of such processing.
  • What forms of ID will I need to provide in order to access this?
    DataEgg Ltd accepts the following forms of ID when information on your personal data is requested:
  • ●  Passport
  • ●  Driving licence
  • ●  Birth certificate

Copyright © 2018 DataEgg Ltd. All rights reserved.

Cookie Policy

Cookie policy DataEgg

This website, like most others, uses cookies to help provide you with the best browsing experience.

Cookies are small text files that are placed on your computer or mobile device when you first visit a website or page.

We use cookies to:

  • Make our website work as you’d expect
  • Improve the speed/security of the site
  • Allow you to share pages on social networks
  • Make improvements to our website by seeing how users navigate around it

We do not use cookies to:

  • Collect any personally identifiable information (without your express permission)
  • Collect any sensitive information (without your express permission)
  • Pass data to advertising networks
  • Pass personally identifiable data to third parties

Giving us permission to use cookies

If your browser is set to accept cookies, we take this, and your continued use of our site as acceptance of our cookie policy. If you wish not to accept the use of cookies, or to delete any that have already been set, you can find out how below. Please bear in mind that some features on our website might not work correctly with cookies disabled.

Our cookies

  • DataEgg

These are session cookies. Session Cookies are only stored temporarily and are deleted from the user’s device when the browser is closed.

Anonymous visitor statistics

We use Google Analytics to measure how our site is used by visitors and to generate reports for our own use. Google Analytics does not collect any personal information about you. The following cookies are set by Google Analytics:

  • _utma
  • _utmb
  • _utmc
  • _utmz

Third party cookies:

TWITTER

We may use Twitter to feed the latest news about DataEgg™ to our website, and Twitter sets the following cookies:

  • guest_id
  • k
  • original_referer
  • _twitter_sess

Managing cookies

If you want to, you can usually stop your browser accepting cookies from all sites, or stop it accepting cookies from a particular website. However, as cookies are a standard part of most modern websites, this will probably limit the functionality of not only our site but many others too.

You can find the tools to manage cookies in the ‘preferences’ or ‘tools’ menu of your browser. Below are links to instructions for the four main browsers, otherwise you should use the ‘Help’ option in your browser for more details.

Pin It on Pinterest

Share This