Privacy Policy
Last updated: May 17, 2026
Synaps is a native Atlassian Forge plugin. Your Jira data stays exclusively within your instance via Atlassian's secure infrastructure (Forge KVS). No data is ever sent to third-party servers.
For how we secure the app and the systems around it, see our Security Policy.
01. Who we are
Synaps is a Jira plugin published on the Atlassian Marketplace.
Contact: [email protected]
02. Cookies and analytics
This website does not use cookies, tracking pixels, or any third-party analytics tools. No browsing data is collected when you visit this site.
03. Data we access
Synaps accesses the following Jira data to build and display dependency maps:
- Issues: issue IDs, blocks and relates link relationships, summaries, and assignees
- Projects: project keys, project names, project categories, project leads, and issue count per project
Synaps does not access issue descriptions, comments, or attachments.
Confluence (optional export feature). If you choose to export a dependency map to Confluence, Synaps additionally accesses Confluence to support that feature:
- Spaces and pages: space names and keys, and page titles, so you can pick where to export. Synaps does not read the content or body of your existing Confluence pages.
- Page creation: when you confirm an export, Synaps creates a new Confluence page containing your dependency map, in the space and location you choose, acting on your behalf with your own permissions.
If you never use the Confluence export, no Confluence data is accessed. Any page created this way lives in your Confluence instance, not on any Synaps server.
04. How data is stored
- Atlassian Forge KVS (Key-Value Store): the only persistent storage used by Synaps. Data is stored exclusively within Atlassian Forge infrastructure, inside your Jira Cloud instance. The KVS is hosted on AWS infrastructure managed by Atlassian. The storage region is determined by your Atlassian Cloud instance region and is not controlled by Synaps.
- Local user cache: a temporary in-memory cache scoped to the current user session within your Jira instance. It is never written to disk or transmitted externally. Cached items expire individually with a maximum lifetime of 24 hours (shorter for volatile data such as ticket counts), after which they are automatically purged.
Synaps operates no servers, databases, or external storage of any kind. All data remains within your Atlassian Jira Cloud instance at all times.
05. Legal basis (GDPR)
Processing is based on the following legal grounds:
- Article 6(1)(b) GDPR (performance of a contract): for users on a paid plan, as part of providing the Synaps service.
- Article 6(1)(f) GDPR (legitimate interests): for users on the free plan, to operate and improve the plugin. Our legitimate interest is to provide a functional and reliable dependency mapping service within your Jira instance.
06. Data retention
- Local cache: purged within 24 hours (per-item TTL)
- KVS data: retained for the duration of your active installation
- Full deletion within 30 days of plugin uninstallation
07. International transfers
Atlassian Inc. (headquartered in the US) hosts the Forge infrastructure. Transfers to the US are governed by Standard Contractual Clauses (SCCs) and the EU-US Data Privacy Framework (DPF), to which Atlassian is certified. See Atlassian Privacy Policy for details.
08. Your rights
Depending on your location, you may have rights including access, rectification, erasure, portability, and objection. To exercise any of these rights, contact us at: [email protected]
If you are located in the European Union and believe your data has been processed unlawfully, you have the right to lodge a complaint with your local supervisory authority.
09. Changes to this policy
We may update this policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision. In the event of material changes, we will notify users via the Atlassian Marketplace listing. We encourage you to review this policy periodically.