Data and privacy

Close Review keeps the evidence needed to compare Jira time entries and record your review. The app runs on Atlassian Forge.

This disclosure describes Close Review by TanSolutions. Last reviewed: 20 September 2026. For a question or request, email oguztan48@proton.me.

What the app uses

It reads Jira project, issue and worklog identities, worklog dates and durations, source timestamps, and access information needed to check whether a result can be shown. It stores the selected period and timezone, relevant identifiers and durations, check coverage, content fingerprints, priority settings, and saved review decisions and reasons.

Those records can relate to people even without a stored name. The app does not persist Jira names, email addresses, issue descriptions, worklog comments, billing rates or raw API responses. Period names and review reasons are text you enter; avoid unnecessary personal or confidential information in them.

Where information goes

The installed app uses Forge storage scoped to the installation. Its current manifest has no external server, AI processor, email sender or external data store. There is no cross-customer model training. The app reads Jira; it does not edit worklogs or perform financial transactions.

If you email support, your message and attachments go to the support mailbox and its email provider, separately from the Forge app. Exported files leave the app under your control. This documentation site has no forms, analytics scripts or advertising code; its hosting provider may process ordinary request information to deliver and secure the pages.

Who can see a review

Jira administrator access is required. The app checks current project, issue and worklog access before displaying protected captured details, history or exports. A stored result does not grant access after Jira permissions change. Customers remain responsible for the people and permissions they manage in Jira.

Temporary browser data

An unfinished request can be held in the tab’s session storage to recover an interrupted save. It may contain a review note or period details, is separated by Jira site, account and environment, and is cleared when the result is confirmed. It cannot bypass server permissions.

Unsaved review notes are kept in the current app instance’s memory while you navigate, limited to 200 notes of up to 500 characters. They are not sent until saved and do not survive closing or reloading the app.

Retention, deletion and recovery

Period data expires 90 days after creation. The app stops serving expired data; physical platform cleanup can occur later. You can delete a period or erase app data. Cleanup prevents old queued work from recreating deleted records. Bounded technical operation receipts and scan-quota counters may remain; they do not contain worklog contents.

Uninstalling follows Atlassian’s storage lifecycle. A reinstall creates a new partition, so old reviews do not automatically return. Atlassian currently documents a 28-day retention period and a recovery request deadline of 21 days. Customer consent and an Atlassian support process are required. See Atlassian’s storage recovery documentation. App deletion is separate from uninstall recovery.

Your choices

You can export saved changes, review reports and decision history; pause daily monitoring; or erase the app’s data. Cancelling a subscription pauses new collection and review changes while authorized historical export and erasure remain available within retention.

For access, correction or deletion requests that you cannot complete in the app, contact support. We need to verify your authority for the affected Jira installation before taking action. Your organization controls its Jira source records and any copies of exported files.

Changes to this disclosure

Changes to implemented processing will be reflected here with an updated review date. This page does not claim certifications, legal compliance guarantees or processing arrangements that have not been verified.