\n
\n {{ $t(\"team.reportTheme.customThemeBackgroundAndWallpaperTitle\") }}\n
\n\n {{ $t(\"team.reportTheme.customThemeFiltersTitle\") }}\n
\n\n {{ $t(\"team.reportTheme.reportColorsLbl\") }}\n
\n\n {{ $t(\"team.usage.utcWarningLbl\") }}\n
\n\n\n {{ $t(\"team.reportTheme.selectTestReportLbl\") }}\n
\n\nBetween:
\n\n\n Data Controller:\n
\n {{ dataController.company }}\n
\n {{ dataController.address }}, {{ dataController.city }} ({{\n dataController.zip\n }}), {{ dataController.country }}\n
\n {{ $t(\"team.terms.vat\") }} {{ dataController.vat }}\n
\n Contact person:\n
\n {{ contactPerson.firstName }} {{ contactPerson.lastName }}\n
\n {{ contactPerson.email }}\n
\n {{ contactPerson.telephone }}\n
\n and\n
\n Data Processor:\n
intellify ApS,
Hammerensgade 6, st.
1267\n Copenhagen K,
CVR-nr: 37348031
Contact:\n
info@intellify.dk\n
\n The parties are hereinafter referred to as the \"Data Controller\"\n and \"Data Processor\" and \"Part\" or together \"Parties\".\n
\n\n\n By using the intellify platform and any module or function\n associated with the platform (referred to herein as \"the\n Platform\"), the Data Controller will be responsible for its\n processing of Personal Data on the Platform. The Data Processor\n will process personal data on behalf of the Data Controller. In\n order to ensure that the Parties fulfill their obligations under\n national data protection rules as well as European Parliament and\n Council Regulation (EU) 2016/279 (“GDPR”), the Parties have\n entered into this data processing agreement (the “Agreement”),\n which constitutes the instructions of the Data Controller to the\n Data Processor and thus regulates the Data Processor's processing\n of personal data on behalf of the Data Controller.\n
\n\n\n Both Parties confirm that they have the power of attorney /\n authority to sign the Agreement.\n
\n\n\n In addition, the Data Processor only processes Personal\n Information in accordance with the intellify\n
\n The definition of Personal Data, Specific Categories of Data\n (Sensitive Information), Processing, the data subject, Data\n Controller and Data Processor is the same as the relevant Personal\n Data Act, including GDPR.\n
\n\n\n The Agreement governs the Data Processor's Processing of Personal\n Data on behalf of the Data Controller, and describes how the Data\n Processor shall assist in the protection of privacy on behalf of\n the Data Controller and its data subjects through technical and\n organizational measures required under applicable data protection\n legislation, including GDPR of 25. May 2018.\n
\n\n\n The purpose of the Data Processor's Processing of Personal Data on\n behalf of the Data Controller is to ensure, the Data Controller's\n use of the Platform and the fulfillment of this Agreement.\n
\n\n\n The Agreement takes precedence over other conflicting provisions\n regarding the Processing of Personal Data as regards to the Terms\n and Conditions for use of the Platform or in other agreements\n between the Parties. The Agreement is valid as long as the Data\n Controller has an account on the Platform and the Data Processor\n must therefore process Personal Data on behalf of the Data\n Controller. However, this Agreement does not take precedence if\n the Parties have entered into another Data Processor Agreement,\n stating that the Data Processor Agreement takes precedence over\n this Agreement.\n
\n\n\n The Data Processor must process Personal Data solely on behalf of\n and following the instructions of the Data Controller. By entering\n into this Agreement, the Data Controller instructs to process\n Personal Data in the following ways: (i) in accordance with\n applicable law; (ii) to fulfill its obligations under the\n Subscription Terms of the Platform; and (iv) as described in this\n Agreement.\n
\n\n\n The categories of Data Subjects and Personal Information processed\n under this Agreement are described in Appendix A.\n
\n\n\n As part of being able to deliver the Platform, the Data Processor\n is obliged at all times to provide the Data Controller with good\n and competitive solutions that accompany the development. The Data\n Processor can offer better solutions tailored to the needs of each\n Data Provider by registering how the Data Controller and its\n representatives use the Platform. This enables the Data Processor\n to make a better version of the Platform, and generally provide\n better services and provide more relevant communication to the\n Data Controller and its representatives. The goal is for the Data\n Controller to solve as many challenges as possible in one place.\n To the extent that Personal information from the Platform is\n included in this work, it is processed in accordance with this\n Agreement and applicable law, and may be shared with companies in\n the intellify Group for the purpose of this work.\n
\n\n\n The Data Processor has no reason to believe that current\n legislation prevents the Data Processor from complying with the\n instructions set out above. The Data Processor shall, if it\n becomes aware of this, notify the Data Controller of instructions\n or other processing activities performed by the Data Controller\n which, in the Data Processor's opinion, contravene the applicable\n data protection law.\n
\n\n\n Taking into account the technology available and the cost of\n implementation, as well as the scope, context and purpose of the\n processing, the Data Processor is required to take all reasonable\n measures, including technical and organizational, to ensure an\n adequate level of security in relation to the risk and the\n category of Personal Information to be protected.\n
\n\n\n The Data Processor shall assist the Data Controller with\n appropriate technical and organizational measures where possible\n and taking into account the nature of the processing and the\n category of information available to the Data Processor to ensure\n compliance with the Data Controller's obligations under applicable\n Data Protection Laws, including assistance with respect to the\n fulfillment of requests by the Data Subjects as well as general\n compliance with the provisions of GDPR Articles 32-36.\n
\n\n\n The Data Processor must notify the Data Controller without\n unnecessary delay through the contact person stated in the Data\n Processor Agreement if the Data Processor becomes aware of a\n security breach.\n
\n\n\n Furthermore, the Data Processor shall, as far as possible and\n legally, notify the Data Controller if;\n
1. A request for access to Personal Information is received\n directly from the Data Subject
2. A request for access to\n Personal Data is received directly from state authorities,\n including the police\n
\n The Data Processor may not respond to such requests by the Data\n Subjects unless authorized by the Data Controller to do so.\n Further, the Data Processor will not disclose information about\n this Agreement to state authorities such as the police, including\n Personal Data, unless the Data Processor is required by law, such\n as a court order or similar.\n
\n\n\n If the Data Controller requires information or assistance\n regarding security measures, documentation or information on how\n the Data Processor processes Personal Data in general and such\n request contains information that goes beyond what is required by\n applicable Data Protection Laws, the Data Processor may require\n payment for such additional services.\n
\n\n\n The Data Processor and its employees must ensure confidentiality\n in relation to Personal Data processed under the Agreement. This\n provision shall also apply after termination of the Agreement.\n
\n\n\n Upon entering into this agreement, the Data Controller confirms\n that:\n
The Data Controller shall, using the Platform provided by\n the Data Processor, only process Personal Data in accordance with\n the requirements of the applicable Data Protection Law.
The\n Data Controller has a legal basis for processing and disclosing\n Personal Data to the Data Processor (including sub-processors used\n by the Data Processor).
The Data Controller is responsible\n for the accuracy, integrity, content of the reliability and\n legality of the Personal Data processed by the Data Processor.\n
The Data Controller has fulfilled all mandatory requirements\n and obligations in relation to notification or obtaining\n permission from the relevant public authorities as regards the\n processing of Personal Data.
The Data Controller has\n fulfilled its disclosure obligations to the Data Subjects\n regarding the processing of Personal Data in accordance with\n applicable data protection legislation.
The Data Controller\n agrees that the Data Processor has provided the relevant\n guarantees regarding the implementation of technical and\n organizational security measures to safeguard the rights of the\n Data Subjects and their Personal Information.
The Data\n Controller shall, when using the Platform, not process Sensitive\n information other than as specified in Appendix A.
The Data\n Controller must have an up-to-date list of the categories of\n Personal Data that it processes, this is especially true to the\n extent that such Processing contains Personal Sensitive\n Information.\n
\n As part of the operation of the Platform, the Data Processor uses\n subcontractors (“Data Sub-Processors”). Such Data Sub-Processors\n may be other companies within the intellify Group, or third-party\n suppliers in and outside the EU. The Data Processor's\n subcontractors are listed in the constantly updated list of Data\n Sub-Processors, which can be viewed\n
\n The Data Processor must ensure that its Data Sub-Processors comply\n with similar obligations and requirements set forth in the\n Agreement. All use of Data Sub-Processors is also subject to the\n intellify Privacy Policy.\n
\n\n\n This Agreement constitutes the prior general and specific written\n approval of the Data Controller for the Data Processor's use of\n Data Sub-Processors.\n
\n\n\n If a Data Sub-Processor is established outside or Personal Data is\n stored outside the EU / EEA, the Data Controller authorizes the\n Data Processor to secure a sufficient basis for the transfer of\n Personal Data to third countries on behalf of the Data Controller,\n including using the EU Commission's standard contracts or in\n accordance with Privacy Shield.\n
\n\n\n The Data Controller must be informed before the Data Processor\n replaces its Data Sub-Processors. However, the Data Controller is\n only entitled to protest against a new Data Sub-Processor, which\n processes Personal Data on behalf of the Data Controller if it\n does not process data in accordance with applicable data\n protection legislation. In such a situation, the Data Processor\n must demonstrate compliance by giving the Data Controller access\n to the Data Processor's data protection assessment of the Data\n Sub-Processor. If there is still disagreement about the use of the\n Data Sub-Processor, the Data Controller may request the deletion\n of his account on the Platform and that the Data Controller's\n Personal Information is not processed by the Data Sub-Processor in\n question.\n
\n\n\n The Data Processor is required to ensure a high level of security\n in its products and services, which is ensured by relevant\n organizational, technical and physical security measures as\n required by information on security measures described in GDPR,\n Article 32.\n
\n\n\n Furthermore, the intellify Group's internal data protection\n policies aim to ensure confidentiality, integrity, resilience and\n secure access to Personal Data. The following measures are\n particularly important:\n
Classification of Personal Data to ensure the implementation\n of security measures relevant to risk assessments.\n
Assessment of encryption and pseudonymization as\n risk-reducing factors.
Limit access to Personal Data to the\n relevant persons required to comply with the requirements and\n obligations of the Agreement or relevant to the Parties agreement\n on the use of the Platform.
Identify the security structure\n and how Personal Data is transferred between the Parties.\n
Conduct own security assessment to ensure that current\n technical and organizational measures are adequate for the\n protection of Personal Data, including Article 32 of the GDPR on\n processing security and Article 25 on Privacy by Design and\n Default.
Access to audit.\n
\n The Data Controller is entitled to initiate an audit of the Data\n Processor's obligations under the Agreement once a year. If the\n Data Controller is obliged to do so in accordance with current\n legislation, audits may be carried out more often than once a\n year. When requesting an audit, the Data Controller must provide a\n detailed audit plan with a description of the scope, duration and\n start date at least four weeks in advance of the proposed start\n date. It must be decided jointly between the Parties if a third\n party is to conduct the audit. However, the Data Controller may\n allow the Data Processor to decide that the audit for security\n reasons must be done by a neutral third party of the Data\n Processor's choice, in the case of a processing environment where\n multiple Data Controllers' data have been used.\n
\n\n\n If the proposed scope of the audit follows an ISAE, ISO or similar\n certification report conducted by a qualified third party auditor\n within the previous twelve months and the Data Processor confirms\n that there have been no material changes to the measures under\n audit, the Data Controller shall accept this audit instead of\n requesting a new revision of the measures already covered.\n
\n\n\n In any case, audits must be conducted during normal office hours\n at the appropriate facility in accordance with the Data\n Processor's policies and must not unduly interfere with the Data\n Processor's usual commercial activities.\n
\n\n\n The Data Controller is responsible for all costs associated with\n the request for audit. The Data Processor's assistance in\n connection with this, which exceeds the ordinary service that the\n Data Processor and / or the intellify Group must make available as\n a result of the applicable data protection legislation, is charged\n separately.\n
\n\n\n The Agreement is valid as long as the Data Processor processes\n Personal Data on behalf of the Data Controller in connection with\n the Data Controller's use of the Platform.\n
\n\n\n This Agreement will automatically terminate upon deletion of the\n Data Controller’s account on the Platform. Upon termination of the\n Account, the Data Processor will delete all Personal Information\n processed by the Data Processor on behalf of the Data Controller\n under the Agreement.\n
\n\n\n The Data Processor is entitled to retain Personal Data upon\n termination of the Agreement to the extent required by applicable\n law, which will then be in accordance with the technical and\n organizational security measures described in the Agreement.\n
\n\n\n Amendments to the Agreement must be included in a separate\n appendix to the Agreement.\n
\n\n\n If any of the provisions of the Agreement are invalid, this will\n not affect the remaining provisions. The Parties must replace\n invalid provisions with a legal provision that reflects the\n purpose of the invalid provision.\n
\n\n\n Liability for actions in violation of the terms of this Agreement\n is governed by the provisions of liability and damages in the\n terms of use of the intellify Platform. This also applies to any\n infringement committed by the Data Processor's Sub-Processors.\n
\n\n\n The agreement is governed by Danish law and any dispute must be\n presented to a Danish court.\n
\n\n\n Categories of Data Subjects and Personal Information processed\n under the Agreement\n
\n a. Categories of Data Subjects\n
The Data Controller’s end users
The Data Controller’s\n employees
The Data Controller’s contacts
The Data\n Controller’s customers and customers end users
The Data\n Controller’s customers employees
The Data Controller’s\n customers contacts
Optional\n
\n b. Categories of Personal Information\n
Name
Titel
Phone number
E-mail\n
Address
Social Security number (CPR)
Job\n category, information on salary, working hours, absence, pension,\n tax, bank account
Possibly other personal information\n necessary for the Data Controller to manage the employment\n relationship
Optional\n
\n {{ $t(\"team.reportTheme.fileJsonErrorMsg\") }}\n
\n \n0\">\n {{\n $t(\n \"integrations.integrationSettings.createIntegration.createPbiIntegration.addGroupsToClientResponseDialog.addingAlreadyExistsGroupUserNotSupportedError\",\n {\n number:\n response.addingAlreadyExistsGroupUserNotSupportedError,\n }\n )\n }}\n
\n0\">\n {{\n $t(\n \"integrations.integrationSettings.createIntegration.createPbiIntegration.addGroupsToClientResponseDialog.invalidRequest\",\n { number: response.invalidRequest }\n )\n }}\n
\n\n0\">\n {{\n $t(\n \"integrations.integrationSettings.createIntegration.createPbiIntegration.addGroupsToClientResponseDialog.powerBiNotAuthorizedException\",\n { number: response.powerBiNotAuthorizedException }\n )\n }}\n
\n\n0\">\n {{\n $t(\n \"integrations.integrationSettings.createIntegration.createPbiIntegration.addGroupsToClientResponseDialog.unknown\",\n { number: response.unknown }\n )\n }}\n
\n\n {{ $t(\"team.teamFacts.terminateTeam.text-line-0\") }}\n {{ GetCurrentTeamData.name }}.\n
\n \n \n\n
{{ $t(\"team.terms.dataController.missingInfoTxt\") }}
\n\n {{ $t(\"newTeamHomeScreen.infoSubTitle\") }}\n
\n\n