HaulcopyPrivacy · 17 October 2026
Privacy policy
Haulcopy is published by:
Emanuel José Vargas Luís (sole trader, empresário em nome individual)
Avenida do Atlântico 16, 14º, Escritório 8
1990-019 Lisboa, Portugal
VAT ID / NIF: PT233800263
Email: support@haulcopy.com
(privacy@haulcopy.com for privacy requests;
security@haulcopy.com for security).
The Marketplace name is Haulcopy: Scheduled Excel, CSV & PDF Export for Jira.
“We” means that sole trader. “The app” means Haulcopy on a customer’s Jira Cloud site. Atlassian provides Jira and Forge. We are not Atlassian.
This website
haulcopy.com, including /docs, /privacy, /terms, and /support, is a static site. No ad trackers. Privacy-friendly, cookie-free page stats only. There is no account and no form. If you email privacy@haulcopy.com, support@haulcopy.com, or security@haulcopy.com, we receive what you send and use it to answer you.
What the app does
A Jira user chooses a JQL search, fields, and formats (Excel, CSV, PDF). The app reads those issues and writes the file inside the same Atlassian site. A user can save that setup as a preset or a schedule. A schedule later runs the search as the user who created it.
What is stored, and where
The app stores data only in Forge storage on the customer’s Atlassian site. There is no vendor server and no analytics endpoint.
| Data | Where | How long |
|---|---|---|
| Export files (the field values the user selected) | Forge Object Store | 7 days, then the object expires |
| Job records: JQL, field ids, format, status, size, timestamps, the runner’s Atlassian account id | Forge Key-Value Store | Until uninstall removes the installation’s Forge storage |
| Presets and schedules: name, JQL, fields, formats, cadence, timezone, owner account id | Forge Key-Value Store | Until a user deletes them, or until uninstall |
| PDF title and PNG logo | Forge storage | Until a user replaces or clears them, or until uninstall |
Issue field values are written into the export file. They are not copied to us. Forge follows the data-residency location the customer’s admin has pinned for Jira. The app does not pick a region of its own.
What we do not do
- We do not sell personal data.
- We do not use personal data for advertising.
- We do not ask for an Atlassian password or a personal access token.
- We do not send issue data, account ids, or files to a third party.
- We do not log issue summaries, descriptions, comments, or file contents.
The app writes operational log lines on Atlassian’s Forge logging service: a phase name, a job id, counts, timings, and, when an export fails, a shortened error string from Jira of at most 300 characters. That error can mention a field or a search. It stays in Atlassian logs. We do not ship those logs elsewhere.
Who decides
For the issue content and account identifiers inside a customer’s Jira site, the customer decides why that data is processed. We process it to produce the export the customer’s users asked for, on Atlassian’s platform. Our working view is that the customer is the controller of that content and we are the processor. We would be controller of our own invoices and of support email. A data processing addendum is not published yet. It will be linked here if counsel confirms it is required before we take payment.
Retention after uninstall
Export files expire after seven days while the app is installed. The app has nowhere outside Atlassian to keep a copy. Forge installation storage is the only store.
Requests
A user who wants access, correction, or deletion of issue data should use Jira, which holds it. Deleting a preset or schedule in the app removes that record. Export files expire after seven days. A request about this policy can go to privacy@haulcopy.com. We may have to refer it to the customer who controls the Jira site.