Draft. This app is not yet available.

Privacy Policy: BinSafe – Recycle Bin for Deleted Work Items

Last updated: October 21, 2026 Provider: YuvGev, Israel ("we", "us") Contact: [email protected] (privacy and support)

1. What this policy covers

This policy explains how BinSafe (the "App"), an Atlassian Forge app for Jira Cloud, handles data. It also covers the limited data we receive when you email us for support.

The App runs entirely on Atlassian's Forge platform inside your Jira Cloud site. We do not operate any servers, databases, analytics or third-party services for the App, and the App makes no network calls outside Atlassian. The App is designed to qualify for Atlassian's "Runs on Atlassian" program.

2. Data the App stores

For each Jira site that installs the App, the App stores the following in Atlassian Forge hosted storage (Key-Value Store and Custom Entity Store):

• Work-item snapshots: fields (summary, description, type, status, priority, labels, components, versions, dates, custom-field values), comments (up to 100 per work item), worklogs (up to 100), issue links, subtask references, and attachment names and sizes.
• Small attachment files: the content of attachments of 120 KB or less, up to 600 KB per work item.
• People data in those snapshots: Atlassian account IDs and display names of reporters, assignees, creators, comment and worklog authors, and the person who deleted a work item.
• Audit log entries: for each capture, deletion, restore, purge, retention change and redaction, the action, time, actor account ID, actor display name, work-item key, project ID and a short note (for example "Retention changed from 90 to 30 days"). Audit entries don't contain descriptions, comments or file contents.
• Settings: the retention period and app configuration.

3. Where the data is stored

All data above stays in Forge hosted storage on Atlassian infrastructure. Forge keeps it in the same data residency location as your Jira site, and moves it when a Jira administrator moves Jira (Forge data residency). We don't copy, export or download it, and we don't use sub-processors for it.

Atlassian processes this data as the platform provider under its own terms and privacy policy.

4. Why the data is processed

The data is processed only to provide the App's function: letting authorized Jira users find a deleted work item and recreate it. We don't use it for advertising, profiling, analytics or AI training, and we don't sell or share it.

For work-item content, your organization (the Jira site owner) decides what is processed and is responsible for having a lawful basis to do so. We process that content only on your instructions, given by installing and configuring the App.

5. Who can access the data

Inside Jira: - Jira site administrators can see all snapshots. - Project administrators, and users with Browse projects plus Delete issues, can see snapshots for that project. - Snapshots of work items that had an issue security level are limited to site and project administrators. - Restoring also needs Create issues, except for site administrators.

Us: The App has no back door, admin console or remote access. We can't read your snapshots. If you contact support, we see only what you choose to send us (for example, a screenshot).

6. How long the data is kept

• While installed: a Jira administrator chooses a retention period of 30, 90 or 365 days. A daily job permanently deletes snapshots older than that, including ones already restored.
• After uninstall: the App can no longer read its data. Atlassian soft-deletes Forge hosted storage and keeps it for 28 days before deleting it, and reinstalling doesn't restore it automatically (Forge storage overview). We'll ask Atlassian to re-link the data only with your written request and consent, and only if it can be filed within 21 days of uninstall.
• Support emails: kept as long as needed to resolve the request and for up to 24 months afterwards, unless you ask us to delete them sooner.

7. Your choices and rights

• A Jira administrator can delete stored data by shortening retention, purging, or uninstalling the App.
• A Jira administrator can redact a person: their account ID and display name are replaced with "Redacted user" in stored snapshots and deletion records. Free text that mentions the person, such as comment text, is not rewritten.
• If you're an end user of a customer's Jira site, please contact that organization to access, correct or delete your data. We'll help them.

• For anything else, email [email protected]. We reply within 5 business days.

8. Security

• The App uses only the Jira permissions (scopes) a site administrator approves at install: read:jira-work, write:jira-work (both with user impersonation, so restored comments can be posted as the original author) and storage:app.
• We never ask for passwords, API tokens or personal access tokens.
• Stored data is protected by Atlassian's Forge platform security controls. See the Atlassian Trust Center.

9. Data we receive directly (support)

When you email support, we receive your name, email address and whatever you include in the message. We use it only to answer you. Mail sent to our addresses is received through Cloudflare Email Routing (which forwards it without storing it) and is stored in Google Gmail.

10. Children

The App is a business tool and isn't directed at children.

11. Changes

We'll update the "Last updated" date when this policy changes. Material changes will also be noted in the App's Marketplace release notes.

12. Contact

YuvGev, Israel. [email protected]