Data Processing Agreement

Pursuant to Art. 28 (3) p. 1 GDPR

– hereinafter referred to as the DPA

between

Name/Co.: ____________________________
Street: ____________________________
Zip Code, City, Country: ____________________________
Commercial Register No.: ____________________________
Managing Director: ____________________________

– hereinafter referred to as Controller

and

Name/Co.: uphill GmbH
Street: Oranienstr. 188
Zip Code, City, Country: 10999 Berlin, Deutschland
Commercial Register No.: Amtsgericht Berlin, HRB 123671 B
Managing Director: Stephan Eyl, Nicolas Graf von Kanitz

– hereinafter referred to as Processor

– The Processor and the Controller are hereinafter referred to as (contractual) Parties. –

Annexes

  • Annex 1 “Security of processing”.
  • Annex 2 “Subprocessors”.

The Subject-Matter of the Contract, Categories of Data, Data Subjects, Nature, Scope and Purpose of the Processing (Art. 28 (3), 30 (2) GDPR)

  1. The subject of the DPA, the personal data processed within the scope of the assignment (Art, 4 Nos. 1 and 2 GDPR; hereinafter referred to as "Data"), the data subjects concerned and the nature, scope and purposes of the processing, are determined by the following legal relationship(s) between the contractual Parties (hereinafter referred to as the "Principal Agreement"):

    Agreement on the use of Fanpage Karma and the websites, tools, functions and services associated with the services of Fanpage Karma.

    The provisions of this DPA take precedence over the Principal Agreement.

  2. The Principal Agreement includes the following basic features and special features and services provided by Fanpage Karma:

Name of the function/service:

Fanpage Karma Tool

Basic information on the processing of personal data

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • The processing of the following data is necessary to establish and implement the contractual relationship with regard to the use of the Fanpage Karma Tool and the services and functions associated with it in accordance with the Principal Agreement.
  • The Fanpage Karma Tool provides various functionalities (e.g. Analytics, Monitoring, Engagement, etc.). The processing of personal data within these functionalities is described separately and applies in addition to the general information in the case of the use of these functionalities by the customer.
  • To use Fanpage Karma's tools, a Facebook login is required.
  • The information accessible via the Fanpage Karma Tool can be made available (within the framework of the specification according to the Principal Agreement) via an Application-Programming-Interface (API).

Types of data which are regularly the subject of processing:

  • Inventory data/master data (first name, surname, gender, country code).
  • Contact data (e-mail address).
  • Data concerning the online accounts linked in the context of the use of the Fanpage Karma Tool: profile ID, authorization key (access token), list of profiles for which the Controller has special access rights (e.g. Facebook, Twitter, Instagram, LinkedIn etc.), creation date, login times, language, time zone, preferred currency, account ID, newsletter, wallpaper, own profile picture; when logging in via a mobile app: Firebase Cloud Messaging Token; email signature (for use in Engage).
  • Data regarding the use of the tool (time and functions used).
  • Meta / communication data (device IDs, IP addresses, location data).
  • In order to perform analyses for profiles, it may be necessary for the Controller to log in to the profiles and for access to the Processor's app (e.g. Twitter or LinkedIn). In these cases, the account name, account ID, access token, token secret and their expiration date are stored.

Additional types of data that are regularly processed in the case of paid accounts:

  • Inventory data/master data (company name, contact person, street, postal code, city, country).
  • Contact data (e-mail, telephone).
  • Contract and payment data (payment method, account holder, IBAN, BIC, bank (if payment by electronic direct debiting), customer reference number, ID at the payment service provider for debiting via credit card data stored there, tax identification number, list of all associated users).
  • Authorizations within the Fanpage Karma Tools to employees, the contractor stores their names, e-mail addresses and Facebook IDs.

Note: If the client has a paid subscription, an account will be created for the client, to which other users can then also be invited. In the case of invitations to an account, the contractor stores the first and last name as well as the e-mail address of the invited person.

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

The client and his employees as well as other users invited to the usage of the tool.

Name of the function/service:

