AttachPulse for Jira: privacy policy
Last updated 17 October 2026. Vendor: PuzariCloud (Ritom Puzari), support@puzaricloud.in.
Summary
AttachPulse runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It sends no data outside Atlassian, has no external servers, uses no analytics or tracking, and has no storage of its own.
What the app reads
- The list of attachments on the issue you are viewing or editing (file name, size, type and date), read with your own Jira permissions so you can pick files for a slot.
- Image thumbnails and file contents when you view or download a file, also with your own permissions.
- When an issue with a filled slot is opened, a Forge function on Atlassian's infrastructure reads that issue's attachment list to remove files that were deleted from the issue.
- The list of Jira fields, when a Jira administrator configures the workflow validator.
What is stored, and where
- Slot values (attachment IDs, file names, sizes and types) are saved by Jira as the value of the custom field on the issue, like any other field value. They stay inside your Jira site and are deleted with the issue or the field.
- Slot rules (allowed types, size and count limits, hint) are saved by Jira as the field's context configuration.
- Validator settings (slot, minimum count, file types, message) are saved by Jira in the workflow.
- The app stores no user names, account IDs or e-mail addresses, and keeps no logs of issue content.
Personal data
AttachPulse does not store personal data. File names are part of your Jira content and stay in Jira.
Sharing
We do not receive, sell or share any of your data. PuzariCloud has no access to your Jira content.
Uninstalling
When the app is uninstalled, Jira hides the slot fields. Atlassian keeps their values for 30 days in case you reinstall. Your attachments themselves are never touched.
Contact
Questions: support@puzaricloud.in.