TestLens privacy notice

Last updated: 16 November 2026.

TestLens is an experimental Jira Cloud app operated by James Cullimore. Contact: info@jamescullimore.dev.

TestLens processes requirements, test mappings, source snapshots and execution reports that users explicitly import. These may contain personal data if users include it. Use synthetic examples for this evaluation; do not upload secrets, credentials or confidential customer data.

The app reads Jira issue and project information to identify the current workspace, display issue summaries and check the invoking user's access. It stores Jira issue/project identifiers and the invoking user's Atlassian account ID alongside review actions and timestamps. Account IDs identify who changed evidence; they are personal data even though the app does not request profile names or email addresses.

Evidence is stored in Atlassian Forge hosted storage, separated by installation and environment. The app has no external backend, advertising or third-party analytics. It does not execute uploaded source code. The optional Ask TestLens feature uses Atlassian Rovo to explain evidence. Its read-only action returns a limited summary of requirements, criterion decisions, evidence references and next-test recommendations for an issue the invoking user can access. It does not return original imports, source-file bodies or reviewer account IDs to the agent. Your chat prompts and these summaries are processed by Atlassian’s Rovo service under its applicable AI terms. Rovo cannot approve mappings or change stored evidence. Atlassian operates the underlying Jira and Forge services, including platform diagnostics.

Users may explicitly import acceptance criteria from a selected Jira text field. TestLens retains the accepted text and checks it against the current field when evidence is viewed or refreshed. It retains up to three compact prior evidence snapshots within the workspace size budget. Users may preview and confirm a follow-up Jira issue; the app creates it with a link to the source issue and the source issue’s security level. Follow-up identifiers and creation markers are retained to track progress and avoid duplicate creation. Clearing TestLens evidence does not delete those Jira issues. Project-wide Rovo summaries apply the invoking user’s issue permissions and report their pagination limits.

People who can access the relevant Jira issue or project can view its evidence. Mutations require the appropriate Jira edit or administration permission. Authorised app administrators may access app storage or platform diagnostics when operating or supporting the app; no routine evidence export to a separate service is configured.

Evidence remains until an authorised user clears the workspace. There is currently no automatic time-based expiry. Each workspace retains up to 20 original imports and the latest 100 audit entries, within a 220 KB snapshot limit. Export evidence → Export evidence JSON downloads a local copy. Clear this evidence workspace removes the active evidence, source content and audit history from that workspace; a revision marker and identifier-only project index remain. Exported copies are controlled by the person who downloaded them.

Uninstalling is subject to Atlassian's hosted-storage retention and recovery lifecycle; it is not a promise of immediate deletion from all platform backups. See Atlassian's storage lifecycle.

For questions about your data, access, correction or deletion, contact the operator above and identify the relevant Jira site and issue without sending passwords or tokens. This notice must be updated if the app's processing changes.

The optional GitHub Actions connection accepts test reports and source snapshots from an administrator-approved workflow. TestLens checks short-lived GitHub identity tokens against public signing keys fetched from token.actions.githubusercontent.com; it does not store these tokens or send evidence to GitHub. Stored receipts include repository and workflow identifiers, the approved commit, run link, timestamps and report hashes. The approved workflow attests execution. Connections remain active until revoked or the workspace is cleared, and need renewed approval for a different commit. Rovo may include these receipt details in its read-only summary.