Fanpage Karma Tool – Fanpage Karma Analytics

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • With the help of Fanpage Karma Analytics, the client can analyze key figures and content and compare profiles for his own and third-party social media profiles (e.g. on Facebook, Twitter, Instagram, YouTube, Google+, Pinterest, LinkedIn etc.).
  • To view protected key figures (e.g. reach, clicks, demographic data), the client must grant rights to the respective network. The Contractor shall only disclose this restricted data to authorised persons.
  • The data all come via the public interfaces of the social media platforms and are not enriched by the client.

Types of data which are regularly the subject of processing:

  • Data concerning the online accounts linked in the course of using the Fanpage Karma Tool (Facebook User ID, Facebook Access Token, list of Facebook pages for which the client has insights, Twitter Access Token, Instagram Access Token, LinkedIn Access Token, list of LinkedIn profiles for which the client has access).
  • In order to perform analyses for profiles, it may be necessary for the client to log in to these and grant access to the app of the contractor (e.g. Twitter or LinkedIn). In these cases, the account name, account ID, access token, token secret and their expiration date are stored.

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Users of the social media profiles.

Name of the function/service:

Fanpage Karma Tool – Fanpage Karma Monitoring

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • With the assistance of Fanpage Karma Monitoring, the client can monitor keywords in public postings on social media services that are accessible for the search.
  • The contractor will query the keywords defined by the client via the public interfaces of the platforms. No special authorizations are required for this.

Types of data which are regularly the subject of processing:

Public data that is searched for after entering a keyword and made available for viewing via a link.

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Users of the social media profiles.

Name of the function/service:

Fanpage Karma Tool – Fanpage Karma Engage

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • Fanpage Karma Engage is a community management tool for answering inquiries, contributions and comments (hereinafter "messages") on social media platforms (e.g. Facebook, Twitter, Instagram) and those received by e-mail.
  • Clients grant the contractor permission so that the Karma Engage fan page can publish the answers on their behalf on the various platforms.
  • The messages can be publicly visible (e.g. Facebook Post comments or Twitter Replies) or non-public (e.g. Facebook/Twitter direct message, e-mail).

Types of data which are regularly the subject of processing:

  • Inventory data/master data (names, account names, user IDs, links to these).
  • Content data (texts, links, images, videos, documents and files published or sent by users).
  • Usage data (time of request).
  • Location data (information on places where the contributions were written).

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Authors of the messages within the social media profiles.

Name of the function/service:

Fanpage Karma Tool – Fanpage Karma Publish

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • Fanpage Karma Publish is a tool for the editorial management and automatic publication of posts on social media platforms.
  • Users can create postings with text, links, images, documents, time of publication, restriction to user groups etc. and release them for publication through a simple release process.
  • For networks on which an automatic publication is possible (and the user has released the corresponding authorization) Fanpage Karma Engage can automatically publish the postings at the set time. In other cases, users will be asked by e-mail to publish their data.
  • Already used media (e.g. pictures, videos) can be viewed via a media library and used for further contributions.

Types of data which are regularly the subject of processing:

  • Inventory data/master data (names, account names of authors).
  • Content data (texts, links, images, videos, documents and files that are published).
  • Usage data (time of planning and publication, profile(s) to be published, restriction to user groups (targeting)).

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Authors of the published contents

Name of the function/service:

Fanpage Karma Tool – Fanpage Karma TeamBoard

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • TeamBoard is an easy way to share a live dashboard with other users who do not need a login. The dashboard can be accessed via a unique URL (the user may be able to set a password to protect access).
  • For information on data processing see Fanpage Karma Analytics.

Types of data which are regularly the subject of processing:

  • For information on data processed, please refer is made to Fanpage Karma Analytics.
  • In addition, data relating to the persons participating in the sharing process of the dashboard will be processed (time of sharing, persons involved).

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

  • For information on data subjects, please refer is made to Fanpage Karma Analytics.
  • Also affected are the people/employees participating in the process of sharing the dashboard.

Name of the function/service:

Fanpage Karma ELON Brand Report

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • The Fanpage Karma ELON Brand Report includes information about the active fans of a Facebook page, the fan loyalty, the range competition, interests and personas of the fans. The statements are only made available to the client in aggregated form. The analysis is based exclusively on publicly available data that is accessed via the Facebook API.
  • The report is provided as a PDF and/or as a printout.
  • The report also contains statements about competitors (key figures, names, profile pictures, links, contributions to Facebook pages).

