Blog ·
Jira GDPR compliance: what Atlassian covers, and what you own
Jira GDPR compliance is a shared job. Atlassian acts as your processor: it signs a Data Processing Addendum (DPA), relies on the Standard Contractual Clauses for transfers out of Europe, and gives organisation admins tools to delete and export a person's data. You stay the controller. That means you decide what personal data goes into Jira, how long it stays, who can see it, and you answer data subject requests on time. The tool covers the first half. This guide covers both, and shows how to make GDPR's recurring reviews arrive as tickets before they are due.
Statements about Atlassian's GDPR programme are as of October 2026, read from Atlassian's own trust and legal pages. This is a practical guide, not legal advice. Your data protection officer decides what your obligations are.
Is Jira GDPR compliant? #
No tool is GDPR compliant on its own, because the regulation mostly governs what an organisation does with data. What you can check is whether Atlassian gives you what a controller needs from a processor. As of October 2026, its GDPR page says Atlassian:
- offers a DPA that lets customers "lawfully transfer personal data to Atlassian Cloud products outside of the EEA by relying on the Standard Contractual Clauses";
- publishes a Data Transfer Impact Assessment and lets you pin in-scope product content at rest to a location through data residency;
- encrypts data in transit and at rest;
- lists its sub-processors on a public page with an RSS feed for changes;
- gives organisation admins deletion and access tools for the accounts they manage.
The DPA itself, in the version effective from August 17, 2026, sets out the roles plainly. The customer is the controller (or a processor for its affiliate) and "Atlassian is a Processor (or respectively, a Sub-processor) of Customer Data."
What Atlassian's DPA commits to #
The DPA is the contract that makes Atlassian a processor you can use. These are the clauses a Jira admin most often gets asked about:
| Topic | What the DPA says, as of October 2026 |
|---|---|
| Roles | Customer is controller, Atlassian is processor |
| Security incidents | Atlassian notifies the customer "without undue delay and, where feasible, no later than seventy-two (72) hours after becoming aware" |
| Data subject rights | Atlassian provides "reasonable and timely assistance" with access, rectification, erasure, restriction, objection and portability requests |
| Deletion during the subscription | Customers and users can access, retrieve or delete personal data through the product's features |
| Deletion after termination | Atlassian deletes customer personal data, with stated exceptions such as legal retention |
| Transfers | Region-specific terms, including the EU Standard Contractual Clauses, sit in Schedule 2 |
Note what the incident clause gives you. Atlassian's 72 hours run to you. Your own 72 hours to tell the supervisory authority, under Article 33 of the GDPR, run from when you become aware of a breach. Atlassian's notice starts your clock; it does not run it for you.
Where personal data hides in Jira #
Most teams think of Jira as work data. GDPR counts anything that identifies a person, and Jira collects a lot of it without anyone deciding to:
- User accounts: names, email addresses, avatars, time zones.
- Issue fields: reporter, assignee, watchers, and every name in a comment.
- Service desk tickets: customers' names, emails, phone numbers, and whatever they paste into the request.
- Attachments: screenshots of customer records, exported spreadsheets, log files with IP addresses.
- Custom fields that someone added for "customer name" or "account email" two years ago.
- Marketplace apps that read issue content and store or send it somewhere else.
A record of processing activities (Article 30) should list Jira, and each of these, by purpose. If a support project holds customer data, that is a processing activity with a purpose, a retention period and a lawful basis, the same as your CRM.
The rights requests, and their clock #
Data subjects can ask to see, correct, delete or move their data. Article 12(3) gives you one month from receipt to respond, extendable by two further months where necessary, with a reason given within the first month.
For Jira, Atlassian's GDPR page describes two paths:
- Managed users (accounts your organisation manages): an organisation admin can delete the account from the admin portal, and request access to the user's data through Atlassian support.
- Unmanaged users and people without an account: they can start a deletion or access request themselves, from their account profile or Atlassian's request form.
Deleting an account does not remove a person's name from comments or ticket descriptions your own team typed. That cleanup is yours. Find the person's data with a JQL search across the projects that hold personal data, for example a text search on their email address, and redact or delete what you find under your retention policy.
The one-month deadline is where a ticket helps most. Log every request as an issue with a due date 30 days after receipt, and the date becomes visible on a board instead of in someone's inbox. Our guide to setting the due date automatically shows four ways to do that.
The recurring work GDPR asks for #
The setup happens once. Several GDPR duties come back on a cycle, and none of them come with a reminder. Article 32 asks for "a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures". Article 5(1)(e) says data is kept no longer than necessary, which only holds if somebody deletes it. Article 28 makes you choose processors with care, which includes noticing when the processor's sub-processor list changes.
A typical calendar looks like this. The cadence is your organisation's decision, so treat this column as an example to adjust:
| Review | Example cadence | What goes wrong without a ticket |
|---|---|---|
| Retention cleanup (closed service tickets, old attachments) | Monthly or quarterly | Personal data stays years past its purpose |
| User access review (who can see projects holding personal data) | Quarterly | Leavers and role changes keep access they should not |
| Sub-processor list check (Atlassian's and each app vendor's) | Quarterly | A new sub-processor goes unreviewed |
| Marketplace app review (what each app reads and sends) | Twice a year | An app added for one team quietly processes customer data |
| Record of processing activities update | Yearly | The record describes projects you no longer run |
| Data protection impact assessment review | Yearly, and after major changes | The assessment covers a system that has changed |
| Security measures evaluation (Article 32) | Yearly | Controls drift and nobody tests them |
| Staff data protection training reminder | Yearly | Nobody chases the people who did not complete it |
A recurring review should create its own ticket, assigned and dated, before it is due. A spreadsheet or one person's calendar is a single point of failure, and accountability under Article 5(2) means showing that each review happened, not only that you planned it.
Three ways to make the reviews create tickets #
| By hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Effort | Every ticket, every cycle | One rule per review, written once | One rule per review, chosen from a form |
| Schedule | Whoever remembers | Fixed rate or cron expression | Daily, weekly, or monthly on a day or a weekday, every N months |
| Lives in | Somebody's calendar | The automation rules list | The privacy project itself |
| Evidence a run happened | The ticket, if it was made | The rule's audit log | Run history: created, skipped or failed, with the reason |
By hand #
Workable for a small team with a few dates a year. One person owns the calendar and clones last cycle's ticket; our Jira task template guide makes those clones quick. The weak point is the owner's holiday.
Jira Automation #
A scheduled rule can create a work item at a fixed rate or on a cron expression, and it covers most of the calendar above. Two cautions. A date like "the first working day of the quarter" is awkward in cron (see our Jira cron expression guide), and rule runs count toward your plan's automation usage, explained in Jira Automation pricing. Also keep personal data out of any rule that sends email.
A scheduling app #
Recurring Work Items for Jira creates issues on a schedule, with rules scoped to one project. A privacy team's calendar lives inside the privacy project instead of a site-wide rules list other admins edit, and a project administrator turns it on for that project alone. Like any Marketplace app, it belongs in your own app review: check what it stores before you install it, and keep its templates free of personal data.
Set up the review calendar #
Whichever tool you choose, the setup is the same shape. With Recurring Work Items it runs like this:
- Create a privacy project with restricted permissions. It tracks that each review happened and links to where the evidence lives.
- Turn the app on for that project only.
- Create one rule per review. A quarterly access review is a monthly rule repeating every 3 months; a yearly DPIA review repeats every 12 months.
- Pick the day, such as "the 1st" or "the first Monday of the month".
- Set working days and holidays, then choose Move it to the next working day under If it falls on a non-working day, so a review that would land on a weekend moves to a working day: a new rule runs on the day it falls on, holiday or not.
- Title each cycle distinctly with tokens, for example
Quarterly access review {{now.year}}, so this quarter's ticket and the last one never get confused. - Fill in the template: the owner, a due date a set number of days after the run, a label such as
gdpr-review, and a description naming the article it serves and the checklist to follow. - Add subtasks where the review has steps: export access list, compare to roster, remove stale access, record sign-off.
The run history answers the first question an auditor or regulator asks, which is whether the review ticket was raised. The ticket's own history answers the second: who closed it, and when.
Data subject requests are different. They arrive when a person sends one, so they are a request type or an intake form, not a schedule. What a schedule can add is a weekly "open rights requests" check that lists anything near its one-month deadline. Our Jira weekly report guide shows the filter behind that kind of ticket.
When the manual way is enough #
A scheduled calendar pays off once the reviews outgrow one person's memory. You may not need one if:
- you are a small team with a handful of dates you already track reliably;
- you run a dedicated privacy platform that assigns and evidences these reviews already;
- Jira holds no customer or end-user data, only your team's own work.
In that last case, your GDPR work for Jira is mostly the staff accounts themselves, and Atlassian's admin tools handle their deletion.
For the wider compliance calendar, see our guides to Jira ISO 27001, the Atlassian SOC 2 report and Jira HIPAA compliance, which share most of the same recurring reviews.
FAQ #
Is Jira GDPR compliant? Atlassian offers a DPA with the Standard Contractual Clauses, data residency for in-scope content, and admin tools for deletion and access requests. Compliance itself is shared: Atlassian covers its processor duties, and you remain responsible as controller.
Where is Atlassian's DPA? It is published on Atlassian's legal pages. As of October 2026 the current version is effective from August 17, 2026, and it supplements the Atlassian Customer Agreement.
How do I delete a user's data from Jira? An organisation admin can delete a managed account from the admin portal. Names typed into comments, descriptions and attachments are your team's content, so search for them and redact them yourself.
How long do we have to answer a GDPR request? One month from receipt under Article 12(3), extendable by two further months where necessary. Logging each request as a Jira issue with a due date keeps that deadline visible.
Can Jira remind us about GDPR reviews? Not from a date field on its own. A scheduled rule, in Jira Automation or an app like Recurring Work Items for Jira, can create each review ticket ahead of its due date.