Draft. This app is not yet available.

Privacy Policy: LabelSafe – Rename, Merge & Undo Labels for Jira

Last updated: October 21, 2026 Provider: YuvGev, Israel ("we", "us") Contact: support@yuvgev.com (privacy and support)

1. What this policy covers

How LabelSafe (the "App"), an Atlassian Forge app for Jira Cloud, handles data, plus the limited data we receive when you email support.

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

2. Data the App reads but does not store

• Labels and issue keys of matching issues, to count, preview and edit labels.
• The newest comment on an issue, shown as a text excerpt (max 280 characters) with author display name and date in the "Last comment" panel. It is fetched as the viewing user, displayed, and not stored or logged.

The App does not copy issue summaries, descriptions, comment bodies or attachments into its storage.

3. Data the App stores

In Atlassian Forge Key-Value Store, per installed site: - Settings: whether project admins may run cleanups. - Job and audit records for the newest 30 bulk jobs: job type, label names, scope (project key / JQL built by the App), status, counts, timestamps, and the Atlassian account ID of the admin who started it. - Undo records: for each edited issue, the issue key and the label names added or removed.

Older finished jobs (beyond the newest 30) are deleted automatically, including their undo records.

4. Where the data is stored

Only in Forge hosted storage on Atlassian infrastructure, in your Jira site's data residency location (Forge data residency). We don't copy, export or download it, and use no sub-processors for it. Atlassian processes it under its own terms and privacy policy.

5. Why the data is processed

Only to provide the App's function: renaming, merging and deleting labels, showing job progress and undoing jobs. No advertising, profiling, analytics or AI training; we don't sell or share data. Your organization decides what is processed.

6. Who can access the data

• Jira site administrators: the admin page, all jobs and undo.
• Project administrators: project-scoped cleanup only after a site admin enables "Allow project admins" (off by default).
• Anyone who can view an issue: the Last comment panel, subject to Jira's own comment visibility.
• Us: no back door, admin console or remote access. In support we see only what you send us.

7. How long the data is kept

• While installed: the newest 30 jobs; older finished jobs are deleted automatically.
• After uninstall: the App can no longer read its data. Atlassian soft-deletes Forge hosted storage and keeps it 28 days; reinstalling doesn't restore it (Forge storage overview). We'll ask Atlassian to re-link data only with your written request and consent, filed within 21 days of uninstall.
• Support emails: as long as needed to resolve the request and up to 24 months after, unless you ask us to delete them sooner.

8. Your choices and rights

• A Jira administrator can delete job history from Activity → Clear history (type clear to confirm). It deletes all job records in the audit list, their undo pages and claims; it doesn't change labels on issues or settings, and it's refused while any job is queued, running or undoing. After clearing, those jobs can no longer be undone. Uninstalling removes everything the App stores.
• End users of a customer's site should contact that organization; we'll help them.

• Otherwise email support@yuvgev.com. We reply within 5 business days.

9. Security

• Scopes approved at install: read:jira-work, write:jira-work and storage:app only.
• We never ask for passwords, API tokens or personal access tokens.
• Diagnostic logs are allow-listed (job id, status, error code, counts); issue keys, labels, summaries, comments and account IDs are not logged.
• Stored data is protected by Forge platform controls (Atlassian Trust Center).

10. Data we receive directly (support)

Your name, email address and whatever you include. Used 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.

11. Children

Business tool, not directed at children.

12. Changes

We update the "Last updated" date on change; material changes are noted in Marketplace release notes.

13. Contact

YuvGev, Israel. support@yuvgev.com