Types of data which are regularly the subject of processing:

  • User IDs of all users who have publicly posted a comment to a post on a Facebook page, as well as the time of the comment and the profile ID of the Facebook page to which the users have posted the comment.
  • The period for the data of a report is 3 months (plus the previous quarter and the month after for comparison). All public comments from the largest German-speaking Facebook pages are examined.

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Users of the social media profiles.

Name of the function/service:

Fanpage Karma Good Luck Fairy

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • Automatic evaluation of Facebook promotions, sweepstakes, etc. The information on a competition posting is imported into the Fanpage Karma Tool via the Facebook API and then evaluated according to the specified criteria. As a result, profiles of Facebook users who could have won a promotion according to various possible criteria are displayed to the client (the name, the profile picture and a link to the profile are displayed). In addition, the client can download a file showing the names and Facebook IDs of all participants as well as a file containing all user comments.

Types of data which are regularly the subject of processing:

  • User IDs, names and links to profile pictures of all users who made a comment publicly on the Facebook page to be evaluated or reacted with a reaction to the promotion (e.g. Like, Haha), as well as the time of the action and, if necessary, the text of the comment.

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Users of social media profiles / participants in promotions.

Name of the function/service:

Fanpage Karma Job Börse

Purpose of the contract/services provided in the course of the contract/scope, type and purpose of data processing:

  • In the Fanpage Karma Job Market registered users can make and publish entries to job advertisements. These entries are visible to the public. Creators can disable the entries so that they are no longer publicly visible.

Types of data which are regularly the subject of processing:

  • Inventory data / master data, content data, contact data, metadata, usage data.
  • Advertisement title, job title, company name, country, city, type of employment, description, company logo, website, company description, contact person (name, email), link to application form.

Are special categories of data being processed?

No special categories of data are processed.

The categories of data subjects affected by the processing include:

Job applicants, job providers.

2. Controller and right of Instruction

  1. As the person responsible pursuant to Art. 4 No. 7 GDPR, the Controller is responsible for compliance with data protection regulations, in particular the selection of the Processor, the Data transmitted to him and the instructions issued (Art. 28 (3) a, 29 and 32 (4) GDPR).
  2. The Processor may process Data only within the framework of the Principal Agreement and the instructions of the Controller (including in particular the modification, erasure or restriction of the Data) and only to the extent that the processing is necessary for the agreed purpose, unless the Processor is required to process Data for another purpose by Union or Member State law to which the Processor is subject; in such a case, the Processor shall inform the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest (Art. 28 (3) p. 2 a GDPR).
  3. The Controller has the right to issue additional instructions at any time with regard to the processing of the Data and the security measures.
  4. If the Processor is of the opinion that an instruction by the Controller violates applicable data protection law, he will immediately point this out to the Controller. If the Processor is of the opinion that an instruction of the Controller violates applicable data protection law, then the Processor is entitled to suspend the execution of the instruction until the Controller confirms the instruction or to reject the instruction in the case of an obviously illegal instruction.
  5. The Processor may refuse instructions if they are not possible or unreasonable for the Processor (in particular because compliance with them would impose disproportionate effort or due to a lack of technical possibilities of the Processor). The rejection is only admissible under appropriate consideration of the protection of the Data of the data subjects concerned and entitles the Controller to a termination without notice for a compelling reason of the Principal Agreement, if its continuation is unreasonable for the Controller. If termination takes place before expiry of the agreed contract period of the Principal Agreement, the Controller is obliged to continue paying the agreed remuneration, unless and insofar as the reason for the instruction leading to termination was attributable to the Processor or was in the Processor's risk sphere.
  6. If additional instructions of the Controller go beyond the contractual duty of the Processor under the Principal Agreement and are not based on misconduct on the part of the Processor, then the Controller shall reimburse the Processor separately for the additional time and effort arising therefrom.
  7. The contracting Parties may appoint persons entitled to issue and receive instructions (in particular, if the responsible persons do not already follow from the Principal Agreement) and are obliged to notify the contractual Parties of any changes without delay.
  8. Responsible on the part of the Processor:
    Nicolas Graf von Kanitz
    Tel: +49 30 55656912, Fax: +49 30 577095069, E-Mail: .

