1. Who this policy covers
This policy applies to the CloseReply app for Jira and Jira Service Management, provided by Voidworks. Your organisation remains responsible for how it configures Jira, grants access, and uses content created through the app.
2. Data CloseReply processes
Content configured by your team
- Response templates, folders, variables, and optional after-send actions.
- Personal, project, and global signatures.
- Files uploaded for use with a response template.
- Private preferences such as a user’s starred templates.
Jira data used when you act
When a user previews or applies a template, CloseReply reads the Jira issue or request details needed to resolve variables. When the user confirms an action, the app may add a comment, update permitted fields, transition an issue, attach a selected file, or prepare a follow-up request.
Technical information
Atlassian may provide installation, account, site, project, issue, and request identifiers required to isolate data and complete an authorised action.
3. Where data is stored
Templates, signatures, folders, actions, and user preferences are stored in Atlassian Forge hosted storage. Template files are stored in Forge Object Store. CloseReply has no external egress configured, so app data is not transmitted to Voidworks-managed servers.
4. Who can see configured content
Access follows the content’s scope and the current user’s Jira permissions. Personal content is tied to an Atlassian account. Project content is available within its project, and global content is available within the installation to eligible users. Sites and installations are isolated from one another.
If an administrator explicitly approves a template for the customer portal, CloseReply exposes only the sanitised text content needed for that portal experience. Attachments, signatures, after-send actions, and private metadata are excluded.
5. Legal basis and purpose
CloseReply processes data only to provide the app functions selected by the customer and its authorised users. Voidworks does not sell customer data, use it for advertising, or use customer content to train AI models.
6. Retention and deletion
Administrators and authorised users can update or delete supported app records through the product interface. Atlassian controls the underlying Forge platform lifecycle, backups, and post-uninstall retention. For an export or deletion question that cannot be completed in the app, contact us.
7. Security and incident contact
We minimise permissions, rely on Atlassian’s hosted Forge services, and review app access boundaries as the product changes. Security details and reporting instructions are available on our security page.
8. Changes to this policy
We may update this policy as CloseReply changes or as legal and platform requirements evolve. The current version and effective date will remain published here.
9. Contact
Email privacy and data questions to [email protected], or visit support for product help.