Jira data residency

Where your data is stored

Balsamiq for Jira saves your project files as attachments to Jira issues, so at rest they follow your site's data residency region. You can use Balsamiq for Jira Cloud on a site in any of standard Atlassian Cloud's regions.

Balsamiq for Jira Cloud also keeps some data outside Atlassian, in AWS US East-1, whatever your site's region:

• A working copy of the wireframes you open, for auto-saving and real-time collaboration, in an encrypted database. It's unloaded after 30 days of no use, once your changes are saved back to Jira, and its backups are deleted within 7 days after that.
• The image links, public shares and prototype links you create, with their images. They stay available until you delete them, or the board (once you empty the trash), in the editor, or delete the Balsamiq project in Jira. Deleting the issue, or removing the project's attachment outside the editor, doesn't delete them. If you uninstall the app, we delete them within 30 days, and their backups within 30 days after that. If your license ends but the app stays installed, they stay available until you delete them or uninstall the app.
• AI features, if you use them: the prompts and board content they work on are processed by Balsamiq's AI server, also in AWS US East-1, and by the AI providers listed on our subprocessors page. We keep these AI inputs and outputs for 60 days after each request, and their backups for up to 35 days after that.

Atlassian Isolated Cloud

Balsamiq for Jira isn't available for Atlassian Isolated Cloud, and we don't plan to offer it there. Your project files are stored as attachments on your Jira issues, but Balsamiq for Jira Cloud is a Forge app whose editor runs on Balsamiq's own servers on AWS, outside Atlassian's infrastructure, and the working copy and links listed above are kept on those servers. That doesn't fit Isolated Cloud's model. Balsamiq for Jira is fully supported on standard Jira Cloud, and it's also available on Atlassian Government Cloud.