3. Security of Processing and Related Obligations

  1. The Processor shall structure the internal organisation in his area of responsibility in accordance with the legal requirements and shall in particular take technical and organisational measures for appropriate security, in particular the confidentiality, integrity and availability of the Controller's Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of data subjects and ensuring their safeguarding (Art. 28 (3) and 32 - 39 in conjunction with Art 5 GDPR). Technical and organisational measures include in particular physical access control, access to processing systems, control of access to Data and input of Data, Data transfer control, control of orders and assignments, availability and integrity control, guarantee of the principle of purpose/ segregation of data and securing the rights of the affected data subjects.
  2. The technical and organisational measures on which this DPA is based are set out in Annex 1 "Security of Processing". They may be further improved in the light of technical progress and replaced by adequate protective measures, provided that they do not fall below the safety level of the measures laid down and provided that the Controller is notified of any significant changes.
  3. The Processor ensures that persons authorised to process the personal data have committed themselves to confidentiality (Art. 28 (3) S. 2 b. and 29, 32 (4) GDPR) and have been instructed in the data protection regulations of the GDPR or are subject to an appropriate statutory obligation of confidentiality.
  4. The Data and data carriers and all copies made of them within the scope of the DPA shall remain the property of the Controller, shall be carefully stored by the Processor, protected from access by unauthorized third parties and may only be deleted with the consent of the Controller, and then only in accordance with data protection law. Copies of Data may only be made if they are necessary to fulfil the main and secondary contractual obligations of the Processor towards the Controller (e.g. backups).
  5. If specified by the GDPR or supplementary regulations, in particular national regulations, the Processor shall appoint a data protection officer in accordance with legal requirements and inform the Controller accordingly (Art. 37 to 39 GDPR).
  6. Data protection officer of the Processor:
    Dr. Thomas Schwenke, Paul-Lincke-Ufer 42/43, 10999 Berlin
    E-Mail:

4. Information Duties and Duties to Cooperate

  1. The rights of the data subjects are to be fulfilled by the Controller, whereby the Processor supports the Controller according to Art. 28 (3) S. 2 e. GDPR and informs him in particular about the enquiries of the data subjects received by the Processor.
  2. The Controller must inform the Processor immediately and completely if he detects errors or irregularities with regard to the processing of the Data or with regard to compliance with the provisions of this DPA or relevant data protection regulations.
  3. In the event that the Processor ascertains facts which justify the assumption that the protection of the Data processed for the Controller has been breached, the Processor must immediately and completely inform the Controller, take the necessary protective measures without delay and assist in the fulfilment of the obligations incumbent on the Controller pursuant to Articles 33 and 34 GDPR.
  4. Should the security of the Controller's Data be endangered by third-party actions (e.g. creditors, authorities, courts with seizure, confiscation, insolvency proceedings, etc.) the Processor will immediately inform the third parties that the sovereignty and ownership of the Data lies exclusively with the Controller and, after consultation with the Controller, will, if necessary, take appropriate protective measures (e.g. file objections, applications, etc.).
  5. The Processor shall inform the Controller without delay if a supervisory authority takes action against the Processor and its activities may affect the Data processed for the Controller. The Processor supports the Controller in the performance of his duties (in particular the provision of information and toleration of inspections) towards supervisory authorities (Art. 31 GDPR).
  6. The Processor shall provide the Controller with the information necessary for the fulfilment of legal obligations (which may include, in particular, inquiries from data subjects or authorities and compliance with his accountability duties pursuant to Art. 5 (2) GDPR, as well as the carrying out of a data protection impact assessment pursuant to Art. 35 GDPR) and shall provide the necessary information regarding the processing of Data within the scope of this DPA, if the Controller cannot acquire this information himself. The information must be accessible to the Processor and does not have to be obtained from third parties, whereby employees, agents and subprocessors of the Controller are not considered as third parties.
  7. If the provision of the necessary information and the cooperation go beyond the duties of the Processor according to the Principal Agreement and is not based on misconduct on the part of the Processor, the Controller shall reimburse the Processor separately for the additional work and expenses arising therefrom.

