Rixter Data Protection Addendum (DPA) — Azure DevOps
Part of: Rixter Provider-Specific Terms for Azure DevOps
This Data Protection Addendum (“DPA”) forms part of the agreement governing the Customer’s use of Rixter’s Products (“Agreement”) between Rixter AB (“Rixter”) and the customer identified in the Agreement (“Customer”).
This DPA describes the parties’ data protection responsibilities in connection with Rixter applications, extensions, and integrations (“Products”) for:
- Microsoft Azure DevOps Services — cloud.
- Microsoft Azure DevOps Server — on-premises or self-hosted.
1. Definitions
“Data Protection Laws” means all laws applicable to the processing of Personal Data under this DPA, including, where applicable:
- The General Data Protection Regulation (EU) 2016/679 (“GDPR”).
- The United Kingdom General Data Protection Regulation and Data Protection Act 2018 (“UK GDPR”).
- The California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020, and applicable implementing regulations (“CCPA”).
“Personal Data” means information relating to an identified or identifiable natural person, including “personal information” under the CCPA where applicable.
“App Data” means information stored or otherwise processed by the Products within Customer’s Azure DevOps instance, including configuration data and any Personal Data contained within that information.
“Customer Personal Data” means Personal Data that Rixter actually processes on Customer’s behalf, such as Personal Data Customer provides for technical support or separately agreed services.
“Purchase and Contact Data” means information concerning the purchasing company and its contact persons that Rixter collects or receives to administer purchases and the customer relationship.
“Subprocessor” means a third party engaged by Rixter to process Customer Personal Data on Customer’s behalf.
“Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data.
The terms “controller,” “processor,” “data subject,” and “processing” have the meanings given in applicable Data Protection Laws.
2. App Deployment and Data Storage
Rixter supplies the Products for use within Customer’s Azure DevOps instance.
Rixter does not host Customer’s instance or App Data. App Data remains within Customer’s instance and is not accessible to Rixter. This applies to both cloud and on-premises deployments.
Customer’s instance may be hosted by Microsoft, Customer, or a hosting provider appointed under Customer’s own arrangements. The relevant platform and hosting agreements govern those services.
Customer is responsible for administering its instance and App Data, including user permissions, configuration, retention, export, and deletion, together with the relevant platform or hosting provider where applicable.
Rixter remains responsible for its obligations concerning the Products it supplies and any Personal Data it actually processes.
3. Scope and Data Protection Roles
3.1 App Data
Supplying the Products does not, by itself, involve Rixter receiving, accessing, or hosting App Data.
The processor obligations in this DPA apply only to Customer Personal Data actually processed by Rixter or its Subprocessors on Customer’s behalf. They do not imply that Rixter can access or administer App Data within Customer’s instance.
3.2 Purchase and Contact Data
When an app is purchased, Rixter collects or receives information about the purchasing company and its contact person or persons.
This may include the company’s name and business details, the contact person’s name and business contact details, and associated purchase, licence, or subscription information.
To the extent this information constitutes Personal Data, Rixter acts as an independent controller when using it to administer purchases, licences, subscriptions, customer communications, and its legal obligations.
This processing is governed by applicable Data Protection Laws and Rixter’s applicable privacy notice. It is not processing on Customer’s behalf under the processor provisions of this DPA.
3.3 Payments and Paddle
Payments are handled by Paddle. Rixter does not store credit card information.
Paddle processes payment information under its applicable terms and privacy notice. For payment, transaction, and related activities for which Paddle determines the purposes and means of processing, Paddle acts as an independent controller.
Paddle is not a Subprocessor under this DPA merely because it handles purchases or payments.
Rixter may receive purchase, subscription, and transaction-status information needed to administer the Product and customer relationship. Such information is handled as Purchase and Contact Data.
3.4 Support and Separately Agreed Services
If Customer provides Personal Data to Rixter for technical support or separately agreed services, Rixter acts as a processor to the extent it processes that data on Customer’s behalf. Where applicable under the CCPA, Rixter acts as a service provider.
Customer acts as controller or, where Customer itself acts as a processor, confirms that it is authorized to give the relevant instructions.
Customer should redact unnecessary Personal Data from support requests, screenshots, logs, and other materials before providing them to Rixter.
4. Processing Instructions and Confidentiality
For Customer Personal Data, Rixter shall:
- Process the data only on Customer’s documented instructions and as necessary to provide the requested support or agreed services.
- Treat the Agreement, this DPA, and Customer’s documented service and support requests as instructions.
- Process the data for another purpose only where required by applicable law. Where legally permitted, Rixter shall inform Customer of that requirement before processing.
- Inform Customer without undue delay if Rixter considers an instruction to infringe applicable Data Protection Laws.
- Ensure that authorized persons are subject to appropriate confidentiality obligations.
- Limit access to persons who require it to perform the relevant services.
Customer is responsible for the lawfulness of its instructions and for providing any required notices and establishing an appropriate legal basis for the processing it requests.
Where the CCPA applies, Rixter shall:
- Process Customer Personal Data only for the specific business purposes described in this DPA and the Agreement.
- Not sell or share Customer Personal Data, as those terms are defined by the CCPA.
- Not retain, use, or disclose Customer Personal Data outside the direct business relationship with Customer or for purposes other than the agreed services, except as permitted by the CCPA.
- Not combine Customer Personal Data with Personal Data from other customers or Rixter’s own interactions with individuals, except as permitted by the CCPA.
- Provide the level of privacy protection required by the CCPA and notify Customer if Rixter determines that it can no longer meet its applicable obligations.
Customer may take reasonable and appropriate steps to verify compliance and, upon notice, stop and remediate unauthorized use of Customer Personal Data.
5. Subprocessors
Rixter does not engage Subprocessors to host or access App Data within Customer’s instance.
Microsoft and providers used under Customer’s own platform or hosting arrangements are not Rixter’s Subprocessors merely because Customer uses the Products.
Before engaging a Subprocessor for Customer Personal Data, Rixter shall identify its legal entity, processing function, and processing locations and obtain Customer’s written authorization.
Where Customer grants general written authorization, Rixter shall provide at least 15 days’ advance notice of an intended addition or replacement. Customer may object within that period on reasonable data protection grounds.
The parties shall work in good faith to resolve an objection. If no reasonable resolution is available, Customer may discontinue the affected support or service before the proposed Subprocessor begins processing its data.
Rixter shall impose substantially equivalent applicable data protection obligations on each Subprocessor through a written agreement and remain responsible for the Subprocessor’s performance of those obligations.
6. Security Measures
Rixter shall implement and maintain technical and organizational measures appropriate to the nature of Customer Personal Data and the risks of processing it.
As appropriate to the relevant processing, these measures shall include:
- Encryption in transit.
- Authentication and access controls.
- Access limited to authorized personnel.
- Confidentiality obligations.
- Secure handling and deletion of support materials.
- Vulnerability management and secure software development practices.
- Measures supporting the confidentiality, integrity, availability, and resilience of systems used to process Customer Personal Data.
- Regular assessment of the effectiveness of relevant security measures.
These obligations concern processing and systems within Rixter’s control. They do not imply that Rixter operates, monitors, or backs up Customer’s instance.
7. Assistance and Data Subject Rights
Taking into account the nature of the processing and the information available to it, Rixter shall reasonably assist Customer with:
- Responding to applicable requests for access, correction, deletion, restriction, objection, portability, and other data subject or consumer rights.
- Meeting applicable security and Personal Data Breach obligations.
- Carrying out data protection impact assessments and prior consultation with supervisory authorities where required.
Rixter shall promptly notify Customer of requests received directly from individuals concerning Customer Personal Data. Rixter shall not respond substantively except on Customer’s instructions or as required by law.
Requests relating to Purchase and Contact Data processed by Rixter as an independent controller shall be handled by Rixter under its applicable privacy notice and Data Protection Laws.
8. Personal Data Breach Notification
Rixter shall notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data.
To the extent available, the notification shall include:
- The nature of the breach.
- The categories and approximate numbers of affected individuals and records.
- The likely consequences.
- Measures taken or proposed to address the breach and mitigate its effects.
- A contact point for further information.
Information may be provided in phases as it becomes available. Rixter shall reasonably cooperate with Customer in investigating and addressing the breach.
This notification obligation concerns Customer Personal Data processed by Rixter or its Subprocessors. Security incidents involving only Customer’s instance are managed under Customer’s applicable platform and hosting arrangements.
Unless prohibited by law, Rixter shall notify Customer of legally binding governmental requests for disclosure of Customer Personal Data.
9. International Data Transfers
Rixter shall transfer Customer Personal Data outside the European Economic Area or the United Kingdom only in accordance with Customer’s documented instructions and applicable Data Protection Laws.
Where required, an appropriate transfer mechanism shall be implemented before the transfer, such as:
- An applicable adequacy decision.
- The European Commission’s Standard Contractual Clauses, using the appropriate module and completed annexes.
- The UK International Data Transfer Agreement or the UK Addendum to the Standard Contractual Clauses.
- Another mechanism permitted by applicable Data Protection Laws.
Rixter shall carry out any required transfer assessment and implement appropriate supplementary measures.
These obligations also apply to transfers by Subprocessors, including remote access where it constitutes an international transfer.
Transfers performed by Customer or its independently appointed platform or hosting providers are governed by their respective arrangements and applicable law.
10. Data Return, Deletion, and Retention
Upon completion or termination of the relevant processing services, Rixter shall, at Customer’s choice, return or delete Customer Personal Data and delete existing copies, unless applicable law requires retention.
Rixter shall complete the return or deletion within 60 days, unless a shorter period is required by law or agreed in writing. During that period, data awaiting deletion shall remain protected under this DPA and shall not be used for other purposes.
Where retention is legally required, Rixter shall retain only the necessary data for the required period and restrict processing to that purpose.
Customer manages the retention, export, and deletion of App Data within its own instance. Rixter cannot return or delete App Data that it does not possess or control.
Purchase and Contact Data processed by Rixter as an independent controller is retained according to its applicable privacy notice and legal obligations. The processor deletion period in this section does not govern those records.
11. Information and Audit Rights
Rixter shall make available information reasonably necessary to demonstrate compliance with its processor obligations under this DPA.
Rixter shall allow for and contribute to audits, including inspections, conducted by Customer or an independent auditor appointed by Customer, concerning processing of Customer Personal Data.
The parties shall agree reasonable arrangements for notice, scope, confidentiality, security, and minimizing disruption. Such arrangements shall not prevent an audit required by applicable Data Protection Laws.
Where available, Rixter may initially provide relevant compliance documentation or independent audit reports. These materials shall not replace further audit rights where necessary to meet applicable legal requirements.
Audit rights under this section do not grant access to other customers’ data or to Customer’s independently appointed platform providers.
12. Liability
Notwithstanding Section 14.3 of the Standard Agreement, the General Cap shall apply to all claims, including those arising under this DPA. The Enhanced Cap shall not apply.
Nothing in this DPA limits liability or rights that cannot lawfully be limited, including applicable rights of data subjects and powers of supervisory authorities.
13. Miscellaneous
This DPA shall remain effective for as long as Rixter or its Subprocessors retain Customer Personal Data.
In the event of a conflict between this DPA and the Agreement, this DPA shall prevail concerning data protection obligations. Applicable mandatory international transfer clauses shall prevail to the extent they require otherwise.
If a proposed change to Product functionality or service delivery would involve Rixter receiving, accessing, or hosting App Data, the parties shall document the changed processing and implement any required contractual arrangements and safeguards before that processing begins.
Appendix A — Processing on Customer’s Behalf
| Item | Description |
|---|---|
| Subject matter | Technical support or separately agreed services involving Customer Personal Data for the Products for Azure DevOps. |
| Nature of processing | Receipt, review, organization, storage, use, return, and deletion of information Customer provides for the relevant service. |
| Purpose | Investigating and resolving support requests or performing separately agreed services on Customer’s documented instructions. |
| Duration | The period necessary to perform the relevant service, followed by return or deletion under Section 10. |
| Frequency | Occasional, when Customer provides Personal Data for support or separately agreed services. |
| Data subjects | Customer’s contact persons, users, administrators, employees, contractors, and other individuals whose Personal Data is included in the materials supplied. |
| Personal Data | Names, business contact details, user identifiers, and any Personal Data contained in support messages, screenshots, logs, or other materials Customer provides. |
| Sensitive data | Special-category data and criminal-offence data are not required for ordinary support. Customer shall not instruct their processing unless expressly agreed in writing with appropriate safeguards. |
| App Data | App Data remains in Customer’s instance and is inaccessible to Rixter. Any extract Customer separately sends to Rixter for processing on its behalf becomes Customer Personal Data for that processing. |
| Customer’s rights and obligations | Customer determines the lawful purpose and scope of the requested processing, provides documented instructions, and exercises the rights described in this DPA. |
| Subprocessor processing | Limited to the authorized services, duration, and processing details disclosed under Section 5. |
Appendix B — Purchase and Payment Information
This appendix describes processing separate from Rixter’s processor activities.
| Information | Responsibility and handling |
|---|---|
| Purchasing company information | Rixter collects or receives company information to administer purchases and the customer relationship. Company information is Personal Data only to the extent it relates to an identifiable individual. |
| Contact person information | Rixter processes contact persons’ names and business contact details as an independent controller for purchase administration and customer communications. |
| Purchase and subscription records | Rixter may receive and retain information needed to administer licences, subscriptions, purchase status, and related obligations. |
| Credit card information | Rixter does not store credit card information. Payment handling is provided by Paddle. |
| Paddle processing | Paddle’s processing is governed by its applicable terms and privacy notice. Paddle acts as an independent controller for its payment and related activities. |
| Retention and individual rights | Rixter’s applicable privacy notice and Data Protection Laws govern its controller processing. Paddle’s privacy notice governs requests concerning processing for which Paddle is responsible. |
Rixter AB
Data protection contact: support@rixter.se