Security policy
Last updated 4 October 2026
How Tidepool is built
- Runs on Atlassian. Tidepool is an Atlassian Forge app. All of its code runs on Atlassian's infrastructure, and it makes no requests to external servers.
- Data stays in your site. Diagrams are stored in your Confluence pages and Jira issues, so they follow Atlassian's permissions, encryption, backups and data residency. Forge storage holds only per-site AI usage counts.
- No personal data. Tidepool stores no account IDs, names, emails or other personal data.
- Least privilege. The app asks only for the scopes it needs: read and write Jira work items, read Confluence pages, and app storage. Jira requests run as the signed-in user, so people only see and edit what Jira already allows them to.
- AI within Atlassian. AI drafting is processed by Atlassian's Forge LLM service or Rovo. We never receive prompts or diagrams.
- Safe rendering. Diagrams are rendered with Mermaid in strict security mode, which sanitises labels and blocks scripts and click handlers.
- No secrets. Tidepool never asks for passwords, API tokens or personal access tokens.
- Minimal logging. Logs record errors only, never diagram content, and stay within Atlassian's Forge platform.
Development practices
- Source code is kept in a private repository with access limited to the developer.
- Every change runs automated unit and end-to-end tests before release.
- Dependencies are kept up to date, and security advisories are reviewed and patched promptly.
Reporting a vulnerability
Please email security@tidepoolapp.dev and don't open a public issue. Include steps to reproduce if you can.
- We acknowledge reports within 2 business days.
- We aim to fix critical and high-severity issues within the timeframes in Atlassian's Marketplace security requirements, and we tell affected customers when action is needed.
- We won't take legal action against good-faith research that avoids privacy violations, data destruction and service disruption.