5. Audits and Inspections

  1. The Controller has the right to audit the Processor's compliance with the legal requirements and the regulations of this DPA, in particular the technical and organisational measures, at any time to the required extent (Art. 28 (3) h. GDPR).
  2. On-site inspections are carried out within normal business hours, must be announced by the Controller within a reasonable period (at least 14 days, except in emergencies) and have to be supported by the Processor (e.g. by the provision of the necessary personnel).
  3. The inspections are limited to the necessary scope and must take into account the Processor's trade and business secrets as well as the protection of personal data of third parties (e.g. other Controllers or employees of the Processor). Only qualified inspectors are permitted to carry out the inspection, who also can identify themselves and who are bound to confidentiality with regard to the business and trade secrets and processes of the Processor and personal data or other confidential information of third parties.
  4. Instead of audits and on-site inspections, the Processor may refer the Controller to an equivalent inspection or audit by independent third parties (e.g. neutral data protection auditors), compliance with approved rules of conduct (Art. 40 GDPR) or suitable data protection or IT security certifications in accordance with Art. 42 GDPR. This applies in particular if business and trade secrets of the Processor or personal data or other confidential information of third parties would be at risk due to the audits or inspections.
  5. If the acceptance and cooperation in the inspections or adequate alternative measures of the Controller exceeds the contractual obligations of the Processor in accordance with the Principal Agreement and are not based on misconduct on the part of the Processor, the Controller shall reimburse the Processor separately for the additional time and effort arising therefrom.

6. Engagement of Subprocessors

  1. If the Processor uses the services of a subprocessor in order to carry out specific processing activities on behalf of the Controller, the same data protection obligations as set out in this DPA or other legal act between the Controller and the Processor shall be imposed on the subprocessor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of this DPA and the applicable data protection law (in particular with regard to compliance with instructions off the Controller, compliance with technical and organisational measures, provision of information and the toleration of inspections). Furthermore, the Processor must carefully select the subprocessor, check its reliability and monitor its compliance with the requirements of this DPA and the data protection law (Art. 28 (2) and 4 GDPR).
  2. Without prejudice to any restrictions by the Principal Agreement, the Controller generally agrees that the Processor may engage subprocessors for the processing of the Data.
  3. The subprocessing relationships already in existence at the time of the conclusion of this DPA are listed by the Processor in Annex 2 "Subprocessors" and are considered authorized by the Processor.
  4. The Processor shall inform the Controller of any changes to the subprocessors that are relevant to the processing of the Data. The Controller shall exercise its right to object to the changes or new subprocessors only in compliance with the principles of good faith, fairness and equity.
  5. Contractual relationships in which the Processor uses the services of third parties as a purely ancillary service in order to carry out his business activities (e.g. cleaning, security or transport services) do not constitute subprocessing within the meaning of the above provisions of this DPA. Nevertheless, the Processor must ensure, e.g. through contractual agreements or information and instructions, that the security of the Data is not endangered and that the requirements of this DPA and the data protection laws are complied with.

7. Processing in Third Countries

  1. The processing of Data as contractually specified is carried out only in a Member State of the European Union or in another state party to the Agreement on the European Economic Area (EEA).
  2. The processing of Data in a third country, also by subprocessors, may only be carried out on documented instructions from the Controller and if the particular requirements of Art. 44 ff. GDPR are met, unless the Processor is obliged to carry out processing in the third country by the law of the Union or the Member States to which the Processor is subject, in which case the Processor shall notify the Controller of these legal requirements before processing, unless the law prohibits such an information on important grounds of public interest (Article 28 (3) S. 2 a. GDPR).
  3. The authorisation of the Controller for processing in the third country shall be considered to have been given in respect of the processes listed in Annex 2 "Subprocessors".

