Kenvara
Data processing agreement
The Article 28 terms on which ITSM Ltd processes personal data for customers of Kenvara.
This Data Processing Agreement (“DPA”) is incorporated into and forms part of the End User Terms for Kenvara between ITSM Ltd and the customer identified in the applicable Atlassian Marketplace order. It takes effect automatically on installation of the App and requires no signature, but we will countersign a copy on request to support@itsm-ltd.com.
A note on scope before you read further. Kenvara runs entirely on Atlassian Forge and stores all customer data inside Atlassian’s infrastructure. It declares no external access and sends no customer data to us. The personal data that reaches our own systems is support correspondence, licence records and, in an incident, the records clause 10 describes. This DPA is nonetheless a full Article 28 agreement, because we still determine how the App processes personal data on your behalf.
Two features need your attention before you install. First, you decide which customers see which known issues, and Kenvara enforces it. Entitlement follows your Jira Service Management customer organisations, so keeping their membership right is yours. Second, Kenvara’s history of changes cannot be edited. It keeps the account ids of the people who made each change until Atlassian reports their account closed (clause 9.5).
1. Definitions
“Controller”, “Processor”, “Data Subject”, “Personal Data”, “Personal Data Breach”, “Processing” and “Supervisory Authority” have the meanings given in the UK GDPR.
“Customer Personal Data” means Personal Data contained within Your Data (as defined in the End User Terms) that we Process on your behalf under this DPA. “Data Protection Laws” means all laws applicable to the Processing of Personal Data under this DPA, including the UK GDPR, the Data Protection Act 2018 (as amended by the Data (Use and Access) Act 2025), the EU GDPR where applicable, and the Privacy and Electronic Communications Regulations 2003. “Restricted Transfer” means a transfer of Personal Data to a country not covered by UK or EU adequacy regulations, where such transfer requires a lawful transfer mechanism. “Standard Contractual Clauses” or “SCCs” means the clauses annexed to European Commission Implementing Decision (EU) 2021/914. “UK Addendum” means the International Data Transfer Addendum to the EU SCCs issued by the Information Commissioner under section 119A of the Data Protection Act 2018. “UK GDPR” has the meaning given in section 3(10) of the Data Protection Act 2018. “Sub-processor” means any third party engaged by us to Process Customer Personal Data.
“App”, “Atlassian”, “Your Data”, “Portal Customer”, “Export File” and “Subscription Term” have the meanings given in the End User Terms, as do all other capitalised terms not defined here. In the event of conflict between this DPA and the End User Terms in respect of the Processing of Personal Data, this DPA prevails.
2. Roles of the parties
2.1 In respect of Customer Personal Data, you are the Controller and we are the Processor. Where you are yourself a Processor acting for a third-party Controller, as a managed service provider running Kenvara for its own clients may be, we act as a Sub-processor and you warrant that you have the authority of that Controller to enter into this DPA.
2.2 Atlassian’s position in the chain. Because the App is hosted on Atlassian Forge, Atlassian acts as our Sub-processor for the hosting, compute and storage on which the App depends. Atlassian may separately act as your own Processor under your direct agreement with Atlassian for the underlying Jira product. Those two relationships are distinct: this DPA governs only our Processing, and nothing in it varies your agreement with Atlassian.
2.3 We act as an independent Controller in respect of support correspondence, licence and billing records, business contact data, and the active-site count, security review and incident records described in section 4 of the Privacy Policy. This DPA does not apply to that Processing, which is governed by the Privacy Policy and by Data Protection Laws directly.
2.4 Each party is independently responsible for its own compliance with Data Protection Laws applicable to it in its own role.
2.5 Your customers. Where you run Kenvara for clients of your own, the decision to publish a known issue to them, and its lawful basis, are yours. Kenvara is the means by which you show it only to the people entitled to see it.
3. Scope and duration of Processing
3.1 The subject matter, duration, nature and purpose of the Processing, the types of Personal Data and the categories of Data Subjects are set out in Annex 1.
3.2 This DPA applies for as long as we Process Customer Personal Data on your behalf, and survives termination of the End User Terms to the extent any such Processing continues.
4. Processing on documented instructions
4.1 We will Process Customer Personal Data only on your documented instructions, including in relation to Restricted Transfers, unless required to do otherwise by law to which we are subject. Where such a legal requirement applies, we will inform you before Processing unless the law prohibits it on important grounds of public interest.
4.2 Your instructions comprise: the End User Terms; this DPA; the configuration choices you and your users make within the App; and the operations the App performs in response to actions taken by your users. Your instructions also comprise the processing Kenvara performs on its own schedule to carry them out:
- its daily checks (review reminders, retirements, reconciliation, the organisation census and the deletions in Annex 1);
- its weekly report to Atlassian of the account ids it holds;
- its hourly check of its own licence;
- its responses to events in your Jira site;
- queued work, such as an export or import you start.
4.3 We will inform you if, in our opinion, an instruction infringes Data Protection Laws. We may suspend the affected Processing until the instruction is confirmed, withdrawn or amended.
4.4 No AI or machine learning use of your data. We will not sell Customer Personal Data, and will not use it for our own purposes, for advertising or for profiling. We will not use Customer Personal Data to develop, train, fine-tune or evaluate any machine learning or artificial intelligence model. This version of Kenvara contains no AI or machine learning feature and makes no call to any model or inference service. This undertaking is unqualified. The log lines we read (section 5.6 of the Privacy Policy) hold no Customer Personal Data by design, so counting the sites that use Kenvara does not use Customer Personal Data for our own purposes.
4.5 You warrant that you have a lawful basis for the Processing you instruct, have provided any notices and obtained any consents required, and that your instructions comply with Data Protection Laws. You are responsible for the accuracy and legality of Customer Personal Data and for the content your users place in your Atlassian site and in the App.
5. Confidentiality
ITSM Ltd is one person, who is bound by a statutory duty of confidentiality and by this DPA. Anyone we later authorise to Process Customer Personal Data will first be bound by a written obligation of confidentiality, given access on a need-to-know and least-privilege basis, and trained in data protection and security awareness.
6. Security
6.1 We implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, as required by Article 32 UK GDPR. Those measures are described in Annex 2 and, in more detail, in the Cloud Security Statement at https://kenvara.itsm-ltd.com/legal/cloud-security-statement/.
6.2 You acknowledge that the security of Customer Personal Data stored by the App depends substantially on controls operated by Atlassian, and that Annex 2 accordingly distinguishes platform-provided measures from measures we implement ourselves.
6.3 We may update the measures in Annex 2 provided the updated measures do not materially reduce the overall level of security.
6.4 You decide who holds the agent, publishing and administration roles in Jira Service Management, which customer organisations exist and who is in them, and which known issues are published to whom. Kenvara enforces those decisions; it does not make them. Section 9 of the End User Terms sets out what you should check, including the membership of any organisation you publish to.
7. Sub-processors
7.1 General authorisation. You give us general written authorisation to engage Sub-processors, subject to this section. The Sub-processors authorised at the effective date are listed in Annex 3. Only Atlassian Processes Customer Personal Data held by the App; the other exists solely for support correspondence.
7.2 Notice of change. We will give you at least 30 days’ notice of any intended addition or replacement of a Sub-processor, by updating Annex 3 and the sub-processor tables in the Privacy Policy and Cloud Security Statement, and by email to the technical contact on your licence.
7.3 Objection. You may object on reasonable data protection grounds within the notice period by emailing support@itsm-ltd.com. We will work with you in good faith to address the objection. If we cannot do so within 30 days, you may terminate the affected subscription by written notice and request a pro-rata refund from Atlassian for the unused portion of the Subscription Term.
7.4 Objection to Atlassian. Atlassian is a Sub-processor that cannot be replaced or removed: the App exists only on the Atlassian platform. If you object to Atlassian as a Sub-processor, your only remedy is to terminate under clause 7.3.
7.5 Terms and liability. We impose on each Sub-processor data protection obligations no less protective than those in this DPA, and we remain fully liable to you for the acts and omissions of our Sub-processors as if they were our own.
8. International transfers
8.1 Customer Personal Data stored by the App resides in Forge SQL and Forge’s key-value store, which follow the data residency of your Jira site. Where you have pinned your product data to a UK or EEA region, the App’s data is pinned to the same region. Section 3.4 of the Cloud Security Statement sets out what the App treats as in scope and out of scope for data residency.
8.2 Where a Restricted Transfer occurs, the parties agree that the mechanism set out in Annex 4 applies, and that Annex 4 is incorporated into this DPA.
8.3 We will not make a Restricted Transfer of Customer Personal Data except in accordance with Annex 4 or another lawful transfer mechanism.
8.4 Each party will provide reasonable assistance to the other in carrying out any transfer risk assessment required by Data Protection Laws.
9. Assistance with Data Subject rights
9.1 Taking into account the nature of the Processing, we will assist you by appropriate technical and organisational measures, insofar as possible, in fulfilling your obligation to respond to requests to exercise Data Subject rights under Chapter III UK GDPR.
9.2 The practical position. Because Customer Personal Data resides in your own Atlassian site, you can in most cases respond to a Data Subject request directly, without our involvement, using the administrative tools in your Atlassian product and the App. A portal customer’s feedback can be erased at once with “Delete per-customer portal data now” on the Kenvara page in Apps administration, and an access request about it can be answered by describing the data and its 30-day life (Annex 1). Where App data must be located, amended or deleted and you cannot do so yourself, contact support@itsm-ltd.com and we will assist.
9.3 If we receive a request directly from a Data Subject relating to Customer Personal Data, we will not respond to it substantively. We will acknowledge receipt, direct the individual to you, and notify you within 5 business days.
9.4 What can be corrected or removed within the App. Within Kenvara, a known error can be corrected while the licence is active, and withdrawn or retired in any licence state, which takes it off the portal. No one can delete a known error, its published versions or its history. An administrator can change the settings at any time.
9.5 What cannot: the history of changes. Kenvara’s history of changes is append-only. It records the Atlassian account id of the person who made each change, and stores no display name or email address. Kenvara reports the account ids it holds to Atlassian every week, in every licence state, and replaces any Atlassian reports closed with “erased”, keeping no trace of it. Until then an id is kept for the life of the installation, and an export taken earlier keeps it. A Portal Customer’s feedback is kept for 30 days under a one-way code in place of who they are, and your administrator can delete all of it at once to answer an erasure request sooner.
Where you receive an erasure request that engages the history, we will help you assess it, including by identifying the records that hold a given account id. Whether an exemption applies, for example that the Processing is necessary for compliance with a legal obligation or for the establishment, exercise or defence of legal claims, is your determination as Controller, on the facts of the request and your own retention position. We do not make that determination for you.
9.6 Assistance under this section is provided at no charge unless a request is manifestly unfounded, excessive or repetitive, or requires bespoke engineering effort, in which case we may charge our reasonable costs, notified to you in advance.
10. Personal Data Breach
10.1 We will notify you of a Personal Data Breach affecting Customer Personal Data without undue delay, and we aim to do so within 72 hours of becoming aware of it.
10.2 The notification will include, to the extent known at the time: the nature of the breach, the categories and approximate number of Data Subjects and records affected, the likely consequences, the measures taken or proposed, and a contact point for further information. Where the information is not all available at once, we will provide it in phases without undue delay.
10.3 We will take reasonable steps to contain, investigate and mitigate the breach, and will preserve relevant evidence.
10.4 We will assist you in meeting your own obligations to notify the Information Commission or other Supervisory Authority and, where required, affected Data Subjects.
10.5 We will not notify any Supervisory Authority or Data Subject about a breach affecting Customer Personal Data on your behalf, or name you publicly in connection with it, unless you instruct us to or we are legally required to.
10.6 We will separately notify Atlassian within 24 hours, as Atlassian’s partner incident programme requires. That notification does not discharge our obligation to you under clause 10.1.
10.7 If a known issue, or a customer organisation’s name, reaches people outside its audience, we treat it as a security incident and, where it carries personal data, as a Personal Data Breach. We will help you contain it, by unpublishing, changing the audience, or switching off organisation-scoped known issues for customers who sign in with an Atlassian account. We will also help you establish what each organisation was shown, using the publication history report your administrator can create. You need not send us that report; if you choose to, we delete it 90 days after the incident closes.
11. Data protection impact assessments
Taking into account the nature of the Processing and the information available to us, we will provide reasonable assistance with any data protection impact assessment or prior consultation with a Supervisory Authority under Articles 35 and 36 UK GDPR. We maintain a standard information pack for this purpose: this DPA, the Cloud Security Statement, and the permission scopes and security description on the App’s website. That pack will normally be sufficient, and is available from support@itsm-ltd.com.
12. Deletion and return of data
12.1 Uninstalling Kenvara offers a choice. If you keep access, Atlassian keeps Kenvara running until the subscription or evaluation ends, plus 60 days. If you remove it immediately, it goes at once and any time left is given up. Either way, Atlassian then deletes its known errors under its own retention rules, up to about 30 days after it goes: its storage documentation gives 28 days, and its data-lifecycle page refers to the retention period in Atlassian’s SOC 2 report. If you reinstall Kenvara and ask within 21 days, Atlassian can relink your earlier data with your consent. We hold no copy of Customer Personal Data: an Export File is how you take your data with you (clause 12.2).
12.2 Export. A Jira administrator can export Your Data at any time, in every licence state, as an Export File holding every known error of the service projects they choose, with its versions, links and audience and, unless they untick it, the audit history of the exported service projects. The file contains the Atlassian account ids of the people who worked on those known errors: store it as you would other personal data. If you need a copy of App data for your own retention purposes, take it before uninstalling.
12.3 Support correspondence and licence records that we hold as Controller are retained and deleted in accordance with the retention table in section 10 of the Privacy Policy.
12.4 We may retain Customer Personal Data to the extent required by law, in which case we will continue to protect it in accordance with this DPA and Process it only for the purpose requiring retention.
12.5 Withdrawing or retiring a known error does not delete its published versions, or the audit entries recording them. Uninstalling removes all of it, once Atlassian deletes the installation.
13. Audit and information
13.1 We will make available to you the information reasonably necessary to demonstrate compliance with Article 28 UK GDPR.
13.2 How we satisfy audit rights in practice. In recognition of the fact that we operate no infrastructure and hold no Customer Personal Data outside Atlassian, other than what clause 10.7 describes in an incident, audit rights are exercised as follows:
- First, by reference to the Cloud Security Statement, this DPA and the App’s published permission scopes.
- Second, by reference to Atlassian’s independent certifications and audit reports covering the infrastructure on which the App runs, which you may obtain directly from Atlassian. We cannot supply Atlassian’s audit reports on Atlassian’s behalf.
- Third, by written questionnaire to support@itsm-ltd.com, which we will answer within 5 business days, no more than once in any 12-month period unless a Personal Data Breach has occurred or a Supervisory Authority requires otherwise.
13.3 On-site or remote inspection. Where the steps in clause 13.2 are demonstrably insufficient to meet a requirement of Data Protection Laws or of a Supervisory Authority, you may conduct an inspection subject to: 30 days’ written notice; conduct during our normal business hours; no more than once in any 12-month period unless a Personal Data Breach has occurred; execution of a confidentiality agreement by you and any auditor; no access to other customers’ data or to our other confidential information; and use of an independent auditor who is not our competitor. You bear your own costs and will reimburse our reasonable costs of supporting an inspection beyond one business day.
13.4 We do not hold, and are not certified under, SOC 2, ISO/IEC 27001 or comparable standards. Section 9 of the Cloud Security Statement explains this and identifies which certifications belong to Atlassian.
14. Liability
14.1 The limitations and exclusions of liability in clause 12 of the End User Terms apply to this DPA, and each party’s total aggregate liability arising out of or in connection with this DPA and the End User Terms together is subject to a single cap as set out in that clause.
14.2 Clause 14.1 does not limit either party’s liability to a Data Subject, or to a Supervisory Authority, or any liability that cannot lawfully be limited under Data Protection Laws.
14.3 Nothing in this DPA affects Article 82 UK GDPR (right to compensation) or Article 83 (administrative fines) as between a party and a Supervisory Authority or Data Subject.
15. California Consumer Privacy Act
Where we Process personal information of California residents on your behalf, we act as a “service provider” as defined by the CCPA as amended by the CPRA. We: Process such personal information only to perform the services under the End User Terms; do not sell or share it; do not retain, use or disclose it for any purpose other than performing the services or as otherwise permitted by the CCPA; do not combine it with personal information from other sources except as permitted; and certify that we understand and will comply with these restrictions. You may take reasonable steps under this DPA to ensure our use is consistent with your CCPA obligations.
16. General
16.1 Changes. We may amend this DPA where required by a change in Data Protection Laws, by a Supervisory Authority, or by a change in our Processing. Where an amendment materially reduces your rights, we will give at least 30 days’ notice to the technical contact on your licence, and it will not apply retrospectively or reduce our obligations during your then-current Subscription Term.
16.2 Governing law. This DPA is governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction, save where a transfer mechanism in Annex 4 requires otherwise for the Processing to which it applies.
16.3 General provisions. Clauses 14.1 to 14.9 of the End User Terms (assignment, publicity, notices, force majeure, entire agreement, third-party rights, severance, waiver, export and sanctions) apply to this DPA as if set out here.
16.4 Order of precedence. Where this DPA conflicts with a transfer mechanism in Annex 4, that mechanism prevails in respect of the transfers it governs.
Annex 1: Details of the Processing
| Item | Details |
|---|---|
| Subject matter | Provision of Kenvara to the Customer through the Atlassian Marketplace |
| Duration | For the Subscription Term and until the App is uninstalled, then until Atlassian deletes the installation, plus any period of legally required retention |
| Nature of Processing | Collection, recording, organisation, structuring, storage, retrieval, consultation, use, alteration, display to Portal Customers and erasure of Customer Personal Data within Forge SQL and Forge’s key-value store, by automated means |
| Purpose | Delivering the documented functions of the App on the Customer’s instructions, and providing support |
| Frequency | In response to user actions, scheduled checks and events in the Customer’s Jira site |
Categories of Data Subjects
- the Customer’s agents, publishers and administrators;
- Portal Customers, including, for a managed service provider, its clients’ people;
- people named in known-error text, if an agent writes them in;
- people named in work items that Kenvara reads for matching, within the call only;
- the assignee of a work item who receives a review reminder (Jira sends it; Kenvara stores nothing about them).
Types of Personal Data
| Record | Personal data it holds | Kept for |
|---|---|---|
| Known errors and their versions | Account ids of the author, editors, owner and publisher; free text agents write | Life of the installation |
| Audiences | Organisation ids and names, which are business data unless an organisation is named after a person | Life of the installation |
| Links to work items | The linking agent’s account id; the work item’s key | Until unlinked or the work item is deleted |
| Applied workarounds | Account ids of the agent who applied it and of whoever recorded the outcome; the reply’s comment id, never its text | Life of the installation |
| History of changes | The actor’s account id, “erased” once closed; otherwise ids, codes, counts and dates only | Life of the installation |
| Settings | The account id of the last editor | Life of the installation |
| Export and import working data | Everything an Export File holds | Until the first daily run 24 hours or more after the job ends |
| Membership cache | A Portal Customer’s account id (in the key), account type, and organisation ids and names | The cache time; expires after a day |
| Permission cache | An agent’s account id | 5 minutes; expires after a day |
| Hourly allowance | A Portal Customer’s account id; numbers and times | Its hour; expires after two hours |
| Feedback | A keyed one-way code in place of the Portal Customer, with the known issue, service project, surface, request type, step, organisation buckets and time | 30 days |
Two points stated explicitly because reviewers ask:
- No email address or display name is stored by the App anywhere. Work-item text read for matching is processed within the call only.
- Other customers’ member lists are not read in this version: the confirmation that would read them is switched off.
Special category or criminal offence data
None is required by the App, and the App does not solicit it. Special category data can appear only in free text an agent writes, or in work-item text read for matching and not stored. If the Customer’s users enter special category or criminal offence data into a known error, the Customer remains the Controller and is responsible for identifying an Article 9 or Article 10 condition and for notifying us in advance so that we can assess whether additional measures are required. The Customer should note in particular that text in a published version of a known error, and in its history, cannot be deleted entry by entry (clause 9.5).
Location of Processing
Forge SQL and Forge’s key-value store, in the region determined by the Customer’s Atlassian data residency configuration.
Annex 2: Technical and organisational measures
This Annex is the authoritative statement of our technical and organisational measures for the purposes of Article 32 UK GDPR and Annex II of the Standard Contractual Clauses. The Cloud Security Statement at https://kenvara.itsm-ltd.com/legal/cloud-security-statement/ is a narrative expansion of the same measures for security reviewers; where the two differ, this Annex governs.
| Area | Measures | By |
|---|---|---|
| Encryption | In transit, TLS 1.2 or above; at rest, AES-256 full-disk encryption, as Atlassian states for its cloud products | Atlassian |
| Isolation | Storage isolated per installation | Atlassian |
| Isolation, in code | Nothing kept in memory between calls; no query reaches beyond the installation’s own storage | ITSM Ltd |
| Confidentiality | Identity only from Atlassian’s signed context; default deny; three server functions; agent and administrator checks; membership read per call or from a bounded cache; no egress; seven named app-level calls | ITSM Ltd |
| Integrity | A strict schema at every server boundary; parameterised SQL only; the history written before the change it records; published versions never altered | ITSM Ltd |
| Minimisation | No email addresses or display names stored; mentions and media removed; feedback under a keyed code for 30 days; caches that expire | ITSM Ltd |
| Testing | The adversarial leakage suite blocks every release; automated checks, run by Kenvara’s deployment command before each deployment it makes and in continuous integration, as section 7 of the Cloud Security Statement sets out | ITSM Ltd |
| Dependencies | Nine pinned runtime dependencies, checked against the lockfile and audited for advisories by Kenvara’s deployment command before each deployment it makes; advisories audited weekly as well; monthly update proposals, each reviewed | ITSM Ltd |
| Logging | Lines carry no account id or record text; kept 30 days | ITSM Ltd and Atlassian |
| Access to ITSM Ltd’s systems | One person; the developer space under multi-factor authentication, its membership reviewed every month from before listing | ITSM Ltd |
| Release | Production deployed only by Steven Godson, from a tagged, checked build | ITSM Ltd |
| Vulnerabilities | Remediated within Atlassian’s timeframes: Critical 10 days, High 4 weeks, Medium 12 weeks, Low 25 weeks | ITSM Ltd |
| Incidents | Atlassian told within 24 hours; customers without undue delay, aiming for 72 hours | ITSM Ltd |
| Availability and backup | Platform compute, storage, backup and disaster recovery; no independent backup is held by us | Atlassian |
Annex 3: Authorised Sub-processors
| Sub-processor | Entity and location | Purpose | Data Processed |
|---|---|---|---|
| Atlassian | Atlassian Pty Ltd (Australia) / Atlassian Corporation (USA); Processing in the region determined by the Customer’s data residency configuration | Hosting, compute and storage for the App; Marketplace licensing and billing; Jira Service Management, our support tool | All Customer Personal Data Processed by the App; and support correspondence held in ITSM Ltd’s Jira Service Management |
| Google Workspace | Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland | Delivery and storage of support email | Support correspondence only, not Customer Personal Data held by the App |
Atlassian is the only Sub-processor that Processes Customer Personal Data held by the App. The only other one, Google, exists because support email has to arrive somewhere. This Annex is kept in step with the sub-processor tables in section 8 of the Privacy Policy and section 10 of the Cloud Security Statement. Changes are notified under clause 7.2.
Annex 4: Restricted Transfers
A. Transfers subject to UK Data Protection Laws
Where a Restricted Transfer is subject to the UK GDPR, the parties adopt the EU Standard Contractual Clauses as modified by the UK International Data Transfer Addendum (version B1.0, in force 21 March 2022), completed as follows:
| Item | Completion |
|---|---|
| Addendum Part 1, Table 1 (Parties) | Exporter: the Customer. Importer: ITSM Ltd. Contact details as recorded in the End User Terms and section 1 of the Privacy Policy |
| Addendum Part 1, Table 2 (Selected SCCs) | Module Two (Controller to Processor), or Module Three (Processor to Processor) where the Customer is itself a Processor |
| Addendum Part 1, Table 3 (Appendix Information) | Annex I(A) and I(B): as set out in Annex 1 of this DPA. Annex II: as set out in Annex 2 of this DPA. Annex III: as set out in Annex 3 of this DPA |
| Addendum Part 1, Table 4 (Ending the Addendum) | Neither party may end the Addendum when the Approved Addendum changes |
| SCC optional clause 7 (docking) | Applies |
| SCC clause 9 (sub-processors) | Option 2, general written authorisation, with the notice period in clause 7.2 of this DPA |
| SCC clause 11 (redress) | The optional independent dispute resolution wording does not apply |
| SCC clause 17 (governing law) | The laws of England and Wales |
| SCC clause 18 (forum) | The courts of England and Wales |
| Competent Supervisory Authority | The Information Commission |
B. Transfers subject to EU Data Protection Laws
Where a Restricted Transfer is subject to the EU GDPR, the parties adopt the Standard Contractual Clauses (Implementing Decision (EU) 2021/914), with the same module selection and optional-clause elections as in Part A, save that: the governing law is the law of Ireland; the forum is the courts of Ireland; and the competent Supervisory Authority is determined in accordance with clause 13 of the SCCs.
C. Transfers subject to Swiss Data Protection Law
Where a Restricted Transfer is subject to the Swiss Federal Act on Data Protection, the SCCs apply with the amendments set out in the Swiss Federal Data Protection and Information Commissioner’s guidance, and references to Supervisory Authorities include the FDPIC.
D. Order of precedence and alternative mechanisms
Where the SCCs or the UK Addendum conflict with any other provision of this DPA or the End User Terms, the SCCs or Addendum prevail in respect of the transfers they govern. If a mechanism adopted here is invalidated, replaced or superseded, the parties will in good faith adopt the successor mechanism or an alternative lawful transfer mechanism without undue delay.
E. Practical note
Where the Customer has configured Atlassian data residency to a UK or EEA region, Customer Personal Data held by the App remains in that region and no Restricted Transfer of App data arises in the ordinary course. Restricted Transfers are most likely to concern support correspondence and licence records. ITSM Ltd keeps support records in Atlassian’s Jira Service Management on its own Atlassian site. Atlassian Corporation is US-incorporated and Atlassian Pty Ltd is Australian, so Part A of this Annex applies to transfers of that data.
Published in accordance with the Atlassian Marketplace Partner Agreement. Read alongside the privacy policy, end user terms, cloud security statement and support and maintenance description for Kenvara.