Trust center

How we handle your data

Last updated: September 27, 2026

Resonate runs entirely inside Jira, on Atlassian's own infrastructure. We don't have a database of your tickets sitting somewhere else. We built it this way on purpose.

We don't want your data

Resonate reads your issue statuses and transitions to compute cycle time. That happens live, inside Jira. We don't copy it out, back it up elsewhere, or keep a second copy of your board anywhere.

Where things live

Board settings and column mappings live in Jira's own storage, right next to your tickets. There's no separate database. Delete the app and your settings go with it. That's intentional, not an oversight.

Runs on Atlassian
App logic executes directly on Atlassian's own serverless runtime, not ours.
Settings live in Jira
Board config and cycle-time numbers sit in Atlassian's Forge storage, not a database we run.
Nothing external
No AWS instance, no separate database, nowhere else your data could end up.

What we can see

We can see that people use Resonate. We can't see your tickets. The app runs inside Atlassian's systems; nothing about what your team is actually working on comes back to us.

Encrypted in transit
Every call between Resonate and your Jira instance happens inside Atlassian's own infrastructure.
Read-only, mostly
We ask for just enough access to calculate cycle time and confirm you're an admin. No write access to your issues, comments, or code.

If something's wrong

Email us. We're a small team, we read everything, and we'd rather hear about a problem from you than find it in a bug report six months later.

[email protected]