8. Duration of the Processing, Termination of Contract and Deletion of Data

  1. This DPA becomes valid upon its conclusion, is concluded for an indefinite period and ends at the latest with the term of the main agreement.
  2. The right to termination without notice for a compelling reason is available to the contracting Parties, in particular in the event of a serious breach of the provisions of this DPA and applicable data protection law. The extraordinary termination must in general be preceded by a warning of the infringements with a reasonable period of notice, whereby the warning is not necessary if it is unlikely that the objected infringements will be remedied or if they are so severe that it is unreasonable to expect the terminating contracting party to adhere to this DPA.
  3. After completion of the processing services under this DPA, the Processor will either delete or return all personal data and copies thereof (as well as all documents obtained in connection with the contractual relationship, processing and processing results obtained and datasets), at the choice of the Controller, unless an obligation to store the personal data exists under Union law or the law of the Member States (Art. 28 (3) S. 2 g. GDPR). The right of retention is excluded with regard to the processed Data and the associated data carriers. With regard to the cancellation or return of the Data, the Controller's rights of information, documentation and inspection shall apply in accordance with this DPA.
  4. In accordance with the Principal Contract, the Contractor is entitled not to delete data that he has collected from generally accessible sources (since this data is used by other customers, etc.) or data that has been anonymised, which means it is not personal data anymore (e.g. aggregated data). The profiles of the customers are deactivated, subject to an explicit deletion request after deactivation, and are only used for reactivation. In the case of test users, only the name and Facebook ID are stored for multiple login detection, and the email address is deleted.
  5. In any case, the obligations arising from this DPA with regard to the Data processed in the assignment shall remain in force even after termination of the DPA.
  6. If the deletion or the return of the Data exceeds the duties of the Processor according to the Principal Agreement and is not based on misconduct on the part of the Processor, then the Controller shall reimburse the Processor separately for the additional time and effort arising therefrom.

9. Remuneration

  1. The remuneration agreed under this DPA also includes an expense allowance for the working hours of the personnel utilized by the Processor as well as necessary expenses (e.g. travel or material costs). If possible, foreseeable and reasonable, the Processor shall inform the Controller of the amount of the remuneration by means of an appropriate estimation.
  2. If the Processor is entitled to remuneration in accordance with this DPA, the remuneration shall be charged at an hourly rate of EUR 120.00 net. In all other respects, the remuneration provisions of the Principal Agreement shall apply (Terms of Service and Pricing).

10. Liability

  1. In the internal relationship with the Processor, the Controller alone shall be responsible to the data subject for the compensation of damages suffered by the data subject due to Data processing or use within the scope of processing instructions which is inadmissible or incorrect in accordance with data protection laws.
  2. The contracting Parties shall indemnify each other from liability if a contracting party proves that it is in no way responsible for the circumstance by which the damage occurred to a data subject.

11. Final Provisions, Amendments, Form of Communication, Choice of Law, Place of Jurisdiction

  1. Amendments, additional agreements and addenda to this DPA and its annexes require a written agreement and an express note that this is an amendment or addition to this DPA. This also applies to the waiver of this formal requirement.
  2. This DPA shall only oblige the Processor in so far as this is necessary to fulfil the statutory obligations, in particular in accordance with Art. 28 ff. GDPR and does not impose any further duties on the Processor.
  3. Unless otherwise stipulated in this DPA and in the main agreement, communication between the Processor and the Controller within the framework of this DPA (in particular with regard to instructions and provision of information) shall at least be in text form (e.g. e-mail). A lesser form (e.g. oral) may be permissible under the circumstances instead of the text form (e.g. in an emergency situation) but must be confirmed immediately at least in text form. If the written form is required, the written form is understood in the meaning of the GDPR.
  4. The law of the Federal Republic of Germany shall apply. The exclusive place of jurisdiction for all disputes arising from or in connection with this DPA shall be the Processor's registered office, provided that the Controller is a merchant, a legal entity under public law or a public law fund or the Controller has no place of jurisdiction in the Federal Republic of Germany. The Processor reserves the right to bring his claims to the legal place of jurisdiction.

................................................................................................................

Place, date, signature of Controller

Berlin, Aug 16, 2018

................................................................................................................

Place, date, signature of Processor


