FoxPlug is live on Product Hunt today. Come say hi

FoxPlug for Jira: privacy and data handling

Last updated 2026-11-15. This page describes what the app's code does today. The general policy for foxplug.com is at https://foxplug.com/legal/privacy and applies as well.

Who is responsible

FoxPlug is operated by Saul Fleischman (sole proprietor), Naka-ku Hatta Kita-cho 10-31-16-410, Sakai City, Osaka 599-8262, Japan. For the Jira app's data this person is the controller of what you choose to send to FoxPlug. Privacy questions: privacy@mentionfox.com. Security reports: hello@foxplug.com. Setup help and bugs: FoxPlug for Jira support.

What the app reads from Jira

One Jira permission: read:jira-work. When someone opens the project page "Shipped this week (FoxPlug)", the app asks Jira, as that signed-in person, for the issues of that one project that were resolved in the last 7 days (at most 25): the issue key, the title, the issue type and the time it was resolved. It never writes to Jira and reads no other project.

What the app stores (inside Forge)

  • The name of the FoxPlug project you chose and, if you set one, the name of your public changelog.
  • Your FoxPlug agent key, saved as a Forge secret. It is never shown again, never sent back to the page and never written to a log.

This is Forge hosted storage on Atlassian's side. The app has no database of its own and stores no Atlassian account IDs, names or email addresses. When the app is uninstalled, Atlassian removes its Forge storage.

The one outside address: foxplug.com

The app's manifest allows exactly one outside address, foxplug.com, and it is declared as in scope for end-user data. It is called in four ways:

  • Send to FoxPlug (only when someone presses the button): the project's display name, and for each closed issue its key and title, as one work record. Sent with your agent key.
  • Check the key: asks FoxPlug whether the key works. No Jira data is sent.
  • Project list: asks FoxPlug for the names of your own FoxPlug projects so you can pick one. No Jira data is sent.
  • Changelog: reads the public feed at https://foxplug.com/feed/<changelog name>.json. Only the changelog name you typed is sent.

Never sent: assignees, reporters, descriptions, comments, attachments, custom fields, Atlassian account IDs, or anything from other projects. Nothing is sent unless someone presses a button; there is no background job.

What FoxPlug does with a sent record

The issue keys and titles are kept as one draft work record in the FoxPlug account that owns the key. It waits there for that person to read and approve. FoxPlug never posts it anywhere on its own. Text that looks like a secret (for example a key or token pasted into a title) is redacted before it is stored. To turn the record into a short summary and a score, FoxPlug may pass the text to the AI service providers named in the "Service providers we use" section of the general policy; nothing is sold. Data sent from Jira is stored in FoxPlug's own backend (database in Mumbai, India); the app does not use Atlassian data residency.

Keeping and deleting

Records already sent stay in the FoxPlug account until its owner deletes them, or deletes the account (Settings, then Delete my account). There is no automatic expiry and no copy is kept after deletion. After uninstalling the Jira app, FoxPlug keeps what was already sent in the same way. To have a record or an account removed on your behalf, email privacy@mentionfox.com from the address on the account.

Security

All traffic uses TLS. The agent key is a Forge secret. The app does not use Atlassian passwords or personal access tokens, runs a current Node.js runtime and has no child processes or arbitrary code execution. The agent key can be revoked in FoxPlug at any time.