Privacy policy

Evidence Log for Rovo. Last updated 14 November 2026.

Who we are

Evidence Log for Rovo is built by Liam Lakevold, an individual developer in Calgary, Alberta, Canada. Contact: liam@kerne.fi.

What the app stores

When an AI agent uses the app's actions, or an app account changes a Jira issue or Confluence page, the app writes an evidence record containing: the Atlassian account ID of the person who asked the agent (and the agent ID Rovo supplies), the agent name, the Jira issue key or Confluence page ID and title, the requested change (for example comment text or a field value), the policy result, the outcome, and a timestamp. Text that looks like a payment card number is blocked and masked. The app also stores its settings (policy) and a signing key generated for your installation.

Where it is stored

All of it is stored in Atlassian Forge storage for your installation, on Atlassian's infrastructure. The app runs on Atlassian (Forge) and makes no calls to any server outside Atlassian. The developer has no access to your data and does not receive copies of it.

Why

The only purpose is to give your team a tamper-evident record of what AI agents did in your site. Nothing is used for advertising, profiling or training.

Retention and deletion

Records are kept while the app is installed, because an evidence log is only useful if it is complete. Site admins can export the log at any time. When the app is uninstalled, Atlassian deletes the app's Forge storage for that installation according to its Forge data retention rules.

Your rights

Requests about personal data in the log are handled by your organisation as the site owner. You can also contact the developer at the address above.