Foliowell for Jira: Privacy Policy
Effective date: October 1, 2026 Publisher: Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA Contact: hello@greatwork.company
This policy explains what information the Foliowell app for Jira Cloud (the "App") processes, where it is kept, and your rights. It covers only the App, not Atlassian's products, which are governed by Atlassian's own privacy policy.
1. Summary
- The App runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It has no servers of its own and sends no data to Great Work or to any third party.
- When you export, the App reads the work items your query matches, with your own Jira permissions, and builds the Word, PDF or Excel file in your browser. The file is saved to your device, or attached to a Jira work item if you choose.
- Scheduled exports are built inside Forge and attached to the Jira work item the schedule names. They only include work items the schedule's owner can browse.
- The App stores Word templates, settings, schedules and their run history in your site's Forge storage. Great Work LLC cannot see your templates, exports or Jira data.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| Work items the export's query matches: fields you chose (summary, description, status, people's display names, dates, labels, versions, custom fields), and if you include them comments, worklogs, change history, subtasks, links and the attachment list (file names and sizes, not file contents) | To fill the document | Downloads: in your browser while the file is made, then only in the file you saved. Scheduled exports: Forge storage in temporary chunks while a run is in progress, deleted when the run ends (or fails), and in the file attached to Jira |
| Word templates your template managers upload, with their name, description, size and who uploaded them (Atlassian account id) | To fill them | Forge app storage until deleted or uninstall |
| Settings: company name, default date format, manager groups (group ids and names) | Printed on documents; access control | Forge app storage until changed or uninstall |
| Schedules: name, query, format and options, cadence and time zone, target work item key, owner (account id and display name) | To run them | Forge app storage until deleted or uninstall |
| Run history: time, result, file name, number of work items, failure reason (last 20 per schedule) | So managers can see what ran | Forge app storage with the schedule |
| Your account id, display name, time zone, groups and admin permission; your site address | Dates in your time zone, "generated by", access control, links to work items | In memory; the site address is kept in Forge storage for links in scheduled files |
| A record of the license state the app last saw | To pause scheduled exports when the subscription is not active | Forge app storage |
The App does not download attachment contents, and it does not collect email addresses, IP addresses, passwords, API tokens, payment card details or analytics. It sets no cookies and loads no third-party scripts or fonts.
3. Where data is stored
All App data is stored by Atlassian in Forge app storage for your Jira site, subject to Atlassian's data residency settings. Files you download are stored wherever you save them. Files the App attaches are Jira attachments, stored and protected by Jira. Atlassian is the hosting provider and acts as a subprocessor under Atlassian's terms. Great Work LLC uses no other subprocessors.
4. Who can see what
- Exports read Jira as the person exporting, so Jira permissions, issue security and field visibility apply.
- Scheduled exports read Jira as the app, then keep only the work items the schedule owner may browse (checked with Jira on every run). The attached file can be opened by everyone who can see the target work item; schedule owners choose that work item.
- Templates can be used by everyone with access to the App; template managers (Jira admins and the groups an admin chooses) can upload, change and delete them.
- Great Work LLC: no access. If you open a support request, we see only what you send us.
- Atlassian: as the platform operator, under Atlassian's privacy policy.
5. Retention and deletion
Template managers can delete templates and schedules at any time; deleting a schedule deletes its run history. Temporary chunks of a scheduled export are deleted when the run finishes. A run that stops responding is cancelled within an hour and its chunks deleted. Uninstalling the App removes its Forge storage according to Atlassian's Forge data deletion process. Files you downloaded and files attached to Jira are under your organization's control.
6. Support requests
If you contact support through our help desk or by email, we process what you send (name, email, message, attachments) only to answer you, keep it up to 24 months, and delete it sooner on request. Please do not send exported documents unless you need to.
7. Your rights
Depending on where you live (for example EU/UK GDPR or US state privacy laws), you may have the right to access, correct, delete or port personal data and to object to processing. For data in your Jira site, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf. For support data, Great Work LLC is the controller: email hello@greatwork.company. We respond within 30 days.
8. Security
The App uses only Atlassian-hosted compute and storage, reads Jira as the signed-in person for exports, checks the schedule owner's permission for every scheduled run, limits templates, schedules and settings to admins and chosen groups, and keeps no secrets of its own. Report vulnerabilities to hello@greatwork.company.
9. Children
The App is a business tool and is not directed to children under 16.
10. Changes
We will post changes here and update the effective date. Material changes will also be announced in the App's Marketplace release notes.
11. Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company