Kenvara
Privacy policy
How ITSM Ltd handles personal data in connection with Kenvara, the known error database for Jira Service Management.
1. Who we are
This privacy policy explains how ITSM Ltd (“we”, “us”, “our”), a company registered in England and Wales under company number 17339600, with its registered office at 167-169 Great Portland Street, 5th Floor, London, W1W 5PF, handles personal data in connection with Kenvara (the “App”), an application for Jira Service Management distributed through the Atlassian Marketplace.
| Contact | Details |
|---|---|
| Data protection contact | support@itsm-ltd.com |
| Support contact | support@itsm-ltd.com |
| Information Commission registration reference | ZC207852 |
| Postal address | 167-169 Great Portland Street, 5th Floor, London, W1W 5PF |
ITSM Ltd is one person, and we are not required to appoint a Data Protection Officer. Enquiries about this policy should be sent to the data protection contact above.
Statement required by Atlassian. ITSM Ltd, and not Atlassian, is responsible for the privacy, security and integrity of any End User Data processed by us or by the App.
2. Scope of this policy
This policy applies to the App only. It does not apply to:
- Atlassian’s own products and services (Jira, Jira Service Management, Atlassian accounts and related services), which are governed by the Atlassian Privacy Policy;
- this website, which is covered by our website privacy notice; or
- any other application we publish, each of which has its own policy.
3. How the App works, and why this matters
Kenvara keeps known errors (records of a problem’s cause and workaround) for a Jira Service Management site, and shows selected ones to the site’s portal customers as known issues, to the audience an agent publishes them to: all customers, or named customer organisations.
- The App is built entirely on Atlassian Forge and runs on compute operated by Atlassian. We operate no servers, databases or hosting infrastructure for it.
- It stores its data in Forge SQL and Forge’s key-value store, inside your installation.
- It declares no external egress and uses no remotes, so it sends nothing to us or to anyone outside Atlassian.
- To do its job it holds ten permissions, three of which let it write to Jira (section 5.2 lists every write), and it runs scheduled checks as well as responding to people.
- We cannot browse, query or export your data. What we can see is Kenvara’s log lines, which hold identifiers, codes and counts, never an account id or the text of a record (section 5.6).
4. Our role under data protection law
4.1 Where we act as a processor. For personal data in the App’s records and in your Atlassian site that the App reads (sections 5.1 to 5.3 and 5.7), you, the Atlassian customer whose site the App is installed on, are the controller, and we act as a processor on your instructions. Atlassian acts as our sub-processor, because it provides the hosting and storage the App depends on. Our processing for you is governed by our Data Processing Agreement, at https://kenvara.itsm-ltd.com/legal/data-processing-agreement/, which forms part of the End User Terms.
If you run Jira Service Management for clients of your own, as a managed service provider does, you may act as their processor. We then act as your sub-processor, and Atlassian as ours. The portal customers who read your known issues are then your clients’ people. Showing one client’s known issue to another would be a security incident between them, and a personal data breach where the known issue, or the organisation’s name, carries personal data. You decide who sees what, and Kenvara enforces it on every page view.
4.2 Where we act as a controller. We act as a controller in our own right for:
- support correspondence you send us (section 5.4);
- licence and subscription records Atlassian supplies to us (section 5.5);
- business contact records relating to your organisation;
- two uses of Kenvara’s log lines: a daily review of security signals, and a weekly count, from lines that identify the site but no person, of how many sites use Kenvara, for our own reporting. We do not match sites across our other apps;
- if there is a security incident, the incident log we keep, and any logs Atlassian shares with us or report you choose to send (section 10).
5. Personal data we process
5.1 Atlassian account ids
Kenvara stores the Atlassian account ids of the agents, publishers and administrators who work with it: on the known errors they write, the versions they publish, the links they make, the workarounds they apply and the history of changes. Account ids are opaque identifiers assigned by Atlassian.
Kenvara stores no display name and no email address. A person’s name is fetched from Atlassian when it is shown, and mentions are removed from known-error text.
A portal customer’s account id is held only briefly, as the key of a cache entry (section 10). Their feedback is kept under a one-way code in place of who they are (section 5.7).
5.2 What the App reads from, and writes to, your Atlassian products
When an agent asks it to, Kenvara reads a work item as that agent: its summary, description, type, project, status, resolution, the fields your administrator maps, and its links. It stores none of the text it reads for matching, and it never reads comments or attachments. When an agent creates a known error from a work item, the summary and mapped fields they accept are copied into it, and links keep the work item’s key.
With no person involved, Kenvara reads:
- the status, resolution, type and project of linked work items, for retirements, reconciliation and imports;
- once a day, the site’s customer organisations, to check the answers given for customers who sign in with an Atlassian account;
- a work item’s project before a review reminder.
To decide what a portal customer may see, it reads the customer organisations Jira Service Management says they belong to. On the portal it reads only which request type a customer chose, never what they type.
Kenvara writes to Jira in five ways:
- when an agent chooses, it raises a problem, with the known error’s title as its summary;
- it links that problem to the incident it was raised from;
- when an agent chooses, it posts a workaround as a public reply on a request, offered only for a known error published to all customers;
- when an administrator saves a service project’s settings, it records where Jira should show Kenvara’s panel;
- its daily checks send a review reminder, through Jira’s own notifications, to the assignee of the work item a known error was written from. The reminder names the service project and the review date, never a known error’s key, title or customer text.
It never deletes anything in Jira.
5.3 App records
Kenvara’s records are:
- known errors, each with a part written for customers and a part for agents only;
- the versions published to the portal, and who they were published to;
- links to work items, and workarounds applied to requests;
- the history of every change;
- each service project’s settings and the site’s settings;
- working copies of an export or import in progress;
- for the portal, counts and feedback (section 5.7).
Your agents write the known-error text, and it can contain personal data if they type it in. DPA Annex 1 gives the full, record-by-record inventory.
5.4 Support correspondence
When you contact support@itsm-ltd.com, we receive your name, email address, employer or Atlassian site details, and whatever you choose to include in your message, including any screenshots you attach. Please do not send us personal data, credentials or confidential content that is not necessary to diagnose your issue. Kenvara support never asks for your export file, and sending an incident report is always optional.
5.5 Licence and billing records
Kenvara is licensed through the Atlassian Marketplace. Atlassian supplies us with licence records, including the Support Entitlement Number (SEN), the user tier Atlassian bills, the licence status and dates, the customer organisation’s name and a technical or billing contact. Atlassian is the merchant of record; we do not receive or process payment card data.
5.6 Kenvara’s log lines
Kenvara writes a log line for each portal call and for errors. A line holds identifiers, codes and counts. Kenvara’s logging code drops any line with a field for an account id, an email address, a display name, an organisation or record text, and any value shaped like an account id. Atlassian keeps the lines for 30 days in our developer console, where we can see which site each came from. A site administrator can switch off developer access to the app’s logs for their site.
5.7 Portal counts and feedback
Kenvara uses no analytics service and sends nothing about your use outside Atlassian. The only record of use we see is Kenvara’s log lines (section 5.6), which identify the site but no person.
While Kenvara’s licence is active, customers’ responses on the portal are stored with a one-way code in place of who they are, for 30 days; after that only counts remain. Kenvara also counts how often each known issue is shown and opened. The counts identify no one. The one-way code is made with a key held on your site, so the responses are pseudonymised personal data, not anonymous data. An administrator can delete every customer’s responses at once, from the Kenvara page in Apps administration.
6. Purposes and lawful bases
| Data | Purpose | Lawful basis (UK GDPR Art. 6) |
|---|---|---|
| Account ids, App records, portal feedback and data read from Jira (5.1 to 5.3, 5.7) | Delivering the App’s functions on the customer’s instructions | Processed for the customer as controller; the customer determines the lawful basis |
| Support correspondence (5.4) | Responding to enquiries, diagnosing faults, keeping a support record | Art. 6(1)(b) performance of a contract; Art. 6(1)(f) legitimate interests in providing support |
| Licence and billing records (5.5) | Verifying entitlement, administering the licence, renewals and compliance | Art. 6(1)(b) performance of a contract; Art. 6(1)(c) legal obligation (accounting records) |
| Kenvara’s log lines (5.6) | A daily security review, and a weekly count of the sites that use Kenvara | Art. 6(1)(f) legitimate interests in keeping the app secure and running the business; the lines identify a site, not a person |
| Incident records (10) | Investigating and notifying a security incident | Art. 6(1)(c) legal obligation; Art. 6(1)(f) legitimate interests |
We do not carry out automated decision-making producing legal or similarly significant effects, and we do not profile individuals. This version of Kenvara contains no artificial intelligence or machine learning feature, and your data is never used to develop, train, fine-tune or evaluate any model. Before any such feature is added, this policy will describe it. We do not knowingly process special category data; if your use of the App involves it, in text your agents write or in work items they read, you remain the controller of that data and are responsible for identifying an Article 9 condition.
7. Where your data is stored
Kenvara stores its data in Forge SQL and Forge’s key-value store, which follow your Jira site’s data residency: where your site’s data is pinned to a region, Kenvara’s is held there too, and moves with it. Forge SQL, and so Kenvara, is not available in Atlassian Government Cloud. Section 3.4 of the cloud security statement sets out what is in scope and out of scope for data residency. Data residency is managed by Atlassian; details and the current list of regions are on Atlassian’s data residency pages.
Support correspondence (5.4) and licence records (5.5) are held in our own business systems: email in Google Workspace, and support records in Jira Service Management, Atlassian’s service desk product, on our own Atlassian site, under that site’s data residency configuration.
8. Sharing and sub-processors
We do not sell personal data, and we do not share it for advertising or marketing.
| Recipient | Role | Purpose | Location |
|---|---|---|---|
| Atlassian Corporation / Atlassian Pty Ltd | Sub-processor | Hosting, compute and storage for the App; Marketplace licensing and billing; Jira Service Management, our support tool | Per your data residency settings |
| Google Ireland Limited (Google Workspace) | Sub-processor | Delivery and storage of support email | Ireland / European Economic Area |
Atlassian is the only recipient that handles data held by the App. The only other one, Google, exists solely because support email has to arrive somewhere.
Two things can leave your site, both through Atlassian or by your own hand. The first is Jira’s notifications: a review reminder, which names the service project and the review date but no known error, and Jira Service Management’s notice of a public reply an agent posts. The second is an export file a Jira administrator takes, which holds the Atlassian account ids of the people who worked on your known errors and the names of your customer organisations, and which is then yours to keep safe.
We will give 30 days’ notice of any change to the list above by updating this policy and its effective date. We may also disclose personal data where required by law, court order or a regulator, or to establish, exercise or defend legal claims.
9. International transfers
Because App data is held within Atlassian’s infrastructure, transfers are governed by Atlassian’s arrangements, including its Data Processing Addendum and the Standard Contractual Clauses with the UK International Data Transfer Addendum where applicable. Where we transfer support or licence data outside the United Kingdom, we rely on UK adequacy regulations or, where no adequacy decision applies, the International Data Transfer Agreement or the Addendum to the EU Standard Contractual Clauses. A copy of the relevant safeguards is available on request.
10. Retention
| Data | Kept for | Ended by |
|---|---|---|
| Known errors, their versions, applied workarounds, settings | The life of the installation | Atlassian’s deletion of the installation |
| Links to work items | Until unlinked, or the work item is deleted | An agent, or Jira’s deletion event |
| The history of changes | The life of the installation | Account ids replaced by “erased” once Atlassian reports the account closed |
| A portal customer’s organisation list (a cache) | Reused for the membership cache time (60 seconds by default); expires after a day | Expiry, or the weekly check on account closure |
| An agent’s permission check (a cache) | Reused for 5 minutes; expires after a day | As above |
| A portal customer’s hourly allowance | Its hour; expires after two hours | As above |
| Feedback, under a one-way code | 30 days | The daily delete, or “Delete per-customer portal data now” |
| The feedback rate counter, keyed by the one-way code | Its hour, then until the next daily run | The daily job |
| Counts per known issue | Daily figures for 90 days, then monthly; a retired record’s monthly figures for 400 days; site totals for the life of the installation | The daily job |
| Export and import working data | Until the first daily run 24 hours or more after the job ends, within about two days; an idle job is closed after 24 hours first | The daily sweep |
| Kenvara’s log lines | 30 days | Atlassian |
| Support correspondence | 24 months from closure of the enquiry | ITSM Ltd |
| Licence and billing records | 7 years, for UK statutory accounting and tax requirements | ITSM Ltd |
| The incident log | 6 years after the incident closes; contact names and addresses replaced by their role after 90 days | ITSM Ltd |
| Logs Atlassian shares in an incident; a report a customer sends | 90 days after the incident closes | ITSM Ltd |
Lifetimes in Forge’s key-value store may run up to 48 hours late, because Atlassian may take that long to delete an expired key; Kenvara never relies on one past its stored time.
Known errors cannot be deleted: an agent withdraws or retires one, which takes it off the portal and keeps its versions and history. If Kenvara stops running, because Atlassian suspends or deactivates its licence, its daily deletes stop with it, and data due for deletion waits for Atlassian to delete the installation.
When the App is uninstalled. 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. We retain no copy.
11. Security
App data is encrypted in transit and at rest by the Atlassian platform, is isolated per installation, and is reachable by the App only through the permissions it declares. Our security measures are described in full in the cloud security statement at https://kenvara.itsm-ltd.com/legal/cloud-security-statement/, which is the authoritative account of them. Where we act as your processor, the same measures are set out in Annex 2 of the Data Processing Agreement.
Where a security incident affects personal data we hold or process, we will tell the technical contact on your licence without undue delay, and we aim to do so within 72 hours of becoming aware, and help you meet your own notification obligations. Section 8 of the cloud security statement describes how we handle incidents.
We are not certified to SOC 2, ISO/IEC 27001 or comparable standards. The Atlassian infrastructure on which the App runs is independently certified; those certifications belong to Atlassian and can be verified at the Atlassian Trust Center.
12. Your rights
Where we act as a controller (support correspondence, licence records, log lines and incident records), you have the right under UK GDPR to: request access to your personal data; request rectification of inaccurate data; request erasure, where a ground applies; request restriction of processing; object to processing carried out on the basis of legitimate interests; request portability of data you provided to us; and withdraw consent, where processing is based on consent, without affecting earlier processing.
To exercise a right, email support@itsm-ltd.com. We will respond within one month, extendable by two further months for complex requests, and we will tell you if an extension applies. There is normally no charge.
Where we act as a processor (data inside the App and your Atlassian site), please send your request to the Atlassian customer whose site holds the data, normally your own organisation’s administrator. If you are a portal customer, ask the organisation that runs the portal; for a client of a managed service provider, that is the provider. We will help that customer respond.
12.1 One limitation you should know about: the history of changes
Kenvara keeps a history of who changed what and when, which no one can edit. That is the point of it: it is how a site shows what each customer organisation was shown, and when.
- The history records an Atlassian account id, never a name or an email address.
- When Atlassian reports an account closed, Kenvara replaces that id with “erased” at its next weekly check, keeping no trace of it. Until then the id is kept for the life of the installation.
- An export taken before the account closed still holds the id.
- A customer’s feedback is kept for 30 days, and an administrator can delete all of it at once.
If you are an individual and this concerns you, raise it with the organisation whose Jira site holds the record; it is the controller. If you are that organisation, clause 9.5 of the Data Processing Agreement sets out how we will help you, and what determination remains yours.
Complaints. If you are dissatisfied with how we have handled your personal data, please tell us first at support@itsm-ltd.com. We will acknowledge your complaint within 5 business days and respond substantively within 30 days. You also have the right to complain to the Information Commission at ico.org.uk/make-a-complaint, by telephone on 0303 123 1113, or by post to the Information Commission, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF.
13. Notice to residents of California
If you are a California resident, you have rights under the California Consumer Privacy Act as amended, including rights to know, delete, correct and opt out. We do not sell or share personal information as those terms are defined under the CCPA/CPRA, and we do not process personal information for cross-context behavioural advertising. We do not use or disclose sensitive personal information for purposes requiring an opt-out. To exercise a right, contact support@itsm-ltd.com; we will not discriminate against you for doing so.
14. Children
The App is a business tool licensed to organisations and is not directed at children. We do not knowingly process the personal data of anyone under 18 in connection with the App.
15. What you tell your own customers
Your portal customers are your data subjects, not ours. You can adapt this paragraph for your portal’s privacy notice:
When you read known issues on this portal, [your organisation] records on its own Atlassian site how often each was shown and opened, and any feedback you give. Your feedback is kept for 30 days with a one-way code in place of who you are; after that only counts remain. None of it leaves Atlassian.
What is published to your customers, and to whom, is your decision. Kenvara enforces it.
16. Changes to this policy
We may update this policy from time to time. Material changes will be notified by updating the effective date above and, where the change materially affects your rights, by email to the technical contact on your licence at least 30 days before the change takes effect. Previous versions are available on request.
This privacy policy is published in accordance with the Atlassian Marketplace Partner Agreement. It should be read alongside the end user terms, the cloud security statement and the support and maintenance description for Kenvara.