Privacy policy
Last updated 4 October 2026
Tidepool is an Atlassian Forge app that renders Mermaid diagrams in Confluence and Jira. This policy explains what data it handles.
Where your data lives
Tidepool runs on Atlassian's Forge platform and does not send data to any external server. Diagram source and rendered images are stored inside your Atlassian site: in the Confluence macro on the page, or in an issue property on the Jira issue. They are covered by Atlassian's permissions, backups, data residency and deletion.
What Tidepool stores
- Diagram source, rendered SVG, and when a diagram was last edited, stored on the page or issue. Tidepool does not store who edited it, or any other Atlassian account ID or personal data.
- Per-site AI usage counts, used to enforce monthly quotas, stored in Forge app storage.
- Unsaved editor drafts, and a count of diagrams you've made (for a one-time review prompt), kept in your own browser's local storage.
AI features
When you ask Tidepool to draft or fix a diagram, your prompt and the current diagram are processed by Atlassian: by Rovo on sites that use it, or by Atlassian's Forge LLM service otherwise. These requests stay within Atlassian's platform and are governed by Atlassian's AI terms. We do not receive or keep them.
What we can see
We, the developer, can't read your pages, issues or diagrams. Forge app logs from your site are visible to us only if your site admin allows log access, and Tidepool logs errors, not diagram content.
Support requests
If you open a GitHub issue, it is public and handled under GitHub's privacy policy. If you email us, we use your message only to answer it. The in-app "Report a problem" link includes diagram source only if you choose to.
This website
This site is hosted on GitHub Pages and uses no cookies or analytics.