---
title: "Data Security and Privacy Statement - Eficode Connector for Atlassian"
canonical: "https://docs.eficode.io/space/EB/19890177/Data+Security+and+Privacy+Statement+-+Eficode+Connector+for+Atlassian"
format: markdown
---
This statement relates to Eficode Connector for Cloud-based Atlassian connect app. It does not cover this website, nor the Eficode Support website or other Eficode Services.

## What data do we store?

**Eficode Connector for Atlassian Cloud** stores the following information on the Eficode server:

- identifying key for the Atlassian Cloud instance that hosts Eficode Connector
- base URL of the Atlassian Cloud instance
- status of the Eficode Connector add-on in the Atlassian Cloud instance

# Jira, Confluence and Bitbucket

### Organisation

1. Admin key (Provided by their admins so that we can use admin endpoints (licences - active users. Plugin information))
2. Atlassian organisation ID

### Tenant

1. URL of the tenant
2. clientKey (provided by Atlassian automatically when installing)
3. product (Jira, Confluence or JSM)
4. Organisation
5. cloudSiteId (Atlassian site id)

# Jira and Confluence

### License

1. product (jira, confluence)
2. activeUserAmount
3. totalUserAmount
4. licenseSize
5. licenseType
6. List of active user hashes (no plain text user identity data, but SHA256 hashed identifiers)

# Jira

### Fields

1. fieldId (ID of the field in Jira)
2. name
3. custom (Boolean if it is custom or not)
4. schema (List JSON what type of the field is and where it is coming from Example → {"type": "option2", "custom": "com.atlassian.plugins.atlassian-connect-plugin:eu.softwareplant.bigpicture__mode", "customId": 10051} or {"type": "string"})

### Issuetype

1. IssueTypeId (ID in Jira)
2. name
3. description
4. subtask ( Boolean if it is a subtask or not)
5. hierarchyLevel (int)
6. teamManaged ( Boolean default false)
7. deleted

### Issuesecurityscheme

1. IssueSecuritySchemeID (ID in Jira)
2. name
3. deleted

### Workflow

1. WorkflowID
2. name
3. schemes (List JSON, name of the scheme in Jira{` "name": "Test Workflow Scheme"`, `"id": "10001",` } )
4. projects (List JSON Name of the projects in the tenant . Everything in projects found in the response <u>[here](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-workflows/#api-rest-api-3-workflow-search-get)</u>)
5. transitions  (To do, In progress, Done.. , Everything in statuses found in the response <u>[here](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-workflows/#api-rest-api-3-workflow-search-get)</u>)
6. readOnly (boolean)
7. deleted

### Project

1. projectId
2. projectKey
3. name
4. projectCategory
5. leadActive ( Boolean )
6. lastIssueUpdateTime (when was the last issue updated)
7. totalIssueCount
8. style (string  classic...)
9. simplified (boolean)
10. archived (boolean)
11. isTemplate (boolean)
12. deleted

### ProjectMetrics

Contains only number of tickets for a given project and no actual ticket data is stored

1. date of metrics
2. created
3. resolved
4. timeInStatusCategories
5. timeInStatusCategoriesBugs
6. unresolved
7. ageBuckets
8. slaBreachedRatio (JSM projects)
9. satisfactionRatings (JSM projects)

### AuditRecordsStatistics

1. referencedAmount
2. recordType
3. type ( name, estimatedValue, estimateAddedDateTime)

### ProjectCategory

1. name
2. deleted

### Features (What features are in use in Jira)

1. templates
2. timetracked
3. tempo
4. testStatus
5. testStatusRatio (decimal, default 0)
6. reviewStatus
7. reviewStatusRatio (decimal, default 0)
8. xrayInUse
9. bigPictureInUse
10. dashboardToProjectRatio
11. projectsToIssuetypeSetsRatio

### Dashboard

1. dashboardAmount

### Status (Jira statuses)

1. statusId
2. name
3. statusCategory
4. workflowUsage (in how many workflows this status is used)
5. projectUsage (in how many projects this status is used)
6. deleted

### Marketplace applications

1. name
2. app Key
3. third party information
4. data residency options
5. GDPR
6. Privacy enhancing techniques
7. Bug bounty participation
8. Cloud fortified
9. Pricing tiers
10. pricing estimates (based on licensed user amount)

# Bitbucket

### Repository

1. Repository ID
2. Last activity date
3. Project name
4. SCM
5. Main branch
6. Is private
7. is deleted?

### Pull requests

1. Pull request ID
2. Created timestamp
3. last updated timestamp
4. merge timestamp
5. closed timestamp
6. first commit timestamp
7. state of the pull request
8. destination branch
9. merge commit SHA

### Deployment

1. Deployment ID
2. pipeline ID
3. environment name
4. commit sha
5. status of the deployment
6. created timestamp
7. completed timestamp

### Active developers

1. hash of the user email
2. date of activity

Eficode <u>does not</u> store the Personally Identifiable Information (PII) such as usernames, first name, last name, email or IP’s, Issue summary or Issue description. All such data remain in your Atlassian Cloud instance.

For troubleshooting purposes, Eficode Connector for Atlassian Cloud stores technical logs for a period of up to 30 days.

## Where is the data stored?

The data that Eficode does store on your behalf resides on a secure server in AWS Ireland. Eficode database is not exposed to the Internet directly, residing in an network-isolated environment to which only the Eficode Connector application and its administrators have access.

## People and access

Only authorized Eficode staff **from EU / EEA area** have access to the logs and database-stored data.

## Backups

Eficode regularly backs up the data stored by Eficode Connector for Atlassian Cloud. The security protections around those backups are at least as comprehensive as the protections around the live database.

## Privacy

Eficode understands the importance of ensuring the privacy of your personally identifiable information. We store data in our database only as a direct consequence of the operation of the Eficode Connector for Atlassian Cloud add-on, and only for that purpose. We will not sell or release those data to anyone, except that, if compelled disclose them by law, we will comply with such orders.

## Service Exit

After the plug-in is uninstalled, any Customer data shall be automatically deleted within thirty (30) days of the uninstallation.