OVERALL RATINGS
INSTALLS
8
SUPPORT
- Partner Supported
- Requires
- JIRA
- Works with
- CONFLUENCE
Privacy and Security details
The Atlassian Marketplace partner is responsible for the accuracy of the information provided below. Details with a verified status are confirmed by Atlassian. For any further queries, contact the partner.
Data storage and management
End-User Data processed and/or stored outside of Atlassian apps and services (excluding process/storage of End-User Data in logs)
The app processes the following types of End-User Data:
Natural-language request text entered by the user — transmitted to the AI provider
SQL query text and database error messages — transmitted to the AI provider; may quote values entered by users
The app stores the following types of End-User Data:
Atlassian account ID
User display name
Work item content — summary, description, comment bodies
Work item metadata and change history — status, dates, changelog values, author attribution
Worklogs — author, date, duration, worklog comment (Jira and Tempo)
Confluence page metadata — title, author, version, URL
Assets (CMDB) object attributes — customer-defined, may contain personal data
Permission metadata — group memberships, project roles, issue security levels, page and space restrictions
Application audit log — account ID, query executed, timestamp
Data residency for in-scope End-User Data
Marketplace app supports data residency and stores End-User Data independently outside of Atlassian apps and services in the following locations:
🇩🇪
Germany
🇬🇧
United Kingdom
🇺🇲
United States of America
🇸🇬
Singapore
🇦🇺
Australia
🇧🇷
Brazil
More information on the Marketplace app’s data residency policy can be found in app’s product documentation or please contact the respective Marketplace app partner at
privacy@circuitsql.comApp REST APIs
This app does not provide REST APIs.
List of in-scope End-User Data
App stores the following types of in-scope end-user data:
Jira work item and field content — summaries, descriptions, custom field values
Comments — work item comments and worklog comments
Board and sprint data
Work item change history and sprint movement
Worklogs — Jira and Tempo time records
Confluence page and blog post data — title, author, version, URL, status
Jira Service Management Assets (CMDB) object attributes
Project and space configuration data — projects, components, versions, spaces, statuses, request types
Permission metadata — project roles, issue security levels, page and space restrictions, group memberships
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
User account information — Atlassian account IDs and display names
AI data — natural-language request text, SQL and database error messages sent to the AI provider (processed in the United States, deleted within 30 days)
Application audit log — account ID, query executed, timestamp
Application and operational logs — Atlassian Forge logging infrastructure
Saved queries, query history and query templates — Atlassian Forge storage
App configuration, role assignments and access rules — Atlassian Forge storage
Custom field value snapshots and work item to option mappings — Atlassian Forge storage
Migration of in-scope End-User Data between data residency supported locations
No
End-User Data shared with third-party entities
Neon, a Databricks company
Link:
https://neon.com
Location:
🇩🇪
Germany
🇬🇧
United Kingdom
🇺🇲
United States of America
🇸🇬
Singapore
🇦🇺
Australia
🇧🇷
Brazil
Purpose:
Cloud hosting of the PostgreSQL database provisioned exclusively for each installation. The customer's administrator selects one region at setup; the default is Frankfurt (Germany). Data is stored in that single region only.
Amazon Web Services, Inc.
Link:
https://aws.amazon.com
Location:
🇩🇪
Germany
🇬🇧
United Kingdom
🇦🇺
Australia
🇸🇬
Singapore
🇦🇹
Austria
🇧🇷
Brazil
Purpose:
Underlying cloud infrastructure on which Neon operates. Onward sub-processor engaged by Neon, not contracted directly by us. Same region as the customer's Neon database.
Anthropic PBC
Link:
https://www.anthropic.com
Location:
🇺🇲
United States of America
Purpose:
Built-in AI features: generating and refining SQL from a natural-language request. Receives the database schema structure, the request text, the SQL being worked on and, when using Fix with AI, the database error message. Query results are never sent. Inputs and outputs are deleted within 30 days and are not used for model training.
End-User Data accessed in logs
Yes
End-User Data processed and/or stored in logs outside of Atlassian apps and services
No
End-User Data in logs shared with third-party entities
No
End-User Data in logs shared with third party entities integral for app functionality
No
End-User Data stored after app is uninstalled
No
Custom retention period for End-User Data
Yes
Supports customer-managed egress
No.
The app only accesses domains declared during installation.
Security and compliance
Contact for app security issues
App’s e-mail contact:
privacy@circuitsql.comIntegration permissions with Atlassian apps
This app will perform the following actions. It can also perform these actions on behalf of users:
Read customer request data, including approvals, attachments, comments, request participants, and status/transitions. Read service desk and request types, including searching for request types and reading request type fields, properties and groups.
Read and write to app storage service
Jira
Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
Create and edit project settings and create new project-level objects (e.g. versions and components).
View boards, issues on a board, issues from a backlog, reports, and versions.
Get list of all Assets object type attributes for a schema or an object type.
Read Assets configuration
Read Assets objects, their attributes values and details.
Get list of or details of individual schemas in Assets.
Read Assets object types and their attributes.
View user groups.
View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
View organization's users.
View organization information.
View permissions.
View organizations associated with service desk.
View sprints and sprint related issues and properties.
View users.
Create or update Assets objects, their attributes values and details.
Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.
Confluence
View and download attachments of a page or blogpost that you have access to.
View and export audit records for Confluence events.
View blogpost content.
View the restrictions on the content.
View details about groups including its members.
View page content.
View space permissions.
View space details
View user details.
Search Confluence. Note, APIs using this scope may also return data allowed by read:confluence-space.summary and read:confluence-content.summary. However, this scope is not a substitute for read:confluence-space.summary or read:confluence-content.summary.
More information on the justification of app’s integration permissions are shared by the app’s partner hereCompliance certifications
None.
Marketplace Security Bug Bounty Program participant
No
CAIQ Lite
CAIQ Lite Questionnaire has not been submitted
Security policy
Full disk encryption for data stored outside of Atlassian
Yes
App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret
No
Privacy
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policyCompany/Organization is a 'data controller' under the General Data Protection Regulation (GDPR) with reference to this app
No
Company/Organization is a 'data processor' under the General Data Protection Regulation (GDPR) with reference to this app
Yes.
Company/Organization is a 'data processor' for the following types of End-User Data:
Atlassian account IDs
User display names
Work item content — summaries, descriptions, comment bodies
Work item metadata and change history — status, dates, changelog values, author attribution
Worklogs — author, date, duration, worklog comment (Jira and Tempo)
Confluence page and blog post metadata — title, author, version, URL
Assets (CMDB) object attributes — customer-defined, may contain personal data
Permission metadata — group memberships, project roles, issue security levels, page and space restrictions
Application audit log — account ID, query executed, timestamp
Natural-language request text entered by the user — transmitted to the AI provider
SQL query text and database error messages — transmitted to the AI provider
Saved queries, query history and query templates — may contain values typed by users
Custom field value snapshots and work item to option mappings
Company/Organization is a 'business' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
No
Company/Organization is a 'service provider' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Yes.
Company/Organization is a 'service provider' for the following types of End-User Data:
Atlassian account IDs
User display names
Work item content — summaries, descriptions, comment bodies
Work item metadata and change history — status, dates, changelog values, author attribution
Worklogs — author, date, duration, worklog comment (Jira and Tempo)
Confluence page and blog post metadata — title, author, version, URL
Assets (CMDB) object attributes — customer-defined, may contain personal data
Permission metadata — group memberships, project roles, issue security levels, page and space restrictions
Application audit log — account ID, query executed, timestamp
Natural-language request text entered by the user — transmitted to the AI provider
SQL query text and database error messages — transmitted to the AI provider
Saved queries, query history and query templates — may contain values typed by users
Custom field value snapshots and work item to option mappings
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
Yes,
Standard Contractual Clauses (EU Commission Implementing Decision 2021/914), Modules Two and Three, with the UK International Data Transfer Addendum and the Swiss addendum; adequacy decision for Switzerland; EU-U.S. Data Privacy Framework
Privacy enhancing technologies (PETs) used to protect End-User Data
Yes
Pseudonymization — Atlassian account IDs are stored as the identifier; display names are resolved at read time and not persisted in the audit log
Data minimization — email addresses, attachments and Confluence page bodies are never mirrored
Row-level security — per-viewer database policies reproducing native Jira and Confluence permissions
Column-level data suppression — restricted columns are removed server-side before the response leaves the backend
Egress minimization — the AI provider receives schema structure, request text and SQL only; query results are never sent
Log minimization — prompt length and row counts are logged instead of content
Encryption at rest and in transit — AES-256 at rest, TLS 1.2+ on every database connection
Read-only query enforcement — SELECT-only validation on every execution path
Data Processing Agreement (DPA) for customers
No
Did you find this information useful?
Atlassian will use this feedback to serve you better.