Introducing Relay™: Smart links for text messaging, powered by Rebrandly and Wonder Cave. Learn more
This Data Processing Addendum (“DPA“) forms part of the Subscription Agreement entered into between the Customer (the “Company”) and RadiateCapital Limited (“Rebrandly”, the “Data Processor”) (together as the “Parties”) (the “Principal Agreement”).
A. The Company acts as a Data Controller.
B. The Company has engaged Rebrandly to provide certain Services under the Principal Agreement which will require the processing of Company Personal Data by Rebrandly, acting as a Data Processor.
C. This DPA sets out the additional terms, requirements and conditions on which Rebrandly will process Company Personal Data when providing services under the Principal Agreement. This DPA contains the mandatory clauses required by Article 28(3) of the retained EU law version of the General Data Protection Regulation ((EU) 2016/679) (UK GDPR) for contracts between controllers and processors and the General Data Protection Regulation ((EU) 2016/679).
a) To the extent the UK GDPR applies, the law of the United Kingdom or of a part of the United Kingdom which relates to the protection of Personal Data.
b) To the extent the EU GDPR applies, the law of the European Union or any member state of the European Union to which the Customer or Provider is subject, which relates to the protection of Personal Data.
"Data Transfer" means:i. a transfer of Company Personal Data from the Company to a Contracted Sub-Processor; or
ii. an onward transfer of Company Personal Data from a Contracted Sub-Processor to another Contracted Sub-Processor, or between two establishments of a Contracted Sub-Processor, in each case, where such transfer would be prohibited by Data Protection Laws (or by the terms of data transfer agreements put in place to address the data transfer restrictions of Data Protection Laws).
"DPA" means this Data Processing Addendum and all Schedules."EEA" the European Economic Area."GDPR" means the General Data Protection Regulation ((EU) 2016/679)."SCC" means the ICO's International Data Transfer Agreement for the transfer of personal data from the UK and/or the ICO's International Data Transfer Addendum to EU Commission Standard Contractual Clauses and/or the European Commission's Standard Contractual Clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 as set out in the Annex to Commission Implementing Decision (EU) 2021/914 and/or the European Commission's Standard Contractual Clauses for the transfer of Personal Data from the European Union to processors established in third countries (controller-to-processor transfers), as set out in the Annex to Commission Decision 2010/87/EU or such alternative clauses as may be approved by the European Commission or by the UK from time to time."Services" means the branded link management dashboard and applications Rebrandly provides. The Services are described in more detail in Schedule 2."Subscription Agreement" means the Terms of Use made available from time to time at rebrandly.com/terms-conditions or such other terms and conditions that are mutually agreed in writing and signed between the Company and Rebrandly."UK GDPR" has the meaning given to it in section 3(10) (as supplemented by section 205(4)) of the Data Protection Act 2018.1.2. The terms, “Commission”, “Controller”, “Data Subject”, “Member State”, “Personal Data”, “Personal Data Breach”, “Processing” and “Supervisory Authority” shall have the same meaning as given to them in Data Protection Laws, and their cognate terms shall be construed accordingly.1.3. This DPA is subject to the terms of the Principal Agreement and is incorporated into the Principal Agreement. Interpretations and defined terms set forth in the Principal Agreement apply to the interpretation of this DPA, unless the context otherwise requires.1.4. The Schedules form part of this DPA and will have effect as if set out in full in the body of this DPA. Any reference to this DPA includes the Schedules.1.5. A reference to writing or written includes email with a clear confirmation of receipt by the other party.1.6. In the case of conflict or ambiguity between:1.6.1. any provision contained in the body of this DPA and any provision contained in the Schedules, the provision in the body of this DPA will prevail;1.6.2. the terms of any accompanying invoice or other documents annexed to this DPA and any provision contained in the Schedules, the provision contained in the Schedules will prevail;1.6.3. any of the provisions of this DPA and the provisions of the Principal Agreement, the provisions of this DPA will prevail; and1.6.4. any of the provisions of this Agreement and any executed SCC, the provisions of the executed SCC will prevail.Rebrandly shall take reasonable steps to ensure the reliability of any employee, agent, contractor or any Contracted Sub-Processor who may have access to the Company Personal Data, ensuring in each case that access is limited to those individuals who need to know / access the relevant Company Personal Data, as strictly necessary for the purposes of the Principal Agreement, and to comply with Data Protection Laws in the context of that individual’s duties to Rebrandly, ensuring that all such individuals are subject to confidentiality undertakings or professional or statutory obligations of confidentiality.
Rebrandly shall provide reasonable assistance to the Company (at the Company’s cost) with any data protection impact assessments, and prior consultations with supervising authorities or other competent data privacy authorities, which Company reasonably considers to be required by article 35 or 36 of the GDPR, the UK GDPR or equivalent provisions of any other Data Protection Laws, in each case solely in relation to Processing of Company Personal Data and taking into account the nature of the Processing and information available to the Contracted Sub-Processors.
At the Company’s request, Rebrandly shall promptly and in any event within 10 business days of the date of cessation of any Services involving the Processing of Company Personal Data (the “Cessation Date”) delete and procure the deletion of Company Personal Data.
Notices. All notices and communications given under this DPA must be in writing. Email confirmation of receipt will be sent by the other party. The Company shall be notified by email sent to the address related to its use of the Service under the Principal Agreement. Rebrandly shall be notified by email sent to the address: legal@rebrandly.com.
This DPA is governed by the laws of the Republic of Ireland.
Any dispute arising in connection with this DPA which the Parties will not be able to resolve amicably, will be submitted to the exclusive jurisdiction of the courts of Dublin subject to possible appeal to the Irish High Courts.
The Company agrees not to include any Company Personal Data in any URL/link created by using the Services nor in any part of the platform (eg.: notes, tags, etc.). It is the Company’s responsibility to notify Rebrandly in advance and in written (and Rebrandly needs to authorize it in written) in the event that the Company includes or wishes to include any Company Personal Data in any URL/link created whilst using the Services or other part of the Rebrandly platform.
Data Subject Types: CustomersAuthorised Persons: List of approved Company Sub-Processors: https://rebrandly.com/SubProcessorsIdentify Rebrandly’s legal basis for processing Company Personal Data outside the EEA in order to comply with cross-border transfer restrictions: Rebrandly’s AWS servers are located mainly in the United States of America. AWS is an approved Contracted Sub-Processor and may process Company Personal Data (i.e. EU Company Personal Data) in the provision of the Services to the Company.The services are offered by RadiateCapital Limited (“Rebrandly”).
Rebrandly is a link management platform designed to brand, track and share short URLs using a custom domain name. Rebrandly provides a complete platform that includes a web-based dashboard, applications for mobiles (iOS and Android), software for Mac and Windows, and browser extensions.
Rebrandly’s latest SOC 2 Type II Reports and annual Penetration Test Reports are made available to Customers and prospects via the Rebrandly Trust Center. Request access here: www.trust.rebrandly.com.
Rebrandly shall implement and maintain technical and organizational measures appropriate to safeguard Company Personal Data against unauthorized destruction, alteration, loss, disclosure or access as set out in this Schedule.
Capitalized terms not defined in this Schedule, or otherwise defined in the DPA, shall have the same meaning as in the Principal Agreement.
“Information Resources” means any computing and other network, systems, applications, and network elements, by or with which Company Personal Data is stored, transmitted or processed pursuant to the Agreement. Strong Encryption means the use of encryption technologies with minimum key lengths of 128-bits for symmetric encryption and 1024-bits for asymmetric encryption.1. System Security RequirementsMonitoring Security Alerts: Actively monitor industry resources (e.g. software vendor mailing lists or websites) for timely notification of all applicable security alerts pertaining to Rebrandly’s Information Resources.System Scanning: Scan both external-facing and internal Information Resources with applicable industry standard security vulnerability scanning software (including, but not limited to, network, server, application, and database scanning tools).Deploy Intrusion Detection/Prevention Systems: Deploy one or more Intrusion Detection/Prevention Systems (IDS or IPS) in an active mode of operation.Remediating Service Vulnerabilities: Use a documented process to remediate security vulnerabilities in the Information Resources, including through industry publications, vulnerability scanning, virus scanning, and the review of security logs, and apply appropriate security patches promptly with respect to the probability that such vulnerability can be, or is in the process of being exploited.Security Administration: Assign security administration responsibilities for configuring host operating systems to specific individuals and ensure that security staff have reasonable and necessary experience in information/network security. Manage IAM Users and their permissions by authorized personnel and follow a least-privilege principle.Server Hardening: Ensure that all of Rebrandly’s servers are and remain ‘hardened’ by restricting access to the company VPN only and by requiring possession of a SSH key to access them, where applicable.Restrict User Privileges and Access: Restrict access by users to only the commands, data and Information Resources necessary to perform authorized functions. System administrator/root (or privileged, super user, or the like) access should be limited to individuals requiring such high-level access in the performance of their jobs and system administrators should not perform tasks for non-privileged users using system administrator accounts or credentials.1. Physical Security RequirementsSecure Facilities: Ensure that all of Rebrandly’s Information Resources are located in secure physical facilities with access limited and restricted to authorized individuals only. AWS controls and monitors access to all data centers.Monitoring and Recording Access: Monitor and record, for audit purposes, access to the physical facilities containing Information Resources used in connection with Rebrandly’s performance of its obligations under the Agreement.3. Network Security RequirementsDetection and Handling of Unauthorized Access: Have a documented process and controls in place to detect and handle unauthorized attempts to access Customer Information. Global management of the Rebrandly infrastructure performed using a primary AWS account which is part of an AWS Organization with governance services enabled (Security Hub, GuardDuty, CloudTrail, Config) to supervise Cloud accesses and threats and continuous compliance.Encryption of Information both in Transit and at Rest: Use Strong Encryption for the transfer of Company Personal Data outside of Company-controlled or Rebrandly-controlled facilities, or when transmitting Company Personal Data over any untrusted network, or when storing Company Personal Data.Remote Access: Require authentication and encryption for any remote access use of Information Resources. Separate the internal network from the internet using firewalls configured to allow only authorized traffic, as defined in Rebrandly's Security Policy. Monitor and screen traffic entering Rebrandly’s production network by firewall and monitoring tools implemented by AWS and configured by Rebrandly, such as VPC logs and CloudTrail.4. Company Personal Data RequirementsSegregation of Company Personal Data: Segregate Company’s applications and Company’s Personal Data from any other applications and information of Rebrandly or Rebrandly’s customers, by using logical access controls.Documentation of Secure Backup, Transport, Storage and Disposal of Customer Information: Have a documented procedure for the secure backup, transport, storage, and disposal of Company Personal Data and upon Company’s request, provide such documented procedure to Company.Business Continuity and Disaster Recovery Plan: Maintain business continuity and disaster recovery plans that ensures that Rebrandly can meet its contractual obligations under the Agreement.5. Identification/Authentication RequirementsUnique Credential and Passwords: Credentials, UserIDs and passwords will not be shared and will not be used by any person other than the assigned individual user.Limit Failed Logins: Limit failed login attempts to no more than six (6) successive attempts and lock the user account upon reaching that limit. Access to the user account can be reactivated subsequently through a manual process requiring verification of the user’s identity or, where such capability exists, can be automatically reactivated after at least three (3) minutes from the last failed login attempt.Terminate Inactive Interactive Sessions: Terminate interactive sessions, or activate a secure, locking screensaver requiring authentication, after a period of inactivity not to exceed fifteen (15) minutes.Passwords: Passwords must meet the minimum requirements of (i) must be a minimum of eight (8) characters in length; (ii) if the password is less than twelve characters in length, it must contain characters from at least three (3) of these groupings: uppercase alpha, lowercase alpha, numeric, and special characters; (iii) must not be the same as the UserID with which they are associated; and (iv) must be complex and not contain names or dictionary words.Secure Conveyance of UserIDs and Passwords: Use a secure method for the conveyance of authentication credentials (e.g., passwords) and authentication mechanisms (e.g., tokens or smart cards). Ensure user session authentication is protected by utilizing TLS encryption on Vendor websites.6. Requirements for Software and Data IntegrityScan and Remove Viruses: Have current antivirus software installed and running to scan for and promptly remove viruses.Separate Production and Non-Production Resources: Separate development and test activities from and restrict developer access to operational environments in order to reduce the risks of inadvertent or unauthorized modifications to the operational system that could compromise the system’s integrity or availability.Software Change Control Process: Implement a documented software change control process including back out procedures.Utilize Database Transaction Logging: For applications which utilize a database that allows modifications to Company Personal Data, have database transaction logging features enabled and retain database transaction logs for a minimum of six (6) months.Review Code for Vulnerabilities and Compliance with Industry Standard Security Requirements: For all software developed, used, furnished and/or supported under this Agreement, review such software to find and remediate security vulnerabilities during initial implementation and upon any modifications and updates and implement OWASP guidelines.Quality Assurance Test Application and Security Vulnerabilities: Perform quality assurance testing for the application functionality and security components (e.g., testing of authentication, authorization, and accounting functions, as well as any other activity designed to validate the security architecture) during initial implementation and upon any modifications and updates.7. Monitoring and Auditing ControlsRestrict Access to Security Logs: Restrict access to security logs to authorized individuals.Review Security Logs and Resolve Security Problems: Review, on a routine basis, security logs for anomalies and document and resolve all logged security problems in a timely manner.Record Retention: Retain complete and accurate records relating to its performance of its obligations arising out of this Schedule and Rebrandly’s compliance in a format that will permit audit for a period of no less than three (3) years, or longer as may be required pursuant to a court order or civil or regulatory proceeding.Annual Compliance Review: At a minimum, annually review this Schedule to ensure that Rebrandly is in compliance with the requirements of this Agreement.8. Personnel Security and Integrity ProceduresPersonnel Procedures and Practices: Deploy appropriate procedures for Rebrandly personnel including, but not limited to, conducting background checks consistent with applicable law.Training of Personnel: Provide appropriate privacy and information security training to Rebrandly’s employees that have access to customer Personal Data or systems.