Data Processing Agreement

Annex 1 – Security of processing

Technical and organisational measures pursuant to Art. 32 GDPR

1. Data Protection Management, Rights of Data Subjects, Privacy by Design and Data Protection regarding Employees

Fundamental measures that are aimed at safeguarding the rights of data subjects, immediate reaction in emergencies, the requirements of privacy by design and data protection with regard to employees:

  • There is an in-house data protection management system, compliance with which is constantly monitored and evaluated on a case-by-case basis and at least every six months.
  • There is a security concept that guarantees the protection of the rights of the data subjects (information, correction, deletion or restriction of processing, Data transfer, revocation & objections) within the legal time limits. It includes forms, instructions and implementation procedures set up, as well as the appointment of the persons in charge of implementation.
  • A security concept exists that guarantees an immediate reaction to data breaches (evaluation, documentation, reporting) in accordance with legal requirements. It includes forms, instructions and implementation procedures set up, as well as the designation of the persons in charge of implementation.
  • The protection of personal data is already incorporated in the development or selection of hardware, software and processes, taking into account the state of the art, the cost of implementation and the nature, scope, context and purpose of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, in accordance with the principle of data protection by design and by default (Art. 25 GDPR).
  • The software used is always kept up to date, as are virus scanners and firewalls.
  • Employees have committed themselves to confidentiality and are instructed as well as informed of possible liability consequences with regard to data protection. If employees work outside the company's premises or use private equipment for Data processing, special regulations exist for the protection of Data in these constellations and for safeguarding the rights of data subjects and Controllers in relation to Art. 28 GDPR.
  • The keys, access cards or codes issued to employees, as well as authorisations issued with regard to the processing of personal data, are withdrawn or revoked after their leave from the company or a change in area of responsibility.
  • The cleaning personnel, security guards and other service providers involved in the performance of ancillary business tasks are carefully selected and it is ensured that they comply with the protection of personal data.
  • A procedure has been implemented for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.

2. Physical Access Control

Measures to prevent unauthorised persons from accessing data processing facilities with which personal data is processed:

  • A "paperless office" is maintained and documents are only stored digitally and only in exceptional cases in paper form.
  • With the exception of workstations and mobile devices, no data processing systems are maintained in the company's own business premises. The Controller's Data is stored at external hosting providers in compliance with the specifications for processing on behalf of other Controllers.
  • There are access regulations for persons not employed by the company.
  • The visitors are being documented.
  • Access to the Processor's data processing systems (EDP rooms at the server location) is completely denied to unauthorised persons and is only granted to authorised employees.
  • Access is secured by a manual locking system with security locks.
  • There is a scheme for issued keys or access cards.

3. Control of Access to Processing Systems

Measures to prevent the use of data processing systems by unauthorised persons:

  • There is a rights management concept with which the access authorizations of employees, representatives and other persons (e.g. users within the system) are defined and only reach as far as they are required for the specified purpose.
  • All data processing systems are password protected.
  • There is a password policy that stipulates that passwords must have a minimum length and complexity that corresponds to the state of the art and security requirements.
  • Password management software is being implemented.
  • Registrations in the processing systems are logged.
  • Anti-virus software is implemented.
  • Software firewalls are implemented.
  • The website and/or access to online software services are protected by an up-to-date TLS/SSL encryption.
  • There is a limitation of failed login attempts to internal systems (e.g. blocking logins or IP addresses).
  • If technically supported, two-factor authentication is used.
  • Encrypted transmission technologies (e.g. VPN) are used for external access to internal systems (e.g. for remote maintenance).
  • Server systems and services with intrusion detection systems are used.

4. Control of Access to Data, Input Control and Integrity Protection

