Data Processing Addendum
1. Introduction
1.1
The Responsible Party wishes to contract or has contracted with Kero for certain Services to be provided by Kero which require or necessarily imply the processing of Personal Data by Kero.
1.2
2. Interpretation
2.1
Unless otherwise defined herein, the terms, “Data Subject”, “Personal Data” and “Processing” where used in this Data Processing Addendum shall have the same meaning as in the relevant Data Protection Laws, and their cognate terms shall be construed accordingly. Capitalized terms and expressions used in this Data Processing Addendum shall be given the following meanings unless the context clearly indicates otherwise:
2.1.1
“Applicable Laws” means any laws other than the Data Protection Laws to which Kero may additionally be subject;
2.1.2
2.1.3
“Cellular Network” means a form of public switched telecommunications network adhering to standards and protocols of the International Telecommunication Union and consisting of, inter alia, wireless radio communications links between nodes in the network;
2.1.4
“Cellular Network Operator” means a person operating a Cellular Network;
2.1.5
“Data Protection Laws” means, to the extent applicable to the Personal Data to be processed by Kero for or on behalf of the Responsible Party, the data protection and privacy laws detailed in Schedule 1 hereto;
2.1.6
“Data Retention and Deletion Policy” means Kero’s Data Retention and Deletion Policy as amended from time to time on written notice to the Responsible Party;
2.1.7
“Data Transfer” means:
2.1.7.1
a transfer of the Responsible Party Personal Data from the Responsible Party to Kero; or
2.1.7.2
2.1.8
“EU” means the European Union;
2.1.9
“EU Data Processing Addendum” means the EU Data Processing Addendum annexed hereto;
2.1.10
“International Telecommunication Union” means the specialized agency of the United Nations intergovernmental organization responsible for the co-ordination of the use of information and communication technologies amongst member states of the United Nations;
2.1.11
“MSISDN” means a Mobile Station International Subscriber Directory Number being a number capable of uniquely identifying a subscriber to a Cellular Network;
2.1.12
2.1.13
“Recipient” means a natural or juristic person who has entered into an agreement with a Cellular Network Operator;
2.1.14
“Regulatory Authority” means the regulatory or supervisory authority acting in terms of the relevant Data Protection Laws;
2.1.15
“Responsible Party Personal Data” means any Personal Data Processed by Kero or by a Sub-Processor on behalf of the Responsible Party pursuant to or in connection with the Principal Agreement, and includes the following categories of personal information processed:
2.1.15.1
Client Data: personal data made available to Kero by the Responsible Party; and
2.1.15.2
2.1.16
“Services” mean the services to be provided by Kero to the Responsible Party in terms of the Principal Agreement which may include but not be limited to services related to the transmission of communications to Recipients by means of Cellular Networks operated by Cellular Network Operators;
2.1.17
“Signature Date” means the date by which this Data Processing Addendum has been signed and accepted by both Parties in writing;
2.1.18
“Sub-Processor” means any person appointed by or on behalf of Kero to process Personal Data on behalf of the Responsible Party in connection with the Principal Agreement; and
2.1.19
“UK” means the United Kingdom of England and Wales;
2.1.20
“UK Data Processing Addendum” means the UK Data Processing Addendum annexed to the EU Data Processing Addendum annexed hereto.
2.2
Capitalized words and phrases used in this Data Processing Addendum that are defined in terms of the Principal Agreement shall, unless expressly defined to the contrary in this Data Processing Addendum, be given the same meanings in this Data Processing Addendum as have been given to them in the Principal Agreement.
2.3
3. Binding Agreement
3.1
3.2
3.3
Changes to the terms and conditions of this Data Processing Addendum may be published to the Kero.chat website from time to time. These changes shall deemed to be binding on a User where a User continues to make use of any Services accessible via the Kero.chat website following the changes being reasonably prominently published on the website or otherwise reasonably drawn to the attention of the User.
4. Processing of Responsible Party Personal Data
4.1
4.2
4.3
4.3.1
4.3.1.1
4.3.1.2
4.3.2
5. Kero Personnel
5.1
6. Security
6.1
6.2
7. Cellular networks and Sub-Processing
7.1
7.2
8. Data Subject Rights
8.1
8.2
8.2.1
promptly notify the Responsible Party if it receives a request from a Data Subject under any Data Protection Law in respect of the Responsible Party Personal Data; and
8.2.2
9. Personal Data Breach
9.1
9.2
10. Data Protection Impact Assessment and Prior Consultation
10.1
11. Deletion or Return of Responsible Party Personal Data
11.1
Kero undertakes to comply with the provisions of its Data Retention and Deletion Policy, a copy of which shall be made available to the Responsible Party on request, and with the provisions of any other Applicable Law relating to the retention or deletion, as the case may be, of the Responsible Party’s Personal Data.
11.2
11.3
12. Audit Rights
12.1
12.2
12.3
12.4
12.4.1
to any individual unless he or she produces reasonable evidence of identity and authority;
12.4.2
12.4.3
SCHEDULE 1 – DATA PROTECTION AND PRIVACY LAWS
For the purposes of clause 2.1.5 of the Data Processing Addendum, the Data Protection Laws shall mean and include the laws of the following territories:
EU DATA PROCESSING ADDENDUM
Incorporating Standard Contractual Clauses contained in the European Commission Implementing Decision dated 4 June 2021 for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council.
SECTION I
Clause 1
Purpose and scope
(a)
(b)
(i)
(ii)
(c)
(d)
Clause 2
Effect and invariability of the Clauses
(a)
(b)
Clause 3
Third-party beneficiaries
(a)
(i)
(ii)
(iii)
(iv)
(v)
(vi)
(vii)
(viii)
(b)
Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
Clause 4
Interpretation
(a)
(b)
(c)
Clause 5
Hierarchy
In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
Clause 6
Description of the transfer(s)
Clause 7
Docking clause
(a)
(b)
(c)
SECTION II – OBLIGATIONS OF THE PARTIES
Clause 8
Data protection safeguards
MODULE ONE: Transfer controller to controller
8.1
Purpose limitation
where it has obtained the data subject’s prior consent;
(ii)
(iii)
8.2
Transparency
(i)
(ii)
(iii)
(iv)
(b)
(c)
(d)
8.3
Accuracy and data minimisation
(a)
(b)
(c)
8.4
Storage limitation
8.5
(b)
(c)
(d)
(e)
(f)
(g)
8.6
Sensitive data
8.7
(ii)
(iii)
(iv)
(v)
(vi)
Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.
8.8
Processing under the authority of the data importer
8.9
Documentation and compliance
(a)
(b)
MODULE TWO: Transfer controller to processor
8.1
Instructions
(b)
8.2
Purpose limitation
8.3
8.4
8.5
8.6
Security of processing
(a)
(b)
(c)
(d)
8.7
Sensitive data
8.8
(i)
(ii)
(iii)
(iv)
8.9
Documentation and compliance
(a)
(b)
(c)
(d)
(e)
MODULE THREE: Transfer processor to processor
8.1
Instructions
(a)
(b)
(c)
(d)
8.2
Purpose limitation
8.3
8.4
If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to rectify or erase the data.
8.5
8.6
(a)
(b)
(c)
(d)
8.7
Sensitive data
8.8
(i)
(ii)
(iii)
(iv)
Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.
8.9
Documentation and compliance
(b)
(c)
The data importer shall make all information necessary to demonstrate compliance with the obligations set out in these Clauses available to the data exporter, which shall provide it to the controller.
(d)
(e)
Where the audit is carried out on the instructions of the controller, the data exporter shall make the results available to the controller.
(f)
(g)
MODULE FOUR: Transfer processor to controller
8.1
Instructions
(b)
(c)
(d)
8.2
Security of processing
(b)
(c)
8.3
Documentation and compliance
(b)
(a)
(b)
(c)
(d)
(e)
MODULE THREE: Transfer processor to processor
(a)
GENERAL WRITTEN AUTHORISATION The data importer has the controller’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the controller in writing of any intended changes to that list through the addition or replacement of sub-processors at least 7 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the controller with the information necessary to enable the controller to exercise its right to object. The data importer shall inform the data exporter of the engagement of the sub-processor(s).
(b)
(c)
(d)
(e)
Clause 10
(a)
(b)
(i)
(ii)
(iii)
(iii)
(c)
(d)
(i)
(ii)
(e)
(f)
(g)
MODULE TWO: Transfer controller to processor
(a)
(b)
(c)
MODULE THREE: Transfer processor to processor
(a)
(b)
(c)
MODULE FOUR: Transfer processor to controller
Clause 11
Redress
(a)
MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
(b)
(c)
(i)
(ii)
(d)
The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
(e)
(f)
The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
Clause 12
Liability
MODULE FOUR: Transfer processor to controller
(a)
(b)
(c)
(d)
The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its / their responsibility for the damage.
(e)
The data importer may not invoke the conduct of a processor or sub-processor to avoid its own liability.
(a)
(b)
(c)
(d)
(e)
(e)
(f)
(g)
(a)
[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.
[Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.
(b)
The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
Clause 14
Local laws and practices affecting compliance with the Clauses
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
MODULE FOUR: Transfer processor to controller (where the EU processor combines the personal data received from the third country-controller with personal data collected by the processor in the EU)
(a)
(b)
(i)
(ii)
(ii)
(c)
(d)
(e)
(f)
Clause 15
Obligations of the data importer in case of access by public authorities
MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
15.1
Notification
(i)
(ii)
(ii)
(b)
(c)
(d)
(e)
Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
15.2
Review of legality and data minimisation
(b)
(c)
SECTION IV – FINAL PROVISIONS
Clause 16
Non-compliance with the Clauses and termination
(a)
(b)
(c)
(i)
(ii)
(ii)
(d)
[For Modules One, Two and Three: Personal data that has been transferred prior to the termination of the contract pursuant to
diately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data.] [For Module Four: Personal data collected by the data exporter in the EU that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall immediately be deleted in its entirety, including any copy thereof.] The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
(e)
Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
MODULE THREE: Transfer processor to processor
(a)
(b)
The Parties agree that those shall be the courts of the Republic of Ireland.
(c)
(d)
APPENDIX
EXPLANATORY NOTE:
ANNEX I
A. LIST OF PARTIES
MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
MODULE FOUR: Transfer processor to controller
Data exporter(s): [Identity and contact details of the data exporter(s) and, where applicable, of its/their data protection officer and/or representative in the European Union]
Data importer(s): [Identity and contact details of the data importer(s), including any contact person with responsibility for data protection]
B. DESCRIPTION OF TRANSFER
MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
MODULE FOUR: Transfer processor to controller
Categories of data subjects whose personal data is transferred
The personal data transferred concern the following categories of data subjects:
- Clients
- Message Recipients
Categories of personal data transferred
The personal data transferred concern the following categories of data:
- Contact information (email, telephone number, mobile phone number, address, company)
- First and last name
- Title
- Account information (user id, username, password)
- Purchasing information (transaction identifiers)
- Connection data (IP address)
- Message Data (message recipient personal data processed on behalf of the client, identified by mobile phone number, and including recipient contact information in the message body)
Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.
Not applicable
The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis).
Continuous during the provision of the messaging services.
Nature of the processing
The personal data transferred will be subject to the following basic processing activities:
- Delivery of messages
- Technical service support
- Connectivity service support
Purpose(s) of the data transfer and further processing
The provision and support of the messaging services.
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period
We receive personal data that is used or intended to be used with our messaging systems, either (a) directly from our clients or (b) in response to a client’s communications or campaign.
(a)
(b)
We retain message sender and receiver identities, including mobile phone numbers, mobile subscriber line identity numbers, IP addresses of persons accessing webpages and links through our messaging systems, as well as message content and sender and receiver locations at the time messages were sent and received.
We automatically log the message personal data described above for each message sent using our messaging systems for a period of up to 1 year, provided however that we remove access to personal Message Data from our production environments to a controlled data warehouse environment within 35 days of the processing of the relevant messages on our messaging platform. We will retain these logs for at least as long as may be required in terms of laws to which we are subject.
We also automatically log the message personal data described above for message received by our messaging system for a period of up to 1 year for incoming messages that are responses to a client’s MT communications. For MO communications sent to a premium rated number (that is a number charged above the standard rate for an SMS message), we automatically log the message personal data received by our messaging system for a period of up to 3 years.
If a complaint in relation to a premium rate number was lodged with the relevant regulatory body in a jurisdiction, we then retain the message personal data, and the associated client account details, for up to 5 years.
We may also retain anonymised sender data for an indefinite period to build up statistical data about the use of our services for business development and planning purposes.
We also retain client account user identities together with other client account user identifying information, including email addresses, physical addresses, telephone numbers, user device identifiers, IP addresses as well as web and application histories of users who have installed cookies on their devices in terms of our Cookie Policy. For juristic persons we may additionally retain entity registration numbers and tax numbers. We also retain client transaction data including financial data and client purchase histories.
We retain client account records for as long as a person remains our client and for a period of up to 7 years thereafter provided however that we remove access to client account data from our production environments to a controlled data storage environment within 180 days from the date of the termination of services. After the retention period of 7 years has expired, we delete client account data from our storage environment.
Where persons are no longer clients of Kero, we may retain client personal data for further marketing purposes. Where such persons request to opt-out of all forms of communication with us as a business, where we act as that personal data controller, we delete such persons’ personal data from our marketing systems within 1-year period of time following the date of last contact with such persons.
We may retain anonymised Client Data for an indefinite period to build up statistical data about the use of our services for business development and planning purposes.
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
See Annex III for details.
C. COMPETENT SUPERVISORY AUTHORITY
MODULE ONE: Transfer controller to controller
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679: The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.
Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679: The supervisory authority of the Republic of Ireland being one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, shall act as competent supervisory authority.
ANNEX II - TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
- We undertake an analysis of the risks presented by our processing, and use this to assess the appropriate level of security we need to put in place.
- When deciding what measures to implement, we take account of the state of the art and costs of implementation.
- We have an information security policy and take steps to make sure the policy is implemented. We also have additional policies and ensure that controls are in place to enforce them.
- We make sure that we regularly review our information security policies and measures and, where necessary, improve them.
- We have put in place basic technical controls such as those specified by established frameworks.
- We understand that we may also need to put other technical measures in place depending on our circumstances and the type of personal data we process.
- We use encryption and pseudonymisation where it is appropriate to do so.
- We understand the requirements of confidentiality, integrity and availability for the personal data we process.
- We make sure that we can restore access to personal data in the event of any incidents, such as by establishing an appropriate backup process.
- We conduct regular testing and reviews of our measures to ensure they remain effective, and act on the results of those tests where they highlight areas for improvement.
- Where appropriate, we implement measures that adhere to an approved industry code of conduct.
- We ensure that any data processor we use also implements appropriate technical and organisational measures.
ANNEX III – LIST OF SUB-PROCESSORS
MODULE TWO: Transfer controller to processor
MODULE THREE: Transfer processor to processor
The controller has authorised the use of the following sub-processors as listed on the Kero website, available here.
UK DATA PROCESSING ADDENDUM
DATE OF THIS UK DATA PROCESSING ADDENDUM:
BACKGROUND:
INTERPRETATION OF THIS DATA PROCESSING ADDENDUM
3. Where this Data Processing Addendum uses terms that are defined in the Annex those terms shall have the same meaning as in the Annex. In addition, the following terms have the following meanings:
This Data Processing Addendum
This Data Processing Addendum to the Clauses.
The Annex
The Standard Contractual Clauses set out in the Annex of Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
All laws relating to data protection, the processing of personal data, privacy and/or electronic communications in force from time to time in the UK, including the UK GDPR and the Data Protection Act 2018.
The United Kingdom General Data Protection Regulation, as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018.
UK
The United Kingdom of Great Britain and Northern Ireland
4.
5.
6.
Any references to legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, reenacted and/or replaced after this Data Processing Addendum has been entered into.
HIERARCHY
7.
In the event of a conflict or inconsistency between this Data Processing Addendum and the provisions of the Clauses or other related agreements between the Parties, existing at the time this Data Processing Addendum is agreed or entered into thereafter, the provisions which provide the most protection to data subjects shall prevail.
INCORPORATION OF THE CLAUSES
8. This Data Processing Addendum incorporates the Clauses which are deemed to be amended to the extent necessary so they operate:
(a)
(b)
to provide appropriate safeguards for the transfers in accordance with Articles 46 of the UK GDPR Laws.
9.
to provide appropriate safeguards for the transfers in accordance with Articles 46 of the UK GDPR Laws.
(a)
(b)
“The details of the transfers(s) and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred) are those specified in Annex I.B where UK Data Protection Laws apply to the data exporter’s processing when making that transfer.”
(c)
(d)
(e)
(f)
(g)
Clause 17 is replaced to state “These Clauses are governed by the laws of England and Wales”.
(h)
“Any dispute arising from these Clauses shall be resolved by the courts of England and Wales. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of any country in the UK. The Parties agree to submit themselves to the jurisdiction of such courts.”
(i)
The footnotes to the Clauses do not form part of the Addendum.
AMENDMENTS TO THIS DATA PROCESSING ADDENDUM
10.
IN WITNESS WHEREOF, this Data Processing Addendum is entered into and becomes a binding part of the Kero Terms of Service with effect from the date first set out above.
By signing we agree to be bound by the UK Data Processing Addendum to the EU Commission Standard Contractual Clauses contained in the EU Data Processing Addendum.