TimeBound privacy policy

Last updated: October 1, 2026.

This policy explains what data the TimeBound app for Jira Cloud ("TimeBound") processes and stores. TimeBound is provided by Selana Technologies LLC ("we", "us"). Contact: hello@selana.io.

Summary

Data TimeBound processes

When a user runs a report or opens an issue, TimeBound reads, as that user and through Atlassian's APIs: the issues matching the JQL query (key, summary, status, priority and created date), the list of statuses, status categories and priorities, each issue's status change history, and which issues match each SLA's scope JQL. It calculates SLA times in memory and returns the result to that user's browser. Nothing is kept after the request.

Because every call runs as the signed-in user, results only include issues that user can already see in Jira.

Data TimeBound stores

SLA settings created by Jira admins: SLA names, scope JQL, status names and categories, goals in hours, calendar names, time zones, working hours and holiday dates. These are stored in Atlassian Forge storage and are deleted by Atlassian when the app is uninstalled, in line with Atlassian's data retention for Forge apps.

Data sharing

We do not sell or share data with third parties. TimeBound sends no data outside Atlassian.

Access and security

Logs

Atlassian Forge may record errors from TimeBound (for example an HTTP status code) for troubleshooting. TimeBound does not log issue content.

Your rights

To ask about data processed by TimeBound, email hello@selana.io. For data stored in Jira itself, Atlassian's privacy policy applies.

Changes

We will update this page and the date above if this policy changes.