The Parties acknowledge that for purposes of Applicable Privacy Laws:
Each Party (the “Indemnifying Party”) agrees to indemnify, keep indemnified and defend at its own expense the other Party (the “Indemnified Party”) against all costs, claims, damages or expenses incurred by the Indemnified Party or for which the Indemnified Party may become liable due to any failure by the Indemnifying Party or its employees, subcontractors or agents to comply with any of its obligations under these Data Privacy Terms or the Applicable Privacy Laws.
| Subject matter of processing The Services as set out in the Agreement. | |||||
| Duration of Processing The Processing shall take place for the duration of the Agreement. | |||||
| Nature and Purpose of Processing The purpose of the Processing shall be as defined in the main Data Privacy Terms. To include: | |||||
| The provision of the Services described in the orders initiated by the Client from time to time under the Agreement | including: | ||||
| Performing services on behalf of the Business | such as maintaining and servicing Client accounts | processing or fulfilling Client’s orders and other transactions; verifying Client’s information; and providing analytic services to Client. | |||
| Providing advertising and marketing services | such as providing a platform for advertising inventory management; and offering services to optimize advertising performance. | ||||
| Auditing related to counting | verifying | and quality control of ad impressions. | |||
| Debugging to identify and repair errors that impair intended functionality. | |||||
| Personal Data Categories First Name | Last Name | Home Address | Email Address | Phone Number | |
| Data Subject Types Clients: Client provided data | including Business Email | First Name | Last Name | and Phone Number | is used to create individual user accounts that provide access our services and applications. |
| Consumer Data: Client provided data may be used for internal analytical purposes to optimize campaign performance. This data may include First Name | Last Name | Home Address | Email Address | Phone Number | |
| Website Visitors: Tracking technologies may be used to capture user activity when visiting any of the Company websites to help facilitate and personalize the website. | |||||
| Approved Subcontractors AdCellerant Subprocessors List | |||||
| Security Measures Physical access controls | |||||
| Access to Company office space requires a Company issued and managed electronic badge along with rotating elevator code. CCTV is monitored and positioned at every entry point. Data Centre is cloud based with physical locations protected by security guards | electronic badging | CCTV and periodic security reviews. | |||
| System access controls | |||||
| Systems are protected with RBAC aligning to the minimum-need-know standard. Access rights are reviewed quarterly. Access is deprovisioned immediately upon termination. | |||||
| Data access controls | |||||
| Data is protected with RBAC aligning to the minimum-need-know standard. Access rights are reviewed quarterly. Access is deprovisioned immediately upon termination. | |||||
| Transmission controls | |||||
| The Transmission of data and the connectivity to any systems | APIs | or other services requires SSL and TLS 1.2 | or above | encryption. | |
| Input controls | |||||
| Technical protections are in place to prevent the input and uploading of inaccurate data and malicious file types. | |||||
| Data backups | |||||
| Backups are performed every hour and housed in a separate geo-location than the primary. Data validation is performed on a continual basis to ensure data integrity. Data at rest is encrypted to a minimum cipher of AES-256. | |||||
| Data segregation | |||||
| Client data is not comingled with that of other clients and production data is not used for development purposes. | |||||
| Activity Monitoring | |||||
| All user activity and data transmissions are monitored 24/7/365 to alert Security Operations personnel of unauthorized or unusual activity that needs to be investigated. | |||||
| Vulnerability Patching | |||||
| Vulnerabilities must be resolved or reduced to a LOW rating using severity-based timelines: URGENT/CRITICAL within 5 calendar days | HIGH within 30 calendar days | and MEDIUM within 60 calendar days |
Subject matter of processing | The Services as set out in the Agreement. |
Duration of Processing | The Processing shall take place for the duration of the Agreement. |
Nature and Purpose of Processing | The purpose of the Processing shall be as defined in the main Data Privacy Terms. To include: The provision of the Services described in the orders initiated by the Client from time to time under the Agreement, including:
|
Personal Data Categories | First Name, Last Name, Home Address, Email Address, Phone Number |
Data Subject Types | Clients: Client provided data, including Business Email, First Name, Last Name, and Phone Number, is used to create individual user accounts that provide access our services and applications. Consumer Data: Client provided data may be used for internal analytical purposes to optimize campaign performance. This data may include First Name, Last Name, Home Address, Email Address, Phone Number Website Visitors: Tracking technologies may be used to capture user activity when visiting any of the Company websites to help facilitate and personalize the website. |
Approved Subcontractors | |
Security Measures |
Access to Company office space requires a Company issued and managed electronic badge along with rotating elevator code. CCTV is monitored and positioned at every entry point. Data Centre is cloud based with physical locations protected by security guards, electronic badging, CCTV and periodic security reviews.
Systems are protected with RBAC aligning to the minimum-need-know standard. Access rights are reviewed quarterly. Access is deprovisioned immediately upon termination.
Data is protected with RBAC aligning to the minimum-need-know standard. Access rights are reviewed quarterly. Access is deprovisioned immediately upon termination.
The Transmission of data and the connectivity to any systems, APIs, or other services requires SSL and TLS 1.2, or above, encryption.
Technical protections are in place to prevent the input and uploading of inaccurate data and malicious file types.
Backups are performed every hour and housed in a separate geo-location than the primary. Data validation is performed on a continual basis to ensure data integrity. Data at rest is encrypted to a minimum cipher of AES-256.
Client data is not comingled with that of other clients and production data is not used for development purposes.
All user activity and data transmissions are monitored 24/7/365 to alert Security Operations personnel of unauthorized or unusual activity that needs to be investigated.
Vulnerabilities must be resolved or reduced to a LOW rating using severity-based timelines: URGENT/CRITICAL within 5 calendar days, HIGH within 30 calendar days, and MEDIUM within 60 calendar days |
(VERSION A1.0, in force 21 March 2022)
This International Data Transfer Agreement (“IDTA”) has been issued by the Information Commissioner for Parties making Restricted Transfers. The Information Commissioner considers that it provides Appropriate Safeguards for Restricted Transfers when it is entered into as a legally binding contract.
This IDTA forms a part of the Data Privacy Terms, and the Agreement, and governs any Restricted Transfers of the Personal Data types and categories listed in Attachment 1 of these Data Privacy terms.
Start date | Shall have the same meaning as the Effective Date in the Agreement. | |
The Parties | Exporter (who sends the Restricted Transfer) | Importer (who receives the Restricted Transfer) |
Parties’ details and Key Contact | The details of the Exporter/Controller, in particular the legal name and information on the contact person for this IDTA, are specified in the Agreement, in which the Controller is referred to as the Client. | Name: AdCellerant UK Ltd Company Number: 16397522 Address: 10 John Street, London, United Kingdom, WC1N 2EB. Contact person’s name, position, and contact details: Douglas Ljung – Director of GRC / Data Protection Officer [email protected] +1 303.656.1355 Data Protection contact details: Douglas Ljung – Director of GRC / Data Protection Officer [email protected] +1 303.656.1355 |
Signatures confirming each Party agrees to be bound by this IDTA | This IDTA are an integral part of Exporter’s Agreement with the Importer/Company. As such, the parties agree that their conclusion of the Agreement shall constitute the conclusion of this IDTA as well. | This IDTA are an integral part of the Importer/Company’s Agreement with the Client. As such, the parties agree that their conclusion of the Agreement shall constitute the conclusion of this IDTA as well. |
UK country’s law that governs the IDTA: | ☒ England and Wales ☐ Northern Ireland ☐ Scotland |
Primary place for legal claims to be made by the Parties | ☒ England and Wales ☐ Northern Ireland ☐ Scotland |
The status of the Exporter | In relation to the Processing of the Transferred Data: ☒ Exporter is a Controller ☐ Exporter is a Processor or Sub-Processor |
The status of the Importer | In relation to the Processing of the Transferred Data: ☐ Importer is a Controller ☒ Importer is the Exporter’s Processor or Sub-Processor ☐ Importer is not the Exporter’s Processor or Sub-Processor (and the Importer has been instructed by a Third Party Controller) |
Whether UK GDPR applies to the Importer | ☒ UK GDPR applies to the Importer’s Processing of the Transferred Data ☐ UK GDPR does not apply to the Importer’s Processing of the Transferred Data |
Linked Agreement | If the Importer is the Exporter’s Processor or Sub-Processor – the agreement(s) between the Parties which sets out the Processor’s or Sub-Processor’s instructions for Processing the Transferred Data: The Agreement and any associated Statement of Work, as defined in the main body of the Data Privacy Terms. |
Term | The Importer may Process the Transferred Data for the following time period: ☒ the period for which the Linked Agreement is in force ☐ time period: ☐ (only if the Importer is a Controller or not the Exporter’s Processor or Sub-Processor) no longer than is necessary for the Purpose. See Part 5, Annex I for the current description of processing, for further information. |
Ending the IDTA before the end of the Term | ☒ the Parties cannot end the IDTA before the end of the Term unless there is a breach of the IDTA or the Parties agree in writing. ☐ the Parties can end the IDTA before the end of the Term by serving: months’ written notice, as set out in Section 29 (How to end this IDTA without there being a breach). |
Ending the IDTA when the Approved IDTA changes | Which Parties may end the IDTA as set out in Section 29.2: ☐ Importer ☐ Exporter ☒ neither Party |
Can the Importer make further transfers of the Transferred Data? | ☒ The Importer MAY transfer on the Transferred Data to another organisation or person (who is a different legal entity) in accordance with Section 16.1 (Transferring on the Transferred Data). ☐ The Importer MAY NOT transfer on the Transferred Data to another organisation or person (who is a different legal entity) in accordance with Section 16.1 (Transferring on the Transferred Data). See Part 5, Annex II for the current list of Sub-processors. |
Specific restrictions when the Importer may transfer on the Transferred Data | The Importer MAY ONLY forward the Transferred Data in accordance with Section 16.1: ☐ if the Exporter tells it in writing that it may do so. ☐ to: ☐ to the authorised receivers (or the categories of authorised receivers) set out in: ☒ there are no specific restrictions. |
Review Dates | ☐ No review is needed as this is a one-off transfer and the Importer does not retain any Transferred Data First review date: The Parties must review the Security Requirements at least once: ☐ each month(s) ☐ each quarter ☐ each 6 months ☒ each year ☐ each year(s) ☐ each time there is a change to the Transferred Data, Purposes, Importer Information, TRA or risk assessment |
Transferred Data | The personal data to be sent to the Importer under this IDTA consists of: ☒ The categories of Transferred Data will update automatically if the information is updated in the Linked Agreement referred to. ☐ The categories of Transferred Data will NOT update automatically if the information is updated in the Linked Agreement referred to. The Parties must agree a change under Section 5.3. See Part 5, Annex I for the current description of processing. |
Special Categories of Personal Data and criminal convictions and offences | The Transferred Data includes data relating to: ☒ racial or ethnic origin ☒ political opinions ☒ religious or philosophical beliefs ☒ trade union membership ☒ genetic data ☒ biometric data for the purpose of uniquely identifying a natural person ☒ physical or mental health ☒ sex life or sexual orientation ☐ criminal convictions and offences ☐ none of the above ☐ set out in: And: ☒ The categories of special category and criminal records data will update automatically if the information is updated in the Linked Agreement referred to. ☐ The categories of special category and criminal records data will NOT update automatically if the information is updated in the Linked Agreement referred to. The Parties must agree a change under Section 5.3. See Part 5, Annex I for the current description of processing for further information. |
Relevant Data Subjects | The Data Subjects of the Transferred Data are: ☒ The categories of Data Subjects will update automatically if the information is updated in the Linked Agreement referred to. ☐ The categories of Data Subjects will not update automatically if the information is updated in the Linked Agreement referred to. The Parties must agree a change under Section 5.3. See Part 5, Annex I for the current description of processing for further information. |
Purpose | ☒ The Importer may Process the Transferred Data for the following purposes: As required for the purposes set out in the Agreement, as noted in the Data Privacy Terms, or as otherwise agreed in writing between the Parties. In both cases, any other purposes which are compatible with the purposes set out above. ☒ The purposes will update automatically if the information is updated in the Linked Agreement referred to. ☐ The purposes will NOT update automatically if the information is updated in the Linked Agreement referred to. The Parties must agree a change under Section 5.3. |
Security of Transmission | Data transmissions must be encrypted to a minimum of TLS 1.2. This includes all data transfers including API’s, email and other like services. |
Security of Storage | Data shall be stored at a minimum of AES-256 with Role Based Access Controls (RBAC) so only those requiring access to the data for their direct job duties have such access. |
Security of Processing | Data shall be processed with appropriate controls including: Physical ( access to processing area is protected from unauthorized access) Technical: Users have Role Based Access. Data is not shared, managed, transmitted, or stored by any vendor, sub-processor or person unless they meet the minimum requirements of Table 4. User: Users that have access to the data are properly vetted and have a direct job responsibility to access or process the data. Solutions: Solutions used to process data shall meet the requirements as outlined in Table 4 |
Organisational security measures | Organizations shall have comprehensive and current policies that are updated annually to govern the management of data and protections as described in Table 4 as well as those for Access management, Employee Security/Compliance training, Alignment to GDPR, and other applicable regulatory requirements as applicable to the services and data included within this agreement. |
Technical security minimum requirements | Data must be encrypted at all times to TLS 1.2, AES-256 or equivalent ciphers. Multi-Factor Authentication of some type, which includes SSO, shall be in place to access data and data processing systems. |
Updates to the Security Requirements | ☒ The Security Requirements will update automatically if the information is updated in the Linked Agreement referred to. ☐ The Security Requirements will NOT update automatically if the information is updated in the Linked Agreement referred to. The Parties must agree a change under Section 5.3. |
Extra Protection Clauses: | Security awareness training shall be performed annually and include a primary pereson that can be contacted to report active incidents and risks. |
(i) Extra technical security protections | Data shall be protected and security standards maintained at all times including when engaged in disaster recovery efforts. |
(ii) Extra organisational protections | An owner shall be identified to address all compliance and security requirements so as to ensure that protections are continually in place and vulnerabilities are addressed in a timely manner. |
(iii) Extra contractual protections | Meeting the requirements as outlined in this document can be satisfied with a comprehensive and current third-party audit, such as SOC 2 Type II, that is conducted by a reputable audit firm and updated no less than annually. |
Commercial Clauses | Further clauses in respect of the processing of personal data are to be found in the Linked Agreement. |
Mandatory Clauses | Mandatory Clauses of the Approved IDTA, being the template IDTA A.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 5.4 of those Mandatory Clauses. |
Better campaigns. Greater experiences. More revenue. It’s all within your grasp.