Measures to ensure that those entitled to use a Data processing system can only access the Data covered by their access authorisation and that personal data cannot be entered, inserted, read, copied, modified or removed without authorisation during processing, use and after storage; and measures to enable the processing operations to be subsequently reconstructed:

  • There is a rights management concept with which the access authorizations of employees, representatives and other persons (e.g. users within the system) are defined and only extend as far as they are required for the specified use.
  • Logging of every single step of Data processing, especially access to applications, especially during Data entry, modification and deletion.
  • Employees' access to Data is logged. If individual accesses are not logged, it is ensured that it is transparent who had access to which Data and when (e.g. by logging software usage or conclusions from access times and the authorization concept).
  • Logging of every single step, especially access to applications, especially when inputting, changing and deleting Data.
  • Data carriers are stored securely.
  • There is an deleting and disposal concept in accordance with DIN 66399 (or an adequate deletion and destruction level) with defined responsibilities and reporting obligations. Employees were informed about legal requirements, deletion periods and specifications for Data deletion or equipment disposal by Data destruction service providers.
  • The processing of Data that is not deleted (e.g. as a result of statutory archiving obligations) is restricted by restriction notes and segregation.

5. Control of Data Transmission and Confidentiality

Measures to ensure that personal data cannot be read, copied, altered or removed without authorisation during electronic transmission or during transport or storage on data carriers and that it is possible to check and establish to which points personal data is to be transmitted by data transmission devices:

  • The persons authorised to hand over data carriers and the persons authorised to receive them shall be determined.
  • The period for which access to the Data is possible is determined.
  • In the case of physical transport, secure transport containers or packaging are chosen, or the security of the Data is guaranteed by personal supervision, provided that this is sufficient in view of the risks to the Data.
  • In the case of remote access to Data, protocol measures ensure that Data transmissions or disclosures are accountable.
  • An overview of periodic retrieval and transmission processes is established and monitored.
  • If necessary, possible and reasonable, Data will be passed on in anonymised form or in pseudonymised form.

6. Control of Orders and Assignments

Measures to ensure that personal data processed on behalf of the Controller can only be processed in accordance with the instructions of the Controller:

  • Obligation of employees and representatives to comply with instructions of the Controller.
  • Written specification and documentation of the instructions.
  • The contractual and legal requirements for the commissioning of subprocessors are complied with by concluding DPAs and securing and monitoring the necessary guarantees.
  • It is ensured that Data is returned or deleted after completion of the assignment.

7. Securing the Availability and Integrity of Data and Resilience of Systems

Measures to ensure that personal data are protected against accidental destruction or loss and that the integrity, availability and resilience of the systems and services associated with the processing are permanently guaranteed, as well as the availability of personal data, and that access to them can be restored in a timely manner in the event of a physical or technical incident:

  • Fail-safe server systems and services are used, which are designed in duplicate or in multiple instances, subject to load tests and hardware tests, have DDoS protection and provide an uninterruptible power supply (e.g. RAID, HA power supplies).
  • Server systems and services are used that offer a backup system at other locations, or at least in other fire sections, on which the current Data is stored and thus provide an operational system even in the event of a disaster.
  • Server systems and services are used which have moisture detectors as well as fire and smoke detection systems and corresponding fire extinguishing devices or fire extinguishers in the EDP room.
  • Server systems and services are used that offer a reliable and controlled backup and recovery concept. Backups are made daily. The backups are encrypted.
  • Backups are also created and controlled for Data processing on workstations and mobile devices. Backups are ongoing. The backups are encrypted.
  • The availability of the data processing systems is permanently monitored.

8. Guarantee of the Principle of Purpose, Anonymisation, Pseudonymisation and the Segregation of Data

Measures to ensure that data collected for different purposes can be processed separately, anonymised and pseudonymised:

  • Where necessary, possible and reasonable, Data is physically separated (e.g. by using different servers). If there is no physical separation, the Data is separated logically (e.g. in different databases or by marking with appropriate purpose attributes or Data fields).
  • If necessary and technically possible and reasonable, data will be pseudonymised and anonymised, in particular using encryption methods for the aforementioned purposes.
  • An unauthorized access to the Data is prevented by an authorization concept.
  • In the case of pseudonymised storage, the identification keys are stored separately from the Data and secured against unauthorised or unintended linkage during processing.
  • Productive and test systems are separated.

Data Processing Agreement

Annex 2 – “Subprocessors”

The current list of subprocessing relationships is published at: https://www.fanpagekarma.com/privacy/subprocessors.

As of: May 2018

Download Agreement
Feedback? Questions?