diff --git a/Target/Dark/Image/GitHub/Astro.svg b/Target/Dark/Image/GitHub/Astro.svg index a1d3a108..316afa57 100644 --- a/Target/Dark/Image/GitHub/Astro.svg +++ b/Target/Dark/Image/GitHub/Astro.svg @@ -1 +1,24 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + diff --git a/Target/Dark/Image/GitHub/Land.svg b/Target/Dark/Image/GitHub/Land.svg index e110e38c..d5de173d 100644 --- a/Target/Dark/Image/GitHub/Land.svg +++ b/Target/Dark/Image/GitHub/Land.svg @@ -1 +1,7 @@ - \ No newline at end of file + + + + + diff --git a/Target/Dark/Image/GitHub/tailwindcss.svg b/Target/Dark/Image/GitHub/tailwindcss.svg index 42ba51ce..3565dc2e 100644 --- a/Target/Dark/Image/GitHub/tailwindcss.svg +++ b/Target/Dark/Image/GitHub/tailwindcss.svg @@ -1 +1,8 @@ - \ No newline at end of file + + + + diff --git a/Target/Favicon/safari-pinned-tab.svg b/Target/Favicon/safari-pinned-tab.svg index 31379f7a..c3ed5ec0 100644 --- a/Target/Favicon/safari-pinned-tab.svg +++ b/Target/Favicon/safari-pinned-tab.svg @@ -1 +1,27 @@ - \ No newline at end of file + + + + + Created by potrace 1.14, written by Peter Selinger 2001-2017 + + + + + diff --git a/Target/Font/AlbertSans100.svg b/Target/Font/AlbertSans100.svg index 9d04908c..096c9ab9 100644 --- a/Target/Font/AlbertSans100.svg +++ b/Target/Font/AlbertSans100.svg @@ -1 +1,411 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans100Italic.svg b/Target/Font/AlbertSans100Italic.svg index 2796e256..0de04e85 100644 --- a/Target/Font/AlbertSans100Italic.svg +++ b/Target/Font/AlbertSans100Italic.svg @@ -1 +1,426 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans200.svg b/Target/Font/AlbertSans200.svg index 51349378..64af2844 100644 --- a/Target/Font/AlbertSans200.svg +++ b/Target/Font/AlbertSans200.svg @@ -1 +1,412 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans200Italic.svg b/Target/Font/AlbertSans200Italic.svg index 0344a5ce..523ce08c 100644 --- a/Target/Font/AlbertSans200Italic.svg +++ b/Target/Font/AlbertSans200Italic.svg @@ -1 +1,426 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans300.svg b/Target/Font/AlbertSans300.svg index cc04c66b..a2938ee2 100644 --- a/Target/Font/AlbertSans300.svg +++ b/Target/Font/AlbertSans300.svg @@ -1 +1,412 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans300Italic.svg b/Target/Font/AlbertSans300Italic.svg index 76e536da..916028c3 100644 --- a/Target/Font/AlbertSans300Italic.svg +++ b/Target/Font/AlbertSans300Italic.svg @@ -1 +1,425 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans500.svg b/Target/Font/AlbertSans500.svg index f3f92f34..fbfcce50 100644 --- a/Target/Font/AlbertSans500.svg +++ b/Target/Font/AlbertSans500.svg @@ -1 +1,413 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans500Italic.svg b/Target/Font/AlbertSans500Italic.svg index 8a902512..2560a63d 100644 --- a/Target/Font/AlbertSans500Italic.svg +++ b/Target/Font/AlbertSans500Italic.svg @@ -1 +1,425 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans600.svg b/Target/Font/AlbertSans600.svg index 5bfdf67a..0bbc1972 100644 --- a/Target/Font/AlbertSans600.svg +++ b/Target/Font/AlbertSans600.svg @@ -1 +1,412 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans600Italic.svg b/Target/Font/AlbertSans600Italic.svg index 92172931..78457965 100644 --- a/Target/Font/AlbertSans600Italic.svg +++ b/Target/Font/AlbertSans600Italic.svg @@ -1 +1,427 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans700.svg b/Target/Font/AlbertSans700.svg index 9795d81c..6ea3718a 100644 --- a/Target/Font/AlbertSans700.svg +++ b/Target/Font/AlbertSans700.svg @@ -1 +1,415 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans700Italic.svg b/Target/Font/AlbertSans700Italic.svg index 74daa103..903b2900 100644 --- a/Target/Font/AlbertSans700Italic.svg +++ b/Target/Font/AlbertSans700Italic.svg @@ -1 +1,427 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans800.svg b/Target/Font/AlbertSans800.svg index 37145121..d9a0da15 100644 --- a/Target/Font/AlbertSans800.svg +++ b/Target/Font/AlbertSans800.svg @@ -1 +1,415 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans800Italic.svg b/Target/Font/AlbertSans800Italic.svg index d564c099..e105d594 100644 --- a/Target/Font/AlbertSans800Italic.svg +++ b/Target/Font/AlbertSans800Italic.svg @@ -1 +1,427 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans900.svg b/Target/Font/AlbertSans900.svg index f58fbc7d..cdc6722b 100644 --- a/Target/Font/AlbertSans900.svg +++ b/Target/Font/AlbertSans900.svg @@ -1 +1,415 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSans900Italic.svg b/Target/Font/AlbertSans900Italic.svg index ac22d548..1d18ad01 100644 --- a/Target/Font/AlbertSans900Italic.svg +++ b/Target/Font/AlbertSans900Italic.svg @@ -1 +1,426 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSansItalic.svg b/Target/Font/AlbertSansItalic.svg index 14af90c0..75f424ab 100644 --- a/Target/Font/AlbertSansItalic.svg +++ b/Target/Font/AlbertSansItalic.svg @@ -1 +1,426 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Font/AlbertSansRegular.svg b/Target/Font/AlbertSansRegular.svg index 5ae87da4..dbe8c126 100644 --- a/Target/Font/AlbertSansRegular.svg +++ b/Target/Font/AlbertSansRegular.svg @@ -1 +1,413 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/GDPR/index.html b/Target/GDPR/index.html index 13dc86a3..5ff594a3 100644 --- a/Target/GDPR/index.html +++ b/Target/GDPR/index.html @@ -1 +1,1673 @@ -Personal Data Protection Policy

PERSONAL DATA PROTECTION POLICY

Effective date: 05.25.2018 / May 25th 2018
Last updated: 02.11.2022 / February 11th 2022

We at PlayForm ltd. are committed to processing personal data securely and respecting privacy of the concerned individuals.

Version No. and date of the last update:

v. 1.0.

February 11th 2022

This policy shall be reviewed annually or each time when the changes in our data processing occur.

Scope and Definitions

  1. Scope. This Personal Data Protection Policy (the “Policy”) describes PlayForm ltd. internal rules for personal data processing and protection. The Policy applies to PlayForm ltd., including PlayForm ltd. employees and contractors (“we”, “us”, “our”, “PlayForm”). The management of each entity is ultimately responsible for the implementation of this policy, as well as to ensure, at entity level, there are adequate and effective procedures in place for its implementation and ongoing monitoring of its adherence. For the purposes of this Policy, employees and contractors are jointly referred to as the “employees”.

  2. Privacy Manager. Privacy Manager is an employee of PlayForm responsible for personal data protection compliance within PlayForm (the “Privacy Manager”). The Privacy Manager is in charge of performing the obligations imposed by this Policy and supervising other employees, who subject to this Policy, regarding their adherence to this Policy. The Privacy Manager must be involved in all projects at an early stage in order to take personal data protection aspects into account as early as the planning phase.
    The designated Privacy Manager at PlayForm ltd. is Nikola Hristov Nikola@PlayForm.LTD.

  3. Definitions.

Competent Supervisory Authoritymeans a public authority that is responsible for regulating and supervising personal data protection with regards to activities of PlayForm.
Data Breach

means a breach of the security and/or confidentiality leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data transmitted, stored or otherwise processed.

This includes but is not limited to e-mails sent to an incorrect or disclosed list of recipients, an unlawful publication of the Personal Data, loss or theft of physical records, and unauthorized access to personal information.

Data Controllermeans the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines (make a decision) the purposes and means of the processing of Personal Data.
Data Processormeans a natural or legal person, public authority, agency or other body which processes the Personal Data on behalf of the data controller.
Data Protection Lawsmean any laws and legal rules on personal data use and protection applicable to the activities of PlayForm, including, but not limited to the Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation, GDPR).
Data Subject Request (DSR)means any request from the Data Subject and concerning their personal data and/or data subject rights.
Data Subjectmeans a natural person, whose Personal Data we process. Data Subjects include but are not limited to users, website visitors, employees, contractors, and partners of PlayForm.
Personal Datameans any information relating to an identified or identifiable Data Subject; a Data Subject can be identified by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or the combination of factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that Data Subject.
Processingmeans any operation or set of operations which is performed by PlayForm on Personal Data, such as 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.
Standard Contractual Clausesmeans the European Commission Decision of February, 5 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC of the European Parliament and of the Council (2010/87/EU).
Third Partymeans a natural or legal person, who accesses the Personal Data for further processing and is not an employee, member or corporate affiliate of PlayForm. This definition does not apply to natural persons, who provide services to PlayForm as contractors on a regular basis.
Usermeans a Data Subject who uses our services provided on PlayForm website.

Data Processing Principles

  1. PlayForm’s processing activities must be in line with the principles specified in this Section. The Privacy Manager must make sure that PlayForm’s compliance documentation, as well as data processing activities, are compliant with the data protection principles.

  2. We must process the Personal Data in accordance with the following principles:

    1. Lawfully, fairly and in a transparent manner (lawfulness, fairness and transparency). We shall always have a legal ground for the processing (described in Section 3 of this Policy), collect the amount of data adequate to the purpose and legal grounds, and we make sure the Data Subjects are aware of the processing;

    2. Collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes (purpose limitation). We must not process the Personal Data for the purposes not specified in our compliance documentation without obtaining specific approval of the Privacy Manager;

    3. Adequate, relevant and limited to what is necessary for the purposes for which they are processed (data minimization). We always make sure the data we collect is not excessive and limited by the strict necessity;

    4. Accurate and, where necessary, kept up to date (accuracy). We endeavor to delete inaccurate or false data about Data Subjects and make sure we update the data. Data Subjects can ask us for a correction of the Personal Data;

    5. Kept in a form which permits identification of Data Subjects for no longer than is necessary for the purposes for which the Personal Data are processed (storage period limitation). The storage periods must be limited as prescribed by Data Protection Laws and this Policy; and

    6. Process in a manner that ensures appropriate security of the Personal Data, including protection against unauthorized or unlawful processing and accidental loss, destruction or damage, using appropriate technical or organizational measures (confidentiality, integrity, and availability).

  3. Accountability.

    1. We shall be able to demonstrate our compliance with Data Protection Laws (accountability principle). In particular, we must ensure and document all relevant procedures, efforts, internal and external consultations on personal data protection including:

      • the fact of appointing a person responsible for PlayForm’s data protection compliance;

      • where necessary, a record of a Data Processing Impact Assessment;

      • developed and implemented notices, policies, and procedures, such as Privacy Notice, this policy or Data Breach response procedure;

      • the fact of staff training on compliance with Data Protection laws; and

      • assessment, implementation, and testing organizational and technical data protection measures.

    2. The Privacy Manager must maintain PlayForm’s Records of processing activities, which is an accountability document that describes personal data processing activities of PlayForm, prepared in accordance with Art. 30 of the GDPR (the “Records of processing activities”). The Records of processing activities must maintain, at least, the following information about each processing activity:

      • contact details of PlayForm, the EU Representative, and, where applicable, of the Data Protection Officer;

      • name of the activity, its purposes and legal basis along with, where applicable, the legitimate interests of PlayForm;

      • data subjects and personal data categories concerned;

      • data retention periods;

      • general description of applicable security measures;

      • recipients, including joint controllers, processors, and contractors involved, as well as the fact of the international data transfer with the safeguards applied to the transfer;

      • where applicable, a reference to the Data Processing Impact Assessment;

      • where applicable, a reference to the record of the data breach occurred involving the personal data;

      • if PlayForm acts as a data processor, the information to be provided includes the names and contact details of controllers, name and contact details of controller’s representative (if applicable), categories of processing (activities), names of third countries or international organizations that personal data are transferred to (if applicable), safeguards for exceptional transfers of personal data to third countries or international organizations (if applicable), and general description of technical and organizational security measures.

  1. Legal grounds.

    1. Each processing activity must have one of the lawful grounds specified in this Section to process the Personal Data. If we do not have any of the described, we cannot collect or further process the Personal Data.

    2. If PlayForm is intended to use personal data for other purposes than those specified in the Records of processing activities, the Privacy Manager must evaluate, determine, and, if necessary, collect/record the appropriate legal basis for it.

    3. Performance of the contract. Where PlayForm has a contract with the Data Subject, e.g., website’s Terms of Use or the employment contract, and the contract requires the provision of personal data from the Data Subject, the applicable legal ground will be the performance of the contract.

    4. Consent. To process the personal data based on the consent, we must obtain the consent before the Processing and keep the evidence of the consent with the records of Data Subject’s Personal Data. The Privacy Manager must make sure that the consent collected from Data Subjects meet the requirements of Data Protection Laws and this Policy. In particular, the Privacy Manager must make sure that:

      • the Data Subject must be free to give or refuse to give consent.

      • the consent is in the form of an active indication from the Data Subject, i.e., the consent checkbox must not be pre-ticked for the user.

      • the request for the consent clearly articulates the purposes of the processing, and other information specified in Subsection 6.2 is available to the Data Subject.

      • the Data Subject must be free to give one’s consent or to revoke it.

    5. Legitimate interests. We have the right to use personal data in our ‘legitimate interests’. The interests can include the purposes that are justified by the nature of our business activities, such as the marketing analysis of personal data. For PlayForm to use legitimate interests as a legal ground for the processing, the Privacy Manager must make sure that:

      • the legitimate interest in the processing is clearly defined and recorded in the Records of processing activities;

      • any envisaged risks to Data Subject rights and interests are spotted. The examples of the risks can be found in Subsection 7.2.;

      • the Data Subjects have reasonable expectations about the processing, and additional protective measures to address the risks are taken;

      • subject to the conditions of Subsection 6.7 (Right to object against the processing), the Data Subject is provided with the opportunity to opt-out from the processing for the described legitimate interests.
        If at least one of the above conditions is not met by PlayForm, the Privacy Manager must choose and propose a different legal ground for the processing, such as consent.

    6. Legal Compliance and Public Interest. Besides the grounds specified afore, we might be requested by the laws of the European Union or laws of the EU Member State to process Personal Data of our Users. For example, we can be required to collect, analyze, and monitor the information of Users to comply with financial or labor laws.
      Whenever we have such an obligation, we must make sure that:

      • we process personal data strictly in accordance with relevant legal requirements;

      • we do not use or store the collected Personal Data for other purposes than legal compliance; and

      • the Data Subjects are properly and timely informed about our obligations, scope, and conditions of personal data processing.

Important: Where PlayForm has the law requirements of another country to process personal data, the Privacy Manager must propose using another legal ground for the processing under Data Protection Laws, such as legitimate interests or consent.

Access to Personal Data

  1. Access to Personal Data.

    1. The employees must have access to the personal data on a “need-to-know” basis. The data can be accessed only if it is strictly necessary to perform one of the activities specified in the Records of processing activities. The employees and contractors shall have access to the Personal Data only if they have the necessary credentials for it.

    2. Heads of the departments within PlayForm are responsible for their employees’ access and processing of personal data. The heads must maintain the list of employees that are entitled to access and process personal data. The Privacy Manager shall have the right to review the list and, where necessary, request the amendments to meet the requirements of this Policy.

    3. Heads of the departments within PlayForm must ensure that the employees under their supervision are aware of the Data Protection Laws and comply with the rules set in this Policy. To make sure our employees are able to comply with the data protection requirements, we must provide them with adequate data protection training.

    4. All employees accessing personal data shall keep strict confidentiality regarding the data they access. The employees that access personal data must use only those means (software, premises, etc.) for the processing that were prescribed by PlayForm. The data must not be disclosed or otherwise made available out of the management instructions.

    5. The employees within their competence must assist PlayForm’s representatives, including the Privacy Manager, in any efforts regarding compliance with Data Protection Laws and/or this Policy.

    6. When an employee detects or believes there is suspicious activity, data breach, non-compliance with Data Protection Laws and/or this Policy, or a DSR was not routed to the competent department within PlayForm, the employee must report such activity to the Privacy Manager.

    7. Employees that are unsure about whether they can legitimately process or disclose Personal Data must seek advice from the Privacy Manager before taking any action.

    8. Any occasional access to personal data for activities not specified in the Records of processing activities is prohibited. If there is a strict necessity for immediate access, the Privacy Manager must approve the access first.

Third Parties

  1. Before sharing personal data with any person outside of PlayForm, the Privacy Manager must ensure that this Third Party has an adequate data protection level and provide sufficient data protection guarantees in accordance with Data Protection Laws, including, but not limited to the processorship requirements (Art. 28 of the GDPR) and international transfers compliance (Section 5 of the GDPR). Where necessary, the Privacy Manager must make sure that PlayForm enters into the appropriate data protection contract with the third party.

  2. An employee can share personal data with third parties only if and to the extent that was directly prescribed by the manager and specified in the Records of processing activities.

  3. If we are required to delete, change, or stop the processing of the Personal Data, we must ensure that the Third Parties, with whom we shared the Personal Data, will fulfill these obligations accordingly.

  4. Whenever PlayForm is engaged as a data processor on behalf of another entity, the Privacy Manager must make sure PlayForm complies with the processorship obligation. In particular, the appropriate data processing agreement in accordance with the Data Protection Laws must be in place. The Privacy Manager must supervise the compliance with data processing instructions from the controller, including regarding the scope of processing activities, involvement of sub-processors, international transfers, storage, and further disposal of processed personal data. The personal data processed under the processor role must not be processed for any other purposes than specified in the relevant instructions, agreement or other legal act regulating the relationships with the controller.

International Transfers

  1. If we have the employees, contractors, corporate affiliates, or Data Processors outside of the EEA, and we transfer Personal Data to them for the processing, the Privacy Manager must make sure PlayForm takes all necessary and appropriate safeguards in accordance with Data Protection Laws.

  2. The Privacy Manager must assess the safeguards available and propose to the PlayForm’s management the appropriate safeguard for each international transfer. The following regimes apply to the transfers of Personal Data outside of the EU:

    • where the European Commission decides that the country has an adequate level of personal data protection, the transfer does not require taking additional safeguards. The full list of adequate jurisdictions can be found on the relevant page of the European Commission’s website1.

    • to transfer Personal Data to our contractors or partners (Data Processors or Controllers) in other third countries, we must conclude Standard Contractual Clauses with that party. The draft version along with the guidance can be found on the relevant page of the European Commission’s website2;

    • if we have a corporate affiliate or an entity in other countries, we may choose to adopt Binding Corporate Rules in accordance with Article 47 of the GDPR or an approved code of conduct pursuant to Article 40 of the GDPR;

    • we also can transfer Personal Data to entities that have an approved certification in accordance with Article 42 of the GDPR, which certifies an appropriate level of company’s data protection.

  1. As a part of the information obligations, PlayForm must inform the Data Subjects that their Personal Data is being transferred to other countries, as well as provide them with the information about the safeguards used for the transfer. The information obligation is to be performed in accordance with Subsection 6.2.

  2. In the exceptional cases (the “Derogation”), where we cannot apply the safeguards mentioned afore and we need to transfer Personal Data, we must take an explicit consent (active statement) from the Data Subject or it must be strictly necessary for the performance of the contract between us and the Data Subject, or other derogation conditions apply in accordance with the Data Protection Laws. The Privacy Manager must pre-approve any Derogation transfers and document the approved Derogations, as well as the rationale for them.

Rights of Data Subjects

  1. Our Responsibilities.

    1. Privacy Manager is ultimately responsible for handing all DSR received by PlayForm. In the case of receiving any outstanding or unusual DSR, the employee must seek advice from the Privacy Manager before taking any action.

    2. DSR Team within PlayForm is responsible for handling DSRs from PlayForm Users on a daily basis. The Human Resources department is responsible for handling the DSR from PlayForm employees.

    3. All DSRs from the Users must be addressed at and answered from the following e-mail address: DSR@PlayForm.LTD. DSR from the employees can be addressed directly to the HR manager or at DSR@PlayForm.LTD.

    4. The responsible employee must answer to the DSR within one (1) month from receiving the request. If complying with the DSR takes more than one month in time, the responsible employee must seek advice from the Privacy Manager and, where necessary, inform the Data Subject about the prolongation of the response term for up to two (2) additional months.

    5. The responsible employee must analyze the received DSR for the following criteria:

      • Data Subject identification. Before considering the DSR content, the responsible employee must make sure the Data Subject is the same person he/she claims to be. For this purpose, the connection between the personal data records and the data subject must be established.

      • Personal data. The responsible employee must check whether PlayForm has access to the personal data requested. If PlayForm does not have the personal data under the control, the responsible employee must inform the Data Subject, and, if possible, instruct on the further steps on how to access the data in question;

      • Content of the request. Depending on the content of the DSR, the responsible employee must define the type of the request and check whether it meets the conditions prescribed by this Policy and Data Protection Laws. The types of requests and the respective conditions for each of them can be consulted in Subsections 6.3-6.9. If the request does not meet the described criteria, the responsible employee must refuse to comply with the DSR and inform the Data Subject about the reasons for refusing;

      • Free of charge. Generally, all requests of Data Subjects and exercises of their rights are free of charge. If the responsible employee finds that the Data Subject exercises the rights in an excessive or unfound way (e.g., intended to harm or interrupt PlayForm’s business activities), the employee must seek the advice from the Privacy Manager, and, upon receiving of the latter, may either charge the Data Subject a reasonable fee or refuse to comply with the request;

      • Documenting. Whenever PlayForm receives the DSR, the Privacy Manager must make sure that the data and time, Data Subject, type of the request and the decision made regarding it are well documented. In the case of refusing to comply with the request, the reasons for refusing must be documented as well;

      • Recipients. When addressing the DSR, the Privacy Manager must make sure that all concerned recipients were informed the necessary actions were taken.

  2. The right to be informed.

    1. PlayForm must notify each Data Subject about the collection and further processing of the Personal Data.

    2. The information to be provided includes: the name and contact details of PlayForm; generic purposes of and the lawful basis for the data collection and further processing; categories of Personal Data collected; recipients/categories of recipients; retention periods; information about data subject rights, including the right to complain to the competent Supervisory Authority; the consequences of the cases where the data is necessary for the contract performance and the Data Subject does not provide the required data; details of the safeguards where personal data is transferred outside the EEA; and any third-party source of the personal data, without specification for the particular case (except if we receive the direct request from the Data Subject).

    3. The Users must be informed by the Privacy Policy accessible at PlayForm’s website and provided during the user registration. The employees and contractors must be informed by a standalone employee privacy statement, which explains the details described in p. 6.2.2 in a case-based manner, describing the particular purposes and activities.

    4. PlayForm must inform Data Subjects about data processing, including any new processing activity introduced at PlayForm within the following term:

      • if personal data is collected from the data subject directly, the data subject must be informed at the time we collect Personal Data from the Data Subjects by showing the Data Subject our privacy statement;

      • if the personal data is collected from other sources: (a) within one month from collecting it; (b) if the personal data are to be used for communication with the data subject, at the latest at the time of the first communication to that data subject; or (c) if a disclosure to another recipient is envisaged, at the latest when the personal data are first disclosed.

      • upon the request of the Data Subject; and

      • within one (1) month after any change of our personal data practices, change of the controller of Personal Data or after significant changes in our privacy statements.

  3. The right to access the information.

    1. The Data Subject must be provided only with those personal data records specified in the request. If the Data Subject requests access to all personal data concerning her or him, the employee must seek advice from the Privacy Manager first, to make sure all personal data of the Data Subject is mapped and provided.

    2. A Data Subject has the right to:

      • learn if we process the Data Subject’s Personal Data;

      • obtain disclosure regarding aspects of the processing, including detailed and case-specific information on purposes, categories of Personal Data, recipients/categories of recipients, retention periods, information about one’s rights, details of the relevant safeguards where personal data is transferred outside the EEA, and any third-party source of the personal data; and

      • obtain a copy of the Personal Data undergoing processing upon the request.

  4. The right to verify the Data Subject’s information and seek its rectification. The information we collect can be/become inaccurate or out-of-date (e.g., mistakes in nationality, date of birth, info on debts, economic activities). If we reveal that the Personal Data is inaccurate or the Data Subject requests us to do so, we must ensure that we correct all mistakes and update the relevant information.

  5. The right to restrict processing.

    1. The restriction of processing allows Data Subjects to temporarily stop the use of their information to prevent the possible harm caused by such use.

    2. This right applies when the Data Subject:

      • contests the accuracy of the Personal Data;

      • believes that we process the Personal Data unlawfully; and

      • objects against the processing and wants us not to process Personal Data while we are considering the request.

    3. In the case of receiving the restriction request, we must not process Personal Data in question for any other purpose than storing it or for legal compliance purposes until the circumstances of restriction cease to exist.

  6. The right to withdraw the consent. For the activities that require consent, the Data Subject can revoke their consent at any time. If the Data Subject revokes the consent, we must record the changes and must not process the Personal Data for consent-based purposes. The withdrawal of consent does not affect the lawfulness of the processing done before the withdrawal.

  7. The right to object against the processing.

    1. If we process the information in our legitimate interests, e.g., for direct marketing emails or for our marketing research purposes, the Data Subject can object against the processing.

    2. In the case of receiving the objection request case, we must consider Data Subject’s request and, where we do not have compelling interests, stop the processing for the specified purposes. If the personal data is still to be processed for other purposes, the Privacy Manager must make sure that the database has a record that the data cannot be further processed for the objected activities.

    3. The objection request can be refused only if the personal data in question is used for scientific/historical research or statistical purposes and was appropriately protected, i.e., by anonymization or pseudonymization techniques.

  8. Right to erasure/to be forgotten.

    1. The Data Subjects have the right to request us to erase their Personal Data if one of the following conditions are met:

      • Personal Data is no longer necessary for the purposes of collection. For example, a user has provided personal data for a one-time activity, such as data validation or participation in a contest, and the purpose is already fulfilled;

      • the Data Subject revokes one’s consent or objects to the processing (where applicable) and there is no other legal ground for the processing; or

      • we process the Personal Data unlawfully or its erasure is required by the applicable legislation of the European Union or one of the Member countries of the European Union.

    2. Conditions, under which we have the right to refuse the erasure:

      • Personal Data is processed for scientific/historical research or statistical purposes and is appropriately protected, i.e., pseudonymized or anonymized;

      • Personal Data is still necessary for legal compliance (e.g., financial or labor laws compliance).

    3. Only those personal data records must be deleted that were specified in the request. If the Data Subject requests the deletion of all personal data concerning her or him, the employee must seek advice from the Privacy Manager first, to make sure all the data about the Data Subject is mapped and can be deleted.

    4. If the User still has an account with us and requests the erasure of information necessary for maintaining the account, we must inform the User that the erasure will affect user experience or can lead to the closure of the account.

  9. Data portability.

    1. Data Subjects can ask us to transfer all the Personal Data and/or its part in a machine-readable format to a third party. This right applies in two cases:

      • personal data was collected for the purpose of provision of our services (performance of the contract); or

      • collected based on consent.

    2. To determine whether one of the p.6.9.1 conditions are met, the employee must seek advice from the Privacy Manager and check the applicable legal basis in the Records of processing activities. If the answer is negative, the request can be refused by PlayForm, and the Privacy Manager must decide whether to comply with the request on a voluntary basis.

    3. To comply with the request, the responsible employee must consolidate requested Personal Data and send the data in the format we are usually working with to the requested organization. The Data Subject must provide the necessary contact details of the organization.

New Data Processing Activities

  1. Notification to Privacy Manager.

    1. Before introducing any new activity that involves the processing of personal data, an employee responsible for its implementation must inform the Privacy Manager.

    2. Upon receiving information about a new activity, Privacy Manager must:

      • determine whether the data processing impact assessment (DPIA) and/or the consultation with the Supervisory Authority is necessary. If the answer is positive, the Privacy Manager must make sure the DPIA is conducted and/or the Supervisory Authority is consulted in accordance with the requirements of this Section and Data Protection Laws;

      • determine the legal basis for the processing and, where necessary, take further action for its fixation;

      • make sure the processing activity is done in accordance with this Policy, other PlayForm’s policies, as well as the Data Protection Laws;

      • add the processing activity to the Records of processing activities;

      • amend the privacy information statements and, where necessary, inform the concerned Data Subject accordingly.

  2. Data Processing Impact Assessment.

    1. To make sure that our current or prospective processing activities do not/will not violate the Data Subjects’ rights, PlayForm must, where required by Data Protection Laws, conduct the Data Processing Impact Assessment (DPIA), a risk-based assessment of the processing and search for the measures to mitigate the risks. The Privacy Manager must make sure the DPIA is conducted in accordance with this Section.

    2. The Privacy Manager, where necessary, involving the competent employees and/or external advisors, must conduct a DPIA if at least one of the following conditions are met:

      • the processing involves the use of new technologies, such as the Artificial Intelligence, use of connected and autonomous devices, etc. that creates certain legal, economic or similar effects to the Data Subject;

      • we systematically assess and evaluate personal aspects of the Data Subjects based on automated profiling, assigning the personal score/rate, and create legal or similar effects for the Data Subject by this activity;

      • we process on a large-scale sensitive data, which includes Personal Data relating to criminal convictions and offences, the data about vulnerable data subjects, the 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;

      • we collect or process Personal Data from a publicly accessible area or public sources on a large scale, or combine or match two different data sets; and

      • the Supervisory Authority in its public list requires conducting a DPIA for a certain type of activity we are involved in. The list of processing activities requiring conducting DPIA can be found on the website of each Supervisory Authority.

    3. The assessment shall contain at least the following details:

      • a systematic description of the processing operations and the purposes of the processing, including, where applicable, the legitimate interest pursued by us. The description must include the envisaged data categories and data subjects concerned, the scale of processing activities, such as its frequency, volume, envisaged number of records, etc.; recipients of the data, retention periods and, where applicable, international transfers;

      • an assessment of the necessity and proportionality of the processing operations in relation to the purposes. The DPIA must explain whether the activity is necessary for the purpose and whether the purpose can be achieved by less intrusive methods;

      • an assessment of the risks to the rights and freedoms of data subjects, including the rights of Data Subjects regarding their Personal Data.

      • The examples of risks are the processing which could lead to physical, material or non-material damage, in particular: where the processing may give rise to discrimination, identity theft or fraud, financial loss, damage to the reputation, loss of confidentiality of personal data protected by professional secrecy, unauthorized reversal of pseudonymization, or any other significant economic or social disadvantage; where data subjects might be deprived of their rights and freedoms or prevented from exercising control over their personal data; where personal data are processed which reveal racial or ethnic origin, political opinions, religion or philosophical beliefs, trade union membership, and the processing of genetic data, data concerning health or data concerning sex life or criminal convictions and offences or related security measures; where personal aspects are evaluated, in particular analyzing or predicting aspects concerning performance at work, economic situation, health, personal preferences or interests, reliability or behavior, location or movements, in order to create or use personal profiles; where personal data of vulnerable natural persons, in particular of children, are processed; or where processing involves a large amount of personal data and affects a large number of data subjects; and

      • the measures to address the risks, including safeguards, security measures, and mechanisms to ensure the protection of personal data and to demonstrate compliance with this Regulation.

    4. Where the DPIA did not provide how to effectively address the risks, the Privacy Manager must initiate the consultation with the competent Supervisory Authority to receive help with searching for the solution. In this case, PlayForm must not conduct the activity before the Supervisory Authority approves the processing activity in question.

Data Retention

  1. General Rule.

    1. The Privacy Manager must make sure that PlayForm clearly defined the data storage periods and/or criteria for determining the storage periods for each processing activity it has. The periods for each processing activity must be specified in the Records of processing activities.

    2. Each department within PlayForm must comply with the data storage periods in accordance with the retention schedule provided in Records of processing activities. The Privacy Manager must supervise each department and make sure they comply with this requirement.

    3. After the storage period ends, the personal data must be removed from the disposal of the department responsible for the processing or, in cases where the data is not needed for any other purposes, destroyed completely, including from back-up copies and other media.

    4. Whenever the storage period for a processing activity has ended, but the personal data processed is necessary for other processing purposes, the department manager must make sure that the personal data is not used for the ceased processing activity, and the responsible employees do not have the access to it unless required for any other activity.

  2. Exemptions. The rules specified in Subsection 8.1 have the following exceptions:

    1. Business needs. Data retention periods can be prolonged, but no longer than 60 days, in the case that the data deletion will interrupt or harm our ongoing business. The Privacy Manager must approve any unforeseen prolongation;

    2. Technical impossibility. Some information is technically impossible or disproportionally difficult to delete. For example, deletion of the information may lead to breach of system integrity, or it is impossible to delete the information from the backup copies. In such a case, the information can be further stored, subject to the approval by the Privacy Manager and making respective amendments to the Records of processing activities; and

    3. Anonymization. The Personal Data can be further processed for any purposes (e.g., marketing) if we fully anonymize these data after the retention period is expired. This means that all personal identifiers and connections to them will be deleted from the data. To consider Personal Data anonymous, it must be impossible to reidentify the Data Subject from the data set.

Security

  1. Each department within PlayForm shall take all appropriate technical and organizational measures that protect against unauthorized, unlawful, and/or accidental access, destruction, modification, blocking, copying, distribution, as well as from other illegal actions of unauthorized persons regarding the personal data under their responsibility.

  2. The employee responsible for the supervision after the security of personal data within PlayForm shall be DSR Officer. This person implements the guidelines and other specifications on data protection and information security in his area of responsibility. He/she advises PlayForm management on the planning and implementation of information security in PlayForm, and must be involved in all projects at an early stage in order to take security-related aspects into account as early as the planning phase.

Data Breach Response Procedure

  1. Response Team.

    1. In case of revealing the Data Breach, CEO of PlayForm shall urgently form the Data Breach Response Team (the “Response Team”), which will handle the Data Breach, notify the appropriate persons, and mitigate its risks.

    2. The Response Team must be а multi-disciplinary group headed by CEO of PlayForm and comprised of the Privacy Manager, privacy laws specialist (whether internal or external), and knowledgeable and skilled information security specialists within PlayForm or outsourcing professionals, if necessary. The team must ensure that all employees and engaged contractors/processors adhere to this Policy and provide an immediate, effective, and skillful response to any suspected/alleged or actual Data Breach affecting PlayForm.

    3. The potential members of the Response Team must be prepared to respond to а Data Breach. The Response Team shall perform all the responsibilities of PlayForm mentioned in this Policy. The duties of the Response Team are:

      • to communicate the Data Breach to the competent Supervisory Authority(-ies);

      • in case of high risk to the rights and freedoms of Data Subjects, to communicate the Data Breach to the Data Subject;

      • if PlayForm obtain data from any third party as a processor, and a Data Breach involves obtained data, to inform the third parties about the Data Breach;

      • to communicate PlayForm’s contractors or any other third parties that process the Personal Data involved in the Data Breach; and

      • to take all appropriate technical and organizational measures to cease the Data Breach and mitigate its consequences;

      • to record the fact of the Data Breach in the Records of processing activities and file an internal data breach report that describes the event.

    4. The Response Team shall perform its duties until all the necessary measures required by this Policy are taken.

  2. Notification to Supervisory Authority.

    1. PlayForm shall inform the Competent Supervisory Authority about the Data Breach without undue delay and, where it is possible, not later than 72 hours after having become aware of the Data Breach.

    2. The Competent Supervisory Authority shall be determined by the residence of the Data Subjects, whose information was involved in the Data Breach. If the Data Breach concerns the Personal Data of Data Subjects from more than one country, PlayForm shall inform all Competent Supervisory Authorities.

    3. To address the notification to the authority, the Response Team should use Annex 1 to this Policy. Annex 1 contains all the necessary contact information of the EU supervisory authorities. If the Data Breach concerns Data Subjects from other than the EU countries, the Response Team shall ask a competent privacy specialist for advice.

    4. The notification to the Competent Supervisory Authority shall contain, at least, following information:

      • the nature of the Data Breach including where possible, the categories and an approximate number of Data Subjects and Personal Data records concerned;

      • the name and contact details of the Response Team, Privacy Manager or, if not applicable, of the CEO;

      • the likely consequences of the Data Breach. Explain PlayForm’s point of view on the purposes and possible further risks of the Data Breach. E.g., the Personal Data may be stolen for the further sale, fraud activities or blackmailing the concerned Data Subjects; and

      • the measures taken or proposed to be taken by PlayForm to address the Data Breach, including, where appropriate, measures to mitigate its possible adverse effects.

    5. To file a notification, the Response Team should use PlayForm’s Data Breach Notification Form to the Supervisory Authority.

  3. Notifications to Data Subjects.

    1. When the Data Breach is likely to result in a high risk to the rights and freedoms of Data Subjects (e.g., stealing of funds, assets, proprietary information), we must also communicate the Data Breach to the concerned Data Subjects without undue delay. The Privacy Manager must determine if there is a high risk based on the risk factors specified in Subsection 7.2.3 of this Policy.

    2. The notification shall contain the following information:

      • description of the Data Breach - what happened and what led to the Data Breach, such as a security breach, employee’s negligence, error in the system work. If the Response Team decided not to disclose the causes of the Data Breach, then this clause must not be mentioned;

      • the measures taken by PlayForm regarding the Data Breach, including security measures, internal investigations, and supervisory authority notice;

      • recommendations for the concerned Data Subjects how to mitigate risks and possible consequences, such as guidelines on how to restore access to an account, preventing measures (change of a password); and

      • the contact information of the Response Team or one of its members.

    3. The notification to the Data Subjects should be carried out by the email letter or, where it is impossible to use the email, by other available means of communication.

    4. Exemptions. We do not have to send the notification to the Data Subjects if any of the following conditions are met:

      • PlayForm has implemented appropriate technical and organizational protection measures, and those measures were applied to the Personal Data affected by the Data Breach, in particular, those that leave the Personal Data inaccessible to any person who is not authorized to access it, such as encryption;

      • PlayForm has taken subsequent measures which ensure that the high risk to the rights and freedoms of Data Subjects referred to in this section is no longer likely to materialize; or

      • it would involve a disproportionate effort to communicate with every concerned Data Subject. In such a case, there shall instead be a public communication or similar measure whereby the Data Subjects are informed in an equally effective manner.

In the case we apply one of the exemptions, we must document the circumstances, reason for not informing, and actions taken to meet one of the exemptions.

  1. Communication with Third Parties.

    1. In the case a Data Breach concerns the Personal Data shared with us or processed by us on behalf of a Third Party, we must also notify the Third Party about it within 24 hours. If we process the Personal Data as a Data Processor, the notification of the Third Party does not exempt us from the duty to mitigate the Data Breach consequences, but we must not inform the Competent Supervisory Authority and Data Subjects.

    2. In case of receiving the notification about the Data Breach from the Data Processor or other Third Parties that have access to the Personal Data, CEO of PlayForm shall, in accordance with this Section:

      • form the Response Team;

      • request the Third Party to send the information mentioned in Subsections 10.2-3 of this Policy;

      • where necessary, inform the Competent Supervisory Authority(-ies) and Data Subjects; and

      • perform other steps of the Data Breach response procedure.

List of Persons Briefed on Personal Data Protection Policy

Full Name

Status

Date

Nikola HristovBriefed05.25.2018

ANNEX 1 TO THE PERSONAL DATA PROTECTION POLICY

European National Data Protection Authorities

Austria

Österreichische Datenschutzbehörde
Hohenstaufengasse 3
1010 Wien
Tel. +43 1 531 15 202525
Fax +43 1 531 15 202690
E-mail: dsb@dsb.gv.at
WebSite: HTTPS://www.dsb.gv.at

Art 29 WP Member: Dr Andrea JELINEK, Director, Österreichische Datenschutzbehörde

Belgium

Commission de la protection de la vie privée
Commissie voor de bescherming van de persoonlijke levenssfeer
Rue de la Presse 35 / Drukpersstraat 35 1000 Bruxelles / 1000 Brussel
Tel. +32 2 274 48 00
Fax +32 2 274 48 35
E-mail: commission@privacycommission.be
WebSite: HTTPS://www.privacycommission.be

Art 29 WP Vice-President: Willem DEBEUCKELAERE, President of the Belgian Privacy commission

Bulgaria

Commission for Personal Data Protection
2, Prof. Tsvetan Lazarov Blvd. Sofia 1592
Tel. +359 2 915 3580
Fax +359 2 915 3525
E-mail: kzld@cpdp.bg
WebSite: HTTPS://www.cpdp.bg

Art 29 WP Member: Mr. Ventsislav KARADJOV, Chairman of the Commission for Personal Data Protection
Art 29 WP Alternate Member: Ms. Mariya MATEVA

Croatia

Croatian Personal Data Protection Agency
Martićeva 14
10000 Zagreb
Tel. +385 1 4609 000
Fax +385 1 4609 099
E-mail: azop@azop.hr or info@azop.hr
WebSite: HTTPS://www.azop.hr

Art 29 WP Member: Mr. Anto RAJKOVAČA, Director of the Croatian Data Protection Agency

Cyprus

Commissioner for Personal Data Protection
1 Iasonos Street,
1082 Nicosia
P.O. Box 23378, CY-1682 Nicosia Tel. +357 22 818 456
Fax +357 22 304 565
E-mail: commissioner@dataprotection.gov.cy
WebSite: HTTPS://www.dataprotection.gov.cy

Art 29 WP Member: Ms. Irene LOIZIDOU NIKOLAIDOU
Art 29 WP Alternate Member: Mr. Constantinos GEORGIADES

Czech Republic

The Office for Personal Data Protection
Urad pro ochranu osobnich udaju Pplk. Sochora 27
170 00 Prague 7
Tel. +420 234 665 111
Fax +420 234 665 444
E-mail: posta@uoou.cz
WebSite: HTTPS://www.uoou.cz

Art 29 WP Member: Ms. Ivana JANŮ, President of the Office for Personal Data Protection
Art 29 WP Alternate Member: Mr. Ivan PROCHÁZKA, Adviser to the President of the Office

Denmark

Datatilsynet
Borgergade 28, 5
1300 Copenhagen K
Tel. +45 33 1932 00
Fax +45 33 19 32 18
E-mail: dt@datatilsynet.dk
WebSite: HTTPS://www.datatilsynet.dk

Art 29 WP Member: Ms. Cristina Angela GULISANO, Director, Danish Data Protection Agency (Datatilsynet)
Art 29 WP Alternate Member: Mr. Peter FOGH KNUDSEN, Head of International Division at the Danish Data Protection Agency (Datatilsynet)

Estonia

Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)
Väike-Ameerika 19
10129 Tallinn
Tel. +372 6274 135
Fax +372 6274 137
E-mail: info@aki.ee
WebSite: HTTPS://www.aki.ee/en

Art 29 WP Member: Mr. Viljar PEEP, Director General, Estonian Data Protection Inspectorate
Art 29 WP Alternate Member: Ms. Maarja Kirss

Finland

Office of the Data Protection Ombudsman
P.O. Box 315
FIN-00181 Helsinki Tel. +358 10 3666 700
Fax +358 10 3666 735
E-mail: tietosuoja@om.fi
WebSite: HTTPS://www.tietosuoja.fi/en

Art 29 WP Member: Mr. Reijo AARNIO, Ombudsman of the Finnish Data Protection Authority
Art 29 WP Alternate Member: Ms. Elisa KUMPULA, Head of Department

France

Commission Nationale de l’Informatique et des Libertés - CNIL
8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02
Tel. +33 1 53 73 22 22
Fax +33 1 53 73 22 00
WebSite: HTTPS://www.cnil.fr

Art 29 WP Member: Ms. Isabelle FALQUE-PIERROTIN, President of CNIL
Art 29 WP Alternate Member: Ms. Florence RAYNAL

Germany

Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit
Husarenstraße 30
53117 Bonn
Tel. +49 228 997799 0; +49 228 81995 0
Fax +49 228 997799 550; +49 228 81995 550
E-mail: poststelle@bfdi.bund.de
WebSite: HTTPS://www.bfdi.bund.de

The competence for complaints is split among different data protection supervisory authorities in Germany.

Competent authorities can be identified according to the list provided under

HTTPS://www.bfdi.bund.de/EN/Service/Anschriften/Laender/Laender-node.html

Art 29 WP Member: Ms. Andrea VOSSHOFF, Federal Commissioner for Freedom of Information
Art 29 WP Alternate Member: Prof. Dr. Johannes CASPAR, representative of the federal states

Greece

Hellenic Data Protection Authority
Kifisias Av. 1-3, PC 11523 Ampelokipi Athens
Tel. +30 210 6475 600
Fax +30 210 6475 628
E-mail: contact@dpa.gr
WebSite: HTTPS://www.dpa.gr

Art 29 WP Member: Mr. Konstantinos Menoudakos, President of the Hellenic DPA
Art 29 WP Alternate Member: Dr. Vasilios ZORKADIS, Director

Hungary

National Authority for Data Protection and Freedom of Information
Szilágyi Erzsébet fasor 22/C H-1125 Budapest
Tel. +36 1 3911 400
E-mail: peterfalvi.attila@naih.hu
WebSite: HTTPS://www.naih.hu

Art 29 WP Member: Dr Attila PÉTERFALVI, President of the National Authority for Data Protection and Freedom of Information
Art 29 WP Alternate Member: Mr. Endre Győző SZABÓ Vice-president of the National Authority for Data Protection and Freedom of Information

Ireland

Data Protection Commissioner
Canal House Station Road Portarlington Co. Laois
Lo-Call: 1890 25 22 31
Tel. +353 57 868 4800
Fax +353 57 868 4757
E-mail: info@dataprotection.ie
WebSite: HTTPS://www.dataprotection.ie

Art 29 WP Member: Ms. Helen DIXON, Data Protection Commissioner
Art 29 WP Alternate Members: Mr. John O’DWYER, Deputy Commissioner; Mr. Dale SUNDERLAND, Deputy Commissioner

Italy

Garante per la protezione dei dati personali
Piazza di Monte Citorio, 121 00186 Roma
Tel. +39 06 69677 1
Fax +39 06 69677 785
E-mail: garante@garanteprivacy.it
WebSite: HTTPS://www.garanteprivacy.it

Art 29 WP Member: Mr. Antonello SORO, President of Garante per la protezione dei dati personali
Art 29 WP Alternate Member: Ms. Giuseppe BUSIA, Secretary General of Garante per la protezione dei dati personali

Latvia

Data State Inspectorate Director: Ms. Daiga Avdejanova
Blaumana str. 11/13-15
1011 Riga
Tel. +371 6722 3131
Fax +371 6722 3556
E-mail: info@dvi.gov.lv
WebSite: HTTPS://www.dvi.gov.lv

Art 29 WP Alternate Member: Ms. Aiga BALODE

Lithuania

State Data Protection
Žygimantų str. 11-6a 011042 Vilnius
Tel. + 370 5 279 14 45
Fax +370 5 261 94 94
E-mail: ada@ada.lt
WebSite: HTTPS://www.ada.lt

Art 29 WP Member: Mr. Raimondas Andrijauskas, Director of the State Data Protection Inspectorate
Art 29 WP Alternate Member: Ms. Neringa KAKTAVIČIŪTĖ-MICKIENĖ, Head of Complaints Investigation and International Cooperation Division

Luxembourg

Commission Nationale pour la Protection des Données
1, avenue du Rock’n’roll L-4361 Esch-sur-Alzette Tel. +352 2610 60 1
Fax +352 2610 60 29
E-mail: info@cnpd.lu
WebSite: HTTPS://www.cnpd.lu

Art 29 WP Member: Ms. Tine A. LARSEN, President of the Commission Nationale pour la Protection des Données
Art 29 WP Alternate Member: Mr. Thierry LALLEMANG, Commissioner

Malta

Office of the Data Protection Commissioner
Data Protection Commissioner: Mr. Joseph Ebejer
2, Airways House
High Street, Sliema SLM 1549 Tel. +356 2328 7100
Fax +356 2328 7198
E-mail: commissioner.dataprotection@gov.mt
WebSite: HTTPS://idpc.org.mt

Art 29 WP Member: Mr. Saviour CACHIA, Information and Data Protection Commissioner
Art 29 WP Alternate Member: Mr. Ian DEGUARA, Director - Operations and Programme Implementation

Netherlands

Autoriteit Persoonsgegevens
Prins Clauslaan 60
P.O. Box 93374
2509 AJ Den Haag/The Hague Tel. +31 70 888 8500
Fax +31 70 888 8501
E-mail: info@autoriteitpersoonsgegevens.nl
WebSite: HTTPS://autoriteitpersoonsgegevens.nl/nl

Art 29 WP Member: Mr. Aleid WOLFSEN, Chairman of Autoriteit Persoonsgegevens

Poland

The Bureau of the Inspector General for the Protection of Personal Data – GIODO
ul. Stawki 2
00-193 Warsaw
Tel. +48 22 53 10 440
Fax +48 22 53 10 441
E-mail: kancelaria@giodo.gov.pl; desiwm@giodo.gov.pl
WebSite: HTTPS://www.giodo.gov.pl

Art 29 WP Member: Ms. Edyta BIELAK-JOMAA, Inspector General for the Protection of Personal Data

Portugal

Comissão Nacional de Protecção de Dados - CNPD
R. de São. Bento, 148-3° 1200-821 Lisboa
Tel. +351 21 392 84 00
Fax +351 21 397 68 32
E-mail: geral@cnpd.pt
WebSite: HTTPS://www.cnpd.pt

Art 29 WP Member: Ms. Filipa CALVÃO, President, Comissão Nacional de Protecção de Dados
Art 29 WP Alternate Member: Isabel CRUZ, Secretary-General of the DPA

Romania

The National Supervisory Authority for Personal Data Processing President: Mrs. Ancuţa Gianina Opre
B-dul Magheru 28-30
Sector 1, BUCUREŞTI
Tel. +40 21 252 5599
Fax +40 21 252 5757
E-mail: anspdcp@dataprotection.ro
WebSite: HTTPS://www.dataprotection.ro

Art 29 WP Member: Ms. Ancuţa Gianina OPRE, President of the National Supervisory Authority for Personal Data Processing
Art 29 WP Alternate Member: Ms. Alina SAVOIU, Head of the Legal and Communication Department

Slovakia

Office for Personal Data Protection of the Slovak Republic
Hraničná 12
820 07 Bratislava 27
Tel.: + 421 2 32 31 32 14
Fax: + 421 2 32 31 32 34
E-mail: statny.dozor@pdp.gov.sk
WebSite: HTTPS://dataprotection.gov.sk

Art 29 WP Member: Ms. Soňa PŐTHEOVÁ, President of the Office for Personal Data Protection of the Slovak Republic
Art 29 WP Alternate Member: Mr. Anna VITTEKOVA, Vice President

Slovenia

Information Commissioner
Ms. Mojca Prelesnik Zaloška 59
1000 Ljubljana
Tel. +386 1 230 9730
Fax +386 1 230 9778
E-mail: gp.ip@ip-rs.si
WebSite: HTTPS://www.ip-rs.si

Art 29 WP Member: Ms. Mojca PRELESNIK, Information Commissioner of the Republic of Slovenia

Spain

Agencia de Protección de Datos
C/Jorge Juan, 6
28001 Madrid
Tel. +34 91399 6200
Fax +34 91455 5699
E-mail: internacional@agpd.es
WebSite: HTTPS://www.agpd.es

Art 29 WP Member: Ms. María del Mar España Martí, Director of the Spanish Data Protection Agency
Art 29 WP Alternate Member: Mr. Rafael GARCIA GOZALO

Sweden

Datainspektionen
Drottninggatan 29 5th Floor
Box 8114
20 Stockholm
Tel. +46 8 657 6100
Fax +46 8 652 8652
E-mail: datainspektionen@datainspektionen.se
WebSite: HTTPS://www.datainspektionen.se

Art 29 WP Member: Ms. Kristina SVAHN STARRSJÖ, Director General of the Data Inspection Board
Art 29 WP Alternate Member: Mr. Hans-Olof LINDBLOM, Chief Legal Adviser

United Kingdom

The Information Commissioner’s Office
Water Lane, Wycliffe House Wilmslow - Cheshire SK9 5AF Tel. +44 1625 545 745
E-mail: international.team@ico.org.uk
WebSite: HTTPS://ico.org.uk

Art 29 WP Member: Ms. Elizabeth DENHAM, Information Commissioner
Art 29 WP Alternate Member: Mr. Steve WOOD, Deputy Commissioner

EUROPEAN FREE TRADE AREA (EFTA)

Iceland

Icelandic Data Protection Agency
Rauðarárstíg 10
Reykjavík
Tel. +354 510 9600; Fax +354 510 9606
E-mail: postur@personuvernd.is
WebSite: HTTPS://www.personuvernd.is

Liechtenstein

Data Protection Office
Kirchstrasse 8, P.O. Box 684
9490 Vaduz
Principality of Liechtenstein Tel. +423 236 6090
E-mail: info.dss@llv.li
WebSite: HTTPS://www.datenschutzstelle.li

Norway

Datatilsynet
Data Protection Authority: Mr. Bjørn Erik THORN
The Data Inspectorate
P.O. Box 8177 Dep 0034 Oslo
Tel. +47 22 39 69 00; Fax +47 22 42 23 50
E-mail: postkasse@datatilsynet.no
WebSite: HTTPS://www.datatilsynet.no

Switzerland

Data Protection and Information Commissioner of Switzerland
Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter Mr. Adrian Lobsiger
Feldeggweg 1
3003 Bern
Tel. +41 58 462 43 95; Fax +41 58 462 99 96
E-mail: contact20@edoeb.admin.ch
WebSite: HTTPS://www.edoeb.admin.ch

Footnotes

  1. HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en; ↩

  2. HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en; ↩

\ No newline at end of file + Personal Data Protection Policy
+

PERSONAL DATA PROTECTION POLICY

+

Effective date: 05.25.2018 / May 25th 2018
+Last updated: 02.11.2022 / February 11th 2022

+

We at PlayForm ltd. are committed to processing personal data securely and +respecting privacy of the concerned individuals.

+ ++++ + + + + + + + + + +
Version No. and date of the last update:

v. 1.0.

+

February 11th 2022

This policy shall be reviewed annually or each time when the changes in our data processing occur.
+

Scope and Definitions

+
    +
  1. +

    Scope. This Personal Data Protection +Policy (the “Policy”) describes PlayForm ltd. internal rules for +personal data processing and protection. The Policy applies to PlayForm +ltd., including PlayForm ltd. employees and contractors (“we”, “us”, +“our”, “PlayForm”). The management of each entity is ultimately +responsible for the implementation of this policy, as well as to ensure, at +entity level, there are adequate and effective procedures in place for its +implementation and ongoing monitoring of its adherence. For the purposes of +this Policy, employees and contractors are jointly referred to as the +“employees”.

    +
    2. +
  2. +

    Privacy Manager. Privacy Manager is an +employee of PlayForm responsible for personal data protection compliance +within PlayForm (the “Privacy Manager”). The Privacy Manager is in +charge of performing the obligations imposed by this Policy and supervising +other employees, who subject to this Policy, regarding their adherence to +this Policy. The Privacy Manager must be involved in all projects at an +early stage in order to take personal data protection aspects into account +as early as the planning phase.
    +The designated Privacy Manager at PlayForm ltd. is Nikola Hristov +Nikola@PlayForm.LTD.

    +
    3. +
  3. +

    Definitions.

    +
    4. +
+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Competent Supervisory Authoritymeans a public authority that is responsible for regulating and supervising personal data protection with regards to activities of PlayForm.
Data Breach

means a breach of the security and/or confidentiality leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data transmitted, stored or otherwise processed.

+

This includes but is not limited to e-mails sent to an incorrect or disclosed list of recipients, an unlawful publication of the Personal Data, loss or theft of physical records, and unauthorized access to personal information.

Data Controllermeans the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines (make a decision) the purposes and means of the processing of Personal Data.
Data Processormeans a natural or legal person, public authority, agency or other body which processes the Personal Data on behalf of the data controller.
Data Protection Lawsmean any laws and legal rules on personal data use and protection applicable to the activities of PlayForm, including, but not limited to the Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation, GDPR).
Data Subject Request (DSR)means any request from the Data Subject and concerning their personal data and/or data subject rights.
Data Subjectmeans a natural person, whose Personal Data we process. Data Subjects include but are not limited to users, website visitors, employees, contractors, and partners of PlayForm.
Personal Datameans any information relating to an identified or identifiable Data Subject; a Data Subject can be identified by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or the combination of factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that Data Subject.
Processingmeans any operation or set of operations which is performed by PlayForm on Personal Data, such as 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.
Standard Contractual Clausesmeans the European Commission Decision of February, 5 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC of the European Parliament and of the Council (2010/87/EU).
Third Partymeans a natural or legal person, who accesses the Personal Data for further processing and is not an employee, member or corporate affiliate of PlayForm. This definition does not apply to natural persons, who provide services to PlayForm as contractors on a regular basis.
Usermeans a Data Subject who uses our services provided on PlayForm website.
+

Data Processing Principles

+
    +
  1. +

    PlayForm’s processing activities must be in line with the principles +specified in this Section. The Privacy Manager must make sure that +PlayForm’s compliance documentation, as well as data processing activities, +are compliant with the data protection principles.

    +
    2. +
  2. +

    We must process the Personal Data in accordance with the following +principles:

    +
      +
    1. +

      Lawfully, fairly and in a transparent manner (lawfulness, fairness and +transparency). We shall always have a legal ground for the processing +(described in Section 3 of this Policy), collect the amount of data +adequate to the purpose and legal grounds, and we make sure the Data +Subjects are aware of the processing;

      +
      2. +
    2. +

      Collected for specified, explicit and legitimate purposes and not +further processed in a manner that is incompatible with those purposes +(purpose limitation). We must not process the Personal Data for the +purposes not specified in our compliance documentation without obtaining +specific approval of the Privacy Manager;

      +
      3. +
    3. +

      Adequate, relevant and limited to what is necessary for the purposes for +which they are processed (data minimization). We always make sure +the data we collect is not excessive and limited by the strict +necessity;

      +
      4. +
    4. +

      Accurate and, where necessary, kept up to date (accuracy). We +endeavor to delete inaccurate or false data about Data Subjects and make +sure we update the data. Data Subjects can ask us for a correction of +the Personal Data;

      +
      5. +
    5. +

      Kept in a form which permits identification of Data Subjects for no +longer than is necessary for the purposes for which the Personal Data +are processed (storage period limitation). The storage periods must +be limited as prescribed by Data Protection Laws and this Policy; and

      +
      6. +
    6. +

      Process in a manner that ensures appropriate security of the Personal +Data, including protection against unauthorized or unlawful processing +and accidental loss, destruction or damage, using appropriate technical +or organizational measures (confidentiality, integrity, and +availability).

      +
      7. +
    +
    3. +
  3. +

    Accountability.

    +
      +
    1. +

      We shall be able to demonstrate our compliance with Data Protection Laws +(accountability principle). In particular, we must ensure and +document all relevant procedures, efforts, internal and external +consultations on personal data protection including:

      +
        +
      • +

        the fact of appointing a person responsible for PlayForm’s data +protection compliance;

        +
        • +
      • +

        where necessary, a record of a Data Processing Impact Assessment;

        +
        • +
      • +

        developed and implemented notices, policies, and procedures, such as +Privacy Notice, this policy or Data Breach response procedure;

        +
        • +
      • +

        the fact of staff training on compliance with Data Protection laws; +and

        +
        • +
      • +

        assessment, implementation, and testing organizational and technical +data protection measures.

        +
        • +
      +
      2. +
    2. +

      The Privacy Manager must maintain PlayForm’s Records of processing +activities, which is an accountability document that describes personal +data processing activities of PlayForm, prepared in accordance with Art. +30 of the GDPR (the “Records of processing activities”). The Records +of processing activities must maintain, at least, the following +information about each processing activity:

      +
        +
      • +

        contact details of PlayForm, the EU Representative, and, where +applicable, of the Data Protection Officer;

        +
        • +
      • +

        name of the activity, its purposes and legal basis along with, where +applicable, the legitimate interests of PlayForm;

        +
        • +
      • +

        data subjects and personal data categories concerned;

        +
        • +
      • +

        data retention periods;

        +
        • +
      • +

        general description of applicable security measures;

        +
        • +
      • +

        recipients, including joint controllers, processors, and contractors +involved, as well as the fact of the international data transfer with +the safeguards applied to the transfer;

        +
        • +
      • +

        where applicable, a reference to the Data Processing Impact +Assessment;

        +
        • +
      • +

        where applicable, a reference to the record of the data breach +occurred involving the personal data;

        +
        • +
      • +

        if PlayForm acts as a data processor, the information to be provided +includes the names and contact details of controllers, name and +contact details of controller’s representative (if applicable), +categories of processing (activities), names of third countries or +international organizations that personal data are transferred to (if +applicable), safeguards for exceptional transfers of personal data to +third countries or international organizations (if applicable), and +general description of technical and organizational security measures.

        +
        • +
      +
      3. +
    +
    4. +
+ +
    +
  1. +

    Legal grounds.

    +
      +
    1. +

      Each processing activity must have one of the lawful grounds specified +in this Section to process the Personal Data. If we do not have any of +the described, we cannot collect or further process the Personal Data.

      +
      2. +
    2. +

      If PlayForm is intended to use personal data for other purposes than +those specified in the Records of processing activities, the Privacy +Manager must evaluate, determine, and, if necessary, collect/record the +appropriate legal basis for it.

      +
      3. +
    3. +

      Performance of the contract. Where PlayForm has a contract with the +Data Subject, e.g., website’s Terms of Use or the employment contract, +and the contract requires the provision of personal data from the Data +Subject, the applicable legal ground will be the performance of the +contract.

      +
      4. +
    4. +

      Consent. To process the personal data based on the consent, we must +obtain the consent before the Processing and keep the evidence of the +consent with the records of Data Subject’s Personal Data. The Privacy +Manager must make sure that the consent collected from Data Subjects +meet the requirements of Data Protection Laws and this Policy. In +particular, the Privacy Manager must make sure that:

      +
        +
      • +

        the Data Subject must be free to give or refuse to give consent.

        +
        • +
      • +

        the consent is in the form of an active indication from the Data +Subject, i.e., the consent checkbox must not be pre-ticked for the +user.

        +
        • +
      • +

        the request for the consent clearly articulates the purposes of the +processing, and other information specified in Subsection 6.2 is +available to the Data Subject.

        +
        • +
      • +

        the Data Subject must be free to give one’s consent or to revoke it.

        +
        • +
      +
      5. +
    5. +

      Legitimate interests. We have the right to use personal data in our +‘legitimate interests’. The interests can include the purposes that are +justified by the nature of our business activities, such as the +marketing analysis of personal data. For PlayForm to use legitimate +interests as a legal ground for the processing, the Privacy Manager must +make sure that:

      +
        +
      • +

        the legitimate interest in the processing is clearly defined and +recorded in the Records of processing activities;

        +
        • +
      • +

        any envisaged risks to Data Subject rights and interests are spotted. +The examples of the risks can be found in Subsection 7.2.;

        +
        • +
      • +

        the Data Subjects have reasonable expectations about the processing, +and additional protective measures to address the risks are taken;

        +
        • +
      • +

        subject to the conditions of Subsection 6.7 (Right to object against +the processing), the Data Subject is provided with the opportunity to +opt-out from the processing for the described legitimate interests.
        +If at least one of the above conditions is not met by PlayForm, the +Privacy Manager must choose and propose a different legal ground for +the processing, such as consent.

        +
        • +
      +
      6. +
    6. +

      Legal Compliance and Public Interest. Besides the grounds specified +afore, we might be requested by the laws of the European Union or laws +of the EU Member State to process Personal Data of our Users. For +example, we can be required to collect, analyze, and monitor the +information of Users to comply with financial or labor laws.
      +Whenever we have such an obligation, we must make sure that:

      +
        +
      • +

        we process personal data strictly in accordance with relevant legal +requirements;

        +
        • +
      • +

        we do not use or store the collected Personal Data for other purposes +than legal compliance; and

        +
        • +
      • +

        the Data Subjects are properly and timely informed about our +obligations, scope, and conditions of personal data processing.

        +
        • +
      +
      7. +
    +
    2. +
+

Important: Where PlayForm has the law requirements of another country to process +personal data, the Privacy Manager must propose using another legal ground for +the processing under Data Protection Laws, such as legitimate interests or +consent.

+

Access to Personal Data

+
    +
  1. +

    Access to Personal Data.

    +
      +
    1. +

      The employees must have access to the personal data on a “need-to-know” +basis. The data can be accessed only if it is strictly necessary to +perform one of the activities specified in the Records of processing +activities. The employees and contractors shall have access to the +Personal Data only if they have the necessary credentials for it.

      +
      2. +
    2. +

      Heads of the departments within PlayForm are responsible for their +employees’ access and processing of personal data. The heads must +maintain the list of employees that are entitled to access and process +personal data. The Privacy Manager shall have the right to review the +list and, where necessary, request the amendments to meet the +requirements of this Policy.

      +
      3. +
    3. +

      Heads of the departments within PlayForm must ensure that the employees +under their supervision are aware of the Data Protection Laws and comply +with the rules set in this Policy. To make sure our employees are able +to comply with the data protection requirements, we must provide them +with adequate data protection training.

      +
      4. +
    4. +

      All employees accessing personal data shall keep strict confidentiality +regarding the data they access. The employees that access personal data +must use only those means (software, premises, etc.) for the processing +that were prescribed by PlayForm. The data must not be disclosed or +otherwise made available out of the management instructions.

      +
      5. +
    5. +

      The employees within their competence must assist PlayForm’s +representatives, including the Privacy Manager, in any efforts regarding +compliance with Data Protection Laws and/or this Policy.

      +
      6. +
    6. +

      When an employee detects or believes there is suspicious activity, data +breach, non-compliance with Data Protection Laws and/or this Policy, or +a DSR was not routed to the competent department within PlayForm, the +employee must report such activity to the Privacy Manager.

      +
      7. +
    7. +

      Employees that are unsure about whether they can legitimately process or +disclose Personal Data must seek advice from the Privacy Manager before +taking any action.

      +
      8. +
    8. +

      Any occasional access to personal data for activities not specified in +the Records of processing activities is prohibited. If there is a strict +necessity for immediate access, the Privacy Manager must approve the +access first.

      +
      9. +
    +
    2. +
+

Third Parties

+
    +
  1. +

    Before sharing personal data with any person outside of PlayForm, the +Privacy Manager must ensure that this Third Party has an adequate data +protection level and provide sufficient data protection guarantees in +accordance with Data Protection Laws, including, but not limited to the +processorship requirements (Art. 28 of the GDPR) and international transfers +compliance (Section 5 of the GDPR). Where necessary, the Privacy Manager +must make sure that PlayForm enters into the appropriate data protection +contract with the third party.

    +
    2. +
  2. +

    An employee can share personal data with third parties only if and to the +extent that was directly prescribed by the manager and specified in the +Records of processing activities.

    +
    3. +
  3. +

    If we are required to delete, change, or stop the processing of the Personal +Data, we must ensure that the Third Parties, with whom we shared the +Personal Data, will fulfill these obligations accordingly.

    +
    4. +
  4. +

    Whenever PlayForm is engaged as a data processor on behalf of another +entity, the Privacy Manager must make sure PlayForm complies with the +processorship obligation. In particular, the appropriate data processing +agreement in accordance with the Data Protection Laws must be in place. The +Privacy Manager must supervise the compliance with data processing +instructions from the controller, including regarding the scope of +processing activities, involvement of sub-processors, international +transfers, storage, and further disposal of processed personal data. The +personal data processed under the processor role must not be processed for +any other purposes than specified in the relevant instructions, agreement or +other legal act regulating the relationships with the controller.

    +
    5. +
+

International Transfers

+
    +
  1. +

    If we have the employees, contractors, corporate affiliates, or Data +Processors outside of the EEA, and we transfer Personal Data to them for the +processing, the Privacy Manager must make sure PlayForm takes all necessary +and appropriate safeguards in accordance with Data Protection Laws.

    +
    2. +
  2. +

    The Privacy Manager must assess the safeguards available and propose to the +PlayForm’s management the appropriate safeguard for each international +transfer. The following regimes apply to the transfers of Personal Data +outside of the EU:

    +
      +
    • +

      where the European Commission decides that the country has an adequate +level of personal data protection, the transfer does not require taking +additional safeguards. The full list of adequate jurisdictions can be +found on the relevant page of the European Commission’s website1.

      +
      • +
    • +

      to transfer Personal Data to our contractors or partners (Data Processors +or Controllers) in other third countries, we must conclude Standard +Contractual Clauses with that party. The draft version along with the +guidance can be found on the relevant page of the European Commission’s +website2;

      +
      • +
    • +

      if we have a corporate affiliate or an entity in other countries, we may +choose to adopt Binding Corporate Rules in accordance with Article 47 of +the GDPR or an approved code of conduct pursuant to Article 40 of the +GDPR;

      +
      • +
    • +

      we also can transfer Personal Data to entities that have an approved +certification in accordance with Article 42 of the GDPR, which certifies +an appropriate level of company’s data protection.

      +
      • +
    +
    3. +
+
    +
  1. +

    As a part of the information obligations, PlayForm must inform the Data +Subjects that their Personal Data is being transferred to other countries, +as well as provide them with the information about the safeguards used for +the transfer. The information obligation is to be performed in accordance +with Subsection 6.2.

    +
    2. +
  2. +

    In the exceptional cases (the “Derogation”), where we cannot apply the +safeguards mentioned afore and we need to transfer Personal Data, we must +take an explicit consent (active statement) from the Data Subject or it must +be strictly necessary for the performance of the contract between us and the +Data Subject, or other derogation conditions apply in accordance with the +Data Protection Laws. The Privacy Manager must pre-approve any Derogation +transfers and document the approved Derogations, as well as the rationale +for them.

    +
    3. +
+

Rights of Data Subjects

+
    +
  1. +

    Our Responsibilities.

    +
      +
    1. +

      Privacy Manager is ultimately responsible for handing all DSR received +by PlayForm. In the case of receiving any outstanding or unusual DSR, +the employee must seek advice from the Privacy Manager before taking any +action.

      +
      2. +
    2. +

      DSR Team within PlayForm is responsible for handling DSRs from PlayForm +Users on a daily basis. The Human Resources department is responsible +for handling the DSR from PlayForm employees.

      +
      3. +
    3. +

      All DSRs from the Users must be addressed at and answered from the +following e-mail address: DSR@PlayForm.LTD. DSR from the employees can +be addressed directly to the HR manager or at DSR@PlayForm.LTD.

      +
      4. +
    4. +

      The responsible employee must answer to the DSR within one (1) month +from receiving the request. If complying with the DSR takes more than +one month in time, the responsible employee must seek advice from the +Privacy Manager and, where necessary, inform the Data Subject about the +prolongation of the response term for up to two (2) additional months.

      +
      5. +
    5. +

      The responsible employee must analyze the received DSR for the following +criteria:

      +
        +
      • +

        Data Subject identification. Before considering the DSR content, +the responsible employee must make sure the Data Subject is the same +person he/she claims to be. For this purpose, the connection between +the personal data records and the data subject must be established.

        +
        • +
      • +

        Personal data. The responsible employee must check whether +PlayForm has access to the personal data requested. If PlayForm does +not have the personal data under the control, the responsible employee +must inform the Data Subject, and, if possible, instruct on the +further steps on how to access the data in question;

        +
        • +
      • +

        Content of the request. Depending on the content of the DSR, the +responsible employee must define the type of the request and check +whether it meets the conditions prescribed by this Policy and Data +Protection Laws. The types of requests and the respective conditions +for each of them can be consulted in Subsections 6.3-6.9. If the +request does not meet the described criteria, the responsible employee +must refuse to comply with the DSR and inform the Data Subject about +the reasons for refusing;

        +
        • +
      • +

        Free of charge. Generally, all requests of Data Subjects and +exercises of their rights are free of charge. If the responsible +employee finds that the Data Subject exercises the rights in an +excessive or unfound way (e.g., intended to harm or interrupt +PlayForm’s business activities), the employee must seek the advice +from the Privacy Manager, and, upon receiving of the latter, may +either charge the Data Subject a reasonable fee or refuse to comply +with the request;

        +
        • +
      • +

        Documenting. Whenever PlayForm receives the DSR, the Privacy +Manager must make sure that the data and time, Data Subject, type of +the request and the decision made regarding it are well documented. In +the case of refusing to comply with the request, the reasons for +refusing must be documented as well;

        +
        • +
      • +

        Recipients. When addressing the DSR, the Privacy Manager must make +sure that all concerned recipients were informed the necessary actions +were taken.

        +
        • +
      +
      6. +
    +
    2. +
  2. +

    The right to be informed.

    +
      +
    1. +

      PlayForm must notify each Data Subject about the collection and further +processing of the Personal Data.

      +
      2. +
    2. +

      The information to be provided includes: the name and contact details of +PlayForm; generic purposes of and the lawful basis for the data +collection and further processing; categories of Personal Data +collected; recipients/categories of recipients; retention periods; +information about data subject rights, including the right to complain +to the competent Supervisory Authority; the consequences of the cases +where the data is necessary for the contract performance and the Data +Subject does not provide the required data; details of the safeguards +where personal data is transferred outside the EEA; and any third-party +source of the personal data, without specification for the particular +case (except if we receive the direct request from the Data Subject).

      +
      3. +
    3. +

      The Users must be informed by the Privacy Policy accessible at +PlayForm’s website and provided during the user registration. The +employees and contractors must be informed by a standalone employee +privacy statement, which explains the details described in p. 6.2.2 in a +case-based manner, describing the particular purposes and activities.

      +
      4. +
    4. +

      PlayForm must inform Data Subjects about data processing, including any +new processing activity introduced at PlayForm within the following +term:

      +
        +
      • +

        if personal data is collected from the data subject directly, the data +subject must be informed at the time we collect Personal Data from the +Data Subjects by showing the Data Subject our privacy statement;

        +
        • +
      • +

        if the personal data is collected from other sources: (a) within one +month from collecting it; (b) if the personal data are to be used for +communication with the data subject, at the latest at the time of the +first communication to that data subject; or (c) if a disclosure to +another recipient is envisaged, at the latest when the personal data +are first disclosed.

        +
        • +
      • +

        upon the request of the Data Subject; and

        +
        • +
      • +

        within one (1) month after any change of our personal data practices, +change of the controller of Personal Data or after significant changes +in our privacy statements.

        +
        • +
      +
      5. +
    +
    3. +
  3. +

    The right to access the information.

    +
      +
    1. +

      The Data Subject must be provided only with those personal data records +specified in the request. If the Data Subject requests access to all +personal data concerning her or him, the employee must seek advice from +the Privacy Manager first, to make sure all personal data of the Data +Subject is mapped and provided.

      +
      2. +
    2. +

      A Data Subject has the right to:

      +
        +
      • +

        learn if we process the Data Subject’s Personal Data;

        +
        • +
      • +

        obtain disclosure regarding aspects of the processing, including +detailed and case-specific information on purposes, categories of +Personal Data, recipients/categories of recipients, retention periods, +information about one’s rights, details of the relevant safeguards +where personal data is transferred outside the EEA, and any +third-party source of the personal data; and

        +
        • +
      • +

        obtain a copy of the Personal Data undergoing processing upon the +request.

        +
        • +
      +
      3. +
    +
    4. +
  4. +

    The right to verify the Data Subject’s information +and seek its rectification. The information we collect can +be/become inaccurate or out-of-date (e.g., mistakes in nationality, date of +birth, info on debts, economic activities). If we reveal that the Personal +Data is inaccurate or the Data Subject requests us to do so, we must ensure +that we correct all mistakes and update the relevant information.

    +
    5. +
  5. +

    The right to restrict processing.

    +
      +
    1. +

      The restriction of processing allows Data Subjects to temporarily stop +the use of their information to prevent the possible harm caused by such +use.

      +
      2. +
    2. +

      This right applies when the Data Subject:

      +
        +
      • +

        contests the accuracy of the Personal Data;

        +
        • +
      • +

        believes that we process the Personal Data unlawfully; and

        +
        • +
      • +

        objects against the processing and wants us not to process Personal +Data while we are considering the request.

        +
        • +
      +
      3. +
    3. +

      In the case of receiving the restriction request, we must not process +Personal Data in question for any other purpose than storing it or for +legal compliance purposes until the circumstances of restriction cease +to exist.

      +
      4. +
    +
    6. +
  6. +

    The right to withdraw the consent. For +the activities that require consent, the Data Subject can revoke their +consent at any time. If the Data Subject revokes the consent, we must record +the changes and must not process the Personal Data for consent-based +purposes. The withdrawal of consent does not affect the lawfulness of the +processing done before the withdrawal.

    +
    7. +
  7. +

    The right to object against the +processing.

    +
      +
    1. +

      If we process the information in our legitimate interests, e.g., for +direct marketing emails or for our marketing research purposes, the Data +Subject can object against the processing.

      +
      2. +
    2. +

      In the case of receiving the objection request case, we must consider +Data Subject’s request and, where we do not have compelling interests, +stop the processing for the specified purposes. If the personal data is +still to be processed for other purposes, the Privacy Manager must make +sure that the database has a record that the data cannot be further +processed for the objected activities.

      +
      3. +
    3. +

      The objection request can be refused only if the personal data in +question is used for scientific/historical research or statistical +purposes and was appropriately protected, i.e., by anonymization or +pseudonymization techniques.

      +
      4. +
    +
    8. +
  8. +

    Right to erasure/to be forgotten.

    +
      +
    1. +

      The Data Subjects have the right to request us to erase their Personal +Data if one of the following conditions are met:

      +
        +
      • +

        Personal Data is no longer necessary for the purposes of collection. +For example, a user has provided personal data for a one-time +activity, such as data validation or participation in a contest, and +the purpose is already fulfilled;

        +
        • +
      • +

        the Data Subject revokes one’s consent or objects to the processing +(where applicable) and there is no other legal ground for the +processing; or

        +
        • +
      • +

        we process the Personal Data unlawfully or its erasure is required by +the applicable legislation of the European Union or one of the Member +countries of the European Union.

        +
        • +
      +
      2. +
    2. +

      Conditions, under which we have the right to refuse the erasure:

      +
        +
      • +

        Personal Data is processed for scientific/historical research or +statistical purposes and is appropriately protected, i.e., +pseudonymized or anonymized;

        +
        • +
      • +

        Personal Data is still necessary for legal compliance (e.g., financial +or labor laws compliance).

        +
        • +
      +
      3. +
    3. +

      Only those personal data records must be deleted that were specified in +the request. If the Data Subject requests the deletion of all personal +data concerning her or him, the employee must seek advice from the +Privacy Manager first, to make sure all the data about the Data Subject +is mapped and can be deleted.

      +
      4. +
    4. +

      If the User still has an account with us and requests the erasure of +information necessary for maintaining the account, we must inform the +User that the erasure will affect user experience or can lead to the +closure of the account.

      +
      5. +
    +
    9. +
  9. +

    Data portability.

    +
      +
    1. +

      Data Subjects can ask us to transfer all the Personal Data and/or its +part in a machine-readable format to a third party. This right applies +in two cases:

      +
        +
      • +

        personal data was collected for the purpose of provision of our +services (performance of the contract); or

        +
        • +
      • +

        collected based on consent.

        +
        • +
      +
      2. +
    2. +

      To determine whether one of the p.6.9.1 conditions are met, the employee +must seek advice from the Privacy Manager and check the applicable legal +basis in the Records of processing activities. If the answer is +negative, the request can be refused by PlayForm, and the Privacy +Manager must decide whether to comply with the request on a voluntary +basis.

      +
      3. +
    3. +

      To comply with the request, the responsible employee must consolidate +requested Personal Data and send the data in the format we are usually +working with to the requested organization. The Data Subject must +provide the necessary contact details of the organization.

      +
      4. +
    +
    10. +
+

New Data Processing Activities

+
    +
  1. +

    Notification to Privacy Manager.

    +
      +
    1. +

      Before introducing any new activity that involves the processing of +personal data, an employee responsible for its implementation must +inform the Privacy Manager.

      +
      2. +
    2. +

      Upon receiving information about a new activity, Privacy Manager must:

      +
        +
      • +

        determine whether the data processing impact assessment (DPIA) and/or +the consultation with the Supervisory Authority is necessary. If the +answer is positive, the Privacy Manager must make sure the DPIA is +conducted and/or the Supervisory Authority is consulted in accordance +with the requirements of this Section and Data Protection Laws;

        +
        • +
      • +

        determine the legal basis for the processing and, where necessary, +take further action for its fixation;

        +
        • +
      • +

        make sure the processing activity is done in accordance with this +Policy, other PlayForm’s policies, as well as the Data Protection +Laws;

        +
        • +
      • +

        add the processing activity to the Records of processing activities;

        +
        • +
      • +

        amend the privacy information statements and, where necessary, inform +the concerned Data Subject accordingly.

        +
        • +
      +
      3. +
    +
    2. +
  2. +

    Data Processing Impact Assessment.

    +
      +
    1. +

      To make sure that our current or prospective processing activities do +not/will not violate the Data Subjects’ rights, PlayForm must, where +required by Data Protection Laws, conduct the Data Processing Impact +Assessment (DPIA), a risk-based assessment of the processing and search +for the measures to mitigate the risks. The Privacy Manager must make +sure the DPIA is conducted in accordance with this Section.

      +
      2. +
    2. +

      The Privacy Manager, where necessary, involving the competent employees +and/or external advisors, must conduct a DPIA if at least one of the +following conditions are met:

      +
        +
      • +

        the processing involves the use of new technologies, such as the +Artificial Intelligence, use of connected and autonomous devices, etc. +that creates certain legal, economic or similar effects to the Data +Subject;

        +
        • +
      • +

        we systematically assess and evaluate personal aspects of the Data +Subjects based on automated profiling, assigning the personal +score/rate, and create legal or similar effects for the Data Subject +by this activity;

        +
        • +
      • +

        we process on a large-scale sensitive data, which includes Personal +Data relating to criminal convictions and offences, the data about +vulnerable data subjects, the 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;

        +
        • +
      • +

        we collect or process Personal Data from a publicly accessible area or +public sources on a large scale, or combine or match two different +data sets; and

        +
        • +
      • +

        the Supervisory Authority in its public list requires conducting a +DPIA for a certain type of activity we are involved in. The list of +processing activities requiring conducting DPIA can be found on the +website of each Supervisory Authority.

        +
        • +
      +
      3. +
    3. +

      The assessment shall contain at least the following details:

      +
        +
      • +

        a systematic description of the processing operations and the purposes +of the processing, including, where applicable, the legitimate +interest pursued by us. The description must include the envisaged +data categories and data subjects concerned, the scale of processing +activities, such as its frequency, volume, envisaged number of +records, etc.; recipients of the data, retention periods and, where +applicable, international transfers;

        +
        • +
      • +

        an assessment of the necessity and proportionality of the processing +operations in relation to the purposes. The DPIA must explain whether +the activity is necessary for the purpose and whether the purpose can +be achieved by less intrusive methods;

        +
        • +
      • +

        an assessment of the risks to the rights and freedoms of data +subjects, including the rights of Data Subjects regarding their +Personal Data.

        +
        • +
      • +

        The examples of risks are the processing which could lead to physical, +material or non-material damage, in particular: where the processing +may give rise to discrimination, identity theft or fraud, financial +loss, damage to the reputation, loss of confidentiality of personal +data protected by professional secrecy, unauthorized reversal of +pseudonymization, or any other significant economic or social +disadvantage; where data subjects might be deprived of their rights +and freedoms or prevented from exercising control over their personal +data; where personal data are processed which reveal racial or ethnic +origin, political opinions, religion or philosophical beliefs, trade +union membership, and the processing of genetic data, data concerning +health or data concerning sex life or criminal convictions and +offences or related security measures; where personal aspects are +evaluated, in particular analyzing or predicting aspects concerning +performance at work, economic situation, health, personal preferences +or interests, reliability or behavior, location or movements, in order +to create or use personal profiles; where personal data of vulnerable +natural persons, in particular of children, are processed; or where +processing involves a large amount of personal data and affects a +large number of data subjects; and

        +
        • +
      • +

        the measures to address the risks, including safeguards, security +measures, and mechanisms to ensure the protection of personal data and +to demonstrate compliance with this Regulation.

        +
        • +
      +
      4. +
    4. +

      Where the DPIA did not provide how to effectively address the risks, the +Privacy Manager must initiate the consultation with the competent +Supervisory Authority to receive help with searching for the solution. +In this case, PlayForm must not conduct the activity before the +Supervisory Authority approves the processing activity in question.

      +
      5. +
    +
    3. +
+

Data Retention

+
    +
  1. +

    General Rule.

    +
      +
    1. +

      The Privacy Manager must make sure that PlayForm clearly defined the +data storage periods and/or criteria for determining the storage periods +for each processing activity it has. The periods for each processing +activity must be specified in the Records of processing activities.

      +
      2. +
    2. +

      Each department within PlayForm must comply with the data storage +periods in accordance with the retention schedule provided in Records of +processing activities. The Privacy Manager must supervise each +department and make sure they comply with this requirement.

      +
      3. +
    3. +

      After the storage period ends, the personal data must be removed from +the disposal of the department responsible for the processing or, in +cases where the data is not needed for any other purposes, destroyed +completely, including from back-up copies and other media.

      +
      4. +
    4. +

      Whenever the storage period for a processing activity has ended, but the +personal data processed is necessary for other processing purposes, the +department manager must make sure that the personal data is not used for +the ceased processing activity, and the responsible employees do not +have the access to it unless required for any other activity.

      +
      5. +
    +
    2. +
  2. +

    Exemptions. The rules specified in +Subsection 8.1 have the following exceptions:

    +
      +
    1. +

      Business needs. Data retention periods can be prolonged, but no +longer than 60 days, in the case that the data deletion will interrupt +or harm our ongoing business. The Privacy Manager must approve any +unforeseen prolongation;

      +
      2. +
    2. +

      Technical impossibility. Some information is technically impossible +or disproportionally difficult to delete. For example, deletion of the +information may lead to breach of system integrity, or it is impossible +to delete the information from the backup copies. In such a case, the +information can be further stored, subject to the approval by the +Privacy Manager and making respective amendments to the Records of +processing activities; and

      +
      3. +
    3. +

      Anonymization. The Personal Data can be further processed for any +purposes (e.g., marketing) if we fully anonymize these data after the +retention period is expired. This means that all personal identifiers +and connections to them will be deleted from the data. To consider +Personal Data anonymous, it must be impossible to reidentify the Data +Subject from the data set.

      +
      4. +
    +
    3. +
+

Security

+
    +
  1. +

    Each department within PlayForm shall take all appropriate technical and +organizational measures that protect against unauthorized, unlawful, and/or +accidental access, destruction, modification, blocking, copying, +distribution, as well as from other illegal actions of unauthorized persons +regarding the personal data under their responsibility.

    +
    2. +
  2. +

    The employee responsible for the supervision after the security of personal +data within PlayForm shall be DSR Officer. This person implements the +guidelines and other specifications on data protection and information +security in his area of responsibility. He/she advises PlayForm management +on the planning and implementation of information security in PlayForm, and +must be involved in all projects at an early stage in order to take +security-related aspects into account as early as the planning phase.

    +
    3. +
+

Data Breach Response Procedure

+
    +
  1. +

    Response Team.

    +
      +
    1. +

      In case of revealing the Data Breach, CEO of PlayForm shall urgently +form the Data Breach Response Team (the “Response Team”), which will +handle the Data Breach, notify the appropriate persons, and mitigate its +risks.

      +
      2. +
    2. +

      The Response Team must be а multi-disciplinary group headed by CEO of +PlayForm and comprised of the Privacy Manager, privacy laws specialist +(whether internal or external), and knowledgeable and skilled +information security specialists within PlayForm or outsourcing +professionals, if necessary. The team must ensure that all employees and +engaged contractors/processors adhere to this Policy and provide an +immediate, effective, and skillful response to any suspected/alleged or +actual Data Breach affecting PlayForm.

      +
      3. +
    3. +

      The potential members of the Response Team must be prepared to respond +to а Data Breach. The Response Team shall perform all the +responsibilities of PlayForm mentioned in this Policy. The duties of the +Response Team are:

      +
        +
      • +

        to communicate the Data Breach to the competent Supervisory +Authority(-ies);

        +
        • +
      • +

        in case of high risk to the rights and freedoms of Data Subjects, to +communicate the Data Breach to the Data Subject;

        +
        • +
      • +

        if PlayForm obtain data from any third party as a processor, and a +Data Breach involves obtained data, to inform the third parties about +the Data Breach;

        +
        • +
      • +

        to communicate PlayForm’s contractors or any other third parties that +process the Personal Data involved in the Data Breach; and

        +
        • +
      • +

        to take all appropriate technical and organizational measures to cease +the Data Breach and mitigate its consequences;

        +
        • +
      • +

        to record the fact of the Data Breach in the Records of processing +activities and file an internal data breach report that describes the +event.

        +
        • +
      +
      4. +
    4. +

      The Response Team shall perform its duties until all the necessary +measures required by this Policy are taken.

      +
      5. +
    +
    2. +
  2. +

    Notification to Supervisory Authority.

    +
      +
    1. +

      PlayForm shall inform the Competent Supervisory Authority about the Data +Breach without undue delay and, where it is possible, not later than 72 +hours after having become aware of the Data Breach.

      +
      2. +
    2. +

      The Competent Supervisory Authority shall be determined by the residence +of the Data Subjects, whose information was involved in the Data Breach. +If the Data Breach concerns the Personal Data of Data Subjects from more +than one country, PlayForm shall inform all Competent Supervisory +Authorities.

      +
      3. +
    3. +

      To address the notification to the authority, the Response Team should +use Annex 1 to this Policy. Annex 1 contains all the necessary contact +information of the EU supervisory authorities. If the Data Breach +concerns Data Subjects from other than the EU countries, the Response +Team shall ask a competent privacy specialist for advice.

      +
      4. +
    4. +

      The notification to the Competent Supervisory Authority shall contain, +at least, following information:

      +
        +
      • +

        the nature of the Data Breach including where possible, the +categories and an approximate number of Data Subjects and Personal +Data records concerned;

        +
        • +
      • +

        the name and contact details of the Response Team, Privacy Manager +or, if not applicable, of the CEO;

        +
        • +
      • +

        the likely consequences of the Data Breach. Explain PlayForm’s point +of view on the purposes and possible further risks of the Data Breach. +E.g., the Personal Data may be stolen for the further sale, fraud +activities or blackmailing the concerned Data Subjects; and

        +
        • +
      • +

        the measures taken or proposed to be taken by PlayForm to address +the Data Breach, including, where appropriate, measures to mitigate +its possible adverse effects.

        +
        • +
      +
      5. +
    5. +

      To file a notification, the Response Team should use PlayForm’s Data +Breach Notification Form to the Supervisory Authority.

      +
      6. +
    +
    3. +
  3. +

    Notifications to Data Subjects.

    +
      +
    1. +

      When the Data Breach is likely to result in a high risk to the rights +and freedoms of Data Subjects (e.g., stealing of funds, assets, +proprietary information), we must also communicate the Data Breach to +the concerned Data Subjects without undue delay. The Privacy Manager +must determine if there is a high risk based on the risk factors +specified in Subsection 7.2.3 of this Policy.

      +
      2. +
    2. +

      The notification shall contain the following information:

      +
        +
      • +

        description of the Data Breach - what happened and what led to the +Data Breach, such as a security breach, employee’s negligence, error +in the system work. If the Response Team decided not to disclose the +causes of the Data Breach, then this clause must not be mentioned;

        +
        • +
      • +

        the measures taken by PlayForm regarding the Data Breach, including +security measures, internal investigations, and supervisory +authority notice;

        +
        • +
      • +

        recommendations for the concerned Data Subjects how to mitigate risks +and possible consequences, such as guidelines on how to restore +access to an account, preventing measures (change of a password); +and

        +
        • +
      • +

        the contact information of the Response Team or one of its members.

        +
        • +
      +
      3. +
    3. +

      The notification to the Data Subjects should be carried out by the +email letter or, where it is impossible to use the email, by other +available means of communication.

      +
      4. +
    4. +

      Exemptions. We do not have to send the notification to the Data +Subjects if any of the following conditions are met:

      +
        +
      • +

        PlayForm has implemented appropriate technical and organizational +protection measures, and those measures were applied to the Personal +Data affected by the Data Breach, in particular, those that leave the +Personal Data inaccessible to any person who is not authorized to +access it, such as encryption;

        +
        • +
      • +

        PlayForm has taken subsequent measures which ensure that the high risk +to the rights and freedoms of Data Subjects referred to in this +section is no longer likely to materialize; or

        +
        • +
      • +

        it would involve a disproportionate effort to communicate with every +concerned Data Subject. In such a case, there shall instead be a +public communication or similar measure whereby the Data Subjects are +informed in an equally effective manner.

        +
        • +
      +
      5. +
    +
    4. +
+

In the case we apply one of the exemptions, we must document the +circumstances, reason for not informing, and actions taken to meet one of the +exemptions.

+
    +
  1. +

    Communication with Third Parties.

    +
      +
    1. +

      In the case a Data Breach concerns the Personal Data shared with us or +processed by us on behalf of a Third Party, we must also notify the +Third Party about it within 24 hours. If we process the Personal Data as +a Data Processor, the notification of the Third Party does not exempt us +from the duty to mitigate the Data Breach consequences, but we must not +inform the Competent Supervisory Authority and Data Subjects.

      +
      2. +
    2. +

      In case of receiving the notification about the Data Breach from the +Data Processor or other Third Parties that have access to the Personal +Data, CEO of PlayForm shall, in accordance with this Section:

      +
        +
      • +

        form the Response Team;

        +
        • +
      • +

        request the Third Party to send the information mentioned in +Subsections 10.2-3 of this Policy;

        +
        • +
      • +

        where necessary, inform the Competent Supervisory Authority(-ies) and +Data Subjects; and

        +
        • +
      • +

        perform other steps of the Data Breach response procedure.

        +
        • +
      +
      3. +
    +
    2. +
+

List of Persons Briefed on Personal Data Protection Policy

+ +++++ + + + + + + + + + + + + +

Full Name

Status

Date

Nikola Hristov Briefed05.25.2018
+

ANNEX 1 TO THE PERSONAL DATA PROTECTION POLICY

+

European National Data Protection Authorities

+

Austria

+

Österreichische Datenschutzbehörde
+Hohenstaufengasse 3
+1010 Wien
+Tel. +43 1 531 15 202525
+Fax +43 1 531 15 202690
+E-mail: dsb@dsb.gv.at
+WebSite: HTTPS://www.dsb.gv.at

+

Art 29 WP Member: Dr Andrea JELINEK, Director, Österreichische +Datenschutzbehörde

+

Belgium

+

Commission de la protection de la vie privée
+Commissie voor de bescherming van de persoonlijke levenssfeer
+Rue de la Presse 35 / Drukpersstraat 35 1000 Bruxelles / 1000 Brussel
+Tel. +32 2 274 48 00
+Fax +32 2 274 48 35
+E-mail: commission@privacycommission.be
+WebSite: HTTPS://www.privacycommission.be

+

Art 29 WP Vice-President: Willem DEBEUCKELAERE, President of the Belgian Privacy +commission

+

Bulgaria

+

Commission for Personal Data Protection
+2, Prof. Tsvetan Lazarov Blvd. Sofia 1592
+Tel. +359 2 915 3580
+Fax +359 2 915 3525
+E-mail: kzld@cpdp.bg
+WebSite: HTTPS://www.cpdp.bg

+

Art 29 WP Member: Mr. Ventsislav KARADJOV, Chairman of the Commission for +Personal Data Protection
+Art 29 WP Alternate Member: Ms. Mariya MATEVA

+

Croatia

+

Croatian Personal Data Protection Agency
+Martićeva 14
+10000 Zagreb
+Tel. +385 1 4609 000
+Fax +385 1 4609 099
+E-mail: azop@azop.hr or info@azop.hr
+WebSite: HTTPS://www.azop.hr

+

Art 29 WP Member: Mr. Anto RAJKOVAČA, Director of the Croatian Data Protection +Agency

+

Cyprus

+

Commissioner for Personal Data Protection
+1 Iasonos Street,
+1082 Nicosia
+P.O. Box 23378, CY-1682 Nicosia Tel. +357 22 818 456
+Fax +357 22 304 565
+E-mail: commissioner@dataprotection.gov.cy
+WebSite: HTTPS://www.dataprotection.gov.cy

+

Art 29 WP Member: Ms. Irene LOIZIDOU NIKOLAIDOU
+Art 29 WP Alternate Member: Mr. Constantinos GEORGIADES

+

Czech Republic

+

The Office for Personal Data Protection
+Urad pro ochranu osobnich udaju Pplk. Sochora 27
+170 00 Prague 7
+Tel. +420 234 665 111
+Fax +420 234 665 444
+E-mail: posta@uoou.cz
+WebSite: HTTPS://www.uoou.cz

+

Art 29 WP Member: Ms. Ivana JANŮ, President of the Office for Personal Data +Protection
+Art 29 WP Alternate Member: Mr. Ivan PROCHÁZKA, Adviser to the President of the +Office

+

Denmark

+

Datatilsynet
+Borgergade 28, 5
+1300 Copenhagen K
+Tel. +45 33 1932 00
+Fax +45 33 19 32 18
+E-mail: dt@datatilsynet.dk
+WebSite: HTTPS://www.datatilsynet.dk

+

Art 29 WP Member: Ms. Cristina Angela GULISANO, Director, Danish Data Protection +Agency (Datatilsynet)
+Art 29 WP Alternate Member: Mr. Peter FOGH KNUDSEN, Head of International +Division at the Danish Data Protection Agency (Datatilsynet)

+

Estonia

+

Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)
+Väike-Ameerika 19
+10129 Tallinn
+Tel. +372 6274 135
+Fax +372 6274 137
+E-mail: info@aki.ee
+WebSite: HTTPS://www.aki.ee/en

+

Art 29 WP Member: Mr. Viljar PEEP, Director General, Estonian Data Protection +Inspectorate
+Art 29 WP Alternate Member: Ms. Maarja Kirss

+

Finland

+

Office of the Data Protection Ombudsman
+P.O. Box 315
+FIN-00181 Helsinki Tel. +358 10 3666 700
+Fax +358 10 3666 735
+E-mail: tietosuoja@om.fi
+WebSite: HTTPS://www.tietosuoja.fi/en

+

Art 29 WP Member: Mr. Reijo AARNIO, Ombudsman of the Finnish Data Protection +Authority
+Art 29 WP Alternate Member: Ms. Elisa KUMPULA, Head of Department

+

France

+

Commission Nationale de l’Informatique et des Libertés - CNIL
+8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02
+Tel. +33 1 53 73 22 22
+Fax +33 1 53 73 22 00
+WebSite: HTTPS://www.cnil.fr

+

Art 29 WP Member: Ms. Isabelle FALQUE-PIERROTIN, President of CNIL
+Art 29 WP Alternate Member: Ms. Florence RAYNAL

+

Germany

+

Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit
+Husarenstraße 30
+53117 Bonn
+Tel. +49 228 997799 0; +49 228 81995 0
+Fax +49 228 997799 550; +49 228 81995 550
+E-mail: poststelle@bfdi.bund.de
+WebSite: HTTPS://www.bfdi.bund.de

+

The competence for complaints is split among different data protection +supervisory authorities in Germany.

+

Competent authorities can be identified according to the list provided under

+

HTTPS://www.bfdi.bund.de/EN/Service/Anschriften/Laender/Laender-node.html

+

Art 29 WP Member: Ms. Andrea VOSSHOFF, Federal Commissioner for Freedom of +Information
+Art 29 WP Alternate Member: Prof. Dr. Johannes CASPAR, representative of the +federal states

+

Greece

+

Hellenic Data Protection Authority
+Kifisias Av. 1-3, PC 11523 Ampelokipi Athens
+Tel. +30 210 6475 600
+Fax +30 210 6475 628
+E-mail: contact@dpa.gr
+WebSite: HTTPS://www.dpa.gr

+

Art 29 WP Member: Mr. Konstantinos Menoudakos, President of the Hellenic DPA
+Art 29 WP Alternate Member: Dr. Vasilios ZORKADIS, Director

+

Hungary

+

National Authority for Data Protection and Freedom of Information
+Szilágyi Erzsébet fasor 22/C H-1125 Budapest
+Tel. +36 1 3911 400
+E-mail: peterfalvi.attila@naih.hu
+WebSite: HTTPS://www.naih.hu

+

Art 29 WP Member: Dr Attila PÉTERFALVI, President of the National Authority for +Data Protection and Freedom of Information
+Art 29 WP Alternate Member: Mr. Endre Győző SZABÓ Vice-president of the National +Authority for Data Protection and Freedom of Information

+

Ireland

+

Data Protection Commissioner
+Canal House Station Road Portarlington Co. Laois
+Lo-Call: 1890 25 22 31
+Tel. +353 57 868 4800
+Fax +353 57 868 4757
+E-mail: info@dataprotection.ie
+WebSite: HTTPS://www.dataprotection.ie

+

Art 29 WP Member: Ms. Helen DIXON, Data Protection Commissioner
+Art 29 WP Alternate Members: Mr. John O’DWYER, Deputy Commissioner; Mr. Dale +SUNDERLAND, Deputy Commissioner

+

Italy

+

Garante per la protezione dei dati personali
+Piazza di Monte Citorio, 121 00186 Roma
+Tel. +39 06 69677 1
+Fax +39 06 69677 785
+E-mail: garante@garanteprivacy.it
+WebSite: HTTPS://www.garanteprivacy.it

+

Art 29 WP Member: Mr. Antonello SORO, President of Garante per la protezione dei +dati personali
+Art 29 WP Alternate Member: Ms. Giuseppe BUSIA, Secretary General of Garante per +la protezione dei dati personali

+

Latvia

+

Data State Inspectorate Director: Ms. Daiga Avdejanova
+Blaumana str. 11/13-15
+1011 Riga
+Tel. +371 6722 3131
+Fax +371 6722 3556
+E-mail: info@dvi.gov.lv
+WebSite: HTTPS://www.dvi.gov.lv

+

Art 29 WP Alternate Member: Ms. Aiga BALODE

+

Lithuania

+

State Data Protection
+Žygimantų str. 11-6a 011042 Vilnius
+Tel. + 370 5 279 14 45
+Fax +370 5 261 94 94
+E-mail: ada@ada.lt
+WebSite: HTTPS://www.ada.lt

+

Art 29 WP Member: Mr. Raimondas Andrijauskas, Director of the State Data +Protection Inspectorate
+Art 29 WP Alternate Member: Ms. Neringa KAKTAVIČIŪTĖ-MICKIENĖ, Head of +Complaints Investigation and International Cooperation Division

+

Luxembourg

+

Commission Nationale pour la Protection des Données
+1, avenue du Rock’n’roll L-4361 Esch-sur-Alzette Tel. +352 2610 60 1
+Fax +352 2610 60 29
+E-mail: info@cnpd.lu
+WebSite: HTTPS://www.cnpd.lu

+

Art 29 WP Member: Ms. Tine A. LARSEN, President of the Commission Nationale pour +la Protection des Données
+Art 29 WP Alternate Member: Mr. Thierry LALLEMANG, Commissioner

+

Malta

+

Office of the Data Protection Commissioner
+Data Protection Commissioner: Mr. Joseph Ebejer
+2, Airways House
+High Street, Sliema SLM 1549 Tel. +356 2328 7100
+Fax +356 2328 7198
+E-mail: commissioner.dataprotection@gov.mt
+WebSite: HTTPS://idpc.org.mt

+

Art 29 WP Member: Mr. Saviour CACHIA, Information and Data Protection +Commissioner
+Art 29 WP Alternate Member: Mr. Ian DEGUARA, Director - Operations and Programme +Implementation

+

Netherlands

+

Autoriteit Persoonsgegevens
+Prins Clauslaan 60
+P.O. Box 93374
+2509 AJ Den Haag/The Hague Tel. +31 70 888 8500
+Fax +31 70 888 8501
+E-mail: info@autoriteitpersoonsgegevens.nl
+WebSite: HTTPS://autoriteitpersoonsgegevens.nl/nl

+

Art 29 WP Member: Mr. Aleid WOLFSEN, Chairman of Autoriteit Persoonsgegevens

+

Poland

+

The Bureau of the Inspector General for the Protection of Personal Data – GIODO
+ul. Stawki 2
+00-193 Warsaw
+Tel. +48 22 53 10 440
+Fax +48 22 53 10 441
+E-mail: kancelaria@giodo.gov.pl; desiwm@giodo.gov.pl
+WebSite: HTTPS://www.giodo.gov.pl

+

Art 29 WP Member: Ms. Edyta BIELAK-JOMAA, Inspector General for the Protection +of Personal Data

+

Portugal

+

Comissão Nacional de Protecção de Dados - CNPD
+R. de São. Bento, 148-3° 1200-821 Lisboa
+Tel. +351 21 392 84 00
+Fax +351 21 397 68 32
+E-mail: geral@cnpd.pt
+WebSite: HTTPS://www.cnpd.pt

+

Art 29 WP Member: Ms. Filipa CALVÃO, President, Comissão Nacional de Protecção +de Dados
+Art 29 WP Alternate Member: Isabel CRUZ, Secretary-General of the DPA

+

Romania

+

The National Supervisory Authority for Personal Data Processing President: Mrs. +Ancuţa Gianina Opre
+B-dul Magheru 28-30
+Sector 1, BUCUREŞTI
+Tel. +40 21 252 5599
+Fax +40 21 252 5757
+E-mail: anspdcp@dataprotection.ro
+WebSite: HTTPS://www.dataprotection.ro

+

Art 29 WP Member: Ms. Ancuţa Gianina OPRE, President of the National Supervisory +Authority for Personal Data Processing
+Art 29 WP Alternate Member: Ms. Alina SAVOIU, Head of the Legal and +Communication Department

+

Slovakia

+

Office for Personal Data Protection of the Slovak Republic
+Hraničná 12
+820 07 Bratislava 27
+Tel.: + 421 2 32 31 32 14
+Fax: + 421 2 32 31 32 34
+E-mail: statny.dozor@pdp.gov.sk
+WebSite: HTTPS://dataprotection.gov.sk

+

Art 29 WP Member: Ms. Soňa PŐTHEOVÁ, President of the Office for Personal Data +Protection of the Slovak Republic
+Art 29 WP Alternate Member: Mr. Anna VITTEKOVA, Vice President

+

Slovenia

+

Information Commissioner
+Ms. Mojca Prelesnik Zaloška 59
+1000 Ljubljana
+Tel. +386 1 230 9730
+Fax +386 1 230 9778
+E-mail: gp.ip@ip-rs.si
+WebSite: HTTPS://www.ip-rs.si

+

Art 29 WP Member: Ms. Mojca PRELESNIK, Information Commissioner of the Republic +of Slovenia

+

Spain

+

Agencia de Protección de Datos
+C/Jorge Juan, 6
+28001 Madrid
+Tel. +34 91399 6200
+Fax +34 91455 5699
+E-mail: internacional@agpd.es
+WebSite: HTTPS://www.agpd.es

+

Art 29 WP Member: Ms. María del Mar España Martí, Director of the Spanish Data +Protection Agency
+Art 29 WP Alternate Member: Mr. Rafael GARCIA GOZALO

+

Sweden

+

Datainspektionen
+Drottninggatan 29 5th Floor
+Box 8114
+20 Stockholm
+Tel. +46 8 657 6100
+Fax +46 8 652 8652
+E-mail: datainspektionen@datainspektionen.se
+WebSite: HTTPS://www.datainspektionen.se

+

Art 29 WP Member: Ms. Kristina SVAHN STARRSJÖ, Director General of the Data +Inspection Board
+Art 29 WP Alternate Member: Mr. Hans-Olof LINDBLOM, Chief Legal Adviser

+

United Kingdom

+

The Information Commissioner’s Office
+Water Lane, Wycliffe House Wilmslow - Cheshire SK9 5AF Tel. +44 1625 545 745
+E-mail: international.team@ico.org.uk
+WebSite: HTTPS://ico.org.uk

+

Art 29 WP Member: Ms. Elizabeth DENHAM, Information Commissioner
+Art 29 WP Alternate Member: Mr. Steve WOOD, Deputy Commissioner

+

EUROPEAN FREE TRADE AREA (EFTA)

+

Iceland

+

Icelandic Data Protection Agency
+Rauðarárstíg 10
+Reykjavík
+Tel. +354 510 9600; Fax +354 510 9606
+E-mail: postur@personuvernd.is
+WebSite: HTTPS://www.personuvernd.is

+

Liechtenstein

+

Data Protection Office
+Kirchstrasse 8, P.O. Box 684
+9490 Vaduz
+Principality of Liechtenstein Tel. +423 236 6090
+E-mail: info.dss@llv.li
+WebSite: HTTPS://www.datenschutzstelle.li

+

Norway

+

Datatilsynet
+Data Protection Authority: Mr. Bjørn Erik THORN
+The Data Inspectorate
+P.O. Box 8177 Dep 0034 Oslo
+Tel. +47 22 39 69 00; Fax +47 22 42 23 50
+E-mail: postkasse@datatilsynet.no
+WebSite: HTTPS://www.datatilsynet.no

+

Switzerland

+

Data Protection and Information Commissioner of Switzerland
+Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter Mr. Adrian +Lobsiger
+Feldeggweg 1
+3003 Bern
+Tel. +41 58 462 43 95; Fax +41 58 462 99 96
+E-mail: contact20@edoeb.admin.ch
+WebSite: HTTPS://www.edoeb.admin.ch

+

Footnotes

+
    +
  1. +

    HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en; ↩

    +
    2. +
  2. +

    HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en; ↩

    +
    3. +
+
\ No newline at end of file diff --git a/Target/Gdpr/index.html b/Target/Gdpr/index.html new file mode 100644 index 00000000..5ff594a3 --- /dev/null +++ b/Target/Gdpr/index.html @@ -0,0 +1,1673 @@ + Personal Data Protection Policy
+

PERSONAL DATA PROTECTION POLICY

+

Effective date: 05.25.2018 / May 25th 2018
+Last updated: 02.11.2022 / February 11th 2022

+

We at PlayForm ltd. are committed to processing personal data securely and +respecting privacy of the concerned individuals.

+ ++++ + + + + + + + + + +
Version No. and date of the last update:

v. 1.0.

+

February 11th 2022

This policy shall be reviewed annually or each time when the changes in our data processing occur.
+

Scope and Definitions

+
    +
  1. +

    Scope. This Personal Data Protection +Policy (the “Policy”) describes PlayForm ltd. internal rules for +personal data processing and protection. The Policy applies to PlayForm +ltd., including PlayForm ltd. employees and contractors (“we”, “us”, +“our”, “PlayForm”). The management of each entity is ultimately +responsible for the implementation of this policy, as well as to ensure, at +entity level, there are adequate and effective procedures in place for its +implementation and ongoing monitoring of its adherence. For the purposes of +this Policy, employees and contractors are jointly referred to as the +“employees”.

    +
    2. +
  2. +

    Privacy Manager. Privacy Manager is an +employee of PlayForm responsible for personal data protection compliance +within PlayForm (the “Privacy Manager”). The Privacy Manager is in +charge of performing the obligations imposed by this Policy and supervising +other employees, who subject to this Policy, regarding their adherence to +this Policy. The Privacy Manager must be involved in all projects at an +early stage in order to take personal data protection aspects into account +as early as the planning phase.
    +The designated Privacy Manager at PlayForm ltd. is Nikola Hristov +Nikola@PlayForm.LTD.

    +
    3. +
  3. +

    Definitions.

    +
    4. +
+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Competent Supervisory Authoritymeans a public authority that is responsible for regulating and supervising personal data protection with regards to activities of PlayForm.
Data Breach

means a breach of the security and/or confidentiality leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data transmitted, stored or otherwise processed.

+

This includes but is not limited to e-mails sent to an incorrect or disclosed list of recipients, an unlawful publication of the Personal Data, loss or theft of physical records, and unauthorized access to personal information.

Data Controllermeans the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines (make a decision) the purposes and means of the processing of Personal Data.
Data Processormeans a natural or legal person, public authority, agency or other body which processes the Personal Data on behalf of the data controller.
Data Protection Lawsmean any laws and legal rules on personal data use and protection applicable to the activities of PlayForm, including, but not limited to the Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation, GDPR).
Data Subject Request (DSR)means any request from the Data Subject and concerning their personal data and/or data subject rights.
Data Subjectmeans a natural person, whose Personal Data we process. Data Subjects include but are not limited to users, website visitors, employees, contractors, and partners of PlayForm.
Personal Datameans any information relating to an identified or identifiable Data Subject; a Data Subject can be identified by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or the combination of factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that Data Subject.
Processingmeans any operation or set of operations which is performed by PlayForm on Personal Data, such as 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.
Standard Contractual Clausesmeans the European Commission Decision of February, 5 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC of the European Parliament and of the Council (2010/87/EU).
Third Partymeans a natural or legal person, who accesses the Personal Data for further processing and is not an employee, member or corporate affiliate of PlayForm. This definition does not apply to natural persons, who provide services to PlayForm as contractors on a regular basis.
Usermeans a Data Subject who uses our services provided on PlayForm website.
+

Data Processing Principles

+
    +
  1. +

    PlayForm’s processing activities must be in line with the principles +specified in this Section. The Privacy Manager must make sure that +PlayForm’s compliance documentation, as well as data processing activities, +are compliant with the data protection principles.

    +
    2. +
  2. +

    We must process the Personal Data in accordance with the following +principles:

    +
      +
    1. +

      Lawfully, fairly and in a transparent manner (lawfulness, fairness and +transparency). We shall always have a legal ground for the processing +(described in Section 3 of this Policy), collect the amount of data +adequate to the purpose and legal grounds, and we make sure the Data +Subjects are aware of the processing;

      +
      2. +
    2. +

      Collected for specified, explicit and legitimate purposes and not +further processed in a manner that is incompatible with those purposes +(purpose limitation). We must not process the Personal Data for the +purposes not specified in our compliance documentation without obtaining +specific approval of the Privacy Manager;

      +
      3. +
    3. +

      Adequate, relevant and limited to what is necessary for the purposes for +which they are processed (data minimization). We always make sure +the data we collect is not excessive and limited by the strict +necessity;

      +
      4. +
    4. +

      Accurate and, where necessary, kept up to date (accuracy). We +endeavor to delete inaccurate or false data about Data Subjects and make +sure we update the data. Data Subjects can ask us for a correction of +the Personal Data;

      +
      5. +
    5. +

      Kept in a form which permits identification of Data Subjects for no +longer than is necessary for the purposes for which the Personal Data +are processed (storage period limitation). The storage periods must +be limited as prescribed by Data Protection Laws and this Policy; and

      +
      6. +
    6. +

      Process in a manner that ensures appropriate security of the Personal +Data, including protection against unauthorized or unlawful processing +and accidental loss, destruction or damage, using appropriate technical +or organizational measures (confidentiality, integrity, and +availability).

      +
      7. +
    +
    3. +
  3. +

    Accountability.

    +
      +
    1. +

      We shall be able to demonstrate our compliance with Data Protection Laws +(accountability principle). In particular, we must ensure and +document all relevant procedures, efforts, internal and external +consultations on personal data protection including:

      +
        +
      • +

        the fact of appointing a person responsible for PlayForm’s data +protection compliance;

        +
        • +
      • +

        where necessary, a record of a Data Processing Impact Assessment;

        +
        • +
      • +

        developed and implemented notices, policies, and procedures, such as +Privacy Notice, this policy or Data Breach response procedure;

        +
        • +
      • +

        the fact of staff training on compliance with Data Protection laws; +and

        +
        • +
      • +

        assessment, implementation, and testing organizational and technical +data protection measures.

        +
        • +
      +
      2. +
    2. +

      The Privacy Manager must maintain PlayForm’s Records of processing +activities, which is an accountability document that describes personal +data processing activities of PlayForm, prepared in accordance with Art. +30 of the GDPR (the “Records of processing activities”). The Records +of processing activities must maintain, at least, the following +information about each processing activity:

      +
        +
      • +

        contact details of PlayForm, the EU Representative, and, where +applicable, of the Data Protection Officer;

        +
        • +
      • +

        name of the activity, its purposes and legal basis along with, where +applicable, the legitimate interests of PlayForm;

        +
        • +
      • +

        data subjects and personal data categories concerned;

        +
        • +
      • +

        data retention periods;

        +
        • +
      • +

        general description of applicable security measures;

        +
        • +
      • +

        recipients, including joint controllers, processors, and contractors +involved, as well as the fact of the international data transfer with +the safeguards applied to the transfer;

        +
        • +
      • +

        where applicable, a reference to the Data Processing Impact +Assessment;

        +
        • +
      • +

        where applicable, a reference to the record of the data breach +occurred involving the personal data;

        +
        • +
      • +

        if PlayForm acts as a data processor, the information to be provided +includes the names and contact details of controllers, name and +contact details of controller’s representative (if applicable), +categories of processing (activities), names of third countries or +international organizations that personal data are transferred to (if +applicable), safeguards for exceptional transfers of personal data to +third countries or international organizations (if applicable), and +general description of technical and organizational security measures.

        +
        • +
      +
      3. +
    +
    4. +
+ +
    +
  1. +

    Legal grounds.

    +
      +
    1. +

      Each processing activity must have one of the lawful grounds specified +in this Section to process the Personal Data. If we do not have any of +the described, we cannot collect or further process the Personal Data.

      +
      2. +
    2. +

      If PlayForm is intended to use personal data for other purposes than +those specified in the Records of processing activities, the Privacy +Manager must evaluate, determine, and, if necessary, collect/record the +appropriate legal basis for it.

      +
      3. +
    3. +

      Performance of the contract. Where PlayForm has a contract with the +Data Subject, e.g., website’s Terms of Use or the employment contract, +and the contract requires the provision of personal data from the Data +Subject, the applicable legal ground will be the performance of the +contract.

      +
      4. +
    4. +

      Consent. To process the personal data based on the consent, we must +obtain the consent before the Processing and keep the evidence of the +consent with the records of Data Subject’s Personal Data. The Privacy +Manager must make sure that the consent collected from Data Subjects +meet the requirements of Data Protection Laws and this Policy. In +particular, the Privacy Manager must make sure that:

      +
        +
      • +

        the Data Subject must be free to give or refuse to give consent.

        +
        • +
      • +

        the consent is in the form of an active indication from the Data +Subject, i.e., the consent checkbox must not be pre-ticked for the +user.

        +
        • +
      • +

        the request for the consent clearly articulates the purposes of the +processing, and other information specified in Subsection 6.2 is +available to the Data Subject.

        +
        • +
      • +

        the Data Subject must be free to give one’s consent or to revoke it.

        +
        • +
      +
      5. +
    5. +

      Legitimate interests. We have the right to use personal data in our +‘legitimate interests’. The interests can include the purposes that are +justified by the nature of our business activities, such as the +marketing analysis of personal data. For PlayForm to use legitimate +interests as a legal ground for the processing, the Privacy Manager must +make sure that:

      +
        +
      • +

        the legitimate interest in the processing is clearly defined and +recorded in the Records of processing activities;

        +
        • +
      • +

        any envisaged risks to Data Subject rights and interests are spotted. +The examples of the risks can be found in Subsection 7.2.;

        +
        • +
      • +

        the Data Subjects have reasonable expectations about the processing, +and additional protective measures to address the risks are taken;

        +
        • +
      • +

        subject to the conditions of Subsection 6.7 (Right to object against +the processing), the Data Subject is provided with the opportunity to +opt-out from the processing for the described legitimate interests.
        +If at least one of the above conditions is not met by PlayForm, the +Privacy Manager must choose and propose a different legal ground for +the processing, such as consent.

        +
        • +
      +
      6. +
    6. +

      Legal Compliance and Public Interest. Besides the grounds specified +afore, we might be requested by the laws of the European Union or laws +of the EU Member State to process Personal Data of our Users. For +example, we can be required to collect, analyze, and monitor the +information of Users to comply with financial or labor laws.
      +Whenever we have such an obligation, we must make sure that:

      +
        +
      • +

        we process personal data strictly in accordance with relevant legal +requirements;

        +
        • +
      • +

        we do not use or store the collected Personal Data for other purposes +than legal compliance; and

        +
        • +
      • +

        the Data Subjects are properly and timely informed about our +obligations, scope, and conditions of personal data processing.

        +
        • +
      +
      7. +
    +
    2. +
+

Important: Where PlayForm has the law requirements of another country to process +personal data, the Privacy Manager must propose using another legal ground for +the processing under Data Protection Laws, such as legitimate interests or +consent.

+

Access to Personal Data

+
    +
  1. +

    Access to Personal Data.

    +
      +
    1. +

      The employees must have access to the personal data on a “need-to-know” +basis. The data can be accessed only if it is strictly necessary to +perform one of the activities specified in the Records of processing +activities. The employees and contractors shall have access to the +Personal Data only if they have the necessary credentials for it.

      +
      2. +
    2. +

      Heads of the departments within PlayForm are responsible for their +employees’ access and processing of personal data. The heads must +maintain the list of employees that are entitled to access and process +personal data. The Privacy Manager shall have the right to review the +list and, where necessary, request the amendments to meet the +requirements of this Policy.

      +
      3. +
    3. +

      Heads of the departments within PlayForm must ensure that the employees +under their supervision are aware of the Data Protection Laws and comply +with the rules set in this Policy. To make sure our employees are able +to comply with the data protection requirements, we must provide them +with adequate data protection training.

      +
      4. +
    4. +

      All employees accessing personal data shall keep strict confidentiality +regarding the data they access. The employees that access personal data +must use only those means (software, premises, etc.) for the processing +that were prescribed by PlayForm. The data must not be disclosed or +otherwise made available out of the management instructions.

      +
      5. +
    5. +

      The employees within their competence must assist PlayForm’s +representatives, including the Privacy Manager, in any efforts regarding +compliance with Data Protection Laws and/or this Policy.

      +
      6. +
    6. +

      When an employee detects or believes there is suspicious activity, data +breach, non-compliance with Data Protection Laws and/or this Policy, or +a DSR was not routed to the competent department within PlayForm, the +employee must report such activity to the Privacy Manager.

      +
      7. +
    7. +

      Employees that are unsure about whether they can legitimately process or +disclose Personal Data must seek advice from the Privacy Manager before +taking any action.

      +
      8. +
    8. +

      Any occasional access to personal data for activities not specified in +the Records of processing activities is prohibited. If there is a strict +necessity for immediate access, the Privacy Manager must approve the +access first.

      +
      9. +
    +
    2. +
+

Third Parties

+
    +
  1. +

    Before sharing personal data with any person outside of PlayForm, the +Privacy Manager must ensure that this Third Party has an adequate data +protection level and provide sufficient data protection guarantees in +accordance with Data Protection Laws, including, but not limited to the +processorship requirements (Art. 28 of the GDPR) and international transfers +compliance (Section 5 of the GDPR). Where necessary, the Privacy Manager +must make sure that PlayForm enters into the appropriate data protection +contract with the third party.

    +
    2. +
  2. +

    An employee can share personal data with third parties only if and to the +extent that was directly prescribed by the manager and specified in the +Records of processing activities.

    +
    3. +
  3. +

    If we are required to delete, change, or stop the processing of the Personal +Data, we must ensure that the Third Parties, with whom we shared the +Personal Data, will fulfill these obligations accordingly.

    +
    4. +
  4. +

    Whenever PlayForm is engaged as a data processor on behalf of another +entity, the Privacy Manager must make sure PlayForm complies with the +processorship obligation. In particular, the appropriate data processing +agreement in accordance with the Data Protection Laws must be in place. The +Privacy Manager must supervise the compliance with data processing +instructions from the controller, including regarding the scope of +processing activities, involvement of sub-processors, international +transfers, storage, and further disposal of processed personal data. The +personal data processed under the processor role must not be processed for +any other purposes than specified in the relevant instructions, agreement or +other legal act regulating the relationships with the controller.

    +
    5. +
+

International Transfers

+
    +
  1. +

    If we have the employees, contractors, corporate affiliates, or Data +Processors outside of the EEA, and we transfer Personal Data to them for the +processing, the Privacy Manager must make sure PlayForm takes all necessary +and appropriate safeguards in accordance with Data Protection Laws.

    +
    2. +
  2. +

    The Privacy Manager must assess the safeguards available and propose to the +PlayForm’s management the appropriate safeguard for each international +transfer. The following regimes apply to the transfers of Personal Data +outside of the EU:

    +
      +
    • +

      where the European Commission decides that the country has an adequate +level of personal data protection, the transfer does not require taking +additional safeguards. The full list of adequate jurisdictions can be +found on the relevant page of the European Commission’s website1.

      +
      • +
    • +

      to transfer Personal Data to our contractors or partners (Data Processors +or Controllers) in other third countries, we must conclude Standard +Contractual Clauses with that party. The draft version along with the +guidance can be found on the relevant page of the European Commission’s +website2;

      +
      • +
    • +

      if we have a corporate affiliate or an entity in other countries, we may +choose to adopt Binding Corporate Rules in accordance with Article 47 of +the GDPR or an approved code of conduct pursuant to Article 40 of the +GDPR;

      +
      • +
    • +

      we also can transfer Personal Data to entities that have an approved +certification in accordance with Article 42 of the GDPR, which certifies +an appropriate level of company’s data protection.

      +
      • +
    +
    3. +
+
    +
  1. +

    As a part of the information obligations, PlayForm must inform the Data +Subjects that their Personal Data is being transferred to other countries, +as well as provide them with the information about the safeguards used for +the transfer. The information obligation is to be performed in accordance +with Subsection 6.2.

    +
    2. +
  2. +

    In the exceptional cases (the “Derogation”), where we cannot apply the +safeguards mentioned afore and we need to transfer Personal Data, we must +take an explicit consent (active statement) from the Data Subject or it must +be strictly necessary for the performance of the contract between us and the +Data Subject, or other derogation conditions apply in accordance with the +Data Protection Laws. The Privacy Manager must pre-approve any Derogation +transfers and document the approved Derogations, as well as the rationale +for them.

    +
    3. +
+

Rights of Data Subjects

+
    +
  1. +

    Our Responsibilities.

    +
      +
    1. +

      Privacy Manager is ultimately responsible for handing all DSR received +by PlayForm. In the case of receiving any outstanding or unusual DSR, +the employee must seek advice from the Privacy Manager before taking any +action.

      +
      2. +
    2. +

      DSR Team within PlayForm is responsible for handling DSRs from PlayForm +Users on a daily basis. The Human Resources department is responsible +for handling the DSR from PlayForm employees.

      +
      3. +
    3. +

      All DSRs from the Users must be addressed at and answered from the +following e-mail address: DSR@PlayForm.LTD. DSR from the employees can +be addressed directly to the HR manager or at DSR@PlayForm.LTD.

      +
      4. +
    4. +

      The responsible employee must answer to the DSR within one (1) month +from receiving the request. If complying with the DSR takes more than +one month in time, the responsible employee must seek advice from the +Privacy Manager and, where necessary, inform the Data Subject about the +prolongation of the response term for up to two (2) additional months.

      +
      5. +
    5. +

      The responsible employee must analyze the received DSR for the following +criteria:

      +
        +
      • +

        Data Subject identification. Before considering the DSR content, +the responsible employee must make sure the Data Subject is the same +person he/she claims to be. For this purpose, the connection between +the personal data records and the data subject must be established.

        +
        • +
      • +

        Personal data. The responsible employee must check whether +PlayForm has access to the personal data requested. If PlayForm does +not have the personal data under the control, the responsible employee +must inform the Data Subject, and, if possible, instruct on the +further steps on how to access the data in question;

        +
        • +
      • +

        Content of the request. Depending on the content of the DSR, the +responsible employee must define the type of the request and check +whether it meets the conditions prescribed by this Policy and Data +Protection Laws. The types of requests and the respective conditions +for each of them can be consulted in Subsections 6.3-6.9. If the +request does not meet the described criteria, the responsible employee +must refuse to comply with the DSR and inform the Data Subject about +the reasons for refusing;

        +
        • +
      • +

        Free of charge. Generally, all requests of Data Subjects and +exercises of their rights are free of charge. If the responsible +employee finds that the Data Subject exercises the rights in an +excessive or unfound way (e.g., intended to harm or interrupt +PlayForm’s business activities), the employee must seek the advice +from the Privacy Manager, and, upon receiving of the latter, may +either charge the Data Subject a reasonable fee or refuse to comply +with the request;

        +
        • +
      • +

        Documenting. Whenever PlayForm receives the DSR, the Privacy +Manager must make sure that the data and time, Data Subject, type of +the request and the decision made regarding it are well documented. In +the case of refusing to comply with the request, the reasons for +refusing must be documented as well;

        +
        • +
      • +

        Recipients. When addressing the DSR, the Privacy Manager must make +sure that all concerned recipients were informed the necessary actions +were taken.

        +
        • +
      +
      6. +
    +
    2. +
  2. +

    The right to be informed.

    +
      +
    1. +

      PlayForm must notify each Data Subject about the collection and further +processing of the Personal Data.

      +
      2. +
    2. +

      The information to be provided includes: the name and contact details of +PlayForm; generic purposes of and the lawful basis for the data +collection and further processing; categories of Personal Data +collected; recipients/categories of recipients; retention periods; +information about data subject rights, including the right to complain +to the competent Supervisory Authority; the consequences of the cases +where the data is necessary for the contract performance and the Data +Subject does not provide the required data; details of the safeguards +where personal data is transferred outside the EEA; and any third-party +source of the personal data, without specification for the particular +case (except if we receive the direct request from the Data Subject).

      +
      3. +
    3. +

      The Users must be informed by the Privacy Policy accessible at +PlayForm’s website and provided during the user registration. The +employees and contractors must be informed by a standalone employee +privacy statement, which explains the details described in p. 6.2.2 in a +case-based manner, describing the particular purposes and activities.

      +
      4. +
    4. +

      PlayForm must inform Data Subjects about data processing, including any +new processing activity introduced at PlayForm within the following +term:

      +
        +
      • +

        if personal data is collected from the data subject directly, the data +subject must be informed at the time we collect Personal Data from the +Data Subjects by showing the Data Subject our privacy statement;

        +
        • +
      • +

        if the personal data is collected from other sources: (a) within one +month from collecting it; (b) if the personal data are to be used for +communication with the data subject, at the latest at the time of the +first communication to that data subject; or (c) if a disclosure to +another recipient is envisaged, at the latest when the personal data +are first disclosed.

        +
        • +
      • +

        upon the request of the Data Subject; and

        +
        • +
      • +

        within one (1) month after any change of our personal data practices, +change of the controller of Personal Data or after significant changes +in our privacy statements.

        +
        • +
      +
      5. +
    +
    3. +
  3. +

    The right to access the information.

    +
      +
    1. +

      The Data Subject must be provided only with those personal data records +specified in the request. If the Data Subject requests access to all +personal data concerning her or him, the employee must seek advice from +the Privacy Manager first, to make sure all personal data of the Data +Subject is mapped and provided.

      +
      2. +
    2. +

      A Data Subject has the right to:

      +
        +
      • +

        learn if we process the Data Subject’s Personal Data;

        +
        • +
      • +

        obtain disclosure regarding aspects of the processing, including +detailed and case-specific information on purposes, categories of +Personal Data, recipients/categories of recipients, retention periods, +information about one’s rights, details of the relevant safeguards +where personal data is transferred outside the EEA, and any +third-party source of the personal data; and

        +
        • +
      • +

        obtain a copy of the Personal Data undergoing processing upon the +request.

        +
        • +
      +
      3. +
    +
    4. +
  4. +

    The right to verify the Data Subject’s information +and seek its rectification. The information we collect can +be/become inaccurate or out-of-date (e.g., mistakes in nationality, date of +birth, info on debts, economic activities). If we reveal that the Personal +Data is inaccurate or the Data Subject requests us to do so, we must ensure +that we correct all mistakes and update the relevant information.

    +
    5. +
  5. +

    The right to restrict processing.

    +
      +
    1. +

      The restriction of processing allows Data Subjects to temporarily stop +the use of their information to prevent the possible harm caused by such +use.

      +
      2. +
    2. +

      This right applies when the Data Subject:

      +
        +
      • +

        contests the accuracy of the Personal Data;

        +
        • +
      • +

        believes that we process the Personal Data unlawfully; and

        +
        • +
      • +

        objects against the processing and wants us not to process Personal +Data while we are considering the request.

        +
        • +
      +
      3. +
    3. +

      In the case of receiving the restriction request, we must not process +Personal Data in question for any other purpose than storing it or for +legal compliance purposes until the circumstances of restriction cease +to exist.

      +
      4. +
    +
    6. +
  6. +

    The right to withdraw the consent. For +the activities that require consent, the Data Subject can revoke their +consent at any time. If the Data Subject revokes the consent, we must record +the changes and must not process the Personal Data for consent-based +purposes. The withdrawal of consent does not affect the lawfulness of the +processing done before the withdrawal.

    +
    7. +
  7. +

    The right to object against the +processing.

    +
      +
    1. +

      If we process the information in our legitimate interests, e.g., for +direct marketing emails or for our marketing research purposes, the Data +Subject can object against the processing.

      +
      2. +
    2. +

      In the case of receiving the objection request case, we must consider +Data Subject’s request and, where we do not have compelling interests, +stop the processing for the specified purposes. If the personal data is +still to be processed for other purposes, the Privacy Manager must make +sure that the database has a record that the data cannot be further +processed for the objected activities.

      +
      3. +
    3. +

      The objection request can be refused only if the personal data in +question is used for scientific/historical research or statistical +purposes and was appropriately protected, i.e., by anonymization or +pseudonymization techniques.

      +
      4. +
    +
    8. +
  8. +

    Right to erasure/to be forgotten.

    +
      +
    1. +

      The Data Subjects have the right to request us to erase their Personal +Data if one of the following conditions are met:

      +
        +
      • +

        Personal Data is no longer necessary for the purposes of collection. +For example, a user has provided personal data for a one-time +activity, such as data validation or participation in a contest, and +the purpose is already fulfilled;

        +
        • +
      • +

        the Data Subject revokes one’s consent or objects to the processing +(where applicable) and there is no other legal ground for the +processing; or

        +
        • +
      • +

        we process the Personal Data unlawfully or its erasure is required by +the applicable legislation of the European Union or one of the Member +countries of the European Union.

        +
        • +
      +
      2. +
    2. +

      Conditions, under which we have the right to refuse the erasure:

      +
        +
      • +

        Personal Data is processed for scientific/historical research or +statistical purposes and is appropriately protected, i.e., +pseudonymized or anonymized;

        +
        • +
      • +

        Personal Data is still necessary for legal compliance (e.g., financial +or labor laws compliance).

        +
        • +
      +
      3. +
    3. +

      Only those personal data records must be deleted that were specified in +the request. If the Data Subject requests the deletion of all personal +data concerning her or him, the employee must seek advice from the +Privacy Manager first, to make sure all the data about the Data Subject +is mapped and can be deleted.

      +
      4. +
    4. +

      If the User still has an account with us and requests the erasure of +information necessary for maintaining the account, we must inform the +User that the erasure will affect user experience or can lead to the +closure of the account.

      +
      5. +
    +
    9. +
  9. +

    Data portability.

    +
      +
    1. +

      Data Subjects can ask us to transfer all the Personal Data and/or its +part in a machine-readable format to a third party. This right applies +in two cases:

      +
        +
      • +

        personal data was collected for the purpose of provision of our +services (performance of the contract); or

        +
        • +
      • +

        collected based on consent.

        +
        • +
      +
      2. +
    2. +

      To determine whether one of the p.6.9.1 conditions are met, the employee +must seek advice from the Privacy Manager and check the applicable legal +basis in the Records of processing activities. If the answer is +negative, the request can be refused by PlayForm, and the Privacy +Manager must decide whether to comply with the request on a voluntary +basis.

      +
      3. +
    3. +

      To comply with the request, the responsible employee must consolidate +requested Personal Data and send the data in the format we are usually +working with to the requested organization. The Data Subject must +provide the necessary contact details of the organization.

      +
      4. +
    +
    10. +
+

New Data Processing Activities

+
    +
  1. +

    Notification to Privacy Manager.

    +
      +
    1. +

      Before introducing any new activity that involves the processing of +personal data, an employee responsible for its implementation must +inform the Privacy Manager.

      +
      2. +
    2. +

      Upon receiving information about a new activity, Privacy Manager must:

      +
        +
      • +

        determine whether the data processing impact assessment (DPIA) and/or +the consultation with the Supervisory Authority is necessary. If the +answer is positive, the Privacy Manager must make sure the DPIA is +conducted and/or the Supervisory Authority is consulted in accordance +with the requirements of this Section and Data Protection Laws;

        +
        • +
      • +

        determine the legal basis for the processing and, where necessary, +take further action for its fixation;

        +
        • +
      • +

        make sure the processing activity is done in accordance with this +Policy, other PlayForm’s policies, as well as the Data Protection +Laws;

        +
        • +
      • +

        add the processing activity to the Records of processing activities;

        +
        • +
      • +

        amend the privacy information statements and, where necessary, inform +the concerned Data Subject accordingly.

        +
        • +
      +
      3. +
    +
    2. +
  2. +

    Data Processing Impact Assessment.

    +
      +
    1. +

      To make sure that our current or prospective processing activities do +not/will not violate the Data Subjects’ rights, PlayForm must, where +required by Data Protection Laws, conduct the Data Processing Impact +Assessment (DPIA), a risk-based assessment of the processing and search +for the measures to mitigate the risks. The Privacy Manager must make +sure the DPIA is conducted in accordance with this Section.

      +
      2. +
    2. +

      The Privacy Manager, where necessary, involving the competent employees +and/or external advisors, must conduct a DPIA if at least one of the +following conditions are met:

      +
        +
      • +

        the processing involves the use of new technologies, such as the +Artificial Intelligence, use of connected and autonomous devices, etc. +that creates certain legal, economic or similar effects to the Data +Subject;

        +
        • +
      • +

        we systematically assess and evaluate personal aspects of the Data +Subjects based on automated profiling, assigning the personal +score/rate, and create legal or similar effects for the Data Subject +by this activity;

        +
        • +
      • +

        we process on a large-scale sensitive data, which includes Personal +Data relating to criminal convictions and offences, the data about +vulnerable data subjects, the 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;

        +
        • +
      • +

        we collect or process Personal Data from a publicly accessible area or +public sources on a large scale, or combine or match two different +data sets; and

        +
        • +
      • +

        the Supervisory Authority in its public list requires conducting a +DPIA for a certain type of activity we are involved in. The list of +processing activities requiring conducting DPIA can be found on the +website of each Supervisory Authority.

        +
        • +
      +
      3. +
    3. +

      The assessment shall contain at least the following details:

      +
        +
      • +

        a systematic description of the processing operations and the purposes +of the processing, including, where applicable, the legitimate +interest pursued by us. The description must include the envisaged +data categories and data subjects concerned, the scale of processing +activities, such as its frequency, volume, envisaged number of +records, etc.; recipients of the data, retention periods and, where +applicable, international transfers;

        +
        • +
      • +

        an assessment of the necessity and proportionality of the processing +operations in relation to the purposes. The DPIA must explain whether +the activity is necessary for the purpose and whether the purpose can +be achieved by less intrusive methods;

        +
        • +
      • +

        an assessment of the risks to the rights and freedoms of data +subjects, including the rights of Data Subjects regarding their +Personal Data.

        +
        • +
      • +

        The examples of risks are the processing which could lead to physical, +material or non-material damage, in particular: where the processing +may give rise to discrimination, identity theft or fraud, financial +loss, damage to the reputation, loss of confidentiality of personal +data protected by professional secrecy, unauthorized reversal of +pseudonymization, or any other significant economic or social +disadvantage; where data subjects might be deprived of their rights +and freedoms or prevented from exercising control over their personal +data; where personal data are processed which reveal racial or ethnic +origin, political opinions, religion or philosophical beliefs, trade +union membership, and the processing of genetic data, data concerning +health or data concerning sex life or criminal convictions and +offences or related security measures; where personal aspects are +evaluated, in particular analyzing or predicting aspects concerning +performance at work, economic situation, health, personal preferences +or interests, reliability or behavior, location or movements, in order +to create or use personal profiles; where personal data of vulnerable +natural persons, in particular of children, are processed; or where +processing involves a large amount of personal data and affects a +large number of data subjects; and

        +
        • +
      • +

        the measures to address the risks, including safeguards, security +measures, and mechanisms to ensure the protection of personal data and +to demonstrate compliance with this Regulation.

        +
        • +
      +
      4. +
    4. +

      Where the DPIA did not provide how to effectively address the risks, the +Privacy Manager must initiate the consultation with the competent +Supervisory Authority to receive help with searching for the solution. +In this case, PlayForm must not conduct the activity before the +Supervisory Authority approves the processing activity in question.

      +
      5. +
    +
    3. +
+

Data Retention

+
    +
  1. +

    General Rule.

    +
      +
    1. +

      The Privacy Manager must make sure that PlayForm clearly defined the +data storage periods and/or criteria for determining the storage periods +for each processing activity it has. The periods for each processing +activity must be specified in the Records of processing activities.

      +
      2. +
    2. +

      Each department within PlayForm must comply with the data storage +periods in accordance with the retention schedule provided in Records of +processing activities. The Privacy Manager must supervise each +department and make sure they comply with this requirement.

      +
      3. +
    3. +

      After the storage period ends, the personal data must be removed from +the disposal of the department responsible for the processing or, in +cases where the data is not needed for any other purposes, destroyed +completely, including from back-up copies and other media.

      +
      4. +
    4. +

      Whenever the storage period for a processing activity has ended, but the +personal data processed is necessary for other processing purposes, the +department manager must make sure that the personal data is not used for +the ceased processing activity, and the responsible employees do not +have the access to it unless required for any other activity.

      +
      5. +
    +
    2. +
  2. +

    Exemptions. The rules specified in +Subsection 8.1 have the following exceptions:

    +
      +
    1. +

      Business needs. Data retention periods can be prolonged, but no +longer than 60 days, in the case that the data deletion will interrupt +or harm our ongoing business. The Privacy Manager must approve any +unforeseen prolongation;

      +
      2. +
    2. +

      Technical impossibility. Some information is technically impossible +or disproportionally difficult to delete. For example, deletion of the +information may lead to breach of system integrity, or it is impossible +to delete the information from the backup copies. In such a case, the +information can be further stored, subject to the approval by the +Privacy Manager and making respective amendments to the Records of +processing activities; and

      +
      3. +
    3. +

      Anonymization. The Personal Data can be further processed for any +purposes (e.g., marketing) if we fully anonymize these data after the +retention period is expired. This means that all personal identifiers +and connections to them will be deleted from the data. To consider +Personal Data anonymous, it must be impossible to reidentify the Data +Subject from the data set.

      +
      4. +
    +
    3. +
+

Security

+
    +
  1. +

    Each department within PlayForm shall take all appropriate technical and +organizational measures that protect against unauthorized, unlawful, and/or +accidental access, destruction, modification, blocking, copying, +distribution, as well as from other illegal actions of unauthorized persons +regarding the personal data under their responsibility.

    +
    2. +
  2. +

    The employee responsible for the supervision after the security of personal +data within PlayForm shall be DSR Officer. This person implements the +guidelines and other specifications on data protection and information +security in his area of responsibility. He/she advises PlayForm management +on the planning and implementation of information security in PlayForm, and +must be involved in all projects at an early stage in order to take +security-related aspects into account as early as the planning phase.

    +
    3. +
+

Data Breach Response Procedure

+
    +
  1. +

    Response Team.

    +
      +
    1. +

      In case of revealing the Data Breach, CEO of PlayForm shall urgently +form the Data Breach Response Team (the “Response Team”), which will +handle the Data Breach, notify the appropriate persons, and mitigate its +risks.

      +
      2. +
    2. +

      The Response Team must be а multi-disciplinary group headed by CEO of +PlayForm and comprised of the Privacy Manager, privacy laws specialist +(whether internal or external), and knowledgeable and skilled +information security specialists within PlayForm or outsourcing +professionals, if necessary. The team must ensure that all employees and +engaged contractors/processors adhere to this Policy and provide an +immediate, effective, and skillful response to any suspected/alleged or +actual Data Breach affecting PlayForm.

      +
      3. +
    3. +

      The potential members of the Response Team must be prepared to respond +to а Data Breach. The Response Team shall perform all the +responsibilities of PlayForm mentioned in this Policy. The duties of the +Response Team are:

      +
        +
      • +

        to communicate the Data Breach to the competent Supervisory +Authority(-ies);

        +
        • +
      • +

        in case of high risk to the rights and freedoms of Data Subjects, to +communicate the Data Breach to the Data Subject;

        +
        • +
      • +

        if PlayForm obtain data from any third party as a processor, and a +Data Breach involves obtained data, to inform the third parties about +the Data Breach;

        +
        • +
      • +

        to communicate PlayForm’s contractors or any other third parties that +process the Personal Data involved in the Data Breach; and

        +
        • +
      • +

        to take all appropriate technical and organizational measures to cease +the Data Breach and mitigate its consequences;

        +
        • +
      • +

        to record the fact of the Data Breach in the Records of processing +activities and file an internal data breach report that describes the +event.

        +
        • +
      +
      4. +
    4. +

      The Response Team shall perform its duties until all the necessary +measures required by this Policy are taken.

      +
      5. +
    +
    2. +
  2. +

    Notification to Supervisory Authority.

    +
      +
    1. +

      PlayForm shall inform the Competent Supervisory Authority about the Data +Breach without undue delay and, where it is possible, not later than 72 +hours after having become aware of the Data Breach.

      +
      2. +
    2. +

      The Competent Supervisory Authority shall be determined by the residence +of the Data Subjects, whose information was involved in the Data Breach. +If the Data Breach concerns the Personal Data of Data Subjects from more +than one country, PlayForm shall inform all Competent Supervisory +Authorities.

      +
      3. +
    3. +

      To address the notification to the authority, the Response Team should +use Annex 1 to this Policy. Annex 1 contains all the necessary contact +information of the EU supervisory authorities. If the Data Breach +concerns Data Subjects from other than the EU countries, the Response +Team shall ask a competent privacy specialist for advice.

      +
      4. +
    4. +

      The notification to the Competent Supervisory Authority shall contain, +at least, following information:

      +
        +
      • +

        the nature of the Data Breach including where possible, the +categories and an approximate number of Data Subjects and Personal +Data records concerned;

        +
        • +
      • +

        the name and contact details of the Response Team, Privacy Manager +or, if not applicable, of the CEO;

        +
        • +
      • +

        the likely consequences of the Data Breach. Explain PlayForm’s point +of view on the purposes and possible further risks of the Data Breach. +E.g., the Personal Data may be stolen for the further sale, fraud +activities or blackmailing the concerned Data Subjects; and

        +
        • +
      • +

        the measures taken or proposed to be taken by PlayForm to address +the Data Breach, including, where appropriate, measures to mitigate +its possible adverse effects.

        +
        • +
      +
      5. +
    5. +

      To file a notification, the Response Team should use PlayForm’s Data +Breach Notification Form to the Supervisory Authority.

      +
      6. +
    +
    3. +
  3. +

    Notifications to Data Subjects.

    +
      +
    1. +

      When the Data Breach is likely to result in a high risk to the rights +and freedoms of Data Subjects (e.g., stealing of funds, assets, +proprietary information), we must also communicate the Data Breach to +the concerned Data Subjects without undue delay. The Privacy Manager +must determine if there is a high risk based on the risk factors +specified in Subsection 7.2.3 of this Policy.

      +
      2. +
    2. +

      The notification shall contain the following information:

      +
        +
      • +

        description of the Data Breach - what happened and what led to the +Data Breach, such as a security breach, employee’s negligence, error +in the system work. If the Response Team decided not to disclose the +causes of the Data Breach, then this clause must not be mentioned;

        +
        • +
      • +

        the measures taken by PlayForm regarding the Data Breach, including +security measures, internal investigations, and supervisory +authority notice;

        +
        • +
      • +

        recommendations for the concerned Data Subjects how to mitigate risks +and possible consequences, such as guidelines on how to restore +access to an account, preventing measures (change of a password); +and

        +
        • +
      • +

        the contact information of the Response Team or one of its members.

        +
        • +
      +
      3. +
    3. +

      The notification to the Data Subjects should be carried out by the +email letter or, where it is impossible to use the email, by other +available means of communication.

      +
      4. +
    4. +

      Exemptions. We do not have to send the notification to the Data +Subjects if any of the following conditions are met:

      +
        +
      • +

        PlayForm has implemented appropriate technical and organizational +protection measures, and those measures were applied to the Personal +Data affected by the Data Breach, in particular, those that leave the +Personal Data inaccessible to any person who is not authorized to +access it, such as encryption;

        +
        • +
      • +

        PlayForm has taken subsequent measures which ensure that the high risk +to the rights and freedoms of Data Subjects referred to in this +section is no longer likely to materialize; or

        +
        • +
      • +

        it would involve a disproportionate effort to communicate with every +concerned Data Subject. In such a case, there shall instead be a +public communication or similar measure whereby the Data Subjects are +informed in an equally effective manner.

        +
        • +
      +
      5. +
    +
    4. +
+

In the case we apply one of the exemptions, we must document the +circumstances, reason for not informing, and actions taken to meet one of the +exemptions.

+
    +
  1. +

    Communication with Third Parties.

    +
      +
    1. +

      In the case a Data Breach concerns the Personal Data shared with us or +processed by us on behalf of a Third Party, we must also notify the +Third Party about it within 24 hours. If we process the Personal Data as +a Data Processor, the notification of the Third Party does not exempt us +from the duty to mitigate the Data Breach consequences, but we must not +inform the Competent Supervisory Authority and Data Subjects.

      +
      2. +
    2. +

      In case of receiving the notification about the Data Breach from the +Data Processor or other Third Parties that have access to the Personal +Data, CEO of PlayForm shall, in accordance with this Section:

      +
        +
      • +

        form the Response Team;

        +
        • +
      • +

        request the Third Party to send the information mentioned in +Subsections 10.2-3 of this Policy;

        +
        • +
      • +

        where necessary, inform the Competent Supervisory Authority(-ies) and +Data Subjects; and

        +
        • +
      • +

        perform other steps of the Data Breach response procedure.

        +
        • +
      +
      3. +
    +
    2. +
+

List of Persons Briefed on Personal Data Protection Policy

+ +++++ + + + + + + + + + + + + +

Full Name

Status

Date

Nikola Hristov Briefed05.25.2018
+

ANNEX 1 TO THE PERSONAL DATA PROTECTION POLICY

+

European National Data Protection Authorities

+

Austria

+

Österreichische Datenschutzbehörde
+Hohenstaufengasse 3
+1010 Wien
+Tel. +43 1 531 15 202525
+Fax +43 1 531 15 202690
+E-mail: dsb@dsb.gv.at
+WebSite: HTTPS://www.dsb.gv.at

+

Art 29 WP Member: Dr Andrea JELINEK, Director, Österreichische +Datenschutzbehörde

+

Belgium

+

Commission de la protection de la vie privée
+Commissie voor de bescherming van de persoonlijke levenssfeer
+Rue de la Presse 35 / Drukpersstraat 35 1000 Bruxelles / 1000 Brussel
+Tel. +32 2 274 48 00
+Fax +32 2 274 48 35
+E-mail: commission@privacycommission.be
+WebSite: HTTPS://www.privacycommission.be

+

Art 29 WP Vice-President: Willem DEBEUCKELAERE, President of the Belgian Privacy +commission

+

Bulgaria

+

Commission for Personal Data Protection
+2, Prof. Tsvetan Lazarov Blvd. Sofia 1592
+Tel. +359 2 915 3580
+Fax +359 2 915 3525
+E-mail: kzld@cpdp.bg
+WebSite: HTTPS://www.cpdp.bg

+

Art 29 WP Member: Mr. Ventsislav KARADJOV, Chairman of the Commission for +Personal Data Protection
+Art 29 WP Alternate Member: Ms. Mariya MATEVA

+

Croatia

+

Croatian Personal Data Protection Agency
+Martićeva 14
+10000 Zagreb
+Tel. +385 1 4609 000
+Fax +385 1 4609 099
+E-mail: azop@azop.hr or info@azop.hr
+WebSite: HTTPS://www.azop.hr

+

Art 29 WP Member: Mr. Anto RAJKOVAČA, Director of the Croatian Data Protection +Agency

+

Cyprus

+

Commissioner for Personal Data Protection
+1 Iasonos Street,
+1082 Nicosia
+P.O. Box 23378, CY-1682 Nicosia Tel. +357 22 818 456
+Fax +357 22 304 565
+E-mail: commissioner@dataprotection.gov.cy
+WebSite: HTTPS://www.dataprotection.gov.cy

+

Art 29 WP Member: Ms. Irene LOIZIDOU NIKOLAIDOU
+Art 29 WP Alternate Member: Mr. Constantinos GEORGIADES

+

Czech Republic

+

The Office for Personal Data Protection
+Urad pro ochranu osobnich udaju Pplk. Sochora 27
+170 00 Prague 7
+Tel. +420 234 665 111
+Fax +420 234 665 444
+E-mail: posta@uoou.cz
+WebSite: HTTPS://www.uoou.cz

+

Art 29 WP Member: Ms. Ivana JANŮ, President of the Office for Personal Data +Protection
+Art 29 WP Alternate Member: Mr. Ivan PROCHÁZKA, Adviser to the President of the +Office

+

Denmark

+

Datatilsynet
+Borgergade 28, 5
+1300 Copenhagen K
+Tel. +45 33 1932 00
+Fax +45 33 19 32 18
+E-mail: dt@datatilsynet.dk
+WebSite: HTTPS://www.datatilsynet.dk

+

Art 29 WP Member: Ms. Cristina Angela GULISANO, Director, Danish Data Protection +Agency (Datatilsynet)
+Art 29 WP Alternate Member: Mr. Peter FOGH KNUDSEN, Head of International +Division at the Danish Data Protection Agency (Datatilsynet)

+

Estonia

+

Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)
+Väike-Ameerika 19
+10129 Tallinn
+Tel. +372 6274 135
+Fax +372 6274 137
+E-mail: info@aki.ee
+WebSite: HTTPS://www.aki.ee/en

+

Art 29 WP Member: Mr. Viljar PEEP, Director General, Estonian Data Protection +Inspectorate
+Art 29 WP Alternate Member: Ms. Maarja Kirss

+

Finland

+

Office of the Data Protection Ombudsman
+P.O. Box 315
+FIN-00181 Helsinki Tel. +358 10 3666 700
+Fax +358 10 3666 735
+E-mail: tietosuoja@om.fi
+WebSite: HTTPS://www.tietosuoja.fi/en

+

Art 29 WP Member: Mr. Reijo AARNIO, Ombudsman of the Finnish Data Protection +Authority
+Art 29 WP Alternate Member: Ms. Elisa KUMPULA, Head of Department

+

France

+

Commission Nationale de l’Informatique et des Libertés - CNIL
+8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02
+Tel. +33 1 53 73 22 22
+Fax +33 1 53 73 22 00
+WebSite: HTTPS://www.cnil.fr

+

Art 29 WP Member: Ms. Isabelle FALQUE-PIERROTIN, President of CNIL
+Art 29 WP Alternate Member: Ms. Florence RAYNAL

+

Germany

+

Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit
+Husarenstraße 30
+53117 Bonn
+Tel. +49 228 997799 0; +49 228 81995 0
+Fax +49 228 997799 550; +49 228 81995 550
+E-mail: poststelle@bfdi.bund.de
+WebSite: HTTPS://www.bfdi.bund.de

+

The competence for complaints is split among different data protection +supervisory authorities in Germany.

+

Competent authorities can be identified according to the list provided under

+

HTTPS://www.bfdi.bund.de/EN/Service/Anschriften/Laender/Laender-node.html

+

Art 29 WP Member: Ms. Andrea VOSSHOFF, Federal Commissioner for Freedom of +Information
+Art 29 WP Alternate Member: Prof. Dr. Johannes CASPAR, representative of the +federal states

+

Greece

+

Hellenic Data Protection Authority
+Kifisias Av. 1-3, PC 11523 Ampelokipi Athens
+Tel. +30 210 6475 600
+Fax +30 210 6475 628
+E-mail: contact@dpa.gr
+WebSite: HTTPS://www.dpa.gr

+

Art 29 WP Member: Mr. Konstantinos Menoudakos, President of the Hellenic DPA
+Art 29 WP Alternate Member: Dr. Vasilios ZORKADIS, Director

+

Hungary

+

National Authority for Data Protection and Freedom of Information
+Szilágyi Erzsébet fasor 22/C H-1125 Budapest
+Tel. +36 1 3911 400
+E-mail: peterfalvi.attila@naih.hu
+WebSite: HTTPS://www.naih.hu

+

Art 29 WP Member: Dr Attila PÉTERFALVI, President of the National Authority for +Data Protection and Freedom of Information
+Art 29 WP Alternate Member: Mr. Endre Győző SZABÓ Vice-president of the National +Authority for Data Protection and Freedom of Information

+

Ireland

+

Data Protection Commissioner
+Canal House Station Road Portarlington Co. Laois
+Lo-Call: 1890 25 22 31
+Tel. +353 57 868 4800
+Fax +353 57 868 4757
+E-mail: info@dataprotection.ie
+WebSite: HTTPS://www.dataprotection.ie

+

Art 29 WP Member: Ms. Helen DIXON, Data Protection Commissioner
+Art 29 WP Alternate Members: Mr. John O’DWYER, Deputy Commissioner; Mr. Dale +SUNDERLAND, Deputy Commissioner

+

Italy

+

Garante per la protezione dei dati personali
+Piazza di Monte Citorio, 121 00186 Roma
+Tel. +39 06 69677 1
+Fax +39 06 69677 785
+E-mail: garante@garanteprivacy.it
+WebSite: HTTPS://www.garanteprivacy.it

+

Art 29 WP Member: Mr. Antonello SORO, President of Garante per la protezione dei +dati personali
+Art 29 WP Alternate Member: Ms. Giuseppe BUSIA, Secretary General of Garante per +la protezione dei dati personali

+

Latvia

+

Data State Inspectorate Director: Ms. Daiga Avdejanova
+Blaumana str. 11/13-15
+1011 Riga
+Tel. +371 6722 3131
+Fax +371 6722 3556
+E-mail: info@dvi.gov.lv
+WebSite: HTTPS://www.dvi.gov.lv

+

Art 29 WP Alternate Member: Ms. Aiga BALODE

+

Lithuania

+

State Data Protection
+Žygimantų str. 11-6a 011042 Vilnius
+Tel. + 370 5 279 14 45
+Fax +370 5 261 94 94
+E-mail: ada@ada.lt
+WebSite: HTTPS://www.ada.lt

+

Art 29 WP Member: Mr. Raimondas Andrijauskas, Director of the State Data +Protection Inspectorate
+Art 29 WP Alternate Member: Ms. Neringa KAKTAVIČIŪTĖ-MICKIENĖ, Head of +Complaints Investigation and International Cooperation Division

+

Luxembourg

+

Commission Nationale pour la Protection des Données
+1, avenue du Rock’n’roll L-4361 Esch-sur-Alzette Tel. +352 2610 60 1
+Fax +352 2610 60 29
+E-mail: info@cnpd.lu
+WebSite: HTTPS://www.cnpd.lu

+

Art 29 WP Member: Ms. Tine A. LARSEN, President of the Commission Nationale pour +la Protection des Données
+Art 29 WP Alternate Member: Mr. Thierry LALLEMANG, Commissioner

+

Malta

+

Office of the Data Protection Commissioner
+Data Protection Commissioner: Mr. Joseph Ebejer
+2, Airways House
+High Street, Sliema SLM 1549 Tel. +356 2328 7100
+Fax +356 2328 7198
+E-mail: commissioner.dataprotection@gov.mt
+WebSite: HTTPS://idpc.org.mt

+

Art 29 WP Member: Mr. Saviour CACHIA, Information and Data Protection +Commissioner
+Art 29 WP Alternate Member: Mr. Ian DEGUARA, Director - Operations and Programme +Implementation

+

Netherlands

+

Autoriteit Persoonsgegevens
+Prins Clauslaan 60
+P.O. Box 93374
+2509 AJ Den Haag/The Hague Tel. +31 70 888 8500
+Fax +31 70 888 8501
+E-mail: info@autoriteitpersoonsgegevens.nl
+WebSite: HTTPS://autoriteitpersoonsgegevens.nl/nl

+

Art 29 WP Member: Mr. Aleid WOLFSEN, Chairman of Autoriteit Persoonsgegevens

+

Poland

+

The Bureau of the Inspector General for the Protection of Personal Data – GIODO
+ul. Stawki 2
+00-193 Warsaw
+Tel. +48 22 53 10 440
+Fax +48 22 53 10 441
+E-mail: kancelaria@giodo.gov.pl; desiwm@giodo.gov.pl
+WebSite: HTTPS://www.giodo.gov.pl

+

Art 29 WP Member: Ms. Edyta BIELAK-JOMAA, Inspector General for the Protection +of Personal Data

+

Portugal

+

Comissão Nacional de Protecção de Dados - CNPD
+R. de São. Bento, 148-3° 1200-821 Lisboa
+Tel. +351 21 392 84 00
+Fax +351 21 397 68 32
+E-mail: geral@cnpd.pt
+WebSite: HTTPS://www.cnpd.pt

+

Art 29 WP Member: Ms. Filipa CALVÃO, President, Comissão Nacional de Protecção +de Dados
+Art 29 WP Alternate Member: Isabel CRUZ, Secretary-General of the DPA

+

Romania

+

The National Supervisory Authority for Personal Data Processing President: Mrs. +Ancuţa Gianina Opre
+B-dul Magheru 28-30
+Sector 1, BUCUREŞTI
+Tel. +40 21 252 5599
+Fax +40 21 252 5757
+E-mail: anspdcp@dataprotection.ro
+WebSite: HTTPS://www.dataprotection.ro

+

Art 29 WP Member: Ms. Ancuţa Gianina OPRE, President of the National Supervisory +Authority for Personal Data Processing
+Art 29 WP Alternate Member: Ms. Alina SAVOIU, Head of the Legal and +Communication Department

+

Slovakia

+

Office for Personal Data Protection of the Slovak Republic
+Hraničná 12
+820 07 Bratislava 27
+Tel.: + 421 2 32 31 32 14
+Fax: + 421 2 32 31 32 34
+E-mail: statny.dozor@pdp.gov.sk
+WebSite: HTTPS://dataprotection.gov.sk

+

Art 29 WP Member: Ms. Soňa PŐTHEOVÁ, President of the Office for Personal Data +Protection of the Slovak Republic
+Art 29 WP Alternate Member: Mr. Anna VITTEKOVA, Vice President

+

Slovenia

+

Information Commissioner
+Ms. Mojca Prelesnik Zaloška 59
+1000 Ljubljana
+Tel. +386 1 230 9730
+Fax +386 1 230 9778
+E-mail: gp.ip@ip-rs.si
+WebSite: HTTPS://www.ip-rs.si

+

Art 29 WP Member: Ms. Mojca PRELESNIK, Information Commissioner of the Republic +of Slovenia

+

Spain

+

Agencia de Protección de Datos
+C/Jorge Juan, 6
+28001 Madrid
+Tel. +34 91399 6200
+Fax +34 91455 5699
+E-mail: internacional@agpd.es
+WebSite: HTTPS://www.agpd.es

+

Art 29 WP Member: Ms. María del Mar España Martí, Director of the Spanish Data +Protection Agency
+Art 29 WP Alternate Member: Mr. Rafael GARCIA GOZALO

+

Sweden

+

Datainspektionen
+Drottninggatan 29 5th Floor
+Box 8114
+20 Stockholm
+Tel. +46 8 657 6100
+Fax +46 8 652 8652
+E-mail: datainspektionen@datainspektionen.se
+WebSite: HTTPS://www.datainspektionen.se

+

Art 29 WP Member: Ms. Kristina SVAHN STARRSJÖ, Director General of the Data +Inspection Board
+Art 29 WP Alternate Member: Mr. Hans-Olof LINDBLOM, Chief Legal Adviser

+

United Kingdom

+

The Information Commissioner’s Office
+Water Lane, Wycliffe House Wilmslow - Cheshire SK9 5AF Tel. +44 1625 545 745
+E-mail: international.team@ico.org.uk
+WebSite: HTTPS://ico.org.uk

+

Art 29 WP Member: Ms. Elizabeth DENHAM, Information Commissioner
+Art 29 WP Alternate Member: Mr. Steve WOOD, Deputy Commissioner

+

EUROPEAN FREE TRADE AREA (EFTA)

+

Iceland

+

Icelandic Data Protection Agency
+Rauðarárstíg 10
+Reykjavík
+Tel. +354 510 9600; Fax +354 510 9606
+E-mail: postur@personuvernd.is
+WebSite: HTTPS://www.personuvernd.is

+

Liechtenstein

+

Data Protection Office
+Kirchstrasse 8, P.O. Box 684
+9490 Vaduz
+Principality of Liechtenstein Tel. +423 236 6090
+E-mail: info.dss@llv.li
+WebSite: HTTPS://www.datenschutzstelle.li

+

Norway

+

Datatilsynet
+Data Protection Authority: Mr. Bjørn Erik THORN
+The Data Inspectorate
+P.O. Box 8177 Dep 0034 Oslo
+Tel. +47 22 39 69 00; Fax +47 22 42 23 50
+E-mail: postkasse@datatilsynet.no
+WebSite: HTTPS://www.datatilsynet.no

+

Switzerland

+

Data Protection and Information Commissioner of Switzerland
+Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter Mr. Adrian +Lobsiger
+Feldeggweg 1
+3003 Bern
+Tel. +41 58 462 43 95; Fax +41 58 462 99 96
+E-mail: contact20@edoeb.admin.ch
+WebSite: HTTPS://www.edoeb.admin.ch

+

Footnotes

+
    +
  1. +

    HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en; ↩

    +
    2. +
  2. +

    HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en; ↩

    +
    3. +
+
\ No newline at end of file diff --git a/Target/Glyph/Image/GitHub/Tauri.svg b/Target/Glyph/Image/GitHub/Tauri.svg index a0837922..037e6117 100644 --- a/Target/Glyph/Image/GitHub/Tauri.svg +++ b/Target/Glyph/Image/GitHub/Tauri.svg @@ -1 +1,12 @@ - \ No newline at end of file + + + + + + diff --git a/Target/Image/Dark/PlayForm.svg b/Target/Image/Dark/PlayForm.svg index 33dbe34d..038a459e 100644 --- a/Target/Image/Dark/PlayForm.svg +++ b/Target/Image/Dark/PlayForm.svg @@ -1 +1,5 @@ - \ No newline at end of file + + + diff --git a/Target/Image/GitHub/Astro.svg b/Target/Image/GitHub/Astro.svg index 60aa5274..29eca182 100644 --- a/Target/Image/GitHub/Astro.svg +++ b/Target/Image/GitHub/Astro.svg @@ -1 +1,24 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + diff --git a/Target/Image/GitHub/Biome.svg b/Target/Image/GitHub/Biome.svg index f8b92d23..ce5e7804 100644 --- a/Target/Image/GitHub/Biome.svg +++ b/Target/Image/GitHub/Biome.svg @@ -1 +1,5 @@ - \ No newline at end of file + + + diff --git a/Target/Image/GitHub/CC0.svg b/Target/Image/GitHub/CC0.svg index 2be0cc36..fba8472b 100644 --- a/Target/Image/GitHub/CC0.svg +++ b/Target/Image/GitHub/CC0.svg @@ -1 +1,100 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Image/GitHub/Cargo.png b/Target/Image/GitHub/Cargo.png index bc13318d..e3a99208 100644 Binary files a/Target/Image/GitHub/Cargo.png and b/Target/Image/GitHub/Cargo.png differ diff --git a/Target/Image/GitHub/CodeEditorLand/Land/Land.png b/Target/Image/GitHub/CodeEditorLand/Land/Land.png index f7ab4da1..62aa8fa6 100644 Binary files a/Target/Image/GitHub/CodeEditorLand/Land/Land.png and b/Target/Image/GitHub/CodeEditorLand/Land/Land.png differ diff --git a/Target/Image/GitHub/CodeEditorLand/Land/Land.svg b/Target/Image/GitHub/CodeEditorLand/Land/Land.svg index 68a04ed3..9d4ae223 100644 --- a/Target/Image/GitHub/CodeEditorLand/Land/Land.svg +++ b/Target/Image/GitHub/CodeEditorLand/Land/Land.svg @@ -1,3 +1,310 @@ -📣 EchoWebSocket libraryin RustAllows for concurrent communicationbetween the - twotokio::tungstenite🌬️ WindTypeScriptApplicationBinds everythingsolid-js🌌 SkyAstroApplicationRenders the viewastro⛰️ MountainTauriApplicationBundles all of it togethertauri☀️ SunAsync RustLibrarytokio::fsWrites files onto the file system🌊 RiverAsync RustLibrarydashmapLoads files into memoryImplements The - Worker Stealer PatternAsyncConcurrentParallel \ No newline at end of file + + + + + + + + + 📣 Echo + WebSocket libraryin Rust + + + + Allows for concurrent communicationbetween the + two + tokio::tungstenite + + 🌬️ Wind + + TypeScriptApplication + + + + Binds everything + solid-js + + 🌌 Sky + + AstroApplication + + + + Renders the view + astro + + + + ⛰️ Mountain + TauriApplication + + Bundles all of it together + + tauri + ☀️ Sun + Async RustLibrary + + + + tokio::fs + Writes files onto the file system + 🌊 River + Async RustLibrary + + + + dashmap + Loads files into memory + + + + + + + + + + + + + + + + + + + + + + + + + + + + Implements The + Worker Stealer Pattern + + + + + + + + + + + + + + + + + + + + + + + + + Async + + Concurrent + Parallel + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Image/GitHub/Land.svg b/Target/Image/GitHub/Land.svg index a628224d..702b2f72 100644 --- a/Target/Image/GitHub/Land.svg +++ b/Target/Image/GitHub/Land.svg @@ -1 +1,7 @@ - \ No newline at end of file + + + + + diff --git a/Target/Image/GitHub/NPM.svg b/Target/Image/GitHub/NPM.svg index cca3a0a4..00220bc5 100644 --- a/Target/Image/GitHub/NPM.svg +++ b/Target/Image/GitHub/NPM.svg @@ -1 +1,7 @@ - \ No newline at end of file + + + + + + diff --git a/Target/Image/GitHub/OXC.png b/Target/Image/GitHub/OXC.png index fa115051..69bf5073 100644 Binary files a/Target/Image/GitHub/OXC.png and b/Target/Image/GitHub/OXC.png differ diff --git a/Target/Image/GitHub/OXC.svg b/Target/Image/GitHub/OXC.svg index 5c173671..9e9c78c1 100644 --- a/Target/Image/GitHub/OXC.svg +++ b/Target/Image/GitHub/OXC.svg @@ -1 +1,52 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Image/GitHub/Round/Cover.png b/Target/Image/GitHub/Round/Cover.png index 956ec55e..abe9b2b9 100644 Binary files a/Target/Image/GitHub/Round/Cover.png and b/Target/Image/GitHub/Round/Cover.png differ diff --git a/Target/Image/GitHub/Tauri.svg b/Target/Image/GitHub/Tauri.svg index 2fcaff43..afe98a04 100644 --- a/Target/Image/GitHub/Tauri.svg +++ b/Target/Image/GitHub/Tauri.svg @@ -1 +1,27 @@ - \ No newline at end of file + + + + + + + + + + + diff --git a/Target/Image/GitHub/n.svg b/Target/Image/GitHub/n.svg index 3d9ce0ef..1bb38b1a 100644 --- a/Target/Image/GitHub/n.svg +++ b/Target/Image/GitHub/n.svg @@ -1 +1,16 @@ - \ No newline at end of file + + + + + n + + + diff --git a/Target/Image/GitHub/postcss.svg b/Target/Image/GitHub/postcss.svg index c4d84064..45eba7ff 100644 --- a/Target/Image/GitHub/postcss.svg +++ b/Target/Image/GitHub/postcss.svg @@ -1 +1,16 @@ - \ No newline at end of file + + + + + + + + diff --git a/Target/Image/GitHub/tailwindcss.svg b/Target/Image/GitHub/tailwindcss.svg index 31849987..ec35a24b 100644 --- a/Target/Image/GitHub/tailwindcss.svg +++ b/Target/Image/GitHub/tailwindcss.svg @@ -1 +1,13 @@ - \ No newline at end of file + + + + + + + + + + + diff --git a/Target/Image/Page/Index/Discord.svg b/Target/Image/Page/Index/Discord.svg index 336c8efb..e81ac743 100644 --- a/Target/Image/Page/Index/Discord.svg +++ b/Target/Image/Page/Index/Discord.svg @@ -1 +1,31 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + + + + + diff --git a/Target/Image/Page/Index/Meta.svg b/Target/Image/Page/Index/Meta.svg index 807e2e30..238fa866 100644 --- a/Target/Image/Page/Index/Meta.svg +++ b/Target/Image/Page/Index/Meta.svg @@ -1 +1,30 @@ - \ No newline at end of file + + + + + + + + + + + + + + + + diff --git a/Target/Image/Page/Index/Rakuten.svg b/Target/Image/Page/Index/Rakuten.svg index 5858f203..0ccccf43 100644 --- a/Target/Image/Page/Index/Rakuten.svg +++ b/Target/Image/Page/Index/Rakuten.svg @@ -1 +1,25 @@ - \ No newline at end of file + + + diff --git a/Target/Image/PlayForm.svg b/Target/Image/PlayForm.svg index 3a2618bc..052b496e 100644 --- a/Target/Image/PlayForm.svg +++ b/Target/Image/PlayForm.svg @@ -1 +1,5 @@ - \ No newline at end of file + + + diff --git a/Target/Image/vendor/github-mark-white.png b/Target/Image/vendor/github-mark-white.png index 50f52e0e..50b81752 100644 Binary files a/Target/Image/vendor/github-mark-white.png and b/Target/Image/vendor/github-mark-white.png differ diff --git a/Target/Image/vendor/github-mark-white.svg b/Target/Image/vendor/github-mark-white.svg index dd166bdd..57c1b73d 100644 --- a/Target/Image/vendor/github-mark-white.svg +++ b/Target/Image/vendor/github-mark-white.svg @@ -1 +1,5 @@ - \ No newline at end of file + + + diff --git a/Target/Image/vendor/github-mark.png b/Target/Image/vendor/github-mark.png index 81abec05..6cb3b705 100644 Binary files a/Target/Image/vendor/github-mark.png and b/Target/Image/vendor/github-mark.png differ diff --git a/Target/Image/vendor/github-mark.svg b/Target/Image/vendor/github-mark.svg index cc622a48..caf5103a 100644 --- a/Target/Image/vendor/github-mark.svg +++ b/Target/Image/vendor/github-mark.svg @@ -1 +1,5 @@ - \ No newline at end of file + + + diff --git a/Target/PERSONAL-DATA-PROTECTION-POLICY/index.html b/Target/PERSONAL-DATA-PROTECTION-POLICY/index.html index 13dc86a3..5ff594a3 100644 --- a/Target/PERSONAL-DATA-PROTECTION-POLICY/index.html +++ b/Target/PERSONAL-DATA-PROTECTION-POLICY/index.html @@ -1 +1,1673 @@ -Personal Data Protection Policy

PERSONAL DATA PROTECTION POLICY

Effective date: 05.25.2018 / May 25th 2018
Last updated: 02.11.2022 / February 11th 2022

We at PlayForm ltd. are committed to processing personal data securely and respecting privacy of the concerned individuals.

Version No. and date of the last update:

v. 1.0.

February 11th 2022

This policy shall be reviewed annually or each time when the changes in our data processing occur.

Scope and Definitions

  1. Scope. This Personal Data Protection Policy (the “Policy”) describes PlayForm ltd. internal rules for personal data processing and protection. The Policy applies to PlayForm ltd., including PlayForm ltd. employees and contractors (“we”, “us”, “our”, “PlayForm”). The management of each entity is ultimately responsible for the implementation of this policy, as well as to ensure, at entity level, there are adequate and effective procedures in place for its implementation and ongoing monitoring of its adherence. For the purposes of this Policy, employees and contractors are jointly referred to as the “employees”.

  2. Privacy Manager. Privacy Manager is an employee of PlayForm responsible for personal data protection compliance within PlayForm (the “Privacy Manager”). The Privacy Manager is in charge of performing the obligations imposed by this Policy and supervising other employees, who subject to this Policy, regarding their adherence to this Policy. The Privacy Manager must be involved in all projects at an early stage in order to take personal data protection aspects into account as early as the planning phase.
    The designated Privacy Manager at PlayForm ltd. is Nikola Hristov Nikola@PlayForm.LTD.

  3. Definitions.

Competent Supervisory Authoritymeans a public authority that is responsible for regulating and supervising personal data protection with regards to activities of PlayForm.
Data Breach

means a breach of the security and/or confidentiality leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data transmitted, stored or otherwise processed.

This includes but is not limited to e-mails sent to an incorrect or disclosed list of recipients, an unlawful publication of the Personal Data, loss or theft of physical records, and unauthorized access to personal information.

Data Controllermeans the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines (make a decision) the purposes and means of the processing of Personal Data.
Data Processormeans a natural or legal person, public authority, agency or other body which processes the Personal Data on behalf of the data controller.
Data Protection Lawsmean any laws and legal rules on personal data use and protection applicable to the activities of PlayForm, including, but not limited to the Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation, GDPR).
Data Subject Request (DSR)means any request from the Data Subject and concerning their personal data and/or data subject rights.
Data Subjectmeans a natural person, whose Personal Data we process. Data Subjects include but are not limited to users, website visitors, employees, contractors, and partners of PlayForm.
Personal Datameans any information relating to an identified or identifiable Data Subject; a Data Subject can be identified by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or the combination of factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that Data Subject.
Processingmeans any operation or set of operations which is performed by PlayForm on Personal Data, such as 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.
Standard Contractual Clausesmeans the European Commission Decision of February, 5 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC of the European Parliament and of the Council (2010/87/EU).
Third Partymeans a natural or legal person, who accesses the Personal Data for further processing and is not an employee, member or corporate affiliate of PlayForm. This definition does not apply to natural persons, who provide services to PlayForm as contractors on a regular basis.
Usermeans a Data Subject who uses our services provided on PlayForm website.

Data Processing Principles

  1. PlayForm’s processing activities must be in line with the principles specified in this Section. The Privacy Manager must make sure that PlayForm’s compliance documentation, as well as data processing activities, are compliant with the data protection principles.

  2. We must process the Personal Data in accordance with the following principles:

    1. Lawfully, fairly and in a transparent manner (lawfulness, fairness and transparency). We shall always have a legal ground for the processing (described in Section 3 of this Policy), collect the amount of data adequate to the purpose and legal grounds, and we make sure the Data Subjects are aware of the processing;

    2. Collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes (purpose limitation). We must not process the Personal Data for the purposes not specified in our compliance documentation without obtaining specific approval of the Privacy Manager;

    3. Adequate, relevant and limited to what is necessary for the purposes for which they are processed (data minimization). We always make sure the data we collect is not excessive and limited by the strict necessity;

    4. Accurate and, where necessary, kept up to date (accuracy). We endeavor to delete inaccurate or false data about Data Subjects and make sure we update the data. Data Subjects can ask us for a correction of the Personal Data;

    5. Kept in a form which permits identification of Data Subjects for no longer than is necessary for the purposes for which the Personal Data are processed (storage period limitation). The storage periods must be limited as prescribed by Data Protection Laws and this Policy; and

    6. Process in a manner that ensures appropriate security of the Personal Data, including protection against unauthorized or unlawful processing and accidental loss, destruction or damage, using appropriate technical or organizational measures (confidentiality, integrity, and availability).

  3. Accountability.

    1. We shall be able to demonstrate our compliance with Data Protection Laws (accountability principle). In particular, we must ensure and document all relevant procedures, efforts, internal and external consultations on personal data protection including:

      • the fact of appointing a person responsible for PlayForm’s data protection compliance;

      • where necessary, a record of a Data Processing Impact Assessment;

      • developed and implemented notices, policies, and procedures, such as Privacy Notice, this policy or Data Breach response procedure;

      • the fact of staff training on compliance with Data Protection laws; and

      • assessment, implementation, and testing organizational and technical data protection measures.

    2. The Privacy Manager must maintain PlayForm’s Records of processing activities, which is an accountability document that describes personal data processing activities of PlayForm, prepared in accordance with Art. 30 of the GDPR (the “Records of processing activities”). The Records of processing activities must maintain, at least, the following information about each processing activity:

      • contact details of PlayForm, the EU Representative, and, where applicable, of the Data Protection Officer;

      • name of the activity, its purposes and legal basis along with, where applicable, the legitimate interests of PlayForm;

      • data subjects and personal data categories concerned;

      • data retention periods;

      • general description of applicable security measures;

      • recipients, including joint controllers, processors, and contractors involved, as well as the fact of the international data transfer with the safeguards applied to the transfer;

      • where applicable, a reference to the Data Processing Impact Assessment;

      • where applicable, a reference to the record of the data breach occurred involving the personal data;

      • if PlayForm acts as a data processor, the information to be provided includes the names and contact details of controllers, name and contact details of controller’s representative (if applicable), categories of processing (activities), names of third countries or international organizations that personal data are transferred to (if applicable), safeguards for exceptional transfers of personal data to third countries or international organizations (if applicable), and general description of technical and organizational security measures.

  1. Legal grounds.

    1. Each processing activity must have one of the lawful grounds specified in this Section to process the Personal Data. If we do not have any of the described, we cannot collect or further process the Personal Data.

    2. If PlayForm is intended to use personal data for other purposes than those specified in the Records of processing activities, the Privacy Manager must evaluate, determine, and, if necessary, collect/record the appropriate legal basis for it.

    3. Performance of the contract. Where PlayForm has a contract with the Data Subject, e.g., website’s Terms of Use or the employment contract, and the contract requires the provision of personal data from the Data Subject, the applicable legal ground will be the performance of the contract.

    4. Consent. To process the personal data based on the consent, we must obtain the consent before the Processing and keep the evidence of the consent with the records of Data Subject’s Personal Data. The Privacy Manager must make sure that the consent collected from Data Subjects meet the requirements of Data Protection Laws and this Policy. In particular, the Privacy Manager must make sure that:

      • the Data Subject must be free to give or refuse to give consent.

      • the consent is in the form of an active indication from the Data Subject, i.e., the consent checkbox must not be pre-ticked for the user.

      • the request for the consent clearly articulates the purposes of the processing, and other information specified in Subsection 6.2 is available to the Data Subject.

      • the Data Subject must be free to give one’s consent or to revoke it.

    5. Legitimate interests. We have the right to use personal data in our ‘legitimate interests’. The interests can include the purposes that are justified by the nature of our business activities, such as the marketing analysis of personal data. For PlayForm to use legitimate interests as a legal ground for the processing, the Privacy Manager must make sure that:

      • the legitimate interest in the processing is clearly defined and recorded in the Records of processing activities;

      • any envisaged risks to Data Subject rights and interests are spotted. The examples of the risks can be found in Subsection 7.2.;

      • the Data Subjects have reasonable expectations about the processing, and additional protective measures to address the risks are taken;

      • subject to the conditions of Subsection 6.7 (Right to object against the processing), the Data Subject is provided with the opportunity to opt-out from the processing for the described legitimate interests.
        If at least one of the above conditions is not met by PlayForm, the Privacy Manager must choose and propose a different legal ground for the processing, such as consent.

    6. Legal Compliance and Public Interest. Besides the grounds specified afore, we might be requested by the laws of the European Union or laws of the EU Member State to process Personal Data of our Users. For example, we can be required to collect, analyze, and monitor the information of Users to comply with financial or labor laws.
      Whenever we have such an obligation, we must make sure that:

      • we process personal data strictly in accordance with relevant legal requirements;

      • we do not use or store the collected Personal Data for other purposes than legal compliance; and

      • the Data Subjects are properly and timely informed about our obligations, scope, and conditions of personal data processing.

Important: Where PlayForm has the law requirements of another country to process personal data, the Privacy Manager must propose using another legal ground for the processing under Data Protection Laws, such as legitimate interests or consent.

Access to Personal Data

  1. Access to Personal Data.

    1. The employees must have access to the personal data on a “need-to-know” basis. The data can be accessed only if it is strictly necessary to perform one of the activities specified in the Records of processing activities. The employees and contractors shall have access to the Personal Data only if they have the necessary credentials for it.

    2. Heads of the departments within PlayForm are responsible for their employees’ access and processing of personal data. The heads must maintain the list of employees that are entitled to access and process personal data. The Privacy Manager shall have the right to review the list and, where necessary, request the amendments to meet the requirements of this Policy.

    3. Heads of the departments within PlayForm must ensure that the employees under their supervision are aware of the Data Protection Laws and comply with the rules set in this Policy. To make sure our employees are able to comply with the data protection requirements, we must provide them with adequate data protection training.

    4. All employees accessing personal data shall keep strict confidentiality regarding the data they access. The employees that access personal data must use only those means (software, premises, etc.) for the processing that were prescribed by PlayForm. The data must not be disclosed or otherwise made available out of the management instructions.

    5. The employees within their competence must assist PlayForm’s representatives, including the Privacy Manager, in any efforts regarding compliance with Data Protection Laws and/or this Policy.

    6. When an employee detects or believes there is suspicious activity, data breach, non-compliance with Data Protection Laws and/or this Policy, or a DSR was not routed to the competent department within PlayForm, the employee must report such activity to the Privacy Manager.

    7. Employees that are unsure about whether they can legitimately process or disclose Personal Data must seek advice from the Privacy Manager before taking any action.

    8. Any occasional access to personal data for activities not specified in the Records of processing activities is prohibited. If there is a strict necessity for immediate access, the Privacy Manager must approve the access first.

Third Parties

  1. Before sharing personal data with any person outside of PlayForm, the Privacy Manager must ensure that this Third Party has an adequate data protection level and provide sufficient data protection guarantees in accordance with Data Protection Laws, including, but not limited to the processorship requirements (Art. 28 of the GDPR) and international transfers compliance (Section 5 of the GDPR). Where necessary, the Privacy Manager must make sure that PlayForm enters into the appropriate data protection contract with the third party.

  2. An employee can share personal data with third parties only if and to the extent that was directly prescribed by the manager and specified in the Records of processing activities.

  3. If we are required to delete, change, or stop the processing of the Personal Data, we must ensure that the Third Parties, with whom we shared the Personal Data, will fulfill these obligations accordingly.

  4. Whenever PlayForm is engaged as a data processor on behalf of another entity, the Privacy Manager must make sure PlayForm complies with the processorship obligation. In particular, the appropriate data processing agreement in accordance with the Data Protection Laws must be in place. The Privacy Manager must supervise the compliance with data processing instructions from the controller, including regarding the scope of processing activities, involvement of sub-processors, international transfers, storage, and further disposal of processed personal data. The personal data processed under the processor role must not be processed for any other purposes than specified in the relevant instructions, agreement or other legal act regulating the relationships with the controller.

International Transfers

  1. If we have the employees, contractors, corporate affiliates, or Data Processors outside of the EEA, and we transfer Personal Data to them for the processing, the Privacy Manager must make sure PlayForm takes all necessary and appropriate safeguards in accordance with Data Protection Laws.

  2. The Privacy Manager must assess the safeguards available and propose to the PlayForm’s management the appropriate safeguard for each international transfer. The following regimes apply to the transfers of Personal Data outside of the EU:

    • where the European Commission decides that the country has an adequate level of personal data protection, the transfer does not require taking additional safeguards. The full list of adequate jurisdictions can be found on the relevant page of the European Commission’s website1.

    • to transfer Personal Data to our contractors or partners (Data Processors or Controllers) in other third countries, we must conclude Standard Contractual Clauses with that party. The draft version along with the guidance can be found on the relevant page of the European Commission’s website2;

    • if we have a corporate affiliate or an entity in other countries, we may choose to adopt Binding Corporate Rules in accordance with Article 47 of the GDPR or an approved code of conduct pursuant to Article 40 of the GDPR;

    • we also can transfer Personal Data to entities that have an approved certification in accordance with Article 42 of the GDPR, which certifies an appropriate level of company’s data protection.

  1. As a part of the information obligations, PlayForm must inform the Data Subjects that their Personal Data is being transferred to other countries, as well as provide them with the information about the safeguards used for the transfer. The information obligation is to be performed in accordance with Subsection 6.2.

  2. In the exceptional cases (the “Derogation”), where we cannot apply the safeguards mentioned afore and we need to transfer Personal Data, we must take an explicit consent (active statement) from the Data Subject or it must be strictly necessary for the performance of the contract between us and the Data Subject, or other derogation conditions apply in accordance with the Data Protection Laws. The Privacy Manager must pre-approve any Derogation transfers and document the approved Derogations, as well as the rationale for them.

Rights of Data Subjects

  1. Our Responsibilities.

    1. Privacy Manager is ultimately responsible for handing all DSR received by PlayForm. In the case of receiving any outstanding or unusual DSR, the employee must seek advice from the Privacy Manager before taking any action.

    2. DSR Team within PlayForm is responsible for handling DSRs from PlayForm Users on a daily basis. The Human Resources department is responsible for handling the DSR from PlayForm employees.

    3. All DSRs from the Users must be addressed at and answered from the following e-mail address: DSR@PlayForm.LTD. DSR from the employees can be addressed directly to the HR manager or at DSR@PlayForm.LTD.

    4. The responsible employee must answer to the DSR within one (1) month from receiving the request. If complying with the DSR takes more than one month in time, the responsible employee must seek advice from the Privacy Manager and, where necessary, inform the Data Subject about the prolongation of the response term for up to two (2) additional months.

    5. The responsible employee must analyze the received DSR for the following criteria:

      • Data Subject identification. Before considering the DSR content, the responsible employee must make sure the Data Subject is the same person he/she claims to be. For this purpose, the connection between the personal data records and the data subject must be established.

      • Personal data. The responsible employee must check whether PlayForm has access to the personal data requested. If PlayForm does not have the personal data under the control, the responsible employee must inform the Data Subject, and, if possible, instruct on the further steps on how to access the data in question;

      • Content of the request. Depending on the content of the DSR, the responsible employee must define the type of the request and check whether it meets the conditions prescribed by this Policy and Data Protection Laws. The types of requests and the respective conditions for each of them can be consulted in Subsections 6.3-6.9. If the request does not meet the described criteria, the responsible employee must refuse to comply with the DSR and inform the Data Subject about the reasons for refusing;

      • Free of charge. Generally, all requests of Data Subjects and exercises of their rights are free of charge. If the responsible employee finds that the Data Subject exercises the rights in an excessive or unfound way (e.g., intended to harm or interrupt PlayForm’s business activities), the employee must seek the advice from the Privacy Manager, and, upon receiving of the latter, may either charge the Data Subject a reasonable fee or refuse to comply with the request;

      • Documenting. Whenever PlayForm receives the DSR, the Privacy Manager must make sure that the data and time, Data Subject, type of the request and the decision made regarding it are well documented. In the case of refusing to comply with the request, the reasons for refusing must be documented as well;

      • Recipients. When addressing the DSR, the Privacy Manager must make sure that all concerned recipients were informed the necessary actions were taken.

  2. The right to be informed.

    1. PlayForm must notify each Data Subject about the collection and further processing of the Personal Data.

    2. The information to be provided includes: the name and contact details of PlayForm; generic purposes of and the lawful basis for the data collection and further processing; categories of Personal Data collected; recipients/categories of recipients; retention periods; information about data subject rights, including the right to complain to the competent Supervisory Authority; the consequences of the cases where the data is necessary for the contract performance and the Data Subject does not provide the required data; details of the safeguards where personal data is transferred outside the EEA; and any third-party source of the personal data, without specification for the particular case (except if we receive the direct request from the Data Subject).

    3. The Users must be informed by the Privacy Policy accessible at PlayForm’s website and provided during the user registration. The employees and contractors must be informed by a standalone employee privacy statement, which explains the details described in p. 6.2.2 in a case-based manner, describing the particular purposes and activities.

    4. PlayForm must inform Data Subjects about data processing, including any new processing activity introduced at PlayForm within the following term:

      • if personal data is collected from the data subject directly, the data subject must be informed at the time we collect Personal Data from the Data Subjects by showing the Data Subject our privacy statement;

      • if the personal data is collected from other sources: (a) within one month from collecting it; (b) if the personal data are to be used for communication with the data subject, at the latest at the time of the first communication to that data subject; or (c) if a disclosure to another recipient is envisaged, at the latest when the personal data are first disclosed.

      • upon the request of the Data Subject; and

      • within one (1) month after any change of our personal data practices, change of the controller of Personal Data or after significant changes in our privacy statements.

  3. The right to access the information.

    1. The Data Subject must be provided only with those personal data records specified in the request. If the Data Subject requests access to all personal data concerning her or him, the employee must seek advice from the Privacy Manager first, to make sure all personal data of the Data Subject is mapped and provided.

    2. A Data Subject has the right to:

      • learn if we process the Data Subject’s Personal Data;

      • obtain disclosure regarding aspects of the processing, including detailed and case-specific information on purposes, categories of Personal Data, recipients/categories of recipients, retention periods, information about one’s rights, details of the relevant safeguards where personal data is transferred outside the EEA, and any third-party source of the personal data; and

      • obtain a copy of the Personal Data undergoing processing upon the request.

  4. The right to verify the Data Subject’s information and seek its rectification. The information we collect can be/become inaccurate or out-of-date (e.g., mistakes in nationality, date of birth, info on debts, economic activities). If we reveal that the Personal Data is inaccurate or the Data Subject requests us to do so, we must ensure that we correct all mistakes and update the relevant information.

  5. The right to restrict processing.

    1. The restriction of processing allows Data Subjects to temporarily stop the use of their information to prevent the possible harm caused by such use.

    2. This right applies when the Data Subject:

      • contests the accuracy of the Personal Data;

      • believes that we process the Personal Data unlawfully; and

      • objects against the processing and wants us not to process Personal Data while we are considering the request.

    3. In the case of receiving the restriction request, we must not process Personal Data in question for any other purpose than storing it or for legal compliance purposes until the circumstances of restriction cease to exist.

  6. The right to withdraw the consent. For the activities that require consent, the Data Subject can revoke their consent at any time. If the Data Subject revokes the consent, we must record the changes and must not process the Personal Data for consent-based purposes. The withdrawal of consent does not affect the lawfulness of the processing done before the withdrawal.

  7. The right to object against the processing.

    1. If we process the information in our legitimate interests, e.g., for direct marketing emails or for our marketing research purposes, the Data Subject can object against the processing.

    2. In the case of receiving the objection request case, we must consider Data Subject’s request and, where we do not have compelling interests, stop the processing for the specified purposes. If the personal data is still to be processed for other purposes, the Privacy Manager must make sure that the database has a record that the data cannot be further processed for the objected activities.

    3. The objection request can be refused only if the personal data in question is used for scientific/historical research or statistical purposes and was appropriately protected, i.e., by anonymization or pseudonymization techniques.

  8. Right to erasure/to be forgotten.

    1. The Data Subjects have the right to request us to erase their Personal Data if one of the following conditions are met:

      • Personal Data is no longer necessary for the purposes of collection. For example, a user has provided personal data for a one-time activity, such as data validation or participation in a contest, and the purpose is already fulfilled;

      • the Data Subject revokes one’s consent or objects to the processing (where applicable) and there is no other legal ground for the processing; or

      • we process the Personal Data unlawfully or its erasure is required by the applicable legislation of the European Union or one of the Member countries of the European Union.

    2. Conditions, under which we have the right to refuse the erasure:

      • Personal Data is processed for scientific/historical research or statistical purposes and is appropriately protected, i.e., pseudonymized or anonymized;

      • Personal Data is still necessary for legal compliance (e.g., financial or labor laws compliance).

    3. Only those personal data records must be deleted that were specified in the request. If the Data Subject requests the deletion of all personal data concerning her or him, the employee must seek advice from the Privacy Manager first, to make sure all the data about the Data Subject is mapped and can be deleted.

    4. If the User still has an account with us and requests the erasure of information necessary for maintaining the account, we must inform the User that the erasure will affect user experience or can lead to the closure of the account.

  9. Data portability.

    1. Data Subjects can ask us to transfer all the Personal Data and/or its part in a machine-readable format to a third party. This right applies in two cases:

      • personal data was collected for the purpose of provision of our services (performance of the contract); or

      • collected based on consent.

    2. To determine whether one of the p.6.9.1 conditions are met, the employee must seek advice from the Privacy Manager and check the applicable legal basis in the Records of processing activities. If the answer is negative, the request can be refused by PlayForm, and the Privacy Manager must decide whether to comply with the request on a voluntary basis.

    3. To comply with the request, the responsible employee must consolidate requested Personal Data and send the data in the format we are usually working with to the requested organization. The Data Subject must provide the necessary contact details of the organization.

New Data Processing Activities

  1. Notification to Privacy Manager.

    1. Before introducing any new activity that involves the processing of personal data, an employee responsible for its implementation must inform the Privacy Manager.

    2. Upon receiving information about a new activity, Privacy Manager must:

      • determine whether the data processing impact assessment (DPIA) and/or the consultation with the Supervisory Authority is necessary. If the answer is positive, the Privacy Manager must make sure the DPIA is conducted and/or the Supervisory Authority is consulted in accordance with the requirements of this Section and Data Protection Laws;

      • determine the legal basis for the processing and, where necessary, take further action for its fixation;

      • make sure the processing activity is done in accordance with this Policy, other PlayForm’s policies, as well as the Data Protection Laws;

      • add the processing activity to the Records of processing activities;

      • amend the privacy information statements and, where necessary, inform the concerned Data Subject accordingly.

  2. Data Processing Impact Assessment.

    1. To make sure that our current or prospective processing activities do not/will not violate the Data Subjects’ rights, PlayForm must, where required by Data Protection Laws, conduct the Data Processing Impact Assessment (DPIA), a risk-based assessment of the processing and search for the measures to mitigate the risks. The Privacy Manager must make sure the DPIA is conducted in accordance with this Section.

    2. The Privacy Manager, where necessary, involving the competent employees and/or external advisors, must conduct a DPIA if at least one of the following conditions are met:

      • the processing involves the use of new technologies, such as the Artificial Intelligence, use of connected and autonomous devices, etc. that creates certain legal, economic or similar effects to the Data Subject;

      • we systematically assess and evaluate personal aspects of the Data Subjects based on automated profiling, assigning the personal score/rate, and create legal or similar effects for the Data Subject by this activity;

      • we process on a large-scale sensitive data, which includes Personal Data relating to criminal convictions and offences, the data about vulnerable data subjects, the 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;

      • we collect or process Personal Data from a publicly accessible area or public sources on a large scale, or combine or match two different data sets; and

      • the Supervisory Authority in its public list requires conducting a DPIA for a certain type of activity we are involved in. The list of processing activities requiring conducting DPIA can be found on the website of each Supervisory Authority.

    3. The assessment shall contain at least the following details:

      • a systematic description of the processing operations and the purposes of the processing, including, where applicable, the legitimate interest pursued by us. The description must include the envisaged data categories and data subjects concerned, the scale of processing activities, such as its frequency, volume, envisaged number of records, etc.; recipients of the data, retention periods and, where applicable, international transfers;

      • an assessment of the necessity and proportionality of the processing operations in relation to the purposes. The DPIA must explain whether the activity is necessary for the purpose and whether the purpose can be achieved by less intrusive methods;

      • an assessment of the risks to the rights and freedoms of data subjects, including the rights of Data Subjects regarding their Personal Data.

      • The examples of risks are the processing which could lead to physical, material or non-material damage, in particular: where the processing may give rise to discrimination, identity theft or fraud, financial loss, damage to the reputation, loss of confidentiality of personal data protected by professional secrecy, unauthorized reversal of pseudonymization, or any other significant economic or social disadvantage; where data subjects might be deprived of their rights and freedoms or prevented from exercising control over their personal data; where personal data are processed which reveal racial or ethnic origin, political opinions, religion or philosophical beliefs, trade union membership, and the processing of genetic data, data concerning health or data concerning sex life or criminal convictions and offences or related security measures; where personal aspects are evaluated, in particular analyzing or predicting aspects concerning performance at work, economic situation, health, personal preferences or interests, reliability or behavior, location or movements, in order to create or use personal profiles; where personal data of vulnerable natural persons, in particular of children, are processed; or where processing involves a large amount of personal data and affects a large number of data subjects; and

      • the measures to address the risks, including safeguards, security measures, and mechanisms to ensure the protection of personal data and to demonstrate compliance with this Regulation.

    4. Where the DPIA did not provide how to effectively address the risks, the Privacy Manager must initiate the consultation with the competent Supervisory Authority to receive help with searching for the solution. In this case, PlayForm must not conduct the activity before the Supervisory Authority approves the processing activity in question.

Data Retention

  1. General Rule.

    1. The Privacy Manager must make sure that PlayForm clearly defined the data storage periods and/or criteria for determining the storage periods for each processing activity it has. The periods for each processing activity must be specified in the Records of processing activities.

    2. Each department within PlayForm must comply with the data storage periods in accordance with the retention schedule provided in Records of processing activities. The Privacy Manager must supervise each department and make sure they comply with this requirement.

    3. After the storage period ends, the personal data must be removed from the disposal of the department responsible for the processing or, in cases where the data is not needed for any other purposes, destroyed completely, including from back-up copies and other media.

    4. Whenever the storage period for a processing activity has ended, but the personal data processed is necessary for other processing purposes, the department manager must make sure that the personal data is not used for the ceased processing activity, and the responsible employees do not have the access to it unless required for any other activity.

  2. Exemptions. The rules specified in Subsection 8.1 have the following exceptions:

    1. Business needs. Data retention periods can be prolonged, but no longer than 60 days, in the case that the data deletion will interrupt or harm our ongoing business. The Privacy Manager must approve any unforeseen prolongation;

    2. Technical impossibility. Some information is technically impossible or disproportionally difficult to delete. For example, deletion of the information may lead to breach of system integrity, or it is impossible to delete the information from the backup copies. In such a case, the information can be further stored, subject to the approval by the Privacy Manager and making respective amendments to the Records of processing activities; and

    3. Anonymization. The Personal Data can be further processed for any purposes (e.g., marketing) if we fully anonymize these data after the retention period is expired. This means that all personal identifiers and connections to them will be deleted from the data. To consider Personal Data anonymous, it must be impossible to reidentify the Data Subject from the data set.

Security

  1. Each department within PlayForm shall take all appropriate technical and organizational measures that protect against unauthorized, unlawful, and/or accidental access, destruction, modification, blocking, copying, distribution, as well as from other illegal actions of unauthorized persons regarding the personal data under their responsibility.

  2. The employee responsible for the supervision after the security of personal data within PlayForm shall be DSR Officer. This person implements the guidelines and other specifications on data protection and information security in his area of responsibility. He/she advises PlayForm management on the planning and implementation of information security in PlayForm, and must be involved in all projects at an early stage in order to take security-related aspects into account as early as the planning phase.

Data Breach Response Procedure

  1. Response Team.

    1. In case of revealing the Data Breach, CEO of PlayForm shall urgently form the Data Breach Response Team (the “Response Team”), which will handle the Data Breach, notify the appropriate persons, and mitigate its risks.

    2. The Response Team must be а multi-disciplinary group headed by CEO of PlayForm and comprised of the Privacy Manager, privacy laws specialist (whether internal or external), and knowledgeable and skilled information security specialists within PlayForm or outsourcing professionals, if necessary. The team must ensure that all employees and engaged contractors/processors adhere to this Policy and provide an immediate, effective, and skillful response to any suspected/alleged or actual Data Breach affecting PlayForm.

    3. The potential members of the Response Team must be prepared to respond to а Data Breach. The Response Team shall perform all the responsibilities of PlayForm mentioned in this Policy. The duties of the Response Team are:

      • to communicate the Data Breach to the competent Supervisory Authority(-ies);

      • in case of high risk to the rights and freedoms of Data Subjects, to communicate the Data Breach to the Data Subject;

      • if PlayForm obtain data from any third party as a processor, and a Data Breach involves obtained data, to inform the third parties about the Data Breach;

      • to communicate PlayForm’s contractors or any other third parties that process the Personal Data involved in the Data Breach; and

      • to take all appropriate technical and organizational measures to cease the Data Breach and mitigate its consequences;

      • to record the fact of the Data Breach in the Records of processing activities and file an internal data breach report that describes the event.

    4. The Response Team shall perform its duties until all the necessary measures required by this Policy are taken.

  2. Notification to Supervisory Authority.

    1. PlayForm shall inform the Competent Supervisory Authority about the Data Breach without undue delay and, where it is possible, not later than 72 hours after having become aware of the Data Breach.

    2. The Competent Supervisory Authority shall be determined by the residence of the Data Subjects, whose information was involved in the Data Breach. If the Data Breach concerns the Personal Data of Data Subjects from more than one country, PlayForm shall inform all Competent Supervisory Authorities.

    3. To address the notification to the authority, the Response Team should use Annex 1 to this Policy. Annex 1 contains all the necessary contact information of the EU supervisory authorities. If the Data Breach concerns Data Subjects from other than the EU countries, the Response Team shall ask a competent privacy specialist for advice.

    4. The notification to the Competent Supervisory Authority shall contain, at least, following information:

      • the nature of the Data Breach including where possible, the categories and an approximate number of Data Subjects and Personal Data records concerned;

      • the name and contact details of the Response Team, Privacy Manager or, if not applicable, of the CEO;

      • the likely consequences of the Data Breach. Explain PlayForm’s point of view on the purposes and possible further risks of the Data Breach. E.g., the Personal Data may be stolen for the further sale, fraud activities or blackmailing the concerned Data Subjects; and

      • the measures taken or proposed to be taken by PlayForm to address the Data Breach, including, where appropriate, measures to mitigate its possible adverse effects.

    5. To file a notification, the Response Team should use PlayForm’s Data Breach Notification Form to the Supervisory Authority.

  3. Notifications to Data Subjects.

    1. When the Data Breach is likely to result in a high risk to the rights and freedoms of Data Subjects (e.g., stealing of funds, assets, proprietary information), we must also communicate the Data Breach to the concerned Data Subjects without undue delay. The Privacy Manager must determine if there is a high risk based on the risk factors specified in Subsection 7.2.3 of this Policy.

    2. The notification shall contain the following information:

      • description of the Data Breach - what happened and what led to the Data Breach, such as a security breach, employee’s negligence, error in the system work. If the Response Team decided not to disclose the causes of the Data Breach, then this clause must not be mentioned;

      • the measures taken by PlayForm regarding the Data Breach, including security measures, internal investigations, and supervisory authority notice;

      • recommendations for the concerned Data Subjects how to mitigate risks and possible consequences, such as guidelines on how to restore access to an account, preventing measures (change of a password); and

      • the contact information of the Response Team or one of its members.

    3. The notification to the Data Subjects should be carried out by the email letter or, where it is impossible to use the email, by other available means of communication.

    4. Exemptions. We do not have to send the notification to the Data Subjects if any of the following conditions are met:

      • PlayForm has implemented appropriate technical and organizational protection measures, and those measures were applied to the Personal Data affected by the Data Breach, in particular, those that leave the Personal Data inaccessible to any person who is not authorized to access it, such as encryption;

      • PlayForm has taken subsequent measures which ensure that the high risk to the rights and freedoms of Data Subjects referred to in this section is no longer likely to materialize; or

      • it would involve a disproportionate effort to communicate with every concerned Data Subject. In such a case, there shall instead be a public communication or similar measure whereby the Data Subjects are informed in an equally effective manner.

In the case we apply one of the exemptions, we must document the circumstances, reason for not informing, and actions taken to meet one of the exemptions.

  1. Communication with Third Parties.

    1. In the case a Data Breach concerns the Personal Data shared with us or processed by us on behalf of a Third Party, we must also notify the Third Party about it within 24 hours. If we process the Personal Data as a Data Processor, the notification of the Third Party does not exempt us from the duty to mitigate the Data Breach consequences, but we must not inform the Competent Supervisory Authority and Data Subjects.

    2. In case of receiving the notification about the Data Breach from the Data Processor or other Third Parties that have access to the Personal Data, CEO of PlayForm shall, in accordance with this Section:

      • form the Response Team;

      • request the Third Party to send the information mentioned in Subsections 10.2-3 of this Policy;

      • where necessary, inform the Competent Supervisory Authority(-ies) and Data Subjects; and

      • perform other steps of the Data Breach response procedure.

List of Persons Briefed on Personal Data Protection Policy

Full Name

Status

Date

Nikola HristovBriefed05.25.2018

ANNEX 1 TO THE PERSONAL DATA PROTECTION POLICY

European National Data Protection Authorities

Austria

Österreichische Datenschutzbehörde
Hohenstaufengasse 3
1010 Wien
Tel. +43 1 531 15 202525
Fax +43 1 531 15 202690
E-mail: dsb@dsb.gv.at
WebSite: HTTPS://www.dsb.gv.at

Art 29 WP Member: Dr Andrea JELINEK, Director, Österreichische Datenschutzbehörde

Belgium

Commission de la protection de la vie privée
Commissie voor de bescherming van de persoonlijke levenssfeer
Rue de la Presse 35 / Drukpersstraat 35 1000 Bruxelles / 1000 Brussel
Tel. +32 2 274 48 00
Fax +32 2 274 48 35
E-mail: commission@privacycommission.be
WebSite: HTTPS://www.privacycommission.be

Art 29 WP Vice-President: Willem DEBEUCKELAERE, President of the Belgian Privacy commission

Bulgaria

Commission for Personal Data Protection
2, Prof. Tsvetan Lazarov Blvd. Sofia 1592
Tel. +359 2 915 3580
Fax +359 2 915 3525
E-mail: kzld@cpdp.bg
WebSite: HTTPS://www.cpdp.bg

Art 29 WP Member: Mr. Ventsislav KARADJOV, Chairman of the Commission for Personal Data Protection
Art 29 WP Alternate Member: Ms. Mariya MATEVA

Croatia

Croatian Personal Data Protection Agency
Martićeva 14
10000 Zagreb
Tel. +385 1 4609 000
Fax +385 1 4609 099
E-mail: azop@azop.hr or info@azop.hr
WebSite: HTTPS://www.azop.hr

Art 29 WP Member: Mr. Anto RAJKOVAČA, Director of the Croatian Data Protection Agency

Cyprus

Commissioner for Personal Data Protection
1 Iasonos Street,
1082 Nicosia
P.O. Box 23378, CY-1682 Nicosia Tel. +357 22 818 456
Fax +357 22 304 565
E-mail: commissioner@dataprotection.gov.cy
WebSite: HTTPS://www.dataprotection.gov.cy

Art 29 WP Member: Ms. Irene LOIZIDOU NIKOLAIDOU
Art 29 WP Alternate Member: Mr. Constantinos GEORGIADES

Czech Republic

The Office for Personal Data Protection
Urad pro ochranu osobnich udaju Pplk. Sochora 27
170 00 Prague 7
Tel. +420 234 665 111
Fax +420 234 665 444
E-mail: posta@uoou.cz
WebSite: HTTPS://www.uoou.cz

Art 29 WP Member: Ms. Ivana JANŮ, President of the Office for Personal Data Protection
Art 29 WP Alternate Member: Mr. Ivan PROCHÁZKA, Adviser to the President of the Office

Denmark

Datatilsynet
Borgergade 28, 5
1300 Copenhagen K
Tel. +45 33 1932 00
Fax +45 33 19 32 18
E-mail: dt@datatilsynet.dk
WebSite: HTTPS://www.datatilsynet.dk

Art 29 WP Member: Ms. Cristina Angela GULISANO, Director, Danish Data Protection Agency (Datatilsynet)
Art 29 WP Alternate Member: Mr. Peter FOGH KNUDSEN, Head of International Division at the Danish Data Protection Agency (Datatilsynet)

Estonia

Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)
Väike-Ameerika 19
10129 Tallinn
Tel. +372 6274 135
Fax +372 6274 137
E-mail: info@aki.ee
WebSite: HTTPS://www.aki.ee/en

Art 29 WP Member: Mr. Viljar PEEP, Director General, Estonian Data Protection Inspectorate
Art 29 WP Alternate Member: Ms. Maarja Kirss

Finland

Office of the Data Protection Ombudsman
P.O. Box 315
FIN-00181 Helsinki Tel. +358 10 3666 700
Fax +358 10 3666 735
E-mail: tietosuoja@om.fi
WebSite: HTTPS://www.tietosuoja.fi/en

Art 29 WP Member: Mr. Reijo AARNIO, Ombudsman of the Finnish Data Protection Authority
Art 29 WP Alternate Member: Ms. Elisa KUMPULA, Head of Department

France

Commission Nationale de l’Informatique et des Libertés - CNIL
8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02
Tel. +33 1 53 73 22 22
Fax +33 1 53 73 22 00
WebSite: HTTPS://www.cnil.fr

Art 29 WP Member: Ms. Isabelle FALQUE-PIERROTIN, President of CNIL
Art 29 WP Alternate Member: Ms. Florence RAYNAL

Germany

Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit
Husarenstraße 30
53117 Bonn
Tel. +49 228 997799 0; +49 228 81995 0
Fax +49 228 997799 550; +49 228 81995 550
E-mail: poststelle@bfdi.bund.de
WebSite: HTTPS://www.bfdi.bund.de

The competence for complaints is split among different data protection supervisory authorities in Germany.

Competent authorities can be identified according to the list provided under

HTTPS://www.bfdi.bund.de/EN/Service/Anschriften/Laender/Laender-node.html

Art 29 WP Member: Ms. Andrea VOSSHOFF, Federal Commissioner for Freedom of Information
Art 29 WP Alternate Member: Prof. Dr. Johannes CASPAR, representative of the federal states

Greece

Hellenic Data Protection Authority
Kifisias Av. 1-3, PC 11523 Ampelokipi Athens
Tel. +30 210 6475 600
Fax +30 210 6475 628
E-mail: contact@dpa.gr
WebSite: HTTPS://www.dpa.gr

Art 29 WP Member: Mr. Konstantinos Menoudakos, President of the Hellenic DPA
Art 29 WP Alternate Member: Dr. Vasilios ZORKADIS, Director

Hungary

National Authority for Data Protection and Freedom of Information
Szilágyi Erzsébet fasor 22/C H-1125 Budapest
Tel. +36 1 3911 400
E-mail: peterfalvi.attila@naih.hu
WebSite: HTTPS://www.naih.hu

Art 29 WP Member: Dr Attila PÉTERFALVI, President of the National Authority for Data Protection and Freedom of Information
Art 29 WP Alternate Member: Mr. Endre Győző SZABÓ Vice-president of the National Authority for Data Protection and Freedom of Information

Ireland

Data Protection Commissioner
Canal House Station Road Portarlington Co. Laois
Lo-Call: 1890 25 22 31
Tel. +353 57 868 4800
Fax +353 57 868 4757
E-mail: info@dataprotection.ie
WebSite: HTTPS://www.dataprotection.ie

Art 29 WP Member: Ms. Helen DIXON, Data Protection Commissioner
Art 29 WP Alternate Members: Mr. John O’DWYER, Deputy Commissioner; Mr. Dale SUNDERLAND, Deputy Commissioner

Italy

Garante per la protezione dei dati personali
Piazza di Monte Citorio, 121 00186 Roma
Tel. +39 06 69677 1
Fax +39 06 69677 785
E-mail: garante@garanteprivacy.it
WebSite: HTTPS://www.garanteprivacy.it

Art 29 WP Member: Mr. Antonello SORO, President of Garante per la protezione dei dati personali
Art 29 WP Alternate Member: Ms. Giuseppe BUSIA, Secretary General of Garante per la protezione dei dati personali

Latvia

Data State Inspectorate Director: Ms. Daiga Avdejanova
Blaumana str. 11/13-15
1011 Riga
Tel. +371 6722 3131
Fax +371 6722 3556
E-mail: info@dvi.gov.lv
WebSite: HTTPS://www.dvi.gov.lv

Art 29 WP Alternate Member: Ms. Aiga BALODE

Lithuania

State Data Protection
Žygimantų str. 11-6a 011042 Vilnius
Tel. + 370 5 279 14 45
Fax +370 5 261 94 94
E-mail: ada@ada.lt
WebSite: HTTPS://www.ada.lt

Art 29 WP Member: Mr. Raimondas Andrijauskas, Director of the State Data Protection Inspectorate
Art 29 WP Alternate Member: Ms. Neringa KAKTAVIČIŪTĖ-MICKIENĖ, Head of Complaints Investigation and International Cooperation Division

Luxembourg

Commission Nationale pour la Protection des Données
1, avenue du Rock’n’roll L-4361 Esch-sur-Alzette Tel. +352 2610 60 1
Fax +352 2610 60 29
E-mail: info@cnpd.lu
WebSite: HTTPS://www.cnpd.lu

Art 29 WP Member: Ms. Tine A. LARSEN, President of the Commission Nationale pour la Protection des Données
Art 29 WP Alternate Member: Mr. Thierry LALLEMANG, Commissioner

Malta

Office of the Data Protection Commissioner
Data Protection Commissioner: Mr. Joseph Ebejer
2, Airways House
High Street, Sliema SLM 1549 Tel. +356 2328 7100
Fax +356 2328 7198
E-mail: commissioner.dataprotection@gov.mt
WebSite: HTTPS://idpc.org.mt

Art 29 WP Member: Mr. Saviour CACHIA, Information and Data Protection Commissioner
Art 29 WP Alternate Member: Mr. Ian DEGUARA, Director - Operations and Programme Implementation

Netherlands

Autoriteit Persoonsgegevens
Prins Clauslaan 60
P.O. Box 93374
2509 AJ Den Haag/The Hague Tel. +31 70 888 8500
Fax +31 70 888 8501
E-mail: info@autoriteitpersoonsgegevens.nl
WebSite: HTTPS://autoriteitpersoonsgegevens.nl/nl

Art 29 WP Member: Mr. Aleid WOLFSEN, Chairman of Autoriteit Persoonsgegevens

Poland

The Bureau of the Inspector General for the Protection of Personal Data – GIODO
ul. Stawki 2
00-193 Warsaw
Tel. +48 22 53 10 440
Fax +48 22 53 10 441
E-mail: kancelaria@giodo.gov.pl; desiwm@giodo.gov.pl
WebSite: HTTPS://www.giodo.gov.pl

Art 29 WP Member: Ms. Edyta BIELAK-JOMAA, Inspector General for the Protection of Personal Data

Portugal

Comissão Nacional de Protecção de Dados - CNPD
R. de São. Bento, 148-3° 1200-821 Lisboa
Tel. +351 21 392 84 00
Fax +351 21 397 68 32
E-mail: geral@cnpd.pt
WebSite: HTTPS://www.cnpd.pt

Art 29 WP Member: Ms. Filipa CALVÃO, President, Comissão Nacional de Protecção de Dados
Art 29 WP Alternate Member: Isabel CRUZ, Secretary-General of the DPA

Romania

The National Supervisory Authority for Personal Data Processing President: Mrs. Ancuţa Gianina Opre
B-dul Magheru 28-30
Sector 1, BUCUREŞTI
Tel. +40 21 252 5599
Fax +40 21 252 5757
E-mail: anspdcp@dataprotection.ro
WebSite: HTTPS://www.dataprotection.ro

Art 29 WP Member: Ms. Ancuţa Gianina OPRE, President of the National Supervisory Authority for Personal Data Processing
Art 29 WP Alternate Member: Ms. Alina SAVOIU, Head of the Legal and Communication Department

Slovakia

Office for Personal Data Protection of the Slovak Republic
Hraničná 12
820 07 Bratislava 27
Tel.: + 421 2 32 31 32 14
Fax: + 421 2 32 31 32 34
E-mail: statny.dozor@pdp.gov.sk
WebSite: HTTPS://dataprotection.gov.sk

Art 29 WP Member: Ms. Soňa PŐTHEOVÁ, President of the Office for Personal Data Protection of the Slovak Republic
Art 29 WP Alternate Member: Mr. Anna VITTEKOVA, Vice President

Slovenia

Information Commissioner
Ms. Mojca Prelesnik Zaloška 59
1000 Ljubljana
Tel. +386 1 230 9730
Fax +386 1 230 9778
E-mail: gp.ip@ip-rs.si
WebSite: HTTPS://www.ip-rs.si

Art 29 WP Member: Ms. Mojca PRELESNIK, Information Commissioner of the Republic of Slovenia

Spain

Agencia de Protección de Datos
C/Jorge Juan, 6
28001 Madrid
Tel. +34 91399 6200
Fax +34 91455 5699
E-mail: internacional@agpd.es
WebSite: HTTPS://www.agpd.es

Art 29 WP Member: Ms. María del Mar España Martí, Director of the Spanish Data Protection Agency
Art 29 WP Alternate Member: Mr. Rafael GARCIA GOZALO

Sweden

Datainspektionen
Drottninggatan 29 5th Floor
Box 8114
20 Stockholm
Tel. +46 8 657 6100
Fax +46 8 652 8652
E-mail: datainspektionen@datainspektionen.se
WebSite: HTTPS://www.datainspektionen.se

Art 29 WP Member: Ms. Kristina SVAHN STARRSJÖ, Director General of the Data Inspection Board
Art 29 WP Alternate Member: Mr. Hans-Olof LINDBLOM, Chief Legal Adviser

United Kingdom

The Information Commissioner’s Office
Water Lane, Wycliffe House Wilmslow - Cheshire SK9 5AF Tel. +44 1625 545 745
E-mail: international.team@ico.org.uk
WebSite: HTTPS://ico.org.uk

Art 29 WP Member: Ms. Elizabeth DENHAM, Information Commissioner
Art 29 WP Alternate Member: Mr. Steve WOOD, Deputy Commissioner

EUROPEAN FREE TRADE AREA (EFTA)

Iceland

Icelandic Data Protection Agency
Rauðarárstíg 10
Reykjavík
Tel. +354 510 9600; Fax +354 510 9606
E-mail: postur@personuvernd.is
WebSite: HTTPS://www.personuvernd.is

Liechtenstein

Data Protection Office
Kirchstrasse 8, P.O. Box 684
9490 Vaduz
Principality of Liechtenstein Tel. +423 236 6090
E-mail: info.dss@llv.li
WebSite: HTTPS://www.datenschutzstelle.li

Norway

Datatilsynet
Data Protection Authority: Mr. Bjørn Erik THORN
The Data Inspectorate
P.O. Box 8177 Dep 0034 Oslo
Tel. +47 22 39 69 00; Fax +47 22 42 23 50
E-mail: postkasse@datatilsynet.no
WebSite: HTTPS://www.datatilsynet.no

Switzerland

Data Protection and Information Commissioner of Switzerland
Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter Mr. Adrian Lobsiger
Feldeggweg 1
3003 Bern
Tel. +41 58 462 43 95; Fax +41 58 462 99 96
E-mail: contact20@edoeb.admin.ch
WebSite: HTTPS://www.edoeb.admin.ch

Footnotes

  1. HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en; ↩

  2. HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en; ↩

\ No newline at end of file + Personal Data Protection Policy
+

PERSONAL DATA PROTECTION POLICY

+

Effective date: 05.25.2018 / May 25th 2018
+Last updated: 02.11.2022 / February 11th 2022

+

We at PlayForm ltd. are committed to processing personal data securely and +respecting privacy of the concerned individuals.

+ ++++ + + + + + + + + + +
Version No. and date of the last update:

v. 1.0.

+

February 11th 2022

This policy shall be reviewed annually or each time when the changes in our data processing occur.
+

Scope and Definitions

+
    +
  1. +

    Scope. This Personal Data Protection +Policy (the “Policy”) describes PlayForm ltd. internal rules for +personal data processing and protection. The Policy applies to PlayForm +ltd., including PlayForm ltd. employees and contractors (“we”, “us”, +“our”, “PlayForm”). The management of each entity is ultimately +responsible for the implementation of this policy, as well as to ensure, at +entity level, there are adequate and effective procedures in place for its +implementation and ongoing monitoring of its adherence. For the purposes of +this Policy, employees and contractors are jointly referred to as the +“employees”.

    +
    2. +
  2. +

    Privacy Manager. Privacy Manager is an +employee of PlayForm responsible for personal data protection compliance +within PlayForm (the “Privacy Manager”). The Privacy Manager is in +charge of performing the obligations imposed by this Policy and supervising +other employees, who subject to this Policy, regarding their adherence to +this Policy. The Privacy Manager must be involved in all projects at an +early stage in order to take personal data protection aspects into account +as early as the planning phase.
    +The designated Privacy Manager at PlayForm ltd. is Nikola Hristov +Nikola@PlayForm.LTD.

    +
    3. +
  3. +

    Definitions.

    +
    4. +
+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Competent Supervisory Authoritymeans a public authority that is responsible for regulating and supervising personal data protection with regards to activities of PlayForm.
Data Breach

means a breach of the security and/or confidentiality leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data transmitted, stored or otherwise processed.

+

This includes but is not limited to e-mails sent to an incorrect or disclosed list of recipients, an unlawful publication of the Personal Data, loss or theft of physical records, and unauthorized access to personal information.

Data Controllermeans the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines (make a decision) the purposes and means of the processing of Personal Data.
Data Processormeans a natural or legal person, public authority, agency or other body which processes the Personal Data on behalf of the data controller.
Data Protection Lawsmean any laws and legal rules on personal data use and protection applicable to the activities of PlayForm, including, but not limited to the Regulation (EU) 2016/679 of the European Parliament and of the Council of April 27, 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation, GDPR).
Data Subject Request (DSR)means any request from the Data Subject and concerning their personal data and/or data subject rights.
Data Subjectmeans a natural person, whose Personal Data we process. Data Subjects include but are not limited to users, website visitors, employees, contractors, and partners of PlayForm.
Personal Datameans any information relating to an identified or identifiable Data Subject; a Data Subject can be identified by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or the combination of factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that Data Subject.
Processingmeans any operation or set of operations which is performed by PlayForm on Personal Data, such as 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.
Standard Contractual Clausesmeans the European Commission Decision of February, 5 2010 on standard contractual clauses for the transfer of personal data to processors established in third countries under Directive 95/46/EC of the European Parliament and of the Council (2010/87/EU).
Third Partymeans a natural or legal person, who accesses the Personal Data for further processing and is not an employee, member or corporate affiliate of PlayForm. This definition does not apply to natural persons, who provide services to PlayForm as contractors on a regular basis.
Usermeans a Data Subject who uses our services provided on PlayForm website.
+

Data Processing Principles

+
    +
  1. +

    PlayForm’s processing activities must be in line with the principles +specified in this Section. The Privacy Manager must make sure that +PlayForm’s compliance documentation, as well as data processing activities, +are compliant with the data protection principles.

    +
    2. +
  2. +

    We must process the Personal Data in accordance with the following +principles:

    +
      +
    1. +

      Lawfully, fairly and in a transparent manner (lawfulness, fairness and +transparency). We shall always have a legal ground for the processing +(described in Section 3 of this Policy), collect the amount of data +adequate to the purpose and legal grounds, and we make sure the Data +Subjects are aware of the processing;

      +
      2. +
    2. +

      Collected for specified, explicit and legitimate purposes and not +further processed in a manner that is incompatible with those purposes +(purpose limitation). We must not process the Personal Data for the +purposes not specified in our compliance documentation without obtaining +specific approval of the Privacy Manager;

      +
      3. +
    3. +

      Adequate, relevant and limited to what is necessary for the purposes for +which they are processed (data minimization). We always make sure +the data we collect is not excessive and limited by the strict +necessity;

      +
      4. +
    4. +

      Accurate and, where necessary, kept up to date (accuracy). We +endeavor to delete inaccurate or false data about Data Subjects and make +sure we update the data. Data Subjects can ask us for a correction of +the Personal Data;

      +
      5. +
    5. +

      Kept in a form which permits identification of Data Subjects for no +longer than is necessary for the purposes for which the Personal Data +are processed (storage period limitation). The storage periods must +be limited as prescribed by Data Protection Laws and this Policy; and

      +
      6. +
    6. +

      Process in a manner that ensures appropriate security of the Personal +Data, including protection against unauthorized or unlawful processing +and accidental loss, destruction or damage, using appropriate technical +or organizational measures (confidentiality, integrity, and +availability).

      +
      7. +
    +
    3. +
  3. +

    Accountability.

    +
      +
    1. +

      We shall be able to demonstrate our compliance with Data Protection Laws +(accountability principle). In particular, we must ensure and +document all relevant procedures, efforts, internal and external +consultations on personal data protection including:

      +
        +
      • +

        the fact of appointing a person responsible for PlayForm’s data +protection compliance;

        +
        • +
      • +

        where necessary, a record of a Data Processing Impact Assessment;

        +
        • +
      • +

        developed and implemented notices, policies, and procedures, such as +Privacy Notice, this policy or Data Breach response procedure;

        +
        • +
      • +

        the fact of staff training on compliance with Data Protection laws; +and

        +
        • +
      • +

        assessment, implementation, and testing organizational and technical +data protection measures.

        +
        • +
      +
      2. +
    2. +

      The Privacy Manager must maintain PlayForm’s Records of processing +activities, which is an accountability document that describes personal +data processing activities of PlayForm, prepared in accordance with Art. +30 of the GDPR (the “Records of processing activities”). The Records +of processing activities must maintain, at least, the following +information about each processing activity:

      +
        +
      • +

        contact details of PlayForm, the EU Representative, and, where +applicable, of the Data Protection Officer;

        +
        • +
      • +

        name of the activity, its purposes and legal basis along with, where +applicable, the legitimate interests of PlayForm;

        +
        • +
      • +

        data subjects and personal data categories concerned;

        +
        • +
      • +

        data retention periods;

        +
        • +
      • +

        general description of applicable security measures;

        +
        • +
      • +

        recipients, including joint controllers, processors, and contractors +involved, as well as the fact of the international data transfer with +the safeguards applied to the transfer;

        +
        • +
      • +

        where applicable, a reference to the Data Processing Impact +Assessment;

        +
        • +
      • +

        where applicable, a reference to the record of the data breach +occurred involving the personal data;

        +
        • +
      • +

        if PlayForm acts as a data processor, the information to be provided +includes the names and contact details of controllers, name and +contact details of controller’s representative (if applicable), +categories of processing (activities), names of third countries or +international organizations that personal data are transferred to (if +applicable), safeguards for exceptional transfers of personal data to +third countries or international organizations (if applicable), and +general description of technical and organizational security measures.

        +
        • +
      +
      3. +
    +
    4. +
+ +
    +
  1. +

    Legal grounds.

    +
      +
    1. +

      Each processing activity must have one of the lawful grounds specified +in this Section to process the Personal Data. If we do not have any of +the described, we cannot collect or further process the Personal Data.

      +
      2. +
    2. +

      If PlayForm is intended to use personal data for other purposes than +those specified in the Records of processing activities, the Privacy +Manager must evaluate, determine, and, if necessary, collect/record the +appropriate legal basis for it.

      +
      3. +
    3. +

      Performance of the contract. Where PlayForm has a contract with the +Data Subject, e.g., website’s Terms of Use or the employment contract, +and the contract requires the provision of personal data from the Data +Subject, the applicable legal ground will be the performance of the +contract.

      +
      4. +
    4. +

      Consent. To process the personal data based on the consent, we must +obtain the consent before the Processing and keep the evidence of the +consent with the records of Data Subject’s Personal Data. The Privacy +Manager must make sure that the consent collected from Data Subjects +meet the requirements of Data Protection Laws and this Policy. In +particular, the Privacy Manager must make sure that:

      +
        +
      • +

        the Data Subject must be free to give or refuse to give consent.

        +
        • +
      • +

        the consent is in the form of an active indication from the Data +Subject, i.e., the consent checkbox must not be pre-ticked for the +user.

        +
        • +
      • +

        the request for the consent clearly articulates the purposes of the +processing, and other information specified in Subsection 6.2 is +available to the Data Subject.

        +
        • +
      • +

        the Data Subject must be free to give one’s consent or to revoke it.

        +
        • +
      +
      5. +
    5. +

      Legitimate interests. We have the right to use personal data in our +‘legitimate interests’. The interests can include the purposes that are +justified by the nature of our business activities, such as the +marketing analysis of personal data. For PlayForm to use legitimate +interests as a legal ground for the processing, the Privacy Manager must +make sure that:

      +
        +
      • +

        the legitimate interest in the processing is clearly defined and +recorded in the Records of processing activities;

        +
        • +
      • +

        any envisaged risks to Data Subject rights and interests are spotted. +The examples of the risks can be found in Subsection 7.2.;

        +
        • +
      • +

        the Data Subjects have reasonable expectations about the processing, +and additional protective measures to address the risks are taken;

        +
        • +
      • +

        subject to the conditions of Subsection 6.7 (Right to object against +the processing), the Data Subject is provided with the opportunity to +opt-out from the processing for the described legitimate interests.
        +If at least one of the above conditions is not met by PlayForm, the +Privacy Manager must choose and propose a different legal ground for +the processing, such as consent.

        +
        • +
      +
      6. +
    6. +

      Legal Compliance and Public Interest. Besides the grounds specified +afore, we might be requested by the laws of the European Union or laws +of the EU Member State to process Personal Data of our Users. For +example, we can be required to collect, analyze, and monitor the +information of Users to comply with financial or labor laws.
      +Whenever we have such an obligation, we must make sure that:

      +
        +
      • +

        we process personal data strictly in accordance with relevant legal +requirements;

        +
        • +
      • +

        we do not use or store the collected Personal Data for other purposes +than legal compliance; and

        +
        • +
      • +

        the Data Subjects are properly and timely informed about our +obligations, scope, and conditions of personal data processing.

        +
        • +
      +
      7. +
    +
    2. +
+

Important: Where PlayForm has the law requirements of another country to process +personal data, the Privacy Manager must propose using another legal ground for +the processing under Data Protection Laws, such as legitimate interests or +consent.

+

Access to Personal Data

+
    +
  1. +

    Access to Personal Data.

    +
      +
    1. +

      The employees must have access to the personal data on a “need-to-know” +basis. The data can be accessed only if it is strictly necessary to +perform one of the activities specified in the Records of processing +activities. The employees and contractors shall have access to the +Personal Data only if they have the necessary credentials for it.

      +
      2. +
    2. +

      Heads of the departments within PlayForm are responsible for their +employees’ access and processing of personal data. The heads must +maintain the list of employees that are entitled to access and process +personal data. The Privacy Manager shall have the right to review the +list and, where necessary, request the amendments to meet the +requirements of this Policy.

      +
      3. +
    3. +

      Heads of the departments within PlayForm must ensure that the employees +under their supervision are aware of the Data Protection Laws and comply +with the rules set in this Policy. To make sure our employees are able +to comply with the data protection requirements, we must provide them +with adequate data protection training.

      +
      4. +
    4. +

      All employees accessing personal data shall keep strict confidentiality +regarding the data they access. The employees that access personal data +must use only those means (software, premises, etc.) for the processing +that were prescribed by PlayForm. The data must not be disclosed or +otherwise made available out of the management instructions.

      +
      5. +
    5. +

      The employees within their competence must assist PlayForm’s +representatives, including the Privacy Manager, in any efforts regarding +compliance with Data Protection Laws and/or this Policy.

      +
      6. +
    6. +

      When an employee detects or believes there is suspicious activity, data +breach, non-compliance with Data Protection Laws and/or this Policy, or +a DSR was not routed to the competent department within PlayForm, the +employee must report such activity to the Privacy Manager.

      +
      7. +
    7. +

      Employees that are unsure about whether they can legitimately process or +disclose Personal Data must seek advice from the Privacy Manager before +taking any action.

      +
      8. +
    8. +

      Any occasional access to personal data for activities not specified in +the Records of processing activities is prohibited. If there is a strict +necessity for immediate access, the Privacy Manager must approve the +access first.

      +
      9. +
    +
    2. +
+

Third Parties

+
    +
  1. +

    Before sharing personal data with any person outside of PlayForm, the +Privacy Manager must ensure that this Third Party has an adequate data +protection level and provide sufficient data protection guarantees in +accordance with Data Protection Laws, including, but not limited to the +processorship requirements (Art. 28 of the GDPR) and international transfers +compliance (Section 5 of the GDPR). Where necessary, the Privacy Manager +must make sure that PlayForm enters into the appropriate data protection +contract with the third party.

    +
    2. +
  2. +

    An employee can share personal data with third parties only if and to the +extent that was directly prescribed by the manager and specified in the +Records of processing activities.

    +
    3. +
  3. +

    If we are required to delete, change, or stop the processing of the Personal +Data, we must ensure that the Third Parties, with whom we shared the +Personal Data, will fulfill these obligations accordingly.

    +
    4. +
  4. +

    Whenever PlayForm is engaged as a data processor on behalf of another +entity, the Privacy Manager must make sure PlayForm complies with the +processorship obligation. In particular, the appropriate data processing +agreement in accordance with the Data Protection Laws must be in place. The +Privacy Manager must supervise the compliance with data processing +instructions from the controller, including regarding the scope of +processing activities, involvement of sub-processors, international +transfers, storage, and further disposal of processed personal data. The +personal data processed under the processor role must not be processed for +any other purposes than specified in the relevant instructions, agreement or +other legal act regulating the relationships with the controller.

    +
    5. +
+

International Transfers

+
    +
  1. +

    If we have the employees, contractors, corporate affiliates, or Data +Processors outside of the EEA, and we transfer Personal Data to them for the +processing, the Privacy Manager must make sure PlayForm takes all necessary +and appropriate safeguards in accordance with Data Protection Laws.

    +
    2. +
  2. +

    The Privacy Manager must assess the safeguards available and propose to the +PlayForm’s management the appropriate safeguard for each international +transfer. The following regimes apply to the transfers of Personal Data +outside of the EU:

    +
      +
    • +

      where the European Commission decides that the country has an adequate +level of personal data protection, the transfer does not require taking +additional safeguards. The full list of adequate jurisdictions can be +found on the relevant page of the European Commission’s website1.

      +
      • +
    • +

      to transfer Personal Data to our contractors or partners (Data Processors +or Controllers) in other third countries, we must conclude Standard +Contractual Clauses with that party. The draft version along with the +guidance can be found on the relevant page of the European Commission’s +website2;

      +
      • +
    • +

      if we have a corporate affiliate or an entity in other countries, we may +choose to adopt Binding Corporate Rules in accordance with Article 47 of +the GDPR or an approved code of conduct pursuant to Article 40 of the +GDPR;

      +
      • +
    • +

      we also can transfer Personal Data to entities that have an approved +certification in accordance with Article 42 of the GDPR, which certifies +an appropriate level of company’s data protection.

      +
      • +
    +
    3. +
+
    +
  1. +

    As a part of the information obligations, PlayForm must inform the Data +Subjects that their Personal Data is being transferred to other countries, +as well as provide them with the information about the safeguards used for +the transfer. The information obligation is to be performed in accordance +with Subsection 6.2.

    +
    2. +
  2. +

    In the exceptional cases (the “Derogation”), where we cannot apply the +safeguards mentioned afore and we need to transfer Personal Data, we must +take an explicit consent (active statement) from the Data Subject or it must +be strictly necessary for the performance of the contract between us and the +Data Subject, or other derogation conditions apply in accordance with the +Data Protection Laws. The Privacy Manager must pre-approve any Derogation +transfers and document the approved Derogations, as well as the rationale +for them.

    +
    3. +
+

Rights of Data Subjects

+
    +
  1. +

    Our Responsibilities.

    +
      +
    1. +

      Privacy Manager is ultimately responsible for handing all DSR received +by PlayForm. In the case of receiving any outstanding or unusual DSR, +the employee must seek advice from the Privacy Manager before taking any +action.

      +
      2. +
    2. +

      DSR Team within PlayForm is responsible for handling DSRs from PlayForm +Users on a daily basis. The Human Resources department is responsible +for handling the DSR from PlayForm employees.

      +
      3. +
    3. +

      All DSRs from the Users must be addressed at and answered from the +following e-mail address: DSR@PlayForm.LTD. DSR from the employees can +be addressed directly to the HR manager or at DSR@PlayForm.LTD.

      +
      4. +
    4. +

      The responsible employee must answer to the DSR within one (1) month +from receiving the request. If complying with the DSR takes more than +one month in time, the responsible employee must seek advice from the +Privacy Manager and, where necessary, inform the Data Subject about the +prolongation of the response term for up to two (2) additional months.

      +
      5. +
    5. +

      The responsible employee must analyze the received DSR for the following +criteria:

      +
        +
      • +

        Data Subject identification. Before considering the DSR content, +the responsible employee must make sure the Data Subject is the same +person he/she claims to be. For this purpose, the connection between +the personal data records and the data subject must be established.

        +
        • +
      • +

        Personal data. The responsible employee must check whether +PlayForm has access to the personal data requested. If PlayForm does +not have the personal data under the control, the responsible employee +must inform the Data Subject, and, if possible, instruct on the +further steps on how to access the data in question;

        +
        • +
      • +

        Content of the request. Depending on the content of the DSR, the +responsible employee must define the type of the request and check +whether it meets the conditions prescribed by this Policy and Data +Protection Laws. The types of requests and the respective conditions +for each of them can be consulted in Subsections 6.3-6.9. If the +request does not meet the described criteria, the responsible employee +must refuse to comply with the DSR and inform the Data Subject about +the reasons for refusing;

        +
        • +
      • +

        Free of charge. Generally, all requests of Data Subjects and +exercises of their rights are free of charge. If the responsible +employee finds that the Data Subject exercises the rights in an +excessive or unfound way (e.g., intended to harm or interrupt +PlayForm’s business activities), the employee must seek the advice +from the Privacy Manager, and, upon receiving of the latter, may +either charge the Data Subject a reasonable fee or refuse to comply +with the request;

        +
        • +
      • +

        Documenting. Whenever PlayForm receives the DSR, the Privacy +Manager must make sure that the data and time, Data Subject, type of +the request and the decision made regarding it are well documented. In +the case of refusing to comply with the request, the reasons for +refusing must be documented as well;

        +
        • +
      • +

        Recipients. When addressing the DSR, the Privacy Manager must make +sure that all concerned recipients were informed the necessary actions +were taken.

        +
        • +
      +
      6. +
    +
    2. +
  2. +

    The right to be informed.

    +
      +
    1. +

      PlayForm must notify each Data Subject about the collection and further +processing of the Personal Data.

      +
      2. +
    2. +

      The information to be provided includes: the name and contact details of +PlayForm; generic purposes of and the lawful basis for the data +collection and further processing; categories of Personal Data +collected; recipients/categories of recipients; retention periods; +information about data subject rights, including the right to complain +to the competent Supervisory Authority; the consequences of the cases +where the data is necessary for the contract performance and the Data +Subject does not provide the required data; details of the safeguards +where personal data is transferred outside the EEA; and any third-party +source of the personal data, without specification for the particular +case (except if we receive the direct request from the Data Subject).

      +
      3. +
    3. +

      The Users must be informed by the Privacy Policy accessible at +PlayForm’s website and provided during the user registration. The +employees and contractors must be informed by a standalone employee +privacy statement, which explains the details described in p. 6.2.2 in a +case-based manner, describing the particular purposes and activities.

      +
      4. +
    4. +

      PlayForm must inform Data Subjects about data processing, including any +new processing activity introduced at PlayForm within the following +term:

      +
        +
      • +

        if personal data is collected from the data subject directly, the data +subject must be informed at the time we collect Personal Data from the +Data Subjects by showing the Data Subject our privacy statement;

        +
        • +
      • +

        if the personal data is collected from other sources: (a) within one +month from collecting it; (b) if the personal data are to be used for +communication with the data subject, at the latest at the time of the +first communication to that data subject; or (c) if a disclosure to +another recipient is envisaged, at the latest when the personal data +are first disclosed.

        +
        • +
      • +

        upon the request of the Data Subject; and

        +
        • +
      • +

        within one (1) month after any change of our personal data practices, +change of the controller of Personal Data or after significant changes +in our privacy statements.

        +
        • +
      +
      5. +
    +
    3. +
  3. +

    The right to access the information.

    +
      +
    1. +

      The Data Subject must be provided only with those personal data records +specified in the request. If the Data Subject requests access to all +personal data concerning her or him, the employee must seek advice from +the Privacy Manager first, to make sure all personal data of the Data +Subject is mapped and provided.

      +
      2. +
    2. +

      A Data Subject has the right to:

      +
        +
      • +

        learn if we process the Data Subject’s Personal Data;

        +
        • +
      • +

        obtain disclosure regarding aspects of the processing, including +detailed and case-specific information on purposes, categories of +Personal Data, recipients/categories of recipients, retention periods, +information about one’s rights, details of the relevant safeguards +where personal data is transferred outside the EEA, and any +third-party source of the personal data; and

        +
        • +
      • +

        obtain a copy of the Personal Data undergoing processing upon the +request.

        +
        • +
      +
      3. +
    +
    4. +
  4. +

    The right to verify the Data Subject’s information +and seek its rectification. The information we collect can +be/become inaccurate or out-of-date (e.g., mistakes in nationality, date of +birth, info on debts, economic activities). If we reveal that the Personal +Data is inaccurate or the Data Subject requests us to do so, we must ensure +that we correct all mistakes and update the relevant information.

    +
    5. +
  5. +

    The right to restrict processing.

    +
      +
    1. +

      The restriction of processing allows Data Subjects to temporarily stop +the use of their information to prevent the possible harm caused by such +use.

      +
      2. +
    2. +

      This right applies when the Data Subject:

      +
        +
      • +

        contests the accuracy of the Personal Data;

        +
        • +
      • +

        believes that we process the Personal Data unlawfully; and

        +
        • +
      • +

        objects against the processing and wants us not to process Personal +Data while we are considering the request.

        +
        • +
      +
      3. +
    3. +

      In the case of receiving the restriction request, we must not process +Personal Data in question for any other purpose than storing it or for +legal compliance purposes until the circumstances of restriction cease +to exist.

      +
      4. +
    +
    6. +
  6. +

    The right to withdraw the consent. For +the activities that require consent, the Data Subject can revoke their +consent at any time. If the Data Subject revokes the consent, we must record +the changes and must not process the Personal Data for consent-based +purposes. The withdrawal of consent does not affect the lawfulness of the +processing done before the withdrawal.

    +
    7. +
  7. +

    The right to object against the +processing.

    +
      +
    1. +

      If we process the information in our legitimate interests, e.g., for +direct marketing emails or for our marketing research purposes, the Data +Subject can object against the processing.

      +
      2. +
    2. +

      In the case of receiving the objection request case, we must consider +Data Subject’s request and, where we do not have compelling interests, +stop the processing for the specified purposes. If the personal data is +still to be processed for other purposes, the Privacy Manager must make +sure that the database has a record that the data cannot be further +processed for the objected activities.

      +
      3. +
    3. +

      The objection request can be refused only if the personal data in +question is used for scientific/historical research or statistical +purposes and was appropriately protected, i.e., by anonymization or +pseudonymization techniques.

      +
      4. +
    +
    8. +
  8. +

    Right to erasure/to be forgotten.

    +
      +
    1. +

      The Data Subjects have the right to request us to erase their Personal +Data if one of the following conditions are met:

      +
        +
      • +

        Personal Data is no longer necessary for the purposes of collection. +For example, a user has provided personal data for a one-time +activity, such as data validation or participation in a contest, and +the purpose is already fulfilled;

        +
        • +
      • +

        the Data Subject revokes one’s consent or objects to the processing +(where applicable) and there is no other legal ground for the +processing; or

        +
        • +
      • +

        we process the Personal Data unlawfully or its erasure is required by +the applicable legislation of the European Union or one of the Member +countries of the European Union.

        +
        • +
      +
      2. +
    2. +

      Conditions, under which we have the right to refuse the erasure:

      +
        +
      • +

        Personal Data is processed for scientific/historical research or +statistical purposes and is appropriately protected, i.e., +pseudonymized or anonymized;

        +
        • +
      • +

        Personal Data is still necessary for legal compliance (e.g., financial +or labor laws compliance).

        +
        • +
      +
      3. +
    3. +

      Only those personal data records must be deleted that were specified in +the request. If the Data Subject requests the deletion of all personal +data concerning her or him, the employee must seek advice from the +Privacy Manager first, to make sure all the data about the Data Subject +is mapped and can be deleted.

      +
      4. +
    4. +

      If the User still has an account with us and requests the erasure of +information necessary for maintaining the account, we must inform the +User that the erasure will affect user experience or can lead to the +closure of the account.

      +
      5. +
    +
    9. +
  9. +

    Data portability.

    +
      +
    1. +

      Data Subjects can ask us to transfer all the Personal Data and/or its +part in a machine-readable format to a third party. This right applies +in two cases:

      +
        +
      • +

        personal data was collected for the purpose of provision of our +services (performance of the contract); or

        +
        • +
      • +

        collected based on consent.

        +
        • +
      +
      2. +
    2. +

      To determine whether one of the p.6.9.1 conditions are met, the employee +must seek advice from the Privacy Manager and check the applicable legal +basis in the Records of processing activities. If the answer is +negative, the request can be refused by PlayForm, and the Privacy +Manager must decide whether to comply with the request on a voluntary +basis.

      +
      3. +
    3. +

      To comply with the request, the responsible employee must consolidate +requested Personal Data and send the data in the format we are usually +working with to the requested organization. The Data Subject must +provide the necessary contact details of the organization.

      +
      4. +
    +
    10. +
+

New Data Processing Activities

+
    +
  1. +

    Notification to Privacy Manager.

    +
      +
    1. +

      Before introducing any new activity that involves the processing of +personal data, an employee responsible for its implementation must +inform the Privacy Manager.

      +
      2. +
    2. +

      Upon receiving information about a new activity, Privacy Manager must:

      +
        +
      • +

        determine whether the data processing impact assessment (DPIA) and/or +the consultation with the Supervisory Authority is necessary. If the +answer is positive, the Privacy Manager must make sure the DPIA is +conducted and/or the Supervisory Authority is consulted in accordance +with the requirements of this Section and Data Protection Laws;

        +
        • +
      • +

        determine the legal basis for the processing and, where necessary, +take further action for its fixation;

        +
        • +
      • +

        make sure the processing activity is done in accordance with this +Policy, other PlayForm’s policies, as well as the Data Protection +Laws;

        +
        • +
      • +

        add the processing activity to the Records of processing activities;

        +
        • +
      • +

        amend the privacy information statements and, where necessary, inform +the concerned Data Subject accordingly.

        +
        • +
      +
      3. +
    +
    2. +
  2. +

    Data Processing Impact Assessment.

    +
      +
    1. +

      To make sure that our current or prospective processing activities do +not/will not violate the Data Subjects’ rights, PlayForm must, where +required by Data Protection Laws, conduct the Data Processing Impact +Assessment (DPIA), a risk-based assessment of the processing and search +for the measures to mitigate the risks. The Privacy Manager must make +sure the DPIA is conducted in accordance with this Section.

      +
      2. +
    2. +

      The Privacy Manager, where necessary, involving the competent employees +and/or external advisors, must conduct a DPIA if at least one of the +following conditions are met:

      +
        +
      • +

        the processing involves the use of new technologies, such as the +Artificial Intelligence, use of connected and autonomous devices, etc. +that creates certain legal, economic or similar effects to the Data +Subject;

        +
        • +
      • +

        we systematically assess and evaluate personal aspects of the Data +Subjects based on automated profiling, assigning the personal +score/rate, and create legal or similar effects for the Data Subject +by this activity;

        +
        • +
      • +

        we process on a large-scale sensitive data, which includes Personal +Data relating to criminal convictions and offences, the data about +vulnerable data subjects, the 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;

        +
        • +
      • +

        we collect or process Personal Data from a publicly accessible area or +public sources on a large scale, or combine or match two different +data sets; and

        +
        • +
      • +

        the Supervisory Authority in its public list requires conducting a +DPIA for a certain type of activity we are involved in. The list of +processing activities requiring conducting DPIA can be found on the +website of each Supervisory Authority.

        +
        • +
      +
      3. +
    3. +

      The assessment shall contain at least the following details:

      +
        +
      • +

        a systematic description of the processing operations and the purposes +of the processing, including, where applicable, the legitimate +interest pursued by us. The description must include the envisaged +data categories and data subjects concerned, the scale of processing +activities, such as its frequency, volume, envisaged number of +records, etc.; recipients of the data, retention periods and, where +applicable, international transfers;

        +
        • +
      • +

        an assessment of the necessity and proportionality of the processing +operations in relation to the purposes. The DPIA must explain whether +the activity is necessary for the purpose and whether the purpose can +be achieved by less intrusive methods;

        +
        • +
      • +

        an assessment of the risks to the rights and freedoms of data +subjects, including the rights of Data Subjects regarding their +Personal Data.

        +
        • +
      • +

        The examples of risks are the processing which could lead to physical, +material or non-material damage, in particular: where the processing +may give rise to discrimination, identity theft or fraud, financial +loss, damage to the reputation, loss of confidentiality of personal +data protected by professional secrecy, unauthorized reversal of +pseudonymization, or any other significant economic or social +disadvantage; where data subjects might be deprived of their rights +and freedoms or prevented from exercising control over their personal +data; where personal data are processed which reveal racial or ethnic +origin, political opinions, religion or philosophical beliefs, trade +union membership, and the processing of genetic data, data concerning +health or data concerning sex life or criminal convictions and +offences or related security measures; where personal aspects are +evaluated, in particular analyzing or predicting aspects concerning +performance at work, economic situation, health, personal preferences +or interests, reliability or behavior, location or movements, in order +to create or use personal profiles; where personal data of vulnerable +natural persons, in particular of children, are processed; or where +processing involves a large amount of personal data and affects a +large number of data subjects; and

        +
        • +
      • +

        the measures to address the risks, including safeguards, security +measures, and mechanisms to ensure the protection of personal data and +to demonstrate compliance with this Regulation.

        +
        • +
      +
      4. +
    4. +

      Where the DPIA did not provide how to effectively address the risks, the +Privacy Manager must initiate the consultation with the competent +Supervisory Authority to receive help with searching for the solution. +In this case, PlayForm must not conduct the activity before the +Supervisory Authority approves the processing activity in question.

      +
      5. +
    +
    3. +
+

Data Retention

+
    +
  1. +

    General Rule.

    +
      +
    1. +

      The Privacy Manager must make sure that PlayForm clearly defined the +data storage periods and/or criteria for determining the storage periods +for each processing activity it has. The periods for each processing +activity must be specified in the Records of processing activities.

      +
      2. +
    2. +

      Each department within PlayForm must comply with the data storage +periods in accordance with the retention schedule provided in Records of +processing activities. The Privacy Manager must supervise each +department and make sure they comply with this requirement.

      +
      3. +
    3. +

      After the storage period ends, the personal data must be removed from +the disposal of the department responsible for the processing or, in +cases where the data is not needed for any other purposes, destroyed +completely, including from back-up copies and other media.

      +
      4. +
    4. +

      Whenever the storage period for a processing activity has ended, but the +personal data processed is necessary for other processing purposes, the +department manager must make sure that the personal data is not used for +the ceased processing activity, and the responsible employees do not +have the access to it unless required for any other activity.

      +
      5. +
    +
    2. +
  2. +

    Exemptions. The rules specified in +Subsection 8.1 have the following exceptions:

    +
      +
    1. +

      Business needs. Data retention periods can be prolonged, but no +longer than 60 days, in the case that the data deletion will interrupt +or harm our ongoing business. The Privacy Manager must approve any +unforeseen prolongation;

      +
      2. +
    2. +

      Technical impossibility. Some information is technically impossible +or disproportionally difficult to delete. For example, deletion of the +information may lead to breach of system integrity, or it is impossible +to delete the information from the backup copies. In such a case, the +information can be further stored, subject to the approval by the +Privacy Manager and making respective amendments to the Records of +processing activities; and

      +
      3. +
    3. +

      Anonymization. The Personal Data can be further processed for any +purposes (e.g., marketing) if we fully anonymize these data after the +retention period is expired. This means that all personal identifiers +and connections to them will be deleted from the data. To consider +Personal Data anonymous, it must be impossible to reidentify the Data +Subject from the data set.

      +
      4. +
    +
    3. +
+

Security

+
    +
  1. +

    Each department within PlayForm shall take all appropriate technical and +organizational measures that protect against unauthorized, unlawful, and/or +accidental access, destruction, modification, blocking, copying, +distribution, as well as from other illegal actions of unauthorized persons +regarding the personal data under their responsibility.

    +
    2. +
  2. +

    The employee responsible for the supervision after the security of personal +data within PlayForm shall be DSR Officer. This person implements the +guidelines and other specifications on data protection and information +security in his area of responsibility. He/she advises PlayForm management +on the planning and implementation of information security in PlayForm, and +must be involved in all projects at an early stage in order to take +security-related aspects into account as early as the planning phase.

    +
    3. +
+

Data Breach Response Procedure

+
    +
  1. +

    Response Team.

    +
      +
    1. +

      In case of revealing the Data Breach, CEO of PlayForm shall urgently +form the Data Breach Response Team (the “Response Team”), which will +handle the Data Breach, notify the appropriate persons, and mitigate its +risks.

      +
      2. +
    2. +

      The Response Team must be а multi-disciplinary group headed by CEO of +PlayForm and comprised of the Privacy Manager, privacy laws specialist +(whether internal or external), and knowledgeable and skilled +information security specialists within PlayForm or outsourcing +professionals, if necessary. The team must ensure that all employees and +engaged contractors/processors adhere to this Policy and provide an +immediate, effective, and skillful response to any suspected/alleged or +actual Data Breach affecting PlayForm.

      +
      3. +
    3. +

      The potential members of the Response Team must be prepared to respond +to а Data Breach. The Response Team shall perform all the +responsibilities of PlayForm mentioned in this Policy. The duties of the +Response Team are:

      +
        +
      • +

        to communicate the Data Breach to the competent Supervisory +Authority(-ies);

        +
        • +
      • +

        in case of high risk to the rights and freedoms of Data Subjects, to +communicate the Data Breach to the Data Subject;

        +
        • +
      • +

        if PlayForm obtain data from any third party as a processor, and a +Data Breach involves obtained data, to inform the third parties about +the Data Breach;

        +
        • +
      • +

        to communicate PlayForm’s contractors or any other third parties that +process the Personal Data involved in the Data Breach; and

        +
        • +
      • +

        to take all appropriate technical and organizational measures to cease +the Data Breach and mitigate its consequences;

        +
        • +
      • +

        to record the fact of the Data Breach in the Records of processing +activities and file an internal data breach report that describes the +event.

        +
        • +
      +
      4. +
    4. +

      The Response Team shall perform its duties until all the necessary +measures required by this Policy are taken.

      +
      5. +
    +
    2. +
  2. +

    Notification to Supervisory Authority.

    +
      +
    1. +

      PlayForm shall inform the Competent Supervisory Authority about the Data +Breach without undue delay and, where it is possible, not later than 72 +hours after having become aware of the Data Breach.

      +
      2. +
    2. +

      The Competent Supervisory Authority shall be determined by the residence +of the Data Subjects, whose information was involved in the Data Breach. +If the Data Breach concerns the Personal Data of Data Subjects from more +than one country, PlayForm shall inform all Competent Supervisory +Authorities.

      +
      3. +
    3. +

      To address the notification to the authority, the Response Team should +use Annex 1 to this Policy. Annex 1 contains all the necessary contact +information of the EU supervisory authorities. If the Data Breach +concerns Data Subjects from other than the EU countries, the Response +Team shall ask a competent privacy specialist for advice.

      +
      4. +
    4. +

      The notification to the Competent Supervisory Authority shall contain, +at least, following information:

      +
        +
      • +

        the nature of the Data Breach including where possible, the +categories and an approximate number of Data Subjects and Personal +Data records concerned;

        +
        • +
      • +

        the name and contact details of the Response Team, Privacy Manager +or, if not applicable, of the CEO;

        +
        • +
      • +

        the likely consequences of the Data Breach. Explain PlayForm’s point +of view on the purposes and possible further risks of the Data Breach. +E.g., the Personal Data may be stolen for the further sale, fraud +activities or blackmailing the concerned Data Subjects; and

        +
        • +
      • +

        the measures taken or proposed to be taken by PlayForm to address +the Data Breach, including, where appropriate, measures to mitigate +its possible adverse effects.

        +
        • +
      +
      5. +
    5. +

      To file a notification, the Response Team should use PlayForm’s Data +Breach Notification Form to the Supervisory Authority.

      +
      6. +
    +
    3. +
  3. +

    Notifications to Data Subjects.

    +
      +
    1. +

      When the Data Breach is likely to result in a high risk to the rights +and freedoms of Data Subjects (e.g., stealing of funds, assets, +proprietary information), we must also communicate the Data Breach to +the concerned Data Subjects without undue delay. The Privacy Manager +must determine if there is a high risk based on the risk factors +specified in Subsection 7.2.3 of this Policy.

      +
      2. +
    2. +

      The notification shall contain the following information:

      +
        +
      • +

        description of the Data Breach - what happened and what led to the +Data Breach, such as a security breach, employee’s negligence, error +in the system work. If the Response Team decided not to disclose the +causes of the Data Breach, then this clause must not be mentioned;

        +
        • +
      • +

        the measures taken by PlayForm regarding the Data Breach, including +security measures, internal investigations, and supervisory +authority notice;

        +
        • +
      • +

        recommendations for the concerned Data Subjects how to mitigate risks +and possible consequences, such as guidelines on how to restore +access to an account, preventing measures (change of a password); +and

        +
        • +
      • +

        the contact information of the Response Team or one of its members.

        +
        • +
      +
      3. +
    3. +

      The notification to the Data Subjects should be carried out by the +email letter or, where it is impossible to use the email, by other +available means of communication.

      +
      4. +
    4. +

      Exemptions. We do not have to send the notification to the Data +Subjects if any of the following conditions are met:

      +
        +
      • +

        PlayForm has implemented appropriate technical and organizational +protection measures, and those measures were applied to the Personal +Data affected by the Data Breach, in particular, those that leave the +Personal Data inaccessible to any person who is not authorized to +access it, such as encryption;

        +
        • +
      • +

        PlayForm has taken subsequent measures which ensure that the high risk +to the rights and freedoms of Data Subjects referred to in this +section is no longer likely to materialize; or

        +
        • +
      • +

        it would involve a disproportionate effort to communicate with every +concerned Data Subject. In such a case, there shall instead be a +public communication or similar measure whereby the Data Subjects are +informed in an equally effective manner.

        +
        • +
      +
      5. +
    +
    4. +
+

In the case we apply one of the exemptions, we must document the +circumstances, reason for not informing, and actions taken to meet one of the +exemptions.

+
    +
  1. +

    Communication with Third Parties.

    +
      +
    1. +

      In the case a Data Breach concerns the Personal Data shared with us or +processed by us on behalf of a Third Party, we must also notify the +Third Party about it within 24 hours. If we process the Personal Data as +a Data Processor, the notification of the Third Party does not exempt us +from the duty to mitigate the Data Breach consequences, but we must not +inform the Competent Supervisory Authority and Data Subjects.

      +
      2. +
    2. +

      In case of receiving the notification about the Data Breach from the +Data Processor or other Third Parties that have access to the Personal +Data, CEO of PlayForm shall, in accordance with this Section:

      +
        +
      • +

        form the Response Team;

        +
        • +
      • +

        request the Third Party to send the information mentioned in +Subsections 10.2-3 of this Policy;

        +
        • +
      • +

        where necessary, inform the Competent Supervisory Authority(-ies) and +Data Subjects; and

        +
        • +
      • +

        perform other steps of the Data Breach response procedure.

        +
        • +
      +
      3. +
    +
    2. +
+

List of Persons Briefed on Personal Data Protection Policy

+ +++++ + + + + + + + + + + + + +

Full Name

Status

Date

Nikola Hristov Briefed05.25.2018
+

ANNEX 1 TO THE PERSONAL DATA PROTECTION POLICY

+

European National Data Protection Authorities

+

Austria

+

Österreichische Datenschutzbehörde
+Hohenstaufengasse 3
+1010 Wien
+Tel. +43 1 531 15 202525
+Fax +43 1 531 15 202690
+E-mail: dsb@dsb.gv.at
+WebSite: HTTPS://www.dsb.gv.at

+

Art 29 WP Member: Dr Andrea JELINEK, Director, Österreichische +Datenschutzbehörde

+

Belgium

+

Commission de la protection de la vie privée
+Commissie voor de bescherming van de persoonlijke levenssfeer
+Rue de la Presse 35 / Drukpersstraat 35 1000 Bruxelles / 1000 Brussel
+Tel. +32 2 274 48 00
+Fax +32 2 274 48 35
+E-mail: commission@privacycommission.be
+WebSite: HTTPS://www.privacycommission.be

+

Art 29 WP Vice-President: Willem DEBEUCKELAERE, President of the Belgian Privacy +commission

+

Bulgaria

+

Commission for Personal Data Protection
+2, Prof. Tsvetan Lazarov Blvd. Sofia 1592
+Tel. +359 2 915 3580
+Fax +359 2 915 3525
+E-mail: kzld@cpdp.bg
+WebSite: HTTPS://www.cpdp.bg

+

Art 29 WP Member: Mr. Ventsislav KARADJOV, Chairman of the Commission for +Personal Data Protection
+Art 29 WP Alternate Member: Ms. Mariya MATEVA

+

Croatia

+

Croatian Personal Data Protection Agency
+Martićeva 14
+10000 Zagreb
+Tel. +385 1 4609 000
+Fax +385 1 4609 099
+E-mail: azop@azop.hr or info@azop.hr
+WebSite: HTTPS://www.azop.hr

+

Art 29 WP Member: Mr. Anto RAJKOVAČA, Director of the Croatian Data Protection +Agency

+

Cyprus

+

Commissioner for Personal Data Protection
+1 Iasonos Street,
+1082 Nicosia
+P.O. Box 23378, CY-1682 Nicosia Tel. +357 22 818 456
+Fax +357 22 304 565
+E-mail: commissioner@dataprotection.gov.cy
+WebSite: HTTPS://www.dataprotection.gov.cy

+

Art 29 WP Member: Ms. Irene LOIZIDOU NIKOLAIDOU
+Art 29 WP Alternate Member: Mr. Constantinos GEORGIADES

+

Czech Republic

+

The Office for Personal Data Protection
+Urad pro ochranu osobnich udaju Pplk. Sochora 27
+170 00 Prague 7
+Tel. +420 234 665 111
+Fax +420 234 665 444
+E-mail: posta@uoou.cz
+WebSite: HTTPS://www.uoou.cz

+

Art 29 WP Member: Ms. Ivana JANŮ, President of the Office for Personal Data +Protection
+Art 29 WP Alternate Member: Mr. Ivan PROCHÁZKA, Adviser to the President of the +Office

+

Denmark

+

Datatilsynet
+Borgergade 28, 5
+1300 Copenhagen K
+Tel. +45 33 1932 00
+Fax +45 33 19 32 18
+E-mail: dt@datatilsynet.dk
+WebSite: HTTPS://www.datatilsynet.dk

+

Art 29 WP Member: Ms. Cristina Angela GULISANO, Director, Danish Data Protection +Agency (Datatilsynet)
+Art 29 WP Alternate Member: Mr. Peter FOGH KNUDSEN, Head of International +Division at the Danish Data Protection Agency (Datatilsynet)

+

Estonia

+

Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon)
+Väike-Ameerika 19
+10129 Tallinn
+Tel. +372 6274 135
+Fax +372 6274 137
+E-mail: info@aki.ee
+WebSite: HTTPS://www.aki.ee/en

+

Art 29 WP Member: Mr. Viljar PEEP, Director General, Estonian Data Protection +Inspectorate
+Art 29 WP Alternate Member: Ms. Maarja Kirss

+

Finland

+

Office of the Data Protection Ombudsman
+P.O. Box 315
+FIN-00181 Helsinki Tel. +358 10 3666 700
+Fax +358 10 3666 735
+E-mail: tietosuoja@om.fi
+WebSite: HTTPS://www.tietosuoja.fi/en

+

Art 29 WP Member: Mr. Reijo AARNIO, Ombudsman of the Finnish Data Protection +Authority
+Art 29 WP Alternate Member: Ms. Elisa KUMPULA, Head of Department

+

France

+

Commission Nationale de l’Informatique et des Libertés - CNIL
+8 rue Vivienne, CS 30223 F-75002 Paris, Cedex 02
+Tel. +33 1 53 73 22 22
+Fax +33 1 53 73 22 00
+WebSite: HTTPS://www.cnil.fr

+

Art 29 WP Member: Ms. Isabelle FALQUE-PIERROTIN, President of CNIL
+Art 29 WP Alternate Member: Ms. Florence RAYNAL

+

Germany

+

Die Bundesbeauftragte für den Datenschutz und die Informationsfreiheit
+Husarenstraße 30
+53117 Bonn
+Tel. +49 228 997799 0; +49 228 81995 0
+Fax +49 228 997799 550; +49 228 81995 550
+E-mail: poststelle@bfdi.bund.de
+WebSite: HTTPS://www.bfdi.bund.de

+

The competence for complaints is split among different data protection +supervisory authorities in Germany.

+

Competent authorities can be identified according to the list provided under

+

HTTPS://www.bfdi.bund.de/EN/Service/Anschriften/Laender/Laender-node.html

+

Art 29 WP Member: Ms. Andrea VOSSHOFF, Federal Commissioner for Freedom of +Information
+Art 29 WP Alternate Member: Prof. Dr. Johannes CASPAR, representative of the +federal states

+

Greece

+

Hellenic Data Protection Authority
+Kifisias Av. 1-3, PC 11523 Ampelokipi Athens
+Tel. +30 210 6475 600
+Fax +30 210 6475 628
+E-mail: contact@dpa.gr
+WebSite: HTTPS://www.dpa.gr

+

Art 29 WP Member: Mr. Konstantinos Menoudakos, President of the Hellenic DPA
+Art 29 WP Alternate Member: Dr. Vasilios ZORKADIS, Director

+

Hungary

+

National Authority for Data Protection and Freedom of Information
+Szilágyi Erzsébet fasor 22/C H-1125 Budapest
+Tel. +36 1 3911 400
+E-mail: peterfalvi.attila@naih.hu
+WebSite: HTTPS://www.naih.hu

+

Art 29 WP Member: Dr Attila PÉTERFALVI, President of the National Authority for +Data Protection and Freedom of Information
+Art 29 WP Alternate Member: Mr. Endre Győző SZABÓ Vice-president of the National +Authority for Data Protection and Freedom of Information

+

Ireland

+

Data Protection Commissioner
+Canal House Station Road Portarlington Co. Laois
+Lo-Call: 1890 25 22 31
+Tel. +353 57 868 4800
+Fax +353 57 868 4757
+E-mail: info@dataprotection.ie
+WebSite: HTTPS://www.dataprotection.ie

+

Art 29 WP Member: Ms. Helen DIXON, Data Protection Commissioner
+Art 29 WP Alternate Members: Mr. John O’DWYER, Deputy Commissioner; Mr. Dale +SUNDERLAND, Deputy Commissioner

+

Italy

+

Garante per la protezione dei dati personali
+Piazza di Monte Citorio, 121 00186 Roma
+Tel. +39 06 69677 1
+Fax +39 06 69677 785
+E-mail: garante@garanteprivacy.it
+WebSite: HTTPS://www.garanteprivacy.it

+

Art 29 WP Member: Mr. Antonello SORO, President of Garante per la protezione dei +dati personali
+Art 29 WP Alternate Member: Ms. Giuseppe BUSIA, Secretary General of Garante per +la protezione dei dati personali

+

Latvia

+

Data State Inspectorate Director: Ms. Daiga Avdejanova
+Blaumana str. 11/13-15
+1011 Riga
+Tel. +371 6722 3131
+Fax +371 6722 3556
+E-mail: info@dvi.gov.lv
+WebSite: HTTPS://www.dvi.gov.lv

+

Art 29 WP Alternate Member: Ms. Aiga BALODE

+

Lithuania

+

State Data Protection
+Žygimantų str. 11-6a 011042 Vilnius
+Tel. + 370 5 279 14 45
+Fax +370 5 261 94 94
+E-mail: ada@ada.lt
+WebSite: HTTPS://www.ada.lt

+

Art 29 WP Member: Mr. Raimondas Andrijauskas, Director of the State Data +Protection Inspectorate
+Art 29 WP Alternate Member: Ms. Neringa KAKTAVIČIŪTĖ-MICKIENĖ, Head of +Complaints Investigation and International Cooperation Division

+

Luxembourg

+

Commission Nationale pour la Protection des Données
+1, avenue du Rock’n’roll L-4361 Esch-sur-Alzette Tel. +352 2610 60 1
+Fax +352 2610 60 29
+E-mail: info@cnpd.lu
+WebSite: HTTPS://www.cnpd.lu

+

Art 29 WP Member: Ms. Tine A. LARSEN, President of the Commission Nationale pour +la Protection des Données
+Art 29 WP Alternate Member: Mr. Thierry LALLEMANG, Commissioner

+

Malta

+

Office of the Data Protection Commissioner
+Data Protection Commissioner: Mr. Joseph Ebejer
+2, Airways House
+High Street, Sliema SLM 1549 Tel. +356 2328 7100
+Fax +356 2328 7198
+E-mail: commissioner.dataprotection@gov.mt
+WebSite: HTTPS://idpc.org.mt

+

Art 29 WP Member: Mr. Saviour CACHIA, Information and Data Protection +Commissioner
+Art 29 WP Alternate Member: Mr. Ian DEGUARA, Director - Operations and Programme +Implementation

+

Netherlands

+

Autoriteit Persoonsgegevens
+Prins Clauslaan 60
+P.O. Box 93374
+2509 AJ Den Haag/The Hague Tel. +31 70 888 8500
+Fax +31 70 888 8501
+E-mail: info@autoriteitpersoonsgegevens.nl
+WebSite: HTTPS://autoriteitpersoonsgegevens.nl/nl

+

Art 29 WP Member: Mr. Aleid WOLFSEN, Chairman of Autoriteit Persoonsgegevens

+

Poland

+

The Bureau of the Inspector General for the Protection of Personal Data – GIODO
+ul. Stawki 2
+00-193 Warsaw
+Tel. +48 22 53 10 440
+Fax +48 22 53 10 441
+E-mail: kancelaria@giodo.gov.pl; desiwm@giodo.gov.pl
+WebSite: HTTPS://www.giodo.gov.pl

+

Art 29 WP Member: Ms. Edyta BIELAK-JOMAA, Inspector General for the Protection +of Personal Data

+

Portugal

+

Comissão Nacional de Protecção de Dados - CNPD
+R. de São. Bento, 148-3° 1200-821 Lisboa
+Tel. +351 21 392 84 00
+Fax +351 21 397 68 32
+E-mail: geral@cnpd.pt
+WebSite: HTTPS://www.cnpd.pt

+

Art 29 WP Member: Ms. Filipa CALVÃO, President, Comissão Nacional de Protecção +de Dados
+Art 29 WP Alternate Member: Isabel CRUZ, Secretary-General of the DPA

+

Romania

+

The National Supervisory Authority for Personal Data Processing President: Mrs. +Ancuţa Gianina Opre
+B-dul Magheru 28-30
+Sector 1, BUCUREŞTI
+Tel. +40 21 252 5599
+Fax +40 21 252 5757
+E-mail: anspdcp@dataprotection.ro
+WebSite: HTTPS://www.dataprotection.ro

+

Art 29 WP Member: Ms. Ancuţa Gianina OPRE, President of the National Supervisory +Authority for Personal Data Processing
+Art 29 WP Alternate Member: Ms. Alina SAVOIU, Head of the Legal and +Communication Department

+

Slovakia

+

Office for Personal Data Protection of the Slovak Republic
+Hraničná 12
+820 07 Bratislava 27
+Tel.: + 421 2 32 31 32 14
+Fax: + 421 2 32 31 32 34
+E-mail: statny.dozor@pdp.gov.sk
+WebSite: HTTPS://dataprotection.gov.sk

+

Art 29 WP Member: Ms. Soňa PŐTHEOVÁ, President of the Office for Personal Data +Protection of the Slovak Republic
+Art 29 WP Alternate Member: Mr. Anna VITTEKOVA, Vice President

+

Slovenia

+

Information Commissioner
+Ms. Mojca Prelesnik Zaloška 59
+1000 Ljubljana
+Tel. +386 1 230 9730
+Fax +386 1 230 9778
+E-mail: gp.ip@ip-rs.si
+WebSite: HTTPS://www.ip-rs.si

+

Art 29 WP Member: Ms. Mojca PRELESNIK, Information Commissioner of the Republic +of Slovenia

+

Spain

+

Agencia de Protección de Datos
+C/Jorge Juan, 6
+28001 Madrid
+Tel. +34 91399 6200
+Fax +34 91455 5699
+E-mail: internacional@agpd.es
+WebSite: HTTPS://www.agpd.es

+

Art 29 WP Member: Ms. María del Mar España Martí, Director of the Spanish Data +Protection Agency
+Art 29 WP Alternate Member: Mr. Rafael GARCIA GOZALO

+

Sweden

+

Datainspektionen
+Drottninggatan 29 5th Floor
+Box 8114
+20 Stockholm
+Tel. +46 8 657 6100
+Fax +46 8 652 8652
+E-mail: datainspektionen@datainspektionen.se
+WebSite: HTTPS://www.datainspektionen.se

+

Art 29 WP Member: Ms. Kristina SVAHN STARRSJÖ, Director General of the Data +Inspection Board
+Art 29 WP Alternate Member: Mr. Hans-Olof LINDBLOM, Chief Legal Adviser

+

United Kingdom

+

The Information Commissioner’s Office
+Water Lane, Wycliffe House Wilmslow - Cheshire SK9 5AF Tel. +44 1625 545 745
+E-mail: international.team@ico.org.uk
+WebSite: HTTPS://ico.org.uk

+

Art 29 WP Member: Ms. Elizabeth DENHAM, Information Commissioner
+Art 29 WP Alternate Member: Mr. Steve WOOD, Deputy Commissioner

+

EUROPEAN FREE TRADE AREA (EFTA)

+

Iceland

+

Icelandic Data Protection Agency
+Rauðarárstíg 10
+Reykjavík
+Tel. +354 510 9600; Fax +354 510 9606
+E-mail: postur@personuvernd.is
+WebSite: HTTPS://www.personuvernd.is

+

Liechtenstein

+

Data Protection Office
+Kirchstrasse 8, P.O. Box 684
+9490 Vaduz
+Principality of Liechtenstein Tel. +423 236 6090
+E-mail: info.dss@llv.li
+WebSite: HTTPS://www.datenschutzstelle.li

+

Norway

+

Datatilsynet
+Data Protection Authority: Mr. Bjørn Erik THORN
+The Data Inspectorate
+P.O. Box 8177 Dep 0034 Oslo
+Tel. +47 22 39 69 00; Fax +47 22 42 23 50
+E-mail: postkasse@datatilsynet.no
+WebSite: HTTPS://www.datatilsynet.no

+

Switzerland

+

Data Protection and Information Commissioner of Switzerland
+Eidgenössischer Datenschutz- und Öffentlichkeitsbeauftragter Mr. Adrian +Lobsiger
+Feldeggweg 1
+3003 Bern
+Tel. +41 58 462 43 95; Fax +41 58 462 99 96
+E-mail: contact20@edoeb.admin.ch
+WebSite: HTTPS://www.edoeb.admin.ch

+

Footnotes

+
    +
  1. +

    HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en; ↩

    +
    2. +
  2. +

    HTTPS://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en; ↩

    +
    3. +
+
\ No newline at end of file diff --git a/Target/TERMS-OF-SERVICE/index.html b/Target/TERMS-OF-SERVICE/index.html index 541a0b92..a2c920b6 100644 --- a/Target/TERMS-OF-SERVICE/index.html +++ b/Target/TERMS-OF-SERVICE/index.html @@ -1 +1,382 @@ -Terms of Service

TERMS OF SERVICE

Effective date: 01.12.2016 / January 12th 2016
Last updated: 02.11.2022 / February 11th 2022

Introduction

Welcome to PlayForm ltd. (“Company”, “we”, “our”, “us”)! As you have just clicked our Terms of Service, please pause, grab a cup of coffee and carefully read the following pages. It will take you approximately 20 minutes.

These Terms of Service (“Terms”, “Terms of Service”) govern your use of our web pages located at HTTPS://PlayForm.LTD and our mobile application PlayForm (together or individually “Service”) operated by PlayForm ltd.

Our Privacy Policy also governs your use of our Service and explains how we collect, safeguard and disclose information that results from your use of our web pages. Please read it here HTTPS://PlayForm.LTD/Privacy-Policy.

Your agreement with us includes these Terms and our Privacy Policy (“Agreements”). You acknowledge that you have read and understood Agreements, and agree to be bound of them.

If you do not agree with (or cannot comply with) Agreements, then you may not use the Service, but please let us know by emailing at Support@PlayForm.LTD so we can try to find a solution. These Terms apply to all visitors, users and others who wish to access or use Service.

Thank you for being responsible.

Communications

By creating an Account on our Service, you agree to subscribe to newsletters, marketing or promotional materials and other information we may send. However, you may opt out of receiving any, or all, of these communications from us by following the unsubscribe link or by emailing at.

Purchases

If you wish to purchase any product or service made available through Service (“Purchase”), you may be asked to supply certain information relevant to your Purchase including, without limitation, your credit card number, the expiration date of your credit card, your billing address, and your shipping information.

You represent and warrant that:

a) you have the legal right to use any credit card(s) or other payment method(s) in connection with any Purchase; and that

b) the information you supply to us is true, correct and complete.

We may employ the use of third-party services for the purpose of facilitating payment and the completion of Purchases. By submitting your information, you grant us the right to provide the information to these third parties subject to our Privacy Policy.

We reserve the right to refuse or cancel your order at any time for reasons including but not limited to: product or service availability, errors in the description or price of the product or service, error in your order or other reasons.

We reserve the right to refuse or cancel your order if fraud or an unauthorized or illegal transaction is suspected.

Contests, Sweepstakes and Promotions

Any contests, sweepstakes or other promotions (collectively, “Promotions”) made available through Service may be governed by rules that are separate from these Terms of Service. If you participate in any Promotions, please review the applicable rules as well as our Privacy Policy. If the rules for a Promotion conflict with these Terms of Service, Promotion rules will apply.

Subscriptions

Some parts of Service are billed on a subscription basis (“Subscription(s)”). You will be billed in advance on a recurring and periodic basis (“Billing Cycle”). Billing cycles are set either on a monthly or annual basis, depending on the type of subscription plan you select when purchasing a Subscription.

At the end of each Billing Cycle, your Subscription will automatically renew under the exact same conditions unless you cancel it or PlayForm ltd. cancels it. You may cancel your Subscription renewal either through your online account management page or by contacting PlayForm ltd. customer support team.

A valid payment method, including credit card or PayPal, is required to process the payment for your subscription. You shall provide PlayForm ltd. with accurate and complete billing information including full name, address, state, zip code, telephone number, and a valid payment method information. By submitting such payment information, you automatically authorize PlayForm ltd. to charge all Subscription fees incurred through your account to any such payment instruments.

Should automatic billing fail to occur for any reason, PlayForm ltd. will issue an electronic invoice indicating that you must proceed manually, within a certain deadline date, with the full payment corresponding to the billing period as indicated on the invoice.

Free Trial

PlayForm ltd. may, at its sole discretion, offer a Subscription with a free trial for a limited period of time (“Free Trial”).

You may be required to enter your billing information in order to sign up for Free Trial.

If you do enter your billing information when signing up for Free Trial, you will not be charged by PlayForm ltd. until Free Trial has expired. On the last day of Free Trial period, unless you cancelled your Subscription, you will be automatically charged the applicable Subscription fees for the type of Subscription you have selected.

At any time and without notice, PlayForm ltd. reserves the right to

a) modify Terms of Service of Free Trial offer, or

b) cancel such Free Trial offer.

Fee Changes

PlayForm ltd., in its sole discretion and at any time, may modify Subscription fees for the Subscriptions. Any Subscription fee change will become effective at the end of the then-current Billing Cycle.

PlayForm ltd. will provide you with a reasonable prior notice of any change in Subscription fees to give you an opportunity to terminate your Subscription before such change becomes effective.

Your continued use of Service after Subscription fee change comes into effect constitutes your agreement to pay the modified Subscription fee amount.

Refunds

We issue refunds for Contracts within fourteen (14) days of the original purchase of the Contract.

Content

Our Service allows you to post, link, store, share and otherwise make available certain information, text, graphics, videos, or other material (“Content”). You are responsible for Content that you post on or through Service, including its legality, reliability, and appropriateness.

By posting Content on or through Service, You represent and warrant that:

a) Content is yours (you own it) and/or you have the right to use it and the right to grant us the rights and license as provided in these Terms, and

b) that the posting of your Content on or through Service does not violate the privacy rights, publicity rights, copyrights, contract rights or any other rights of any person or entity. We reserve the right to terminate the account of anyone found to be infringing on a copyright.

You retain any and all of your rights to any Content you submit, post or display on or through Service and you are responsible for protecting those rights. We take no responsibility and assume no liability for Content you or any third-party posts on or through Service. However, by posting Content using Service you grant us the right and license to use, modify, publicly perform, publicly display, reproduce, and distribute such Content on and through Service. You agree that this license includes the right for us to make your Content available to other users of Service, who may also use your Content subject to these Terms.

PlayForm ltd. has the right but not the obligation to monitor and edit all Content provided by users.

In addition, Content found on or through this Service are the property of PlayForm ltd. or used with permission. You may not distribute, modify, transmit, reuse, download, repost, copy, or use said Content, whether in whole or in part, for commercial purposes or for personal gain, without express advance written permission from us.

Prohibited Uses

You may use Service only for lawful purposes and in accordance with Terms. You agree not to use Service:

a. In any way that violates any applicable national or international law or regulation.

b. For the purpose of exploiting, harming, or attempting to exploit or harm minors in any way by exposing them to inappropriate content or otherwise.

c. To transmit, or procure the sending of, any advertising or promotional material, including any “junk mail”, “chain letter,” “spam,” or any other similar solicitation.

d. To impersonate or attempt to impersonate Company, a Company employee, another user, or any other person or entity.

e. In any way that infringes upon the rights of others, or in any way is illegal, threatening, fraudulent, or harmful, or in connection with any unlawful, illegal, fraudulent, or harmful purpose or activity.

f. To engage in any other conduct that restricts or inhibits anyone’s use or enjoyment of Service, or which, as determined by us, may harm or offend Company or users of Service or expose them to liability.

Additionally, you agree not to:

a. Use Service in any manner that could disable, overburden, damage, or impair Service or interfere with any other party’s use of Service, including their ability to engage in real time activities through Service.

b. Use any robot, spider, or other automatic device, process, or means to access Service for any purpose, including monitoring or copying any of the material on Service.

c. Use any manual process to monitor or copy any of the material on Service or for any other unauthorized purpose without our prior written consent.

d. Use any device, software, or routine that interferes with the proper working of Service.

e. Introduce any viruses, trojan horses, worms, logic bombs, or other material which is malicious or technologically harmful.

f. Attempt to gain unauthorized access to, interfere with, damage, or disrupt any parts of Service, the server on which Service is stored, or any server, computer, or database connected to Service.

g. Attack Service via a denial-of-service attack or a distributed denial-of-service attack.

h. Take any action that may damage or falsify Company rating.

i. Otherwise attempt to interfere with the proper working of Service.

No Use by Minors

Service is intended only for access and use by individuals at least eighteen (18) years old. By accessing or using any of Company, you warrant and represent that you are at least eighteen (18) years of age and with the full authority, right, and capacity to enter into this agreement and abide by all of the terms and conditions of Terms. If you are not at least eighteen (18) years old, you are prohibited from both the access and usage of Service.

Accounts

When you create an account with us, you guarantee that you are above the age of 18, and that the information you provide us is accurate, complete, and current at all times. Inaccurate, incomplete, or obsolete information may result in the immediate termination of your account on Service.

You are responsible for maintaining the confidentiality of your account and password, including but not limited to the restriction of access to your computer and/or account. You agree to accept responsibility for any and all activities or actions that occur under your account and/or password, whether your password is with our Service or a third-party service. You must notify us immediately upon becoming aware of any breach of security or unauthorized use of your account.

You may not use as a username the name of another person or entity or that is not lawfully available for use, a name or trademark that is subject to any rights of another person or entity other than you, without appropriate authorization. You may not use as a username any name that is offensive, vulgar or obscene.

We reserve the right to refuse service, terminate accounts, remove or edit content, or cancel orders in our sole discretion.

Intellectual Property

Service and its original content (excluding Content provided by users), features and functionality are and will remain the exclusive property of PlayForm ltd. and its licensors. Service is protected by copyright, trademark, and other laws of the United States and foreign countries. Our trademarks and trade dress may not be used in connection with any product or service without the prior written consent of PlayForm ltd.

We respect the intellectual property rights of others. It is our policy to respond to any claim that Content posted on Service infringes on the copyright or other intellectual property rights (“Infringement”) of any person or entity.

If you are a copyright owner, or authorized on behalf of one, and you believe that the copyrighted work has been copied in a way that constitutes copyright infringement, please submit your claim via email to dmca@PlayForm.LTD, with the subject line: “Copyright Infringement” and include in your claim a detailed description of the alleged Infringement as detailed below, under “DMCA Notice and Procedure for Copyright Infringement Claims”

You may be held accountable for damages (including costs and attorneys’ fees) for misrepresentation or bad-faith claims on the infringement of any Content found on and/or through Service on your copyright.

You may submit a notification pursuant to the Digital Millennium Copyright Act (DMCA) by providing our Copyright Agent with the following information in writing (see 17 U.S.C 512(c)(3) for further detail):

a. an electronic or physical signature of the person authorized to act on behalf of the owner of the copyright’s interest;

b. a description of the copyrighted work that you claim has been infringed, including the URL (i.e., web page address) of the location where the copyrighted work exists or a copy of the copyrighted work;

c. identification of the URL or other specific location on Service where the material that you claim is infringing is located;

d. your address, telephone number, and email address;

e. a statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law;

f. a statement by you, made under penalty of perjury, that the above information in your notice is accurate and that you are the copyright owner or authorized to act on the copyright owner’s behalf.

You can contact our Copyright Agent via email at dmca@PlayForm.LTD

Error Reporting and Feedback

You may provide us either directly at Support@PlayForm.LTD or via third party sites and tools with information and feedback concerning errors, suggestions for improvements, ideas, problems, complaints, and other matters related to our Service (“Feedback”). You acknowledge and agree that:

a) you shall not retain, acquire or assert any intellectual property right or other right, title or interest in or to the Feedback;

b) Company may have development ideas similar to the Feedback;

c) Feedback does not contain confidential information or proprietary information from you or any third party; and

d) Company is not under any obligation of confidentiality with respect to the Feedback. In the event the transfer of the ownership to the Feedback is not possible due to applicable mandatory laws, you grant Company and its affiliates an exclusive, transferable, irrevocable, free-of-charge, sub-licensable, unlimited and perpetual right to use (including copy, modify, create derivative works, publish, distribute and commercialize) Feedback in any manner and for any purpose.

Our Service may contain links to third party web sites or services that are not owned or controlled by PlayForm ltd.

PlayForm ltd. has no control over, and assumes no responsibility for the content, privacy policies, or practices of any third-party web sites or services. We do not warrant the offerings of any of these entities/individuals or their websites.

YOU ACKNOWLEDGE AND AGREE THAT PlayForm ltd. SHALL NOT BE RESPONSIBLE OR LIABLE, DIRECTLY OR INDIRECTLY, FOR ANY DAMAGE OR LOSS CAUSED OR ALLEGED TO BE CAUSED BY OR IN CONNECTION WITH USE OF OR RELIANCE ON ANY SUCH CONTENT, GOODS OR SERVICES AVAILABLE ON OR THROUGH ANY SUCH THIRD-PARTY WEB SITES OR SERVICES.

WE STRONGLY ADVISE YOU TO READ THE TERMS OF SERVICE AND PRIVACY POLICIES OF ANY THIRD-PARTY WEB SITES OR SERVICES THAT YOU VISIT.

Disclaimer Of Warranty

THESE SERVICES ARE PROVIDED BY COMPANY ON AN “AS IS” AND “AS AVAILABLE” BASIS. COMPANY MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE OPERATION OF THEIR SERVICES, OR THE INFORMATION, CONTENT OR MATERIALS INCLUDED THEREIN. YOU EXPRESSLY AGREE THAT YOUR USE OF THESE SERVICES, THEIR CONTENT, AND ANY SERVICES OR ITEMS OBTAINED FROM US IS AT YOUR SOLE RISK.

NEITHER COMPANY NOR ANY PERSON ASSOCIATED WITH COMPANY MAKES ANY WARRANTY OR REPRESENTATION WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, ACCURACY, OR AVAILABILITY OF THE SERVICES. WITHOUT LIMITING THE FOREGOING, NEITHER COMPANY NOR ANYONE ASSOCIATED WITH COMPANY REPRESENTS OR WARRANTS THAT THE SERVICES, THEIR CONTENT, OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE SERVICES WILL BE ACCURATE, RELIABLE, ERROR-FREE, OR UNINTERRUPTED, THAT DEFECTS WILL BE CORRECTED, THAT THE SERVICES OR THE SERVER THAT MAKES IT AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS OR THAT THE SERVICES OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE SERVICES WILL OTHERWISE MEET YOUR NEEDS OR EXPECTATIONS.

COMPANY HEREBY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR PARTICULAR PURPOSE.

THE FOREGOING DOES NOT AFFECT ANY WARRANTIES WHICH CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW.

Limitation Of Liability

EXCEPT AS PROHIBITED BY LAW, YOU WILL HOLD US AND OUR OFFICERS, DIRECTORS, EMPLOYEES, AND AGENTS HARMLESS FOR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGE, HOWEVER IT ARISES (INCLUDING ATTORNEYS’ FEES AND ALL RELATED COSTS AND EXPENSES OF LITIGATION AND ARBITRATION, OR AT TRIAL OR ON APPEAL, IF ANY, WHETHER OR NOT LITIGATION OR ARBITRATION IS INSTITUTED), WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE, OR OTHER TORTIOUS ACTION, OR ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT, INCLUDING WITHOUT LIMITATION ANY CLAIM FOR PERSONAL INJURY OR PROPERTY DAMAGE, ARISING FROM THIS AGREEMENT AND ANY VIOLATION BY YOU OF ANY FEDERAL, STATE, OR LOCAL LAWS, STATUTES, RULES, OR REGULATIONS, EVEN IF COMPANY HAS BEEN PREVIOUSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. EXCEPT AS PROHIBITED BY LAW, IF THERE IS LIABILITY FOUND ON THE PART OF COMPANY, IT WILL BE LIMITED TO THE AMOUNT PAID FOR THE PRODUCTS AND/OR SERVICES, AND UNDER NO CIRCUMSTANCES WILL THERE BE CONSEQUENTIAL OR PUNITIVE DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF PUNITIVE, INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE PRIOR LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU.

Termination

We may terminate or suspend your account and bar access to Service immediately, without prior notice or liability, under our sole discretion, for any reason whatsoever and without limitation, including but not limited to a breach of Terms.

If you wish to terminate your account, you may simply discontinue using Service.

All provisions of Terms which by their nature should survive termination shall survive termination, including, without limitation, ownership provisions, warranty disclaimers, indemnity and limitations of liability.

Governing Law

These Terms shall be governed and construed in accordance with the laws of Republic of Bulgaria without regard to its conflict of law provisions.

Our failure to enforce any right or provision of these Terms will not be considered a waiver of those rights. If any provision of these Terms is held to be invalid or unenforceable by a court, the remaining provisions of these Terms will remain in effect. These Terms constitute the entire agreement between us regarding our Service and supersede and replace any prior agreements we might have had between us regarding Service.

Changes To Service

We reserve the right to withdraw or amend our Service, and any service or material we provide via Service, in our sole discretion without notice. We will not be liable if for any reason all or any part of Service is unavailable at any time or for any period. From time to time, we may restrict access to some parts of Service, or the entire Service, to users, including registered users.

Amendments To Terms

We may amend Terms at any time by posting the amended terms on this site. It is your responsibility to review these Terms periodically.

Your continued use of the Platform following the posting of revised Terms means that you accept and agree to the changes. You are expected to check this page frequently so you are aware of any changes, as they are binding on you.

By continuing to access or use our Service after any revisions become effective, you agree to be bound by the revised terms. If you do not agree to the new terms, you are no longer authorized to use Service.

Waiver And Severability

No waiver by Company of any term or condition set forth in Terms shall be deemed a further or continuing waiver of such term or condition or a waiver of any other term or condition, and any failure of Company to assert a right or provision under Terms shall not constitute a waiver of such right or provision.

If any provision of Terms is held by a court or other tribunal of competent jurisdiction to be invalid, illegal or unenforceable for any reason, such provision shall be eliminated or limited to the minimum extent such that the remaining provisions of Terms will continue in full force and effect.

Acknowledgement

BY USING SERVICE OR OTHER SERVICES PROVIDED BY US, YOU ACKNOWLEDGE THAT YOU HAVE READ THESE TERMS OF SERVICE AND AGREE TO BE BOUND BY THEM.

Contact Us

Please send your feedback, comments, requests for technical support:

By email: Support@PlayForm.LTD

By phone number: +359876668093.

By mail: Delta Business Center, Ring Road N 251, Business Park Sofia.

\ No newline at end of file + Terms of Service
+

TERMS OF SERVICE

+

Effective date: 01.12.2016 / January 12th 2016
+Last updated: 02.11.2022 / February 11th 2022

+

Introduction

+

Welcome to PlayForm ltd. (“Company”, “we”, “our”, “us”)! As you +have just clicked our Terms of Service, please pause, grab a cup of coffee and +carefully read the following pages. It will take you approximately 20 minutes.

+

These Terms of Service (“Terms”, “Terms of Service”) govern your use of +our web pages located at HTTPS://PlayForm.LTD and our mobile application +PlayForm (together or individually “Service”) operated by PlayForm ltd.

+

Our Privacy Policy also governs your use of our Service and explains how we +collect, safeguard and disclose information that results from your use of our +web pages. Please read it here HTTPS://PlayForm.LTD/Privacy-Policy.

+

Your agreement with us includes these Terms and our Privacy Policy +(“Agreements”). You acknowledge that you have read and understood +Agreements, and agree to be bound of them.

+

If you do not agree with (or cannot comply with) Agreements, then you may not +use the Service, but please let us know by emailing at Support@PlayForm.LTD so +we can try to find a solution. These Terms apply to all visitors, users and +others who wish to access or use Service.

+

Thank you for being responsible.

+

Communications

+

By creating an Account on our Service, you agree to subscribe to newsletters, +marketing or promotional materials and other information we may send. However, +you may opt out of receiving any, or all, of these communications from us by +following the unsubscribe link or by emailing at.

+

Purchases

+

If you wish to purchase any product or service made available through Service +(“Purchase”), you may be asked to supply certain information relevant to +your Purchase including, without limitation, your credit card number, the +expiration date of your credit card, your billing address, and your shipping +information.

+

You represent and warrant that:

+

a) you have the legal right to use any credit card(s) or other payment method(s) +in connection with any Purchase; and that

+

b) the information you supply to us is true, correct and complete.

+

We may employ the use of third-party services for the purpose of facilitating +payment and the completion of Purchases. By submitting your information, you +grant us the right to provide the information to these third parties subject to +our Privacy Policy.

+

We reserve the right to refuse or cancel your order at any time for reasons +including but not limited to: product or service availability, errors in the +description or price of the product or service, error in your order or other +reasons.

+

We reserve the right to refuse or cancel your order if fraud or an unauthorized +or illegal transaction is suspected.

+

Contests, Sweepstakes and Promotions

+

Any contests, sweepstakes or other promotions (collectively, “Promotions”) +made available through Service may be governed by rules that are separate from +these Terms of Service. If you participate in any Promotions, please review the +applicable rules as well as our Privacy Policy. If the rules for a Promotion +conflict with these Terms of Service, Promotion rules will apply.

+

Subscriptions

+

Some parts of Service are billed on a subscription basis +(“Subscription(s)”). You will be billed in advance on a recurring and +periodic basis (“Billing Cycle”). Billing cycles are set either on a monthly +or annual basis, depending on the type of subscription plan you select when +purchasing a Subscription.

+

At the end of each Billing Cycle, your Subscription will automatically renew +under the exact same conditions unless you cancel it or PlayForm ltd. cancels +it. You may cancel your Subscription renewal either through your online account +management page or by contacting PlayForm ltd. customer support team.

+

A valid payment method, including credit card or PayPal, is required to process +the payment for your subscription. You shall provide PlayForm ltd. with accurate +and complete billing information including full name, address, state, zip code, +telephone number, and a valid payment method information. By submitting such +payment information, you automatically authorize PlayForm ltd. to charge all +Subscription fees incurred through your account to any such payment instruments.

+

Should automatic billing fail to occur for any reason, PlayForm ltd. will issue +an electronic invoice indicating that you must proceed manually, within a +certain deadline date, with the full payment corresponding to the billing period +as indicated on the invoice.

+

Free Trial

+

PlayForm ltd. may, at its sole discretion, offer a Subscription with a free +trial for a limited period of time (“Free Trial”).

+

You may be required to enter your billing information in order to sign up for +Free Trial.

+

If you do enter your billing information when signing up for Free Trial, you +will not be charged by PlayForm ltd. until Free Trial has expired. On the last +day of Free Trial period, unless you cancelled your Subscription, you will be +automatically charged the applicable Subscription fees for the type of +Subscription you have selected.

+

At any time and without notice, PlayForm ltd. reserves the right to

+

a) modify Terms of Service of Free Trial offer, or

+

b) cancel such Free Trial offer.

+

Fee Changes

+

PlayForm ltd., in its sole discretion and at any time, may modify Subscription +fees for the Subscriptions. Any Subscription fee change will become effective at +the end of the then-current Billing Cycle.

+

PlayForm ltd. will provide you with a reasonable prior notice of any change in +Subscription fees to give you an opportunity to terminate your Subscription +before such change becomes effective.

+

Your continued use of Service after Subscription fee change comes into effect +constitutes your agreement to pay the modified Subscription fee amount.

+

Refunds

+

We issue refunds for Contracts within fourteen (14) days of the original +purchase of the Contract.

+

Content

+

Our Service allows you to post, link, store, share and otherwise make available +certain information, text, graphics, videos, or other material (“Content”). +You are responsible for Content that you post on or through Service, including +its legality, reliability, and appropriateness.

+

By posting Content on or through Service, You represent and warrant that:

+

a) Content is yours (you own it) and/or you have the right to use it and the +right to grant us the rights and license as provided in these Terms, and

+

b) that the posting of your Content on or through Service does not violate the +privacy rights, publicity rights, copyrights, contract rights or any other +rights of any person or entity. We reserve the right to terminate the account of +anyone found to be infringing on a copyright.

+

You retain any and all of your rights to any Content you submit, post or display +on or through Service and you are responsible for protecting those rights. We +take no responsibility and assume no liability for Content you or any +third-party posts on or through Service. However, by posting Content using +Service you grant us the right and license to use, modify, publicly perform, +publicly display, reproduce, and distribute such Content on and through Service. +You agree that this license includes the right for us to make your Content +available to other users of Service, who may also use your Content subject to +these Terms.

+

PlayForm ltd. has the right but not the obligation to monitor and edit all +Content provided by users.

+

In addition, Content found on or through this Service are the property of +PlayForm ltd. or used with permission. You may not distribute, modify, transmit, +reuse, download, repost, copy, or use said Content, whether in whole or in part, +for commercial purposes or for personal gain, without express advance written +permission from us.

+

Prohibited Uses

+

You may use Service only for lawful purposes and in accordance with Terms. You +agree not to use Service:

+

a. In any way that violates any applicable national or international law or +regulation.

+

b. For the purpose of exploiting, harming, or attempting to exploit or harm +minors in any way by exposing them to inappropriate content or otherwise.

+

c. To transmit, or procure the sending of, any advertising or promotional +material, including any “junk mail”, “chain letter,” “spam,” or any other +similar solicitation.

+

d. To impersonate or attempt to impersonate Company, a Company employee, another +user, or any other person or entity.

+

e. In any way that infringes upon the rights of others, or in any way is +illegal, threatening, fraudulent, or harmful, or in connection with any +unlawful, illegal, fraudulent, or harmful purpose or activity.

+

f. To engage in any other conduct that restricts or inhibits anyone’s use or +enjoyment of Service, or which, as determined by us, may harm or offend Company +or users of Service or expose them to liability.

+

Additionally, you agree not to:

+

a. Use Service in any manner that could disable, overburden, damage, or impair +Service or interfere with any other party’s use of Service, including their +ability to engage in real time activities through Service.

+

b. Use any robot, spider, or other automatic device, process, or means to access +Service for any purpose, including monitoring or copying any of the material on +Service.

+

c. Use any manual process to monitor or copy any of the material on Service or +for any other unauthorized purpose without our prior written consent.

+

d. Use any device, software, or routine that interferes with the proper working +of Service.

+

e. Introduce any viruses, trojan horses, worms, logic bombs, or other material +which is malicious or technologically harmful.

+

f. Attempt to gain unauthorized access to, interfere with, damage, or disrupt +any parts of Service, the server on which Service is stored, or any server, +computer, or database connected to Service.

+

g. Attack Service via a denial-of-service attack or a distributed +denial-of-service attack.

+

h. Take any action that may damage or falsify Company rating.

+

i. Otherwise attempt to interfere with the proper working of Service.

+

No Use by Minors

+

Service is intended only for access and use by individuals at least eighteen +(18) years old. By accessing or using any of Company, you warrant and represent +that you are at least eighteen (18) years of age and with the full authority, +right, and capacity to enter into this agreement and abide by all of the terms +and conditions of Terms. If you are not at least eighteen (18) years old, you +are prohibited from both the access and usage of Service.

+

Accounts

+

When you create an account with us, you guarantee that you are above the age of +18, and that the information you provide us is accurate, complete, and current +at all times. Inaccurate, incomplete, or obsolete information may result in the +immediate termination of your account on Service.

+

You are responsible for maintaining the confidentiality of your account and +password, including but not limited to the restriction of access to your +computer and/or account. You agree to accept responsibility for any and all +activities or actions that occur under your account and/or password, whether +your password is with our Service or a third-party service. You must notify us +immediately upon becoming aware of any breach of security or unauthorized use of +your account.

+

You may not use as a username the name of another person or entity or that is +not lawfully available for use, a name or trademark that is subject to any +rights of another person or entity other than you, without appropriate +authorization. You may not use as a username any name that is offensive, vulgar +or obscene.

+

We reserve the right to refuse service, terminate accounts, remove or edit +content, or cancel orders in our sole discretion.

+

Intellectual Property

+

Service and its original content (excluding Content provided by users), features +and functionality are and will remain the exclusive property of PlayForm ltd. +and its licensors. Service is protected by copyright, trademark, and other laws +of the United States and foreign countries. Our trademarks and trade dress may +not be used in connection with any product or service without the prior written +consent of PlayForm ltd.

+ +

We respect the intellectual property rights of others. It is our policy to +respond to any claim that Content posted on Service infringes on the copyright +or other intellectual property rights (“Infringement”) of any person or +entity.

+

If you are a copyright owner, or authorized on behalf of one, and you believe +that the copyrighted work has been copied in a way that constitutes copyright +infringement, please submit your claim via email to dmca@PlayForm.LTD, with +the subject line: “Copyright Infringement” and include in your claim a +detailed description of the alleged Infringement as detailed below, under “DMCA +Notice and Procedure for Copyright Infringement Claims”

+

You may be held accountable for damages (including costs and attorneys’ fees) +for misrepresentation or bad-faith claims on the infringement of any Content +found on and/or through Service on your copyright.

+ +

You may submit a notification pursuant to the Digital Millennium Copyright Act +(DMCA) by providing our Copyright Agent with the following information in +writing (see 17 U.S.C 512(c)(3) for further detail):

+

a. an electronic or physical signature of the person authorized to act on behalf +of the owner of the copyright’s interest;

+

b. a description of the copyrighted work that you claim has been infringed, +including the URL (i.e., web page address) of the location where the copyrighted +work exists or a copy of the copyrighted work;

+

c. identification of the URL or other specific location on Service where the +material that you claim is infringing is located;

+

d. your address, telephone number, and email address;

+

e. a statement by you that you have a good faith belief that the disputed use is +not authorized by the copyright owner, its agent, or the law;

+

f. a statement by you, made under penalty of perjury, that the above information +in your notice is accurate and that you are the copyright owner or authorized to +act on the copyright owner’s behalf.

+

You can contact our Copyright Agent via email at dmca@PlayForm.LTD

+

Error Reporting and Feedback

+

You may provide us either directly at Support@PlayForm.LTD or via third party +sites and tools with information and feedback concerning errors, suggestions for +improvements, ideas, problems, complaints, and other matters related to our +Service (“Feedback”). You acknowledge and agree that:

+

a) you shall not retain, acquire or assert any intellectual property right or +other right, title or interest in or to the Feedback;

+

b) Company may have development ideas similar to the Feedback;

+

c) Feedback does not contain confidential information or proprietary information +from you or any third party; and

+

d) Company is not under any obligation of confidentiality with respect to the +Feedback. In the event the transfer of the ownership to the Feedback is not +possible due to applicable mandatory laws, you grant Company and its affiliates +an exclusive, transferable, irrevocable, free-of-charge, sub-licensable, +unlimited and perpetual right to use (including copy, modify, create derivative +works, publish, distribute and commercialize) Feedback in any manner and for any +purpose.

+ +

Our Service may contain links to third party web sites or services that are not +owned or controlled by PlayForm ltd.

+

PlayForm ltd. has no control over, and assumes no responsibility for the +content, privacy policies, or practices of any third-party web sites or +services. We do not warrant the offerings of any of these entities/individuals +or their websites.

+

YOU ACKNOWLEDGE AND AGREE THAT PlayForm ltd. SHALL NOT BE RESPONSIBLE OR LIABLE, +DIRECTLY OR INDIRECTLY, FOR ANY DAMAGE OR LOSS CAUSED OR ALLEGED TO BE CAUSED BY +OR IN CONNECTION WITH USE OF OR RELIANCE ON ANY SUCH CONTENT, GOODS OR SERVICES +AVAILABLE ON OR THROUGH ANY SUCH THIRD-PARTY WEB SITES OR SERVICES.

+

WE STRONGLY ADVISE YOU TO READ THE TERMS OF SERVICE AND PRIVACY POLICIES OF ANY +THIRD-PARTY WEB SITES OR SERVICES THAT YOU VISIT.

+

Disclaimer Of Warranty

+

THESE SERVICES ARE PROVIDED BY COMPANY ON AN “AS IS” AND “AS AVAILABLE” BASIS. +COMPANY MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, +AS TO THE OPERATION OF THEIR SERVICES, OR THE INFORMATION, CONTENT OR MATERIALS +INCLUDED THEREIN. YOU EXPRESSLY AGREE THAT YOUR USE OF THESE SERVICES, THEIR +CONTENT, AND ANY SERVICES OR ITEMS OBTAINED FROM US IS AT YOUR SOLE RISK.

+

NEITHER COMPANY NOR ANY PERSON ASSOCIATED WITH COMPANY MAKES ANY WARRANTY OR +REPRESENTATION WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, +ACCURACY, OR AVAILABILITY OF THE SERVICES. WITHOUT LIMITING THE FOREGOING, +NEITHER COMPANY NOR ANYONE ASSOCIATED WITH COMPANY REPRESENTS OR WARRANTS THAT +THE SERVICES, THEIR CONTENT, OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE +SERVICES WILL BE ACCURATE, RELIABLE, ERROR-FREE, OR UNINTERRUPTED, THAT DEFECTS +WILL BE CORRECTED, THAT THE SERVICES OR THE SERVER THAT MAKES IT AVAILABLE ARE +FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS OR THAT THE SERVICES OR ANY SERVICES +OR ITEMS OBTAINED THROUGH THE SERVICES WILL OTHERWISE MEET YOUR NEEDS OR +EXPECTATIONS.

+

COMPANY HEREBY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, +STATUTORY, OR OTHERWISE, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR PARTICULAR PURPOSE.

+

THE FOREGOING DOES NOT AFFECT ANY WARRANTIES WHICH CANNOT BE EXCLUDED OR LIMITED +UNDER APPLICABLE LAW.

+

Limitation Of Liability

+

EXCEPT AS PROHIBITED BY LAW, YOU WILL HOLD US AND OUR OFFICERS, DIRECTORS, +EMPLOYEES, AND AGENTS HARMLESS FOR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, +OR CONSEQUENTIAL DAMAGE, HOWEVER IT ARISES (INCLUDING ATTORNEYS’ FEES AND ALL +RELATED COSTS AND EXPENSES OF LITIGATION AND ARBITRATION, OR AT TRIAL OR ON +APPEAL, IF ANY, WHETHER OR NOT LITIGATION OR ARBITRATION IS INSTITUTED), WHETHER +IN AN ACTION OF CONTRACT, NEGLIGENCE, OR OTHER TORTIOUS ACTION, OR ARISING OUT +OF OR IN CONNECTION WITH THIS AGREEMENT, INCLUDING WITHOUT LIMITATION ANY CLAIM +FOR PERSONAL INJURY OR PROPERTY DAMAGE, ARISING FROM THIS AGREEMENT AND ANY +VIOLATION BY YOU OF ANY FEDERAL, STATE, OR LOCAL LAWS, STATUTES, RULES, OR +REGULATIONS, EVEN IF COMPANY HAS BEEN PREVIOUSLY ADVISED OF THE POSSIBILITY OF +SUCH DAMAGE. EXCEPT AS PROHIBITED BY LAW, IF THERE IS LIABILITY FOUND ON THE +PART OF COMPANY, IT WILL BE LIMITED TO THE AMOUNT PAID FOR THE PRODUCTS AND/OR +SERVICES, AND UNDER NO CIRCUMSTANCES WILL THERE BE CONSEQUENTIAL OR PUNITIVE +DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF PUNITIVE, +INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE PRIOR LIMITATION OR EXCLUSION MAY +NOT APPLY TO YOU.

+

Termination

+

We may terminate or suspend your account and bar access to Service immediately, +without prior notice or liability, under our sole discretion, for any reason +whatsoever and without limitation, including but not limited to a breach of +Terms.

+

If you wish to terminate your account, you may simply discontinue using Service.

+

All provisions of Terms which by their nature should survive termination shall +survive termination, including, without limitation, ownership provisions, +warranty disclaimers, indemnity and limitations of liability.

+

Governing Law

+

These Terms shall be governed and construed in accordance with the laws of +Republic of Bulgaria without regard to its conflict of law provisions.

+

Our failure to enforce any right or provision of these Terms will not be +considered a waiver of those rights. If any provision of these Terms is held to +be invalid or unenforceable by a court, the remaining provisions of these Terms +will remain in effect. These Terms constitute the entire agreement between us +regarding our Service and supersede and replace any prior agreements we might +have had between us regarding Service.

+

Changes To Service

+

We reserve the right to withdraw or amend our Service, and any service or +material we provide via Service, in our sole discretion without notice. We will +not be liable if for any reason all or any part of Service is unavailable at any +time or for any period. From time to time, we may restrict access to some parts +of Service, or the entire Service, to users, including registered users.

+

Amendments To Terms

+

We may amend Terms at any time by posting the amended terms on this site. It is +your responsibility to review these Terms periodically.

+

Your continued use of the Platform following the posting of revised Terms means +that you accept and agree to the changes. You are expected to check this page +frequently so you are aware of any changes, as they are binding on you.

+

By continuing to access or use our Service after any revisions become effective, +you agree to be bound by the revised terms. If you do not agree to the new +terms, you are no longer authorized to use Service.

+

Waiver And Severability

+

No waiver by Company of any term or condition set forth in Terms shall be deemed +a further or continuing waiver of such term or condition or a waiver of any +other term or condition, and any failure of Company to assert a right or +provision under Terms shall not constitute a waiver of such right or provision.

+

If any provision of Terms is held by a court or other tribunal of competent +jurisdiction to be invalid, illegal or unenforceable for any reason, such +provision shall be eliminated or limited to the minimum extent such that the +remaining provisions of Terms will continue in full force and effect.

+

Acknowledgement

+

BY USING SERVICE OR OTHER SERVICES PROVIDED BY US, YOU ACKNOWLEDGE THAT YOU HAVE +READ THESE TERMS OF SERVICE AND AGREE TO BE BOUND BY THEM.

+

Contact Us

+

Please send your feedback, comments, requests for technical support:

+

By email: Support@PlayForm.LTD

+

By phone number: +359876668093.

+

By mail: Delta Business Center, Ring Road N 251, Business Park Sofia.

\ No newline at end of file diff --git a/Target/_astro/ClientRouter.astro_astro_type_script_index_0_lang.ZAtydGN1.js b/Target/_astro/ClientRouter.astro_astro_type_script_index_0_lang.ZAtydGN1.js index 89320744..bb6f9612 100644 --- a/Target/_astro/ClientRouter.astro_astro_type_script_index_0_lang.ZAtydGN1.js +++ b/Target/_astro/ClientRouter.astro_astro_type_script_index_0_lang.ZAtydGN1.js @@ -1 +1,609 @@ -import{i as q}from"./index.BqqcOND9.js";const y="data-astro-transition-persist";function B(t){for(const e of document.scripts)for(const n of t.scripts)if(!n.hasAttribute("data-astro-rerun")&&(!e.src&&e.textContent===n.textContent||e.src&&e.type===n.type&&e.src===n.src)){n.dataset.astroExec="";break}}function U(t){const e=document.documentElement,n=[...e.attributes].filter((({name:t})=>(e.removeAttribute(t),t.startsWith("data-astro-"))));[...t.documentElement.attributes,...n].forEach((({name:t,value:n})=>e.setAttribute(t,n)))}function W(t){for(const e of Array.from(document.head.children)){const n=j(e,t);n?n.remove():e.remove()}document.head.append(...t.head.children)}function V(t,e){e.replaceWith(t);for(const n of e.querySelectorAll(`[${y}]`)){const e=n.getAttribute(y),o=t.querySelector(`[${y}="${e}"]`);o&&(o.replaceWith(n),"astro-island"===o.localName&&G(n)&&!z(n,o)&&(n.setAttribute("ssr",""),n.setAttribute("props",o.getAttribute("props"))))}}const K=()=>{const t=document.activeElement;if(t?.closest(`[${y}]`)){if(t instanceof HTMLInputElement||t instanceof HTMLTextAreaElement){const e=t.selectionStart,n=t.selectionEnd;return()=>v({activeElement:t,start:e,end:n})}return()=>v({activeElement:t})}return()=>v({activeElement:null})},v=({activeElement:t,start:e,end:n})=>{t&&(t.focus(),(t instanceof HTMLInputElement||t instanceof HTMLTextAreaElement)&&("number"==typeof e&&(t.selectionStart=e),"number"==typeof n&&(t.selectionEnd=n)))},j=(t,e)=>{const n=t.getAttribute(y),o=n&&e.head.querySelector(`[${y}="${n}"]`);if(o)return o;if(t.matches("link[rel=stylesheet]")){const n=t.getAttribute("href");return e.head.querySelector(`link[rel=stylesheet][href="${n}"]`)}return null},G=t=>{const e=t.dataset.astroTransitionPersistProps;return null==e||"false"===e},z=(t,e)=>t.getAttribute("props")===e.getAttribute("props"),J=t=>{B(t),U(t),W(t);const e=K();V(t.body,document.body),e()},Q="astro:before-preparation",Z="astro:after-preparation",tt="astro:before-swap",et="astro:after-swap",nt=t=>document.dispatchEvent(new Event(t));class H extends Event{from;to;direction;navigationType;sourceElement;info;newDocument;signal;constructor(t,e,n,o,r,i,a,s,c,l){super(t,e),this.from=n,this.to=o,this.direction=r,this.navigationType=i,this.sourceElement=a,this.info=s,this.newDocument=c,this.signal=l,Object.defineProperties(this,{from:{enumerable:!0},to:{enumerable:!0,writable:!0},direction:{enumerable:!0,writable:!0},navigationType:{enumerable:!0},sourceElement:{enumerable:!0},info:{enumerable:!0},newDocument:{enumerable:!0,writable:!0},signal:{enumerable:!0}})}}class ot extends H{formData;loader;constructor(t,e,n,o,r,i,a,s,c,l){super(Q,{cancelable:!0},t,e,n,o,r,i,a,s),this.formData=c,this.loader=l.bind(this,this),Object.defineProperties(this,{formData:{enumerable:!0},loader:{enumerable:!0,writable:!0}})}}class rt extends H{direction;viewTransition;swap;constructor(t,e){super(tt,void 0,t.from,t.to,t.direction,t.navigationType,t.sourceElement,t.info,t.newDocument,t.signal),this.direction=t.direction,this.viewTransition=e,this.swap=()=>J(this.newDocument),Object.defineProperties(this,{direction:{enumerable:!0},viewTransition:{enumerable:!0},swap:{enumerable:!0,writable:!0}})}}async function it(t,e,n,o,r,i,a,s,c){const l=new ot(t,e,n,o,r,i,window.document,a,s,c);return document.dispatchEvent(l)&&(await l.loader(),l.defaultPrevented||(nt(Z),"traverse"!==l.navigationType&&R({scrollX:scrollX,scrollY:scrollY}))),l}function st(t,e){const n=new rt(t,e);return document.dispatchEvent(n),n.swap(),n}const at=history.pushState.bind(history),T=history.replaceState.bind(history),R=t=>{history.state&&(history.scrollRestoration="manual",T({...history.state,...t},""))},P=!!document.startViewTransition,x=()=>!!document.querySelector('[name="astro-view-transitions-enabled"]'),O=(t,e)=>t.pathname===e.pathname&&t.search===e.search;let f,b,A;const X=t=>document.dispatchEvent(new Event(t)),Y=()=>X("astro:page-load"),ct=()=>{let t=document.createElement("div");t.setAttribute("aria-live","assertive"),t.setAttribute("aria-atomic","true"),t.className="astro-route-announcer",document.body.append(t),setTimeout((()=>{let e=document.title||document.querySelector("h1")?.textContent||location.pathname;t.textContent=e}),60)},D="data-astro-transition-persist",L="data-astro-transition",S="data-astro-transition-fallback";let k,g=0;async function lt(t,e){try{const n=await fetch(t,e),o=(n.headers.get("content-type")??"").split(";",1)[0].trim();return"text/html"!==o&&"application/xhtml+xml"!==o?null:{html:await n.text(),redirected:n.redirected?n.url:void 0,mediaType:o}}catch{return null}}function _(){const t=document.querySelector('[name="astro-view-transitions-fallback"]');return t?t.getAttribute("content"):"animate"}function ut(){let t=Promise.resolve();for(const e of document.getElementsByTagName("script")){if(""===e.dataset.astroExec)continue;const n=e.getAttribute("type");if(n&&"module"!==n&&"text/javascript"!==n)continue;const o=document.createElement("script");o.innerHTML=e.innerHTML;for(const n of e.attributes){if("src"===n.name){const e=new Promise((t=>{o.onload=o.onerror=t}));t=t.then((()=>e))}o.setAttribute(n.name,n.value)}o.dataset.astroExec="",e.replaceWith(o)}return t}history.state?(g=history.state.index,scrollTo({left:history.state.scrollX,top:history.state.scrollY})):x()&&(T({index:g,scrollX:scrollX,scrollY:scrollY},""),history.scrollRestoration="manual");const C=(t,e,n,o,r)=>{const i=O(e,t),a=document.title;document.title=o;let s=!1;if(t.href!==location.href&&!r)if("replace"===n.history){const e=history.state;T({...n.state,index:e.index,scrollX:e.scrollX,scrollY:e.scrollY},"",t.href)}else at({...n.state,index:++g,scrollX:0,scrollY:0},"",t.href);if(document.title=a,A=t,i||(scrollTo({left:0,top:0,behavior:"instant"}),s=!0),r)scrollTo(r.scrollX,r.scrollY);else{if(t.hash){history.scrollRestoration="auto";const e=history.state;location.href=t.href,history.state||(T(e,""),i&&window.dispatchEvent(new PopStateEvent("popstate")))}else s||scrollTo({left:0,top:0,behavior:"instant"});history.scrollRestoration="manual"}};function dt(t){const e=[];for(const n of t.querySelectorAll("head link[rel=stylesheet]"))if(!document.querySelector(`[${D}="${n.getAttribute(D)}"], link[rel=stylesheet][href="${n.getAttribute("href")}"]`)){const t=document.createElement("link");t.setAttribute("rel","preload"),t.setAttribute("as","style"),t.setAttribute("href",n.getAttribute("href")),e.push(new Promise((e=>{["load","error"].forEach((n=>t.addEventListener(n,e))),document.head.append(t)})))}return e}async function I(t,e,n,o,r){async function i(t){const e=document.getAnimations();document.documentElement.setAttribute(S,t);const n=document.getAnimations().filter((t=>!e.includes(t)&&!function(t){const e=t.effect;return!!(e&&e instanceof KeyframeEffect&&e.target)&&"infinite"===window.getComputedStyle(e.target,e.pseudoElement).animationIterationCount}(t)));return Promise.allSettled(n.map((t=>t.finished)))}if("animate"===r&&!n.transitionSkipped&&!t.signal.aborted)try{await i("old")}catch{}const a=document.title,s=st(t,n.viewTransition);C(s.to,s.from,e,a,o),X(et),"animate"===r&&(n.transitionSkipped||s.signal.aborted?n.viewTransitionFinished():i("new").finally((()=>n.viewTransitionFinished())))}function ft(){return f?.controller.abort(),f={controller:new AbortController}}async function $(t,e,n,o,r){const i=ft();if(!x()||location.origin!==n.origin)return i===f&&(f=void 0),void(location.href=n.href);const a=r?"traverse":"replace"===o.history?"replace":"push";if("traverse"!==a&&R({scrollX:scrollX,scrollY:scrollY}),O(e,n)&&("back"!==t&&n.hash||"back"===t&&e.hash))return C(n,e,o,document.title,r),void(i===f&&(f=void 0));const s=await it(e,n,t,a,o.sourceElement,o.info,i.controller.signal,o.formData,(async function(t){const e=t.to.href,n={signal:t.signal};if(t.formData){n.method="POST";const e=t.sourceElement instanceof HTMLFormElement?t.sourceElement:t.sourceElement instanceof HTMLElement&&"form"in t.sourceElement?t.sourceElement.form:t.sourceElement?.closest("form");n.body="application/x-www-form-urlencoded"===e?.attributes.getNamedItem("enctype")?.value?new URLSearchParams(t.formData):t.formData}const o=await lt(e,n);if(null===o)return void t.preventDefault();if(o.redirected){const e=new URL(o.redirected);if(e.origin!==t.to.origin)return void t.preventDefault();t.to=e}if(k??=new DOMParser,t.newDocument=k.parseFromString(o.html,o.mediaType),t.newDocument.querySelectorAll("noscript").forEach((t=>t.remove())),!t.newDocument.querySelector('[name="astro-view-transitions-enabled"]')&&!t.formData)return void t.preventDefault();const r=dt(t.newDocument);r.length&&!t.signal.aborted&&await Promise.all(r)}));if(s.defaultPrevented||s.signal.aborted)return i===f&&(f=void 0),void(s.signal.aborted||(location.href=n.href));const c=await async function(){if(b&&b.viewTransition){try{b.viewTransition.skipTransition()}catch{}try{await b.viewTransition.updateCallbackDone}catch{}}return b={transitionSkipped:!1}}();if(s.signal.aborted)i===f&&(f=void 0);else{if(document.documentElement.setAttribute(L,s.direction),P)c.viewTransition=document.startViewTransition((async()=>await I(s,o,c,r)));else{const t=(async()=>{await Promise.resolve(),await I(s,o,c,r,_())})();c.viewTransition={updateCallbackDone:t,ready:t,finished:new Promise((t=>c.viewTransitionFinished=t)),skipTransition:()=>{c.transitionSkipped=!0,document.documentElement.removeAttribute(S)}}}c.viewTransition?.updateCallbackDone.finally((async()=>{await ut(),Y(),ct()})),c.viewTransition?.finished.finally((()=>{c.viewTransition=void 0,c===b&&(b=void 0),i===f&&(f=void 0),document.documentElement.removeAttribute(L),document.documentElement.removeAttribute(S)}));try{await(c.viewTransition?.updateCallbackDone)}catch(t){const e=t;console.log("[astro]",e.name,e.message,e.stack)}}}async function N(t,e){await $("forward",A,new URL(t,location.href),e??{})}function mt(t){if(!x()&&t.state)return void location.reload();if(null===t.state)return;const e=history.state,n=e.index,o=n>g?"forward":"back";g=n,$(o,A,new URL(location.href),{},e)}const M=()=>{history.state&&(scrollX!==history.state.scrollX||scrollY!==history.state.scrollY)&&R({scrollX:scrollX,scrollY:scrollY})};if(P||"none"!==_())if(A=new URL(location.href),addEventListener("popstate",mt),addEventListener("load",Y),"onscrollend"in window)addEventListener("scrollend",M);else{let t,e,n,o;const r=()=>o!==history.state?.index?(clearInterval(t),void(t=void 0)):e===scrollY&&n===scrollX?(clearInterval(t),t=void 0,void M()):(e=scrollY,void(n=scrollX));addEventListener("scroll",(()=>{void 0===t&&(o=history.state?.index,e=scrollY,n=scrollX,t=window.setInterval(r,50))}),{passive:!0})}for(const t of document.getElementsByTagName("script"))t.dataset.astroExec="";function ht(){const t=document.querySelector('[name="astro-view-transitions-fallback"]');return t?t.getAttribute("content"):"animate"}function F(t){return void 0!==t.dataset.astroReload}(P||"none"!==ht())&&(document.addEventListener("click",(t=>{let e=t.target;if(t.composed&&(e=t.composedPath()[0]),e instanceof Element&&(e=e.closest("a, area")),!(e instanceof HTMLAnchorElement||e instanceof SVGAElement||e instanceof HTMLAreaElement))return;const n=e instanceof HTMLElement?e.target:e.target.baseVal,o=e instanceof HTMLElement?e.href:e.href.baseVal,r=new URL(o,location.href).origin;F(e)||e.hasAttribute("download")||!e.href||n&&"_self"!==n||r!==location.origin||0!==t.button||t.metaKey||t.ctrlKey||t.altKey||t.shiftKey||t.defaultPrevented||(t.preventDefault(),N(o,{history:"replace"===e.dataset.astroHistory?"replace":"auto",sourceElement:e}))})),document.addEventListener("submit",(t=>{let e=t.target;if("FORM"!==e.tagName||t.defaultPrevented||F(e))return;const n=e,o=t.submitter,r=new FormData(n,o),i="string"==typeof n.action?n.action:n.getAttribute("action"),a="string"==typeof n.method?n.method:n.getAttribute("method");let s=o?.getAttribute("formaction")??i??location.pathname;const c=o?.getAttribute("formmethod")??a??"get";if("dialog"===c||location.origin!==new URL(s,location.href).origin)return;const l={sourceElement:o??n};if("get"===c){const t=new URLSearchParams(r),e=new URL(s);e.search=t.toString(),s=e.toString()}else l.formData=r;t.preventDefault(),N(s,l)})),q({prefetchAll:!0})); \ No newline at end of file +import { i as q } from "./index.BqqcOND9.js"; +const y = "data-astro-transition-persist"; +function B(t) { + for (const e of document.scripts) + for (const n of t.scripts) + if ( + !n.hasAttribute("data-astro-rerun") && + ((!e.src && e.textContent === n.textContent) || + (e.src && e.type === n.type && e.src === n.src)) + ) { + n.dataset.astroExec = ""; + break; + } +} +function U(t) { + const e = document.documentElement, + n = [...e.attributes].filter( + ({ name: o }) => ( + e.removeAttribute(o), o.startsWith("data-astro-") + ), + ); + [...t.documentElement.attributes, ...n].forEach(({ name: o, value: r }) => + e.setAttribute(o, r), + ); +} +function W(t) { + for (const e of Array.from(document.head.children)) { + const n = j(e, t); + n ? n.remove() : e.remove(); + } + document.head.append(...t.head.children); +} +function V(t, e) { + e.replaceWith(t); + for (const n of e.querySelectorAll(`[${y}]`)) { + const o = n.getAttribute(y), + r = t.querySelector(`[${y}="${o}"]`); + r && + (r.replaceWith(n), + r.localName === "astro-island" && + G(n) && + !z(n, r) && + (n.setAttribute("ssr", ""), + n.setAttribute("props", r.getAttribute("props")))); + } +} +const K = () => { + const t = document.activeElement; + if (t?.closest(`[${y}]`)) { + if ( + t instanceof HTMLInputElement || + t instanceof HTMLTextAreaElement + ) { + const e = t.selectionStart, + n = t.selectionEnd; + return () => v({ activeElement: t, start: e, end: n }); + } + return () => v({ activeElement: t }); + } else return () => v({ activeElement: null }); + }, + v = ({ activeElement: t, start: e, end: n }) => { + t && + (t.focus(), + (t instanceof HTMLInputElement || + t instanceof HTMLTextAreaElement) && + (typeof e == "number" && (t.selectionStart = e), + typeof n == "number" && (t.selectionEnd = n))); + }, + j = (t, e) => { + const n = t.getAttribute(y), + o = n && e.head.querySelector(`[${y}="${n}"]`); + if (o) return o; + if (t.matches("link[rel=stylesheet]")) { + const r = t.getAttribute("href"); + return e.head.querySelector(`link[rel=stylesheet][href="${r}"]`); + } + return null; + }, + G = (t) => { + const e = t.dataset.astroTransitionPersistProps; + return e == null || e === "false"; + }, + z = (t, e) => t.getAttribute("props") === e.getAttribute("props"), + J = (t) => { + B(t), U(t), W(t); + const e = K(); + V(t.body, document.body), e(); + }, + Q = "astro:before-preparation", + Z = "astro:after-preparation", + tt = "astro:before-swap", + et = "astro:after-swap", + nt = (t) => document.dispatchEvent(new Event(t)); +class H extends Event { + from; + to; + direction; + navigationType; + sourceElement; + info; + newDocument; + signal; + constructor(e, n, o, r, s, u, a, l, d, c) { + super(e, n), + (this.from = o), + (this.to = r), + (this.direction = s), + (this.navigationType = u), + (this.sourceElement = a), + (this.info = l), + (this.newDocument = d), + (this.signal = c), + Object.defineProperties(this, { + from: { enumerable: !0 }, + to: { enumerable: !0, writable: !0 }, + direction: { enumerable: !0, writable: !0 }, + navigationType: { enumerable: !0 }, + sourceElement: { enumerable: !0 }, + info: { enumerable: !0 }, + newDocument: { enumerable: !0, writable: !0 }, + signal: { enumerable: !0 }, + }); + } +} +class ot extends H { + formData; + loader; + constructor(e, n, o, r, s, u, a, l, d, c) { + super(Q, { cancelable: !0 }, e, n, o, r, s, u, a, l), + (this.formData = d), + (this.loader = c.bind(this, this)), + Object.defineProperties(this, { + formData: { enumerable: !0 }, + loader: { enumerable: !0, writable: !0 }, + }); + } +} +class rt extends H { + direction; + viewTransition; + swap; + constructor(e, n) { + super( + tt, + void 0, + e.from, + e.to, + e.direction, + e.navigationType, + e.sourceElement, + e.info, + e.newDocument, + e.signal, + ), + (this.direction = e.direction), + (this.viewTransition = n), + (this.swap = () => J(this.newDocument)), + Object.defineProperties(this, { + direction: { enumerable: !0 }, + viewTransition: { enumerable: !0 }, + swap: { enumerable: !0, writable: !0 }, + }); + } +} +async function it(t, e, n, o, r, s, u, a, l) { + const d = new ot(t, e, n, o, r, s, window.document, u, a, l); + return ( + document.dispatchEvent(d) && + (await d.loader(), + d.defaultPrevented || + (nt(Z), + d.navigationType !== "traverse" && R({ scrollX, scrollY }))), + d + ); +} +function st(t, e) { + const n = new rt(t, e); + return document.dispatchEvent(n), n.swap(), n; +} +const at = history.pushState.bind(history), + T = history.replaceState.bind(history), + R = (t) => { + history.state && + ((history.scrollRestoration = "manual"), + T({ ...history.state, ...t }, "")); + }, + P = !!document.startViewTransition, + x = () => + !!document.querySelector('[name="astro-view-transitions-enabled"]'), + O = (t, e) => t.pathname === e.pathname && t.search === e.search; +let f, b, A; +const X = (t) => document.dispatchEvent(new Event(t)), + Y = () => X("astro:page-load"), + ct = () => { + let t = document.createElement("div"); + t.setAttribute("aria-live", "assertive"), + t.setAttribute("aria-atomic", "true"), + (t.className = "astro-route-announcer"), + document.body.append(t), + setTimeout(() => { + let e = + document.title || + document.querySelector("h1")?.textContent || + location.pathname; + t.textContent = e; + }, 60); + }, + D = "data-astro-transition-persist", + L = "data-astro-transition", + S = "data-astro-transition-fallback"; +let k, + g = 0; +history.state + ? ((g = history.state.index), + scrollTo({ left: history.state.scrollX, top: history.state.scrollY })) + : x() && + (T({ index: g, scrollX, scrollY }, ""), + (history.scrollRestoration = "manual")); +async function lt(t, e) { + try { + const n = await fetch(t, e), + r = (n.headers.get("content-type") ?? "").split(";", 1)[0].trim(); + return r !== "text/html" && r !== "application/xhtml+xml" + ? null + : { + html: await n.text(), + redirected: n.redirected ? n.url : void 0, + mediaType: r, + }; + } catch { + return null; + } +} +function _() { + const t = document.querySelector( + '[name="astro-view-transitions-fallback"]', + ); + return t ? t.getAttribute("content") : "animate"; +} +function ut() { + let t = Promise.resolve(); + for (const e of document.getElementsByTagName("script")) { + if (e.dataset.astroExec === "") continue; + const n = e.getAttribute("type"); + if (n && n !== "module" && n !== "text/javascript") continue; + const o = document.createElement("script"); + o.innerHTML = e.innerHTML; + for (const r of e.attributes) { + if (r.name === "src") { + const s = new Promise((u) => { + o.onload = o.onerror = u; + }); + t = t.then(() => s); + } + o.setAttribute(r.name, r.value); + } + (o.dataset.astroExec = ""), e.replaceWith(o); + } + return t; +} +const C = (t, e, n, o, r) => { + const s = O(e, t), + u = document.title; + document.title = o; + let a = !1; + if (t.href !== location.href && !r) + if (n.history === "replace") { + const l = history.state; + T( + { + ...n.state, + index: l.index, + scrollX: l.scrollX, + scrollY: l.scrollY, + }, + "", + t.href, + ); + } else + at({ ...n.state, index: ++g, scrollX: 0, scrollY: 0 }, "", t.href); + if ( + ((document.title = u), + (A = t), + s || (scrollTo({ left: 0, top: 0, behavior: "instant" }), (a = !0)), + r) + ) + scrollTo(r.scrollX, r.scrollY); + else { + if (t.hash) { + history.scrollRestoration = "auto"; + const l = history.state; + (location.href = t.href), + history.state || + (T(l, ""), + s && window.dispatchEvent(new PopStateEvent("popstate"))); + } else a || scrollTo({ left: 0, top: 0, behavior: "instant" }); + history.scrollRestoration = "manual"; + } +}; +function dt(t) { + const e = []; + for (const n of t.querySelectorAll("head link[rel=stylesheet]")) + if ( + !document.querySelector( + `[${D}="${n.getAttribute(D)}"], link[rel=stylesheet][href="${n.getAttribute("href")}"]`, + ) + ) { + const o = document.createElement("link"); + o.setAttribute("rel", "preload"), + o.setAttribute("as", "style"), + o.setAttribute("href", n.getAttribute("href")), + e.push( + new Promise((r) => { + ["load", "error"].forEach((s) => + o.addEventListener(s, r), + ), + document.head.append(o); + }), + ); + } + return e; +} +async function I(t, e, n, o, r) { + async function s(l) { + function d(h) { + const m = h.effect; + return !m || !(m instanceof KeyframeEffect) || !m.target + ? !1 + : window.getComputedStyle(m.target, m.pseudoElement) + .animationIterationCount === "infinite"; + } + const c = document.getAnimations(); + document.documentElement.setAttribute(S, l); + const w = document + .getAnimations() + .filter((h) => !c.includes(h) && !d(h)); + return Promise.allSettled(w.map((h) => h.finished)); + } + if (r === "animate" && !n.transitionSkipped && !t.signal.aborted) + try { + await s("old"); + } catch {} + const u = document.title, + a = st(t, n.viewTransition); + C(a.to, a.from, e, u, o), + X(et), + r === "animate" && + (!n.transitionSkipped && !a.signal.aborted + ? s("new").finally(() => n.viewTransitionFinished()) + : n.viewTransitionFinished()); +} +function ft() { + return f?.controller.abort(), (f = { controller: new AbortController() }); +} +async function $(t, e, n, o, r) { + const s = ft(); + if (!x() || location.origin !== n.origin) { + s === f && (f = void 0), (location.href = n.href); + return; + } + const u = r ? "traverse" : o.history === "replace" ? "replace" : "push"; + if ( + (u !== "traverse" && R({ scrollX, scrollY }), + O(e, n) && ((t !== "back" && n.hash) || (t === "back" && e.hash))) + ) { + C(n, e, o, document.title, r), s === f && (f = void 0); + return; + } + const a = await it( + e, + n, + t, + u, + o.sourceElement, + o.info, + s.controller.signal, + o.formData, + l, + ); + if (a.defaultPrevented || a.signal.aborted) { + s === f && (f = void 0), a.signal.aborted || (location.href = n.href); + return; + } + async function l(i) { + const w = i.to.href, + h = { signal: i.signal }; + if (i.formData) { + h.method = "POST"; + const p = + i.sourceElement instanceof HTMLFormElement + ? i.sourceElement + : i.sourceElement instanceof HTMLElement && + "form" in i.sourceElement + ? i.sourceElement.form + : i.sourceElement?.closest("form"); + h.body = + p?.attributes.getNamedItem("enctype")?.value === + "application/x-www-form-urlencoded" + ? new URLSearchParams(i.formData) + : i.formData; + } + const m = await lt(w, h); + if (m === null) { + i.preventDefault(); + return; + } + if (m.redirected) { + const p = new URL(m.redirected); + if (p.origin !== i.to.origin) { + i.preventDefault(); + return; + } + i.to = p; + } + if ( + ((k ??= new DOMParser()), + (i.newDocument = k.parseFromString(m.html, m.mediaType)), + i.newDocument + .querySelectorAll("noscript") + .forEach((p) => p.remove()), + !i.newDocument.querySelector( + '[name="astro-view-transitions-enabled"]', + ) && !i.formData) + ) { + i.preventDefault(); + return; + } + const E = dt(i.newDocument); + E.length && !i.signal.aborted && (await Promise.all(E)); + } + async function d() { + if (b && b.viewTransition) { + try { + b.viewTransition.skipTransition(); + } catch {} + try { + await b.viewTransition.updateCallbackDone; + } catch {} + } + return (b = { transitionSkipped: !1 }); + } + const c = await d(); + if (a.signal.aborted) { + s === f && (f = void 0); + return; + } + if ((document.documentElement.setAttribute(L, a.direction), P)) + c.viewTransition = document.startViewTransition( + async () => await I(a, o, c, r), + ); + else { + const i = (async () => { + await Promise.resolve(), await I(a, o, c, r, _()); + })(); + c.viewTransition = { + updateCallbackDone: i, + ready: i, + finished: new Promise((w) => (c.viewTransitionFinished = w)), + skipTransition: () => { + (c.transitionSkipped = !0), + document.documentElement.removeAttribute(S); + }, + }; + } + c.viewTransition?.updateCallbackDone.finally(async () => { + await ut(), Y(), ct(); + }), + c.viewTransition?.finished.finally(() => { + (c.viewTransition = void 0), + c === b && (b = void 0), + s === f && (f = void 0), + document.documentElement.removeAttribute(L), + document.documentElement.removeAttribute(S); + }); + try { + await c.viewTransition?.updateCallbackDone; + } catch (i) { + const w = i; + console.log("[astro]", w.name, w.message, w.stack); + } +} +async function N(t, e) { + await $("forward", A, new URL(t, location.href), e ?? {}); +} +function mt(t) { + if (!x() && t.state) { + location.reload(); + return; + } + if (t.state === null) return; + const e = history.state, + n = e.index, + o = n > g ? "forward" : "back"; + (g = n), $(o, A, new URL(location.href), {}, e); +} +const M = () => { + history.state && + (scrollX !== history.state.scrollX || + scrollY !== history.state.scrollY) && + R({ scrollX, scrollY }); +}; +{ + if (P || _() !== "none") + if ( + ((A = new URL(location.href)), + addEventListener("popstate", mt), + addEventListener("load", Y), + "onscrollend" in window) + ) + addEventListener("scrollend", M); + else { + let t, e, n, o; + const r = () => { + if (o !== history.state?.index) { + clearInterval(t), (t = void 0); + return; + } + if (e === scrollY && n === scrollX) { + clearInterval(t), (t = void 0), M(); + return; + } else (e = scrollY), (n = scrollX); + }; + addEventListener( + "scroll", + () => { + t === void 0 && + ((o = history.state?.index), + (e = scrollY), + (n = scrollX), + (t = window.setInterval(r, 50))); + }, + { passive: !0 }, + ); + } + for (const t of document.getElementsByTagName("script")) + t.dataset.astroExec = ""; +} +function ht() { + const t = document.querySelector( + '[name="astro-view-transitions-fallback"]', + ); + return t ? t.getAttribute("content") : "animate"; +} +function F(t) { + return t.dataset.astroReload !== void 0; +} +(P || ht() !== "none") && + (document.addEventListener("click", (t) => { + let e = t.target; + if ( + (t.composed && (e = t.composedPath()[0]), + e instanceof Element && (e = e.closest("a, area")), + !(e instanceof HTMLAnchorElement) && + !(e instanceof SVGAElement) && + !(e instanceof HTMLAreaElement)) + ) + return; + const n = e instanceof HTMLElement ? e.target : e.target.baseVal, + o = e instanceof HTMLElement ? e.href : e.href.baseVal, + r = new URL(o, location.href).origin; + F(e) || + e.hasAttribute("download") || + !e.href || + (n && n !== "_self") || + r !== location.origin || + t.button !== 0 || + t.metaKey || + t.ctrlKey || + t.altKey || + t.shiftKey || + t.defaultPrevented || + (t.preventDefault(), + N(o, { + history: + e.dataset.astroHistory === "replace" ? "replace" : "auto", + sourceElement: e, + })); + }), + document.addEventListener("submit", (t) => { + let e = t.target; + if (e.tagName !== "FORM" || t.defaultPrevented || F(e)) return; + const n = e, + o = t.submitter, + r = new FormData(n, o), + s = + typeof n.action == "string" + ? n.action + : n.getAttribute("action"), + u = + typeof n.method == "string" + ? n.method + : n.getAttribute("method"); + let a = o?.getAttribute("formaction") ?? s ?? location.pathname; + const l = o?.getAttribute("formmethod") ?? u ?? "get"; + if ( + l === "dialog" || + location.origin !== new URL(a, location.href).origin + ) + return; + const d = { sourceElement: o ?? n }; + if (l === "get") { + const c = new URLSearchParams(r), + i = new URL(a); + (i.search = c.toString()), (a = i.toString()); + } else d.formData = r; + t.preventDefault(), N(a, d); + }), + q({ prefetchAll: !0 })); +//# sourceMappingURL=ClientRouter.astro_astro_type_script_index_0_lang.ZAtydGN1.js.map diff --git a/Target/_astro/index.BqqcOND9.js b/Target/_astro/index.BqqcOND9.js index 22036b7d..e32b207c 100644 --- a/Target/_astro/index.BqqcOND9.js +++ b/Target/_astro/index.BqqcOND9.js @@ -1 +1,155 @@ -const d=new Set,c=new WeakSet;let f=!0,h="hover",l=!1;function L(e){l||(l=!0,f??=e?.prefetchAll??!1,h??=e?.defaultStrategy??"hover",m(),g(),v(),S())}function m(){for(const e of["touchstart","mousedown"])document.body.addEventListener(e,(e=>{i(e.target,"tap")&&s(e.target.href,{ignoreSlowConnection:!0})}),{passive:!0})}function g(){let e;function t(t){const n=t.target.href;e&&clearTimeout(e),e=setTimeout((()=>{s(n)}),80)}function n(){e&&(clearTimeout(e),e=0)}document.body.addEventListener("focusin",(e=>{i(e.target,"hover")&&t(e)}),{passive:!0}),document.body.addEventListener("focusout",n,{passive:!0}),u((()=>{for(const e of document.getElementsByTagName("a"))c.has(e)||i(e,"hover")&&(c.add(e),e.addEventListener("mouseenter",t,{passive:!0}),e.addEventListener("mouseleave",n,{passive:!0}))}))}function v(){let e;u((()=>{for(const t of document.getElementsByTagName("a"))c.has(t)||i(t,"viewport")&&(c.add(t),e??=y(),e.observe(t))}))}function y(){const e=new WeakMap;return new IntersectionObserver(((t,n)=>{for(const o of t){const t=o.target,r=e.get(t);o.isIntersecting?(r&&clearTimeout(r),e.set(t,setTimeout((()=>{n.unobserve(t),e.delete(t),s(t.href)}),300))):r&&(clearTimeout(r),e.delete(t))}}))}function S(){u((()=>{for(const e of document.getElementsByTagName("a"))i(e,"load")&&s(e.href)}))}function s(e,t){if(w(e=e.replace(/#.*/,""),t?.ignoreSlowConnection??!1))if(d.add(e),HTMLScriptElement.supports?.("speculationrules"))E(e);else if(document.createElement("link").relList?.supports?.("prefetch")&&"fetch"!==t?.with){const t=document.createElement("link");t.rel="prefetch",t.setAttribute("href",e),document.head.append(t)}else fetch(e,{priority:"low"})}function w(e,t){if(!navigator.onLine||!t&&p())return!1;try{const t=new URL(e,location.href);return location.origin===t.origin&&(location.pathname!==t.pathname||location.search!==t.search)&&!d.has(e)}catch{}return!1}function i(e,t){if("A"!==e?.tagName)return!1;const n=e.dataset.astroPrefetch;return"false"!==n&&(!("tap"!==t||null==n&&!f||!p())||(null==n&&f||""===n?t===h:n===t))}function p(){if("connection"in navigator){const e=navigator.connection;return e.saveData||/2g/.test(e.effectiveType)}return!1}function u(e){e();let t=!1;document.addEventListener("astro:page-load",(()=>{t?e():t=!0}))}function E(e){const t=document.createElement("script");t.type="speculationrules",t.textContent=JSON.stringify({prerender:[{source:"list",urls:[e]}],prefetch:[{source:"list",urls:[e]}]}),document.head.append(t)}export{L as i}; \ No newline at end of file +const d = new Set(), + c = new WeakSet(); +let f = !0, + h = "hover", + l = !1; +function L(e) { + l || + ((l = !0), + (f ??= e?.prefetchAll ?? !1), + (h ??= e?.defaultStrategy ?? "hover"), + m(), + g(), + v(), + S()); +} +function m() { + for (const e of ["touchstart", "mousedown"]) + document.body.addEventListener( + e, + (t) => { + i(t.target, "tap") && + s(t.target.href, { ignoreSlowConnection: !0 }); + }, + { passive: !0 }, + ); +} +function g() { + let e; + document.body.addEventListener( + "focusin", + (n) => { + i(n.target, "hover") && t(n); + }, + { passive: !0 }, + ), + document.body.addEventListener("focusout", r, { passive: !0 }), + u(() => { + for (const n of document.getElementsByTagName("a")) + c.has(n) || + (i(n, "hover") && + (c.add(n), + n.addEventListener("mouseenter", t, { passive: !0 }), + n.addEventListener("mouseleave", r, { passive: !0 }))); + }); + function t(n) { + const o = n.target.href; + e && clearTimeout(e), + (e = setTimeout(() => { + s(o); + }, 80)); + } + function r() { + e && (clearTimeout(e), (e = 0)); + } +} +function v() { + let e; + u(() => { + for (const t of document.getElementsByTagName("a")) + c.has(t) || + (i(t, "viewport") && (c.add(t), (e ??= y()), e.observe(t))); + }); +} +function y() { + const e = new WeakMap(); + return new IntersectionObserver((t, r) => { + for (const n of t) { + const o = n.target, + a = e.get(o); + n.isIntersecting + ? (a && clearTimeout(a), + e.set( + o, + setTimeout(() => { + r.unobserve(o), e.delete(o), s(o.href); + }, 300), + )) + : a && (clearTimeout(a), e.delete(o)); + } + }); +} +function S() { + u(() => { + for (const e of document.getElementsByTagName("a")) + i(e, "load") && s(e.href); + }); +} +function s(e, t) { + e = e.replace(/#.*/, ""); + const r = t?.ignoreSlowConnection ?? !1; + if (w(e, r)) + if ((d.add(e), HTMLScriptElement.supports?.("speculationrules"))) E(e); + else if ( + document.createElement("link").relList?.supports?.("prefetch") && + t?.with !== "fetch" + ) { + const n = document.createElement("link"); + (n.rel = "prefetch"), + n.setAttribute("href", e), + document.head.append(n); + } else fetch(e, { priority: "low" }); +} +function w(e, t) { + if (!navigator.onLine || (!t && p())) return !1; + try { + const r = new URL(e, location.href); + return ( + location.origin === r.origin && + (location.pathname !== r.pathname || + location.search !== r.search) && + !d.has(e) + ); + } catch {} + return !1; +} +function i(e, t) { + if (e?.tagName !== "A") return !1; + const r = e.dataset.astroPrefetch; + return r === "false" + ? !1 + : t === "tap" && (r != null || f) && p() + ? !0 + : (r == null && f) || r === "" + ? t === h + : r === t; +} +function p() { + if ("connection" in navigator) { + const e = navigator.connection; + return e.saveData || /2g/.test(e.effectiveType); + } + return !1; +} +function u(e) { + e(); + let t = !1; + document.addEventListener("astro:page-load", () => { + if (!t) { + t = !0; + return; + } + e(); + }); +} +function E(e) { + const t = document.createElement("script"); + (t.type = "speculationrules"), + (t.textContent = JSON.stringify({ + prerender: [{ source: "list", urls: [e] }], + prefetch: [{ source: "list", urls: [e] }], + })), + document.head.append(t); +} +export { L as i }; +//# sourceMappingURL=index.BqqcOND9.js.map diff --git a/Target/_astro/index.esm.CIXTrynS.js b/Target/_astro/index.esm.CIXTrynS.js index 7d4e8bda..2c6890b1 100644 --- a/Target/_astro/index.esm.CIXTrynS.js +++ b/Target/_astro/index.esm.CIXTrynS.js @@ -1 +1,1503 @@ -var L={};const W=function(e){const t=[];let r=0;for(let n=0;n>6|192,t[r++]=63&a|128):55296==(64512&a)&&n+1>18|240,t[r++]=a>>12&63|128,t[r++]=a>>6&63|128,t[r++]=63&a|128):(t[r++]=a>>12|224,t[r++]=a>>6&63|128,t[r++]=63&a|128)}return t},ee=function(e){const t=[];let r=0,n=0;for(;r191&&a<224){const i=e[r++];t[n++]=String.fromCharCode((31&a)<<6|63&i)}else if(a>239&&a<365){const i=((7&a)<<18|(63&e[r++])<<12|(63&e[r++])<<6|63&e[r++])-65536;t[n++]=String.fromCharCode(55296+(i>>10)),t[n++]=String.fromCharCode(56320+(1023&i))}else{const i=e[r++],s=e[r++];t[n++]=String.fromCharCode((15&a)<<12|(63&i)<<6|63&s)}}return t.join("")},G={byteToCharMap_:null,charToByteMap_:null,byteToCharMapWebSafe_:null,charToByteMapWebSafe_:null,ENCODED_VALS_BASE:"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789",get ENCODED_VALS(){return this.ENCODED_VALS_BASE+"+/="},get ENCODED_VALS_WEBSAFE(){return this.ENCODED_VALS_BASE+"-_."},HAS_NATIVE_SUPPORT:"function"==typeof atob,encodeByteArray(e,t){if(!Array.isArray(e))throw Error("encodeByteArray takes an array as a parameter");this.init_();const r=t?this.byteToCharMapWebSafe_:this.byteToCharMap_,n=[];for(let t=0;t>2,l=(3&a)<<4|s>>4;let d=(15&s)<<2|c>>6,u=63&c;o||(u=64,i||(d=64)),n.push(r[h],r[l],r[d],r[u])}return n.join("")},encodeString(e,t){return this.HAS_NATIVE_SUPPORT&&!t?btoa(e):this.encodeByteArray(W(e),t)},decodeString(e,t){return this.HAS_NATIVE_SUPPORT&&!t?atob(e):ee(this.decodeStringToByteArray(e,t))},decodeStringToByteArray(e,t){this.init_();const r=t?this.charToByteMapWebSafe_:this.charToByteMap_,n=[];for(let t=0;t>4;if(n.push(c),64!==s){const e=i<<4&240|s>>2;if(n.push(e),64!==o){const e=s<<6&192|o;n.push(e)}}}return n},init_(){if(!this.byteToCharMap_){this.byteToCharMap_={},this.charToByteMap_={},this.byteToCharMapWebSafe_={},this.charToByteMapWebSafe_={};for(let e=0;e=this.ENCODED_VALS_BASE.length&&(this.charToByteMap_[this.ENCODED_VALS_WEBSAFE.charAt(e)]=e,this.charToByteMapWebSafe_[this.ENCODED_VALS.charAt(e)]=e)}}};class te extends Error{constructor(){super(...arguments),this.name="DecodeBase64StringError"}}const ne=function(e){const t=W(e);return G.encodeByteArray(t,!0)},J=function(e){return ne(e).replace(/\./g,"")},re=function(e){try{return G.decodeString(e,!0)}catch(e){console.error("base64Decode failed: ",e)}return null};function se(){if(typeof self<"u")return self;if(typeof window<"u")return window;if(typeof global<"u")return global;throw new Error("Unable to locate global object.")}const ae=()=>se().__FIREBASE_DEFAULTS__,ie=()=>{if(typeof process>"u"||typeof L>"u")return;const e=L.__FIREBASE_DEFAULTS__;return e?JSON.parse(e):void 0},oe=()=>{if(typeof document>"u")return;let e;try{e=document.cookie.match(/__FIREBASE_DEFAULTS__=([^;]+)/)}catch{return}const t=e&&re(e[1]);return t&&JSON.parse(t)},ce=()=>{try{return ae()||ie()||oe()}catch(e){return void console.info(`Unable to get __FIREBASE_DEFAULTS__ due to: ${e}`)}},he=()=>{var e;return null===(e=ce())||void 0===e?void 0:e.config};class le{constructor(){this.reject=()=>{},this.resolve=()=>{},this.promise=new Promise(((e,t)=>{this.resolve=e,this.reject=t}))}wrapCallback(e){return(t,r)=>{t?this.reject(t):this.resolve(r),"function"==typeof e&&(this.promise.catch((()=>{})),1===e.length?e(t):e(t,r))}}}function de(){try{return"object"==typeof indexedDB}catch{return!1}}function fe(){return new Promise(((e,t)=>{try{let r=!0;const n="validate-browser-context-for-indexeddb-analytics-module",a=self.indexedDB.open(n);a.onsuccess=()=>{a.result.close(),r||self.indexedDB.deleteDatabase(n),e(!0)},a.onupgradeneeded=()=>{r=!1},a.onerror=()=>{var e;t((null===(e=a.error)||void 0===e?void 0:e.message)||"")}}catch(e){t(e)}}))}const ue="FirebaseError";class b extends Error{constructor(e,t,r){super(t),this.code=e,this.customData=r,this.name=ue,Object.setPrototypeOf(this,b.prototype),Error.captureStackTrace&&Error.captureStackTrace(this,K.prototype.create)}}class K{constructor(e,t,r){this.service=e,this.serviceName=t,this.errors=r}create(e,...t){const r=t[0]||{},n=`${this.service}/${e}`,a=this.errors[e],i=a?pe(a,r):"Error",s=`${this.serviceName}: ${i} (${n}).`;return new b(n,s,r)}}function pe(e,t){return e.replace(me,((e,r)=>{const n=t[r];return null!=n?String(n):`<${r}?>`}))}const me=/\{\$([^}]+)}/g;function v(e,t){if(e===t)return!0;const r=Object.keys(e),n=Object.keys(t);for(const a of r){if(!n.includes(a))return!1;const r=e[a],i=t[a];if(H(r)&&H(i)){if(!v(r,i))return!1}else if(r!==i)return!1}for(const e of n)if(!r.includes(e))return!1;return!0}function H(e){return null!==e&&"object"==typeof e}class D{constructor(e,t,r){this.name=e,this.instanceFactory=t,this.type=r,this.multipleInstances=!1,this.serviceProps={},this.instantiationMode="LAZY",this.onInstanceCreated=null}setInstantiationMode(e){return this.instantiationMode=e,this}setMultipleInstances(e){return this.multipleInstances=e,this}setServiceProps(e){return this.serviceProps=e,this}setInstanceCreatedCallback(e){return this.onInstanceCreated=e,this}}const u="[DEFAULT]";class ge{constructor(e,t){this.name=e,this.container=t,this.component=null,this.instances=new Map,this.instancesDeferred=new Map,this.instancesOptions=new Map,this.onInitCallbacks=new Map}get(e){const t=this.normalizeInstanceIdentifier(e);if(!this.instancesDeferred.has(t)){const e=new le;if(this.instancesDeferred.set(t,e),this.isInitialized(t)||this.shouldAutoInitialize())try{const r=this.getOrInitializeService({instanceIdentifier:t});r&&e.resolve(r)}catch{}}return this.instancesDeferred.get(t).promise}getImmediate(e){var t;const r=this.normalizeInstanceIdentifier(e?.identifier),n=null!==(t=e?.optional)&&void 0!==t&&t;if(!this.isInitialized(r)&&!this.shouldAutoInitialize()){if(n)return null;throw Error(`Service ${this.name} is not available`)}try{return this.getOrInitializeService({instanceIdentifier:r})}catch(e){if(n)return null;throw e}}getComponent(){return this.component}setComponent(e){if(e.name!==this.name)throw Error(`Mismatching Component ${e.name} for Provider ${this.name}.`);if(this.component)throw Error(`Component for ${this.name} has already been provided`);if(this.component=e,this.shouldAutoInitialize()){if(_e(e))try{this.getOrInitializeService({instanceIdentifier:u})}catch{}for(const[e,t]of this.instancesDeferred.entries()){const r=this.normalizeInstanceIdentifier(e);try{const e=this.getOrInitializeService({instanceIdentifier:r});t.resolve(e)}catch{}}}}clearInstance(e=u){this.instancesDeferred.delete(e),this.instancesOptions.delete(e),this.instances.delete(e)}async delete(){const e=Array.from(this.instances.values());await Promise.all([...e.filter((e=>"INTERNAL"in e)).map((e=>e.INTERNAL.delete())),...e.filter((e=>"_delete"in e)).map((e=>e._delete()))])}isComponentSet(){return null!=this.component}isInitialized(e=u){return this.instances.has(e)}getOptions(e=u){return this.instancesOptions.get(e)||{}}initialize(e={}){const{options:t={}}=e,r=this.normalizeInstanceIdentifier(e.instanceIdentifier);if(this.isInitialized(r))throw Error(`${this.name}(${r}) has already been initialized`);if(!this.isComponentSet())throw Error(`Component ${this.name} has not been registered yet`);const n=this.getOrInitializeService({instanceIdentifier:r,options:t});for(const[e,t]of this.instancesDeferred.entries()){r===this.normalizeInstanceIdentifier(e)&&t.resolve(n)}return n}onInit(e,t){var r;const n=this.normalizeInstanceIdentifier(t),a=null!==(r=this.onInitCallbacks.get(n))&&void 0!==r?r:new Set;a.add(e),this.onInitCallbacks.set(n,a);const i=this.instances.get(n);return i&&e(i,n),()=>{a.delete(e)}}invokeOnInitCallbacks(e,t){const r=this.onInitCallbacks.get(t);if(r)for(const n of r)try{n(e,t)}catch{}}getOrInitializeService({instanceIdentifier:e,options:t={}}){let r=this.instances.get(e);if(!r&&this.component&&(r=this.component.instanceFactory(this.container,{instanceIdentifier:be(e),options:t}),this.instances.set(e,r),this.instancesOptions.set(e,t),this.invokeOnInitCallbacks(r,e),this.component.onInstanceCreated))try{this.component.onInstanceCreated(this.container,e,r)}catch{}return r||null}normalizeInstanceIdentifier(e=u){return this.component?this.component.multipleInstances?e:u:e}shouldAutoInitialize(){return!!this.component&&"EXPLICIT"!==this.component.instantiationMode}}function be(e){return e===u?void 0:e}function _e(e){return"EAGER"===e.instantiationMode}class Ee{constructor(e){this.name=e,this.providers=new Map}addComponent(e){const t=this.getProvider(e.name);if(t.isComponentSet())throw new Error(`Component ${e.name} has already been registered with ${this.name}`);t.setComponent(e)}addOrOverwriteComponent(e){this.getProvider(e.name).isComponentSet()&&this.providers.delete(e.name),this.addComponent(e)}getProvider(e){if(this.providers.has(e))return this.providers.get(e);const t=new ge(e,this);return this.providers.set(e,t),t}getProviders(){return Array.from(this.providers.values())}}var h;!function(e){e[e.DEBUG=0]="DEBUG",e[e.VERBOSE=1]="VERBOSE",e[e.INFO=2]="INFO",e[e.WARN=3]="WARN",e[e.ERROR=4]="ERROR",e[e.SILENT=5]="SILENT"}(h||(h={}));const ye={debug:h.DEBUG,verbose:h.VERBOSE,info:h.INFO,warn:h.WARN,error:h.ERROR,silent:h.SILENT},De=h.INFO,Ie={[h.DEBUG]:"log",[h.VERBOSE]:"log",[h.INFO]:"info",[h.WARN]:"warn",[h.ERROR]:"error"},we=(e,t,...r)=>{if(tt.some((t=>e instanceof t));let P,F;function ve(){return P||(P=[IDBDatabase,IDBObjectStore,IDBIndex,IDBCursor,IDBTransaction])}function Ae(){return F||(F=[IDBCursor.prototype.advance,IDBCursor.prototype.continue,IDBCursor.prototype.continuePrimaryKey])}const Y=new WeakMap,A=new WeakMap,X=new WeakMap,I=new WeakMap,N=new WeakMap;function Be(e){const t=new Promise(((t,r)=>{const n=()=>{e.removeEventListener("success",a),e.removeEventListener("error",i)},a=()=>{t(f(e.result)),n()},i=()=>{r(e.error),n()};e.addEventListener("success",a),e.addEventListener("error",i)}));return t.then((t=>{t instanceof IDBCursor&&Y.set(t,e)})).catch((()=>{})),N.set(t,e),t}function Oe(e){if(A.has(e))return;const t=new Promise(((t,r)=>{const n=()=>{e.removeEventListener("complete",a),e.removeEventListener("error",i),e.removeEventListener("abort",i)},a=()=>{t(),n()},i=()=>{r(e.error||new DOMException("AbortError","AbortError")),n()};e.addEventListener("complete",a),e.addEventListener("error",i),e.addEventListener("abort",i)}));A.set(e,t)}let B={get(e,t,r){if(e instanceof IDBTransaction){if("done"===t)return A.get(e);if("objectStoreNames"===t)return e.objectStoreNames||X.get(e);if("store"===t)return r.objectStoreNames[1]?void 0:r.objectStore(r.objectStoreNames[0])}return f(e[t])},set:(e,t,r)=>(e[t]=r,!0),has:(e,t)=>e instanceof IDBTransaction&&("done"===t||"store"===t)||t in e};function Te(e){B=e(B)}function Me(e){return e!==IDBDatabase.prototype.transaction||"objectStoreNames"in IDBTransaction.prototype?Ae().includes(e)?function(...t){return e.apply(w(this),t),f(Y.get(this))}:function(...t){return f(e.apply(w(this),t))}:function(t,...r){const n=e.call(w(this),t,...r);return X.set(n,t.sort?t.sort():[t]),f(n)}}function $e(e){return"function"==typeof e?Me(e):(e instanceof IDBTransaction&&Oe(e),Ce(e,ve())?new Proxy(e,B):e)}function f(e){if(e instanceof IDBRequest)return Be(e);if(I.has(e))return I.get(e);const t=$e(e);return t!==e&&(I.set(e,t),N.set(t,e)),t}const w=e=>N.get(e);function Ne(e,t,{blocked:r,upgrade:n,blocking:a,terminated:i}={}){const s=indexedDB.open(e,t),o=f(s);return n&&s.addEventListener("upgradeneeded",(e=>{n(f(s.result),e.oldVersion,e.newVersion,f(s.transaction),e)})),r&&s.addEventListener("blocked",(e=>r(e.oldVersion,e.newVersion,e))),o.then((e=>{i&&e.addEventListener("close",(()=>i())),a&&e.addEventListener("versionchange",(e=>a(e.oldVersion,e.newVersion,e)))})).catch((()=>{})),o}const Re=["get","getKey","getAll","getAllKeys","count"],Le=["put","add","delete","clear"],S=new Map;function x(e,t){if(!(e instanceof IDBDatabase)||t in e||"string"!=typeof t)return;if(S.get(t))return S.get(t);const r=t.replace(/FromIndex$/,""),n=t!==r,a=Le.includes(r);if(!(r in(n?IDBIndex:IDBObjectStore).prototype)||!a&&!Re.includes(r))return;const i=async function(e,...t){const i=this.transaction(e,a?"readwrite":"readonly");let s=i.store;return n&&(s=s.index(t.shift())),(await Promise.all([s[r](...t),a&&i.done]))[0]};return S.set(t,i),i}Te((e=>({...e,get:(t,r,n)=>x(t,r)||e.get(t,r,n),has:(t,r)=>!!x(t,r)||e.has(t,r)})));class He{constructor(e){this.container=e}getPlatformInfoString(){return this.container.getProviders().map((e=>{if(Pe(e)){const t=e.getImmediate();return`${t.library}/${t.version}`}return null})).filter((e=>e)).join(" ")}}function Pe(e){const t=e.getComponent();return"VERSION"===t?.type}const O="@firebase/app",V="0.10.17",d=new Se("@firebase/app"),Fe="@firebase/app-compat",xe="@firebase/analytics-compat",Ve="@firebase/analytics",je="@firebase/app-check-compat",ke="@firebase/app-check",ze="@firebase/auth",Ue="@firebase/auth-compat",We="@firebase/database",Ge="@firebase/data-connect",Je="@firebase/database-compat",Ke="@firebase/functions",Ye="@firebase/functions-compat",Xe="@firebase/installations",Ze="@firebase/installations-compat",qe="@firebase/messaging",Qe="@firebase/messaging-compat",et="@firebase/performance",tt="@firebase/performance-compat",nt="@firebase/remote-config",rt="@firebase/remote-config-compat",st="@firebase/storage",at="@firebase/storage-compat",it="@firebase/firestore",ot="@firebase/vertexai",ct="@firebase/firestore-compat",ht="firebase",lt="[DEFAULT]",dt={[O]:"fire-core",[Fe]:"fire-core-compat",[Ve]:"fire-analytics",[xe]:"fire-analytics-compat",[ke]:"fire-app-check",[je]:"fire-app-check-compat",[ze]:"fire-auth",[Ue]:"fire-auth-compat",[We]:"fire-rtdb",[Ge]:"fire-data-connect",[Je]:"fire-rtdb-compat",[Ke]:"fire-fn",[Ye]:"fire-fn-compat",[Xe]:"fire-iid",[Ze]:"fire-iid-compat",[qe]:"fire-fcm",[Qe]:"fire-fcm-compat",[et]:"fire-perf",[tt]:"fire-perf-compat",[nt]:"fire-rc",[rt]:"fire-rc-compat",[st]:"fire-gcs",[at]:"fire-gcs-compat",[it]:"fire-fst",[ct]:"fire-fst-compat",[ot]:"fire-vertex","fire-js":"fire-js",[ht]:"fire-js-all"},T=new Map,ft=new Map,M=new Map;function j(e,t){try{e.container.addComponent(t)}catch(r){d.debug(`Component ${t.name} failed to register with FirebaseApp ${e.name}`,r)}}function $(e){const t=e.name;if(M.has(t))return d.debug(`There were multiple attempts to register component ${t}.`),!1;M.set(t,e);for(const t of T.values())j(t,e);for(const t of ft.values())j(t,e);return!0}const ut={"no-app":"No Firebase App '{$appName}' has been created - call initializeApp() first","bad-app-name":"Illegal App name: '{$appName}'","duplicate-app":"Firebase App named '{$appName}' already exists with different options or config","app-deleted":"Firebase App named '{$appName}' already deleted","server-app-deleted":"Firebase Server App has been deleted","no-options":"Need to provide options, when not being deployed to hosting via source.","invalid-app-argument":"firebase.{$appName}() takes either no argument or a Firebase App instance.","invalid-log-argument":"First argument to `onLog` must be null or a function.","idb-open":"Error thrown when opening IndexedDB. Original error: {$originalErrorMessage}.","idb-get":"Error thrown when reading from IndexedDB. Original error: {$originalErrorMessage}.","idb-set":"Error thrown when writing to IndexedDB. Original error: {$originalErrorMessage}.","idb-delete":"Error thrown when deleting from IndexedDB. Original error: {$originalErrorMessage}.","finalization-registry-not-supported":"FirebaseServerApp deleteOnDeref field defined but the JS runtime does not support FinalizationRegistry.","invalid-server-app-environment":"FirebaseServerApp is not for use in browser environments."},p=new K("app","Firebase",ut);class pt{constructor(e,t,r){this._isDeleted=!1,this._options=Object.assign({},e),this._config=Object.assign({},t),this._name=t.name,this._automaticDataCollectionEnabled=t.automaticDataCollectionEnabled,this._container=r,this.container.addComponent(new D("app",(()=>this),"PUBLIC"))}get automaticDataCollectionEnabled(){return this.checkDestroyed(),this._automaticDataCollectionEnabled}set automaticDataCollectionEnabled(e){this.checkDestroyed(),this._automaticDataCollectionEnabled=e}get name(){return this.checkDestroyed(),this._name}get options(){return this.checkDestroyed(),this._options}get config(){return this.checkDestroyed(),this._config}get container(){return this._container}get isDeleted(){return this._isDeleted}set isDeleted(e){this._isDeleted=e}checkDestroyed(){if(this.isDeleted)throw p.create("app-deleted",{appName:this._name})}}function vt(e,t={}){let r=e;"object"!=typeof t&&(t={name:t});const n=Object.assign({name:lt,automaticDataCollectionEnabled:!1},t),a=n.name;if("string"!=typeof a||!a)throw p.create("bad-app-name",{appName:String(a)});if(r||(r=he()),!r)throw p.create("no-options");const i=T.get(a);if(i){if(v(r,i.options)&&v(n,i.config))return i;throw p.create("duplicate-app",{appName:a})}const s=new Ee(a);for(const e of M.values())s.addComponent(e);const o=new pt(r,n,s);return T.set(a,o),o}function y(e,t,r){var n;let a=null!==(n=dt[e])&&void 0!==n?n:e;r&&(a+=`-${r}`);const i=a.match(/\s|\//),s=t.match(/\s|\//);if(i||s){const e=[`Unable to register library "${a}" with version "${t}":`];return i&&e.push(`library name "${a}" contains illegal characters (whitespace or "/")`),i&&s&&e.push("and"),s&&e.push(`version name "${t}" contains illegal characters (whitespace or "/")`),void d.warn(e.join(" "))}$(new D(`${a}-version`,(()=>({library:a,version:t})),"VERSION"))}const mt="firebase-heartbeat-database",gt=1,g="firebase-heartbeat-store";let C=null;function Z(){return C||(C=Ne(mt,1,{upgrade:(e,t)=>{if(0===t)try{e.createObjectStore(g)}catch(e){console.warn(e)}}}).catch((e=>{throw p.create("idb-open",{originalErrorMessage:e.message})}))),C}async function bt(e){try{const t=(await Z()).transaction(g),r=await t.objectStore(g).get(q(e));return await t.done,r}catch(e){if(e instanceof b)d.warn(e.message);else{const t=p.create("idb-get",{originalErrorMessage:e?.message});d.warn(t.message)}}}async function k(e,t){try{const r=(await Z()).transaction(g,"readwrite");await r.objectStore(g).put(t,q(e)),await r.done}catch(e){if(e instanceof b)d.warn(e.message);else{const t=p.create("idb-set",{originalErrorMessage:e?.message});d.warn(t.message)}}}function q(e){return`${e.name}!${e.options.appId}`}const _t=1024,Et=2592e6;class yt{constructor(e){this.container=e,this._heartbeatsCache=null;const t=this.container.getProvider("app").getImmediate();this._storage=new It(t),this._heartbeatsCachePromise=this._storage.read().then((e=>(this._heartbeatsCache=e,e)))}async triggerHeartbeat(){var e,t;try{const r=this.container.getProvider("platform-logger").getImmediate().getPlatformInfoString(),n=z();return null==(null===(e=this._heartbeatsCache)||void 0===e?void 0:e.heartbeats)&&(this._heartbeatsCache=await this._heartbeatsCachePromise,null==(null===(t=this._heartbeatsCache)||void 0===t?void 0:t.heartbeats))||this._heartbeatsCache.lastSentHeartbeatDate===n||this._heartbeatsCache.heartbeats.some((e=>e.date===n))?void 0:(this._heartbeatsCache.heartbeats.push({date:n,agent:r}),this._heartbeatsCache.heartbeats=this._heartbeatsCache.heartbeats.filter((e=>{const t=new Date(e.date).valueOf();return Date.now()-t<=Et})),this._storage.overwrite(this._heartbeatsCache))}catch(e){d.warn(e)}}async getHeartbeatsHeader(){var e;try{if(null===this._heartbeatsCache&&await this._heartbeatsCachePromise,null==(null===(e=this._heartbeatsCache)||void 0===e?void 0:e.heartbeats)||0===this._heartbeatsCache.heartbeats.length)return"";const t=z(),{heartbeatsToSend:r,unsentEntries:n}=Dt(this._heartbeatsCache.heartbeats),a=J(JSON.stringify({version:2,heartbeats:r}));return this._heartbeatsCache.lastSentHeartbeatDate=t,n.length>0?(this._heartbeatsCache.heartbeats=n,await this._storage.overwrite(this._heartbeatsCache)):(this._heartbeatsCache.heartbeats=[],this._storage.overwrite(this._heartbeatsCache)),a}catch(e){return d.warn(e),""}}}function z(){return(new Date).toISOString().substring(0,10)}function Dt(e,t=_t){const r=[];let n=e.slice();for(const a of e){const e=r.find((e=>e.agent===a.agent));if(e){if(e.dates.push(a.date),U(r)>t){e.dates.pop();break}}else if(r.push({agent:a.agent,dates:[a.date]}),U(r)>t){r.pop();break}n=n.slice(1)}return{heartbeatsToSend:r,unsentEntries:n}}class It{constructor(e){this.app=e,this._canUseIndexedDBPromise=this.runIndexedDBEnvironmentCheck()}async runIndexedDBEnvironmentCheck(){return!!de()&&fe().then((()=>!0)).catch((()=>!1))}async read(){if(await this._canUseIndexedDBPromise){const e=await bt(this.app);return e?.heartbeats?e:{heartbeats:[]}}return{heartbeats:[]}}async overwrite(e){var t;if(await this._canUseIndexedDBPromise){const r=await this.read();return k(this.app,{lastSentHeartbeatDate:null!==(t=e.lastSentHeartbeatDate)&&void 0!==t?t:r.lastSentHeartbeatDate,heartbeats:e.heartbeats})}}async add(e){var t;if(await this._canUseIndexedDBPromise){const r=await this.read();return k(this.app,{lastSentHeartbeatDate:null!==(t=e.lastSentHeartbeatDate)&&void 0!==t?t:r.lastSentHeartbeatDate,heartbeats:[...r.heartbeats,...e.heartbeats]})}}}function U(e){return J(JSON.stringify({version:2,heartbeats:e})).length}function wt(e){$(new D("platform-logger",(e=>new He(e)),"PRIVATE")),$(new D("heartbeat",(e=>new yt(e)),"PRIVATE")),y(O,V,e),y(O,V,"esm2017"),y("fire-js","")}wt("");var St="firebase",Ct="11.1.0";y(St,Ct,"app");export{b as FirebaseError,lt as _DEFAULT_ENTRY_NAME,j as _addComponent,T as _apps,M as _components,$ as _registerComponent,ft as _serverApps,vt as initializeApp,y as registerVersion}; \ No newline at end of file +var L = {}; /** + * @license + * Copyright 2017 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const W = function (t) { + const e = []; + let n = 0; + for (let s = 0; s < t.length; s++) { + let r = t.charCodeAt(s); + r < 128 + ? (e[n++] = r) + : r < 2048 + ? ((e[n++] = (r >> 6) | 192), (e[n++] = (r & 63) | 128)) + : (r & 64512) === 55296 && + s + 1 < t.length && + (t.charCodeAt(s + 1) & 64512) === 56320 + ? ((r = + 65536 + + ((r & 1023) << 10) + + (t.charCodeAt(++s) & 1023)), + (e[n++] = (r >> 18) | 240), + (e[n++] = ((r >> 12) & 63) | 128), + (e[n++] = ((r >> 6) & 63) | 128), + (e[n++] = (r & 63) | 128)) + : ((e[n++] = (r >> 12) | 224), + (e[n++] = ((r >> 6) & 63) | 128), + (e[n++] = (r & 63) | 128)); + } + return e; + }, + ee = function (t) { + const e = []; + let n = 0, + s = 0; + for (; n < t.length; ) { + const r = t[n++]; + if (r < 128) e[s++] = String.fromCharCode(r); + else if (r > 191 && r < 224) { + const a = t[n++]; + e[s++] = String.fromCharCode(((r & 31) << 6) | (a & 63)); + } else if (r > 239 && r < 365) { + const a = t[n++], + i = t[n++], + o = t[n++], + c = + (((r & 7) << 18) | + ((a & 63) << 12) | + ((i & 63) << 6) | + (o & 63)) - + 65536; + (e[s++] = String.fromCharCode(55296 + (c >> 10))), + (e[s++] = String.fromCharCode(56320 + (c & 1023))); + } else { + const a = t[n++], + i = t[n++]; + e[s++] = String.fromCharCode( + ((r & 15) << 12) | ((a & 63) << 6) | (i & 63), + ); + } + } + return e.join(""); + }, + G = { + byteToCharMap_: null, + charToByteMap_: null, + byteToCharMapWebSafe_: null, + charToByteMapWebSafe_: null, + ENCODED_VALS_BASE: + "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789", + get ENCODED_VALS() { + return this.ENCODED_VALS_BASE + "+/="; + }, + get ENCODED_VALS_WEBSAFE() { + return this.ENCODED_VALS_BASE + "-_."; + }, + HAS_NATIVE_SUPPORT: typeof atob == "function", + encodeByteArray(t, e) { + if (!Array.isArray(t)) + throw Error("encodeByteArray takes an array as a parameter"); + this.init_(); + const n = e ? this.byteToCharMapWebSafe_ : this.byteToCharMap_, + s = []; + for (let r = 0; r < t.length; r += 3) { + const a = t[r], + i = r + 1 < t.length, + o = i ? t[r + 1] : 0, + c = r + 2 < t.length, + l = c ? t[r + 2] : 0, + R = a >> 2, + m = ((a & 3) << 4) | (o >> 4); + let _ = ((o & 15) << 2) | (l >> 6), + E = l & 63; + c || ((E = 64), i || (_ = 64)), s.push(n[R], n[m], n[_], n[E]); + } + return s.join(""); + }, + encodeString(t, e) { + return this.HAS_NATIVE_SUPPORT && !e + ? btoa(t) + : this.encodeByteArray(W(t), e); + }, + decodeString(t, e) { + return this.HAS_NATIVE_SUPPORT && !e + ? atob(t) + : ee(this.decodeStringToByteArray(t, e)); + }, + decodeStringToByteArray(t, e) { + this.init_(); + const n = e ? this.charToByteMapWebSafe_ : this.charToByteMap_, + s = []; + for (let r = 0; r < t.length; ) { + const a = n[t.charAt(r++)], + o = r < t.length ? n[t.charAt(r)] : 0; + ++r; + const l = r < t.length ? n[t.charAt(r)] : 64; + ++r; + const m = r < t.length ? n[t.charAt(r)] : 64; + if ((++r, a == null || o == null || l == null || m == null)) + throw new te(); + const _ = (a << 2) | (o >> 4); + if ((s.push(_), l !== 64)) { + const E = ((o << 4) & 240) | (l >> 2); + if ((s.push(E), m !== 64)) { + const Q = ((l << 6) & 192) | m; + s.push(Q); + } + } + } + return s; + }, + init_() { + if (!this.byteToCharMap_) { + (this.byteToCharMap_ = {}), + (this.charToByteMap_ = {}), + (this.byteToCharMapWebSafe_ = {}), + (this.charToByteMapWebSafe_ = {}); + for (let t = 0; t < this.ENCODED_VALS.length; t++) + (this.byteToCharMap_[t] = this.ENCODED_VALS.charAt(t)), + (this.charToByteMap_[this.byteToCharMap_[t]] = t), + (this.byteToCharMapWebSafe_[t] = + this.ENCODED_VALS_WEBSAFE.charAt(t)), + (this.charToByteMapWebSafe_[ + this.byteToCharMapWebSafe_[t] + ] = t), + t >= this.ENCODED_VALS_BASE.length && + ((this.charToByteMap_[ + this.ENCODED_VALS_WEBSAFE.charAt(t) + ] = t), + (this.charToByteMapWebSafe_[ + this.ENCODED_VALS.charAt(t) + ] = t)); + } + }, + }; +class te extends Error { + constructor() { + super(...arguments), (this.name = "DecodeBase64StringError"); + } +} +const ne = function (t) { + const e = W(t); + return G.encodeByteArray(e, !0); + }, + J = function (t) { + return ne(t).replace(/\./g, ""); + }, + re = function (t) { + try { + return G.decodeString(t, !0); + } catch (e) { + console.error("base64Decode failed: ", e); + } + return null; + }; /** + * @license + * Copyright 2022 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +function se() { + if (typeof self < "u") return self; + if (typeof window < "u") return window; + if (typeof global < "u") return global; + throw new Error("Unable to locate global object."); +} /** + * @license + * Copyright 2022 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const ae = () => se().__FIREBASE_DEFAULTS__, + ie = () => { + if (typeof process > "u" || typeof L > "u") return; + const t = L.__FIREBASE_DEFAULTS__; + if (t) return JSON.parse(t); + }, + oe = () => { + if (typeof document > "u") return; + let t; + try { + t = document.cookie.match(/__FIREBASE_DEFAULTS__=([^;]+)/); + } catch { + return; + } + const e = t && re(t[1]); + return e && JSON.parse(e); + }, + ce = () => { + try { + return ae() || ie() || oe(); + } catch (t) { + console.info(`Unable to get __FIREBASE_DEFAULTS__ due to: ${t}`); + return; + } + }, + he = () => { + var t; + return (t = ce()) === null || t === void 0 ? void 0 : t.config; + }; /** + * @license + * Copyright 2017 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +class le { + constructor() { + (this.reject = () => {}), + (this.resolve = () => {}), + (this.promise = new Promise((e, n) => { + (this.resolve = e), (this.reject = n); + })); + } + wrapCallback(e) { + return (n, s) => { + n ? this.reject(n) : this.resolve(s), + typeof e == "function" && + (this.promise.catch(() => {}), + e.length === 1 ? e(n) : e(n, s)); + }; + } +} +function de() { + try { + return typeof indexedDB == "object"; + } catch { + return !1; + } +} +function fe() { + return new Promise((t, e) => { + try { + let n = !0; + const s = "validate-browser-context-for-indexeddb-analytics-module", + r = self.indexedDB.open(s); + (r.onsuccess = () => { + r.result.close(), n || self.indexedDB.deleteDatabase(s), t(!0); + }), + (r.onupgradeneeded = () => { + n = !1; + }), + (r.onerror = () => { + var a; + e( + ((a = r.error) === null || a === void 0 + ? void 0 + : a.message) || "", + ); + }); + } catch (n) { + e(n); + } + }); +} /** + * @license + * Copyright 2017 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const ue = "FirebaseError"; +class b extends Error { + constructor(e, n, s) { + super(n), + (this.code = e), + (this.customData = s), + (this.name = ue), + Object.setPrototypeOf(this, b.prototype), + Error.captureStackTrace && + Error.captureStackTrace(this, K.prototype.create); + } +} +class K { + constructor(e, n, s) { + (this.service = e), (this.serviceName = n), (this.errors = s); + } + create(e, ...n) { + const s = n[0] || {}, + r = `${this.service}/${e}`, + a = this.errors[e], + i = a ? pe(a, s) : "Error", + o = `${this.serviceName}: ${i} (${r}).`; + return new b(r, o, s); + } +} +function pe(t, e) { + return t.replace(me, (n, s) => { + const r = e[s]; + return r != null ? String(r) : `<${s}?>`; + }); +} +const me = /\{\$([^}]+)}/g; +function v(t, e) { + if (t === e) return !0; + const n = Object.keys(t), + s = Object.keys(e); + for (const r of n) { + if (!s.includes(r)) return !1; + const a = t[r], + i = e[r]; + if (H(a) && H(i)) { + if (!v(a, i)) return !1; + } else if (a !== i) return !1; + } + for (const r of s) if (!n.includes(r)) return !1; + return !0; +} +function H(t) { + return t !== null && typeof t == "object"; +} +class D { + constructor(e, n, s) { + (this.name = e), + (this.instanceFactory = n), + (this.type = s), + (this.multipleInstances = !1), + (this.serviceProps = {}), + (this.instantiationMode = "LAZY"), + (this.onInstanceCreated = null); + } + setInstantiationMode(e) { + return (this.instantiationMode = e), this; + } + setMultipleInstances(e) { + return (this.multipleInstances = e), this; + } + setServiceProps(e) { + return (this.serviceProps = e), this; + } + setInstanceCreatedCallback(e) { + return (this.onInstanceCreated = e), this; + } +} /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const u = "[DEFAULT]"; /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +class ge { + constructor(e, n) { + (this.name = e), + (this.container = n), + (this.component = null), + (this.instances = new Map()), + (this.instancesDeferred = new Map()), + (this.instancesOptions = new Map()), + (this.onInitCallbacks = new Map()); + } + get(e) { + const n = this.normalizeInstanceIdentifier(e); + if (!this.instancesDeferred.has(n)) { + const s = new le(); + if ( + (this.instancesDeferred.set(n, s), + this.isInitialized(n) || this.shouldAutoInitialize()) + ) + try { + const r = this.getOrInitializeService({ + instanceIdentifier: n, + }); + r && s.resolve(r); + } catch {} + } + return this.instancesDeferred.get(n).promise; + } + getImmediate(e) { + var n; + const s = this.normalizeInstanceIdentifier(e?.identifier), + r = (n = e?.optional) !== null && n !== void 0 ? n : !1; + if (this.isInitialized(s) || this.shouldAutoInitialize()) + try { + return this.getOrInitializeService({ instanceIdentifier: s }); + } catch (a) { + if (r) return null; + throw a; + } + else { + if (r) return null; + throw Error(`Service ${this.name} is not available`); + } + } + getComponent() { + return this.component; + } + setComponent(e) { + if (e.name !== this.name) + throw Error( + `Mismatching Component ${e.name} for Provider ${this.name}.`, + ); + if (this.component) + throw Error(`Component for ${this.name} has already been provided`); + if (((this.component = e), !!this.shouldAutoInitialize())) { + if (_e(e)) + try { + this.getOrInitializeService({ instanceIdentifier: u }); + } catch {} + for (const [n, s] of this.instancesDeferred.entries()) { + const r = this.normalizeInstanceIdentifier(n); + try { + const a = this.getOrInitializeService({ + instanceIdentifier: r, + }); + s.resolve(a); + } catch {} + } + } + } + clearInstance(e = u) { + this.instancesDeferred.delete(e), + this.instancesOptions.delete(e), + this.instances.delete(e); + } + async delete() { + const e = Array.from(this.instances.values()); + await Promise.all([ + ...e.filter((n) => "INTERNAL" in n).map((n) => n.INTERNAL.delete()), + ...e.filter((n) => "_delete" in n).map((n) => n._delete()), + ]); + } + isComponentSet() { + return this.component != null; + } + isInitialized(e = u) { + return this.instances.has(e); + } + getOptions(e = u) { + return this.instancesOptions.get(e) || {}; + } + initialize(e = {}) { + const { options: n = {} } = e, + s = this.normalizeInstanceIdentifier(e.instanceIdentifier); + if (this.isInitialized(s)) + throw Error(`${this.name}(${s}) has already been initialized`); + if (!this.isComponentSet()) + throw Error(`Component ${this.name} has not been registered yet`); + const r = this.getOrInitializeService({ + instanceIdentifier: s, + options: n, + }); + for (const [a, i] of this.instancesDeferred.entries()) { + const o = this.normalizeInstanceIdentifier(a); + s === o && i.resolve(r); + } + return r; + } + onInit(e, n) { + var s; + const r = this.normalizeInstanceIdentifier(n), + a = + (s = this.onInitCallbacks.get(r)) !== null && s !== void 0 + ? s + : new Set(); + a.add(e), this.onInitCallbacks.set(r, a); + const i = this.instances.get(r); + return ( + i && e(i, r), + () => { + a.delete(e); + } + ); + } + invokeOnInitCallbacks(e, n) { + const s = this.onInitCallbacks.get(n); + if (s) + for (const r of s) + try { + r(e, n); + } catch {} + } + getOrInitializeService({ instanceIdentifier: e, options: n = {} }) { + let s = this.instances.get(e); + if ( + !s && + this.component && + ((s = this.component.instanceFactory(this.container, { + instanceIdentifier: be(e), + options: n, + })), + this.instances.set(e, s), + this.instancesOptions.set(e, n), + this.invokeOnInitCallbacks(s, e), + this.component.onInstanceCreated) + ) + try { + this.component.onInstanceCreated(this.container, e, s); + } catch {} + return s || null; + } + normalizeInstanceIdentifier(e = u) { + return this.component ? (this.component.multipleInstances ? e : u) : e; + } + shouldAutoInitialize() { + return ( + !!this.component && this.component.instantiationMode !== "EXPLICIT" + ); + } +} +function be(t) { + return t === u ? void 0 : t; +} +function _e(t) { + return t.instantiationMode === "EAGER"; +} /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +class Ee { + constructor(e) { + (this.name = e), (this.providers = new Map()); + } + addComponent(e) { + const n = this.getProvider(e.name); + if (n.isComponentSet()) + throw new Error( + `Component ${e.name} has already been registered with ${this.name}`, + ); + n.setComponent(e); + } + addOrOverwriteComponent(e) { + this.getProvider(e.name).isComponentSet() && + this.providers.delete(e.name), + this.addComponent(e); + } + getProvider(e) { + if (this.providers.has(e)) return this.providers.get(e); + const n = new ge(e, this); + return this.providers.set(e, n), n; + } + getProviders() { + return Array.from(this.providers.values()); + } +} /** + * @license + * Copyright 2017 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +var h; +(function (t) { + (t[(t.DEBUG = 0)] = "DEBUG"), + (t[(t.VERBOSE = 1)] = "VERBOSE"), + (t[(t.INFO = 2)] = "INFO"), + (t[(t.WARN = 3)] = "WARN"), + (t[(t.ERROR = 4)] = "ERROR"), + (t[(t.SILENT = 5)] = "SILENT"); +})(h || (h = {})); +const ye = { + debug: h.DEBUG, + verbose: h.VERBOSE, + info: h.INFO, + warn: h.WARN, + error: h.ERROR, + silent: h.SILENT, + }, + De = h.INFO, + Ie = { + [h.DEBUG]: "log", + [h.VERBOSE]: "log", + [h.INFO]: "info", + [h.WARN]: "warn", + [h.ERROR]: "error", + }, + we = (t, e, ...n) => { + if (e < t.logLevel) return; + const s = new Date().toISOString(), + r = Ie[e]; + if (r) console[r](`[${s}] ${t.name}:`, ...n); + else + throw new Error( + `Attempted to log a message with an invalid logType (value: ${e})`, + ); + }; +class Se { + constructor(e) { + (this.name = e), + (this._logLevel = De), + (this._logHandler = we), + (this._userLogHandler = null); + } + get logLevel() { + return this._logLevel; + } + set logLevel(e) { + if (!(e in h)) + throw new TypeError( + `Invalid value "${e}" assigned to \`logLevel\``, + ); + this._logLevel = e; + } + setLogLevel(e) { + this._logLevel = typeof e == "string" ? ye[e] : e; + } + get logHandler() { + return this._logHandler; + } + set logHandler(e) { + if (typeof e != "function") + throw new TypeError( + "Value assigned to `logHandler` must be a function", + ); + this._logHandler = e; + } + get userLogHandler() { + return this._userLogHandler; + } + set userLogHandler(e) { + this._userLogHandler = e; + } + debug(...e) { + this._userLogHandler && this._userLogHandler(this, h.DEBUG, ...e), + this._logHandler(this, h.DEBUG, ...e); + } + log(...e) { + this._userLogHandler && this._userLogHandler(this, h.VERBOSE, ...e), + this._logHandler(this, h.VERBOSE, ...e); + } + info(...e) { + this._userLogHandler && this._userLogHandler(this, h.INFO, ...e), + this._logHandler(this, h.INFO, ...e); + } + warn(...e) { + this._userLogHandler && this._userLogHandler(this, h.WARN, ...e), + this._logHandler(this, h.WARN, ...e); + } + error(...e) { + this._userLogHandler && this._userLogHandler(this, h.ERROR, ...e), + this._logHandler(this, h.ERROR, ...e); + } +} +const Ce = (t, e) => e.some((n) => t instanceof n); +let P, F; +function ve() { + return ( + P || + (P = [IDBDatabase, IDBObjectStore, IDBIndex, IDBCursor, IDBTransaction]) + ); +} +function Ae() { + return ( + F || + (F = [ + IDBCursor.prototype.advance, + IDBCursor.prototype.continue, + IDBCursor.prototype.continuePrimaryKey, + ]) + ); +} +const Y = new WeakMap(), + A = new WeakMap(), + X = new WeakMap(), + I = new WeakMap(), + N = new WeakMap(); +function Be(t) { + const e = new Promise((n, s) => { + const r = () => { + t.removeEventListener("success", a), + t.removeEventListener("error", i); + }, + a = () => { + n(f(t.result)), r(); + }, + i = () => { + s(t.error), r(); + }; + t.addEventListener("success", a), t.addEventListener("error", i); + }); + return ( + e + .then((n) => { + n instanceof IDBCursor && Y.set(n, t); + }) + .catch(() => {}), + N.set(e, t), + e + ); +} +function Oe(t) { + if (A.has(t)) return; + const e = new Promise((n, s) => { + const r = () => { + t.removeEventListener("complete", a), + t.removeEventListener("error", i), + t.removeEventListener("abort", i); + }, + a = () => { + n(), r(); + }, + i = () => { + s(t.error || new DOMException("AbortError", "AbortError")), r(); + }; + t.addEventListener("complete", a), + t.addEventListener("error", i), + t.addEventListener("abort", i); + }); + A.set(t, e); +} +let B = { + get(t, e, n) { + if (t instanceof IDBTransaction) { + if (e === "done") return A.get(t); + if (e === "objectStoreNames") return t.objectStoreNames || X.get(t); + if (e === "store") + return n.objectStoreNames[1] + ? void 0 + : n.objectStore(n.objectStoreNames[0]); + } + return f(t[e]); + }, + set(t, e, n) { + return (t[e] = n), !0; + }, + has(t, e) { + return t instanceof IDBTransaction && (e === "done" || e === "store") + ? !0 + : e in t; + }, +}; +function Te(t) { + B = t(B); +} +function Me(t) { + return t === IDBDatabase.prototype.transaction && + !("objectStoreNames" in IDBTransaction.prototype) + ? function (e, ...n) { + const s = t.call(w(this), e, ...n); + return X.set(s, e.sort ? e.sort() : [e]), f(s); + } + : Ae().includes(t) + ? function (...e) { + return t.apply(w(this), e), f(Y.get(this)); + } + : function (...e) { + return f(t.apply(w(this), e)); + }; +} +function $e(t) { + return typeof t == "function" + ? Me(t) + : (t instanceof IDBTransaction && Oe(t), + Ce(t, ve()) ? new Proxy(t, B) : t); +} +function f(t) { + if (t instanceof IDBRequest) return Be(t); + if (I.has(t)) return I.get(t); + const e = $e(t); + return e !== t && (I.set(t, e), N.set(e, t)), e; +} +const w = (t) => N.get(t); +function Ne(t, e, { blocked: n, upgrade: s, blocking: r, terminated: a } = {}) { + const i = indexedDB.open(t, e), + o = f(i); + return ( + s && + i.addEventListener("upgradeneeded", (c) => { + s(f(i.result), c.oldVersion, c.newVersion, f(i.transaction), c); + }), + n && + i.addEventListener("blocked", (c) => + n(c.oldVersion, c.newVersion, c), + ), + o + .then((c) => { + a && c.addEventListener("close", () => a()), + r && + c.addEventListener("versionchange", (l) => + r(l.oldVersion, l.newVersion, l), + ); + }) + .catch(() => {}), + o + ); +} +const Re = ["get", "getKey", "getAll", "getAllKeys", "count"], + Le = ["put", "add", "delete", "clear"], + S = new Map(); +function x(t, e) { + if (!(t instanceof IDBDatabase && !(e in t) && typeof e == "string")) + return; + if (S.get(e)) return S.get(e); + const n = e.replace(/FromIndex$/, ""), + s = e !== n, + r = Le.includes(n); + if ( + !(n in (s ? IDBIndex : IDBObjectStore).prototype) || + !(r || Re.includes(n)) + ) + return; + const a = async function (i, ...o) { + const c = this.transaction(i, r ? "readwrite" : "readonly"); + let l = c.store; + return ( + s && (l = l.index(o.shift())), + (await Promise.all([l[n](...o), r && c.done]))[0] + ); + }; + return S.set(e, a), a; +} +Te((t) => ({ + ...t, + get: (e, n, s) => x(e, n) || t.get(e, n, s), + has: (e, n) => !!x(e, n) || t.has(e, n), +})); /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +class He { + constructor(e) { + this.container = e; + } + getPlatformInfoString() { + return this.container + .getProviders() + .map((n) => { + if (Pe(n)) { + const s = n.getImmediate(); + return `${s.library}/${s.version}`; + } else return null; + }) + .filter((n) => n) + .join(" "); + } +} +function Pe(t) { + const e = t.getComponent(); + return e?.type === "VERSION"; +} +const O = "@firebase/app", + V = "0.10.17"; /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const d = new Se("@firebase/app"), + Fe = "@firebase/app-compat", + xe = "@firebase/analytics-compat", + Ve = "@firebase/analytics", + je = "@firebase/app-check-compat", + ke = "@firebase/app-check", + ze = "@firebase/auth", + Ue = "@firebase/auth-compat", + We = "@firebase/database", + Ge = "@firebase/data-connect", + Je = "@firebase/database-compat", + Ke = "@firebase/functions", + Ye = "@firebase/functions-compat", + Xe = "@firebase/installations", + Ze = "@firebase/installations-compat", + qe = "@firebase/messaging", + Qe = "@firebase/messaging-compat", + et = "@firebase/performance", + tt = "@firebase/performance-compat", + nt = "@firebase/remote-config", + rt = "@firebase/remote-config-compat", + st = "@firebase/storage", + at = "@firebase/storage-compat", + it = "@firebase/firestore", + ot = "@firebase/vertexai", + ct = "@firebase/firestore-compat", + ht = "firebase"; /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const lt = "[DEFAULT]", + dt = { + [O]: "fire-core", + [Fe]: "fire-core-compat", + [Ve]: "fire-analytics", + [xe]: "fire-analytics-compat", + [ke]: "fire-app-check", + [je]: "fire-app-check-compat", + [ze]: "fire-auth", + [Ue]: "fire-auth-compat", + [We]: "fire-rtdb", + [Ge]: "fire-data-connect", + [Je]: "fire-rtdb-compat", + [Ke]: "fire-fn", + [Ye]: "fire-fn-compat", + [Xe]: "fire-iid", + [Ze]: "fire-iid-compat", + [qe]: "fire-fcm", + [Qe]: "fire-fcm-compat", + [et]: "fire-perf", + [tt]: "fire-perf-compat", + [nt]: "fire-rc", + [rt]: "fire-rc-compat", + [st]: "fire-gcs", + [at]: "fire-gcs-compat", + [it]: "fire-fst", + [ct]: "fire-fst-compat", + [ot]: "fire-vertex", + "fire-js": "fire-js", + [ht]: "fire-js-all", + }; /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const T = new Map(), + ft = new Map(), + M = new Map(); +function j(t, e) { + try { + t.container.addComponent(e); + } catch (n) { + d.debug( + `Component ${e.name} failed to register with FirebaseApp ${t.name}`, + n, + ); + } +} +function $(t) { + const e = t.name; + if (M.has(e)) + return ( + d.debug(`There were multiple attempts to register component ${e}.`), + !1 + ); + M.set(e, t); + for (const n of T.values()) j(n, t); + for (const n of ft.values()) j(n, t); + return !0; +} /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const ut = { + "no-app": + "No Firebase App '{$appName}' has been created - call initializeApp() first", + "bad-app-name": "Illegal App name: '{$appName}'", + "duplicate-app": + "Firebase App named '{$appName}' already exists with different options or config", + "app-deleted": "Firebase App named '{$appName}' already deleted", + "server-app-deleted": "Firebase Server App has been deleted", + "no-options": + "Need to provide options, when not being deployed to hosting via source.", + "invalid-app-argument": + "firebase.{$appName}() takes either no argument or a Firebase App instance.", + "invalid-log-argument": + "First argument to `onLog` must be null or a function.", + "idb-open": + "Error thrown when opening IndexedDB. Original error: {$originalErrorMessage}.", + "idb-get": + "Error thrown when reading from IndexedDB. Original error: {$originalErrorMessage}.", + "idb-set": + "Error thrown when writing to IndexedDB. Original error: {$originalErrorMessage}.", + "idb-delete": + "Error thrown when deleting from IndexedDB. Original error: {$originalErrorMessage}.", + "finalization-registry-not-supported": + "FirebaseServerApp deleteOnDeref field defined but the JS runtime does not support FinalizationRegistry.", + "invalid-server-app-environment": + "FirebaseServerApp is not for use in browser environments.", + }, + p = new K("app", "Firebase", ut); /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +class pt { + constructor(e, n, s) { + (this._isDeleted = !1), + (this._options = Object.assign({}, e)), + (this._config = Object.assign({}, n)), + (this._name = n.name), + (this._automaticDataCollectionEnabled = + n.automaticDataCollectionEnabled), + (this._container = s), + this.container.addComponent(new D("app", () => this, "PUBLIC")); + } + get automaticDataCollectionEnabled() { + return this.checkDestroyed(), this._automaticDataCollectionEnabled; + } + set automaticDataCollectionEnabled(e) { + this.checkDestroyed(), (this._automaticDataCollectionEnabled = e); + } + get name() { + return this.checkDestroyed(), this._name; + } + get options() { + return this.checkDestroyed(), this._options; + } + get config() { + return this.checkDestroyed(), this._config; + } + get container() { + return this._container; + } + get isDeleted() { + return this._isDeleted; + } + set isDeleted(e) { + this._isDeleted = e; + } + checkDestroyed() { + if (this.isDeleted) + throw p.create("app-deleted", { appName: this._name }); + } +} +function vt(t, e = {}) { + let n = t; + typeof e != "object" && (e = { name: e }); + const s = Object.assign( + { name: lt, automaticDataCollectionEnabled: !1 }, + e, + ), + r = s.name; + if (typeof r != "string" || !r) + throw p.create("bad-app-name", { appName: String(r) }); + if ((n || (n = he()), !n)) throw p.create("no-options"); + const a = T.get(r); + if (a) { + if (v(n, a.options) && v(s, a.config)) return a; + throw p.create("duplicate-app", { appName: r }); + } + const i = new Ee(r); + for (const c of M.values()) i.addComponent(c); + const o = new pt(n, s, i); + return T.set(r, o), o; +} +function y(t, e, n) { + var s; + let r = (s = dt[t]) !== null && s !== void 0 ? s : t; + n && (r += `-${n}`); + const a = r.match(/\s|\//), + i = e.match(/\s|\//); + if (a || i) { + const o = [`Unable to register library "${r}" with version "${e}":`]; + a && + o.push( + `library name "${r}" contains illegal characters (whitespace or "/")`, + ), + a && i && o.push("and"), + i && + o.push( + `version name "${e}" contains illegal characters (whitespace or "/")`, + ), + d.warn(o.join(" ")); + return; + } + $(new D(`${r}-version`, () => ({ library: r, version: e }), "VERSION")); +} /** + * @license + * Copyright 2021 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const mt = "firebase-heartbeat-database", + gt = 1, + g = "firebase-heartbeat-store"; +let C = null; +function Z() { + return ( + C || + (C = Ne(mt, gt, { + upgrade: (t, e) => { + switch (e) { + case 0: + try { + t.createObjectStore(g); + } catch (n) { + console.warn(n); + } + } + }, + }).catch((t) => { + throw p.create("idb-open", { originalErrorMessage: t.message }); + })), + C + ); +} +async function bt(t) { + try { + const n = (await Z()).transaction(g), + s = await n.objectStore(g).get(q(t)); + return await n.done, s; + } catch (e) { + if (e instanceof b) d.warn(e.message); + else { + const n = p.create("idb-get", { originalErrorMessage: e?.message }); + d.warn(n.message); + } + } +} +async function k(t, e) { + try { + const s = (await Z()).transaction(g, "readwrite"); + await s.objectStore(g).put(e, q(t)), await s.done; + } catch (n) { + if (n instanceof b) d.warn(n.message); + else { + const s = p.create("idb-set", { originalErrorMessage: n?.message }); + d.warn(s.message); + } + } +} +function q(t) { + return `${t.name}!${t.options.appId}`; +} /** + * @license + * Copyright 2021 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +const _t = 1024, + Et = 30 * 24 * 60 * 60 * 1e3; +class yt { + constructor(e) { + (this.container = e), (this._heartbeatsCache = null); + const n = this.container.getProvider("app").getImmediate(); + (this._storage = new It(n)), + (this._heartbeatsCachePromise = this._storage + .read() + .then((s) => ((this._heartbeatsCache = s), s))); + } + async triggerHeartbeat() { + var e, n; + try { + const r = this.container + .getProvider("platform-logger") + .getImmediate() + .getPlatformInfoString(), + a = z(); + return (((e = this._heartbeatsCache) === null || e === void 0 + ? void 0 + : e.heartbeats) == null && + ((this._heartbeatsCache = await this._heartbeatsCachePromise), + ((n = this._heartbeatsCache) === null || n === void 0 + ? void 0 + : n.heartbeats) == null)) || + this._heartbeatsCache.lastSentHeartbeatDate === a || + this._heartbeatsCache.heartbeats.some((i) => i.date === a) + ? void 0 + : (this._heartbeatsCache.heartbeats.push({ date: a, agent: r }), + (this._heartbeatsCache.heartbeats = + this._heartbeatsCache.heartbeats.filter((i) => { + const o = new Date(i.date).valueOf(); + return Date.now() - o <= Et; + })), + this._storage.overwrite(this._heartbeatsCache)); + } catch (s) { + d.warn(s); + } + } + async getHeartbeatsHeader() { + var e; + try { + if ( + (this._heartbeatsCache === null && + (await this._heartbeatsCachePromise), + ((e = this._heartbeatsCache) === null || e === void 0 + ? void 0 + : e.heartbeats) == null || + this._heartbeatsCache.heartbeats.length === 0) + ) + return ""; + const n = z(), + { heartbeatsToSend: s, unsentEntries: r } = Dt( + this._heartbeatsCache.heartbeats, + ), + a = J(JSON.stringify({ version: 2, heartbeats: s })); + return ( + (this._heartbeatsCache.lastSentHeartbeatDate = n), + r.length > 0 + ? ((this._heartbeatsCache.heartbeats = r), + await this._storage.overwrite(this._heartbeatsCache)) + : ((this._heartbeatsCache.heartbeats = []), + this._storage.overwrite(this._heartbeatsCache)), + a + ); + } catch (n) { + return d.warn(n), ""; + } + } +} +function z() { + return new Date().toISOString().substring(0, 10); +} +function Dt(t, e = _t) { + const n = []; + let s = t.slice(); + for (const r of t) { + const a = n.find((i) => i.agent === r.agent); + if (a) { + if ((a.dates.push(r.date), U(n) > e)) { + a.dates.pop(); + break; + } + } else if ((n.push({ agent: r.agent, dates: [r.date] }), U(n) > e)) { + n.pop(); + break; + } + s = s.slice(1); + } + return { heartbeatsToSend: n, unsentEntries: s }; +} +class It { + constructor(e) { + (this.app = e), + (this._canUseIndexedDBPromise = + this.runIndexedDBEnvironmentCheck()); + } + async runIndexedDBEnvironmentCheck() { + return de() + ? fe() + .then(() => !0) + .catch(() => !1) + : !1; + } + async read() { + if (await this._canUseIndexedDBPromise) { + const n = await bt(this.app); + return n?.heartbeats ? n : { heartbeats: [] }; + } else return { heartbeats: [] }; + } + async overwrite(e) { + var n; + if (await this._canUseIndexedDBPromise) { + const r = await this.read(); + return k(this.app, { + lastSentHeartbeatDate: + (n = e.lastSentHeartbeatDate) !== null && n !== void 0 + ? n + : r.lastSentHeartbeatDate, + heartbeats: e.heartbeats, + }); + } else return; + } + async add(e) { + var n; + if (await this._canUseIndexedDBPromise) { + const r = await this.read(); + return k(this.app, { + lastSentHeartbeatDate: + (n = e.lastSentHeartbeatDate) !== null && n !== void 0 + ? n + : r.lastSentHeartbeatDate, + heartbeats: [...r.heartbeats, ...e.heartbeats], + }); + } else return; + } +} +function U(t) { + return J(JSON.stringify({ version: 2, heartbeats: t })).length; +} /** + * @license + * Copyright 2019 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +function wt(t) { + $(new D("platform-logger", (e) => new He(e), "PRIVATE")), + $(new D("heartbeat", (e) => new yt(e), "PRIVATE")), + y(O, V, t), + y(O, V, "esm2017"), + y("fire-js", ""); +} +wt(""); +var St = "firebase", + Ct = "11.1.0"; /** + * @license + * Copyright 2020 Google LLC + * + * Licensed under the Apache License, Version 2.0 (the "License"); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +y(St, Ct, "app"); +export { + b as FirebaseError, + lt as _DEFAULT_ENTRY_NAME, + j as _addComponent, + T as _apps, + M as _components, + $ as _registerComponent, + ft as _serverApps, + vt as initializeApp, + y as registerVersion, +}; +//# sourceMappingURL=index.esm.CIXTrynS.js.map diff --git a/Target/_astro/page.EDj8xPHu.js b/Target/_astro/page.EDj8xPHu.js index abd01ea0..cac369f4 100644 --- a/Target/_astro/page.EDj8xPHu.js +++ b/Target/_astro/page.EDj8xPHu.js @@ -1 +1,3 @@ -import{i}from"./index.BqqcOND9.js";i(); \ No newline at end of file +import { i } from "./index.BqqcOND9.js"; +i(); +//# sourceMappingURL=page.EDj8xPHu.js.map