Effective date: 2026-08-25 · Last updated: 2026-11-12
Muhana (business ID 2642201-7, Vahverokuja 9, 70910 Vuorela, Finland) — “we”, “us” — publishes the Atlassian Marketplace app Talteen - Restore Deleted Issues & Attachments for Jira (“the app”).
This policy explains what the app does with data, and what we do with a support request you send us (section 12). It does not cover Atlassian’s own handling of your Jira site, which is governed by the Atlassian Privacy Policy.
The app is installed by a Jira site administrator onto that organisation’s own Jira site. The organisation is the data controller for the Jira content the app handles. We act as a data processor on the organisation’s behalf, and only to provide the app’s function: keeping restorable copies of deleted Jira issues.
That processing is governed by our Data Processing Addendum, which is the contract required by Article 28 GDPR. It sets out what we process, the technical and organisational measures, our sub-processors, and how long the data is kept.
The app has no server. It runs entirely on Atlassian’s Forge platform, using Forge-hosted compute and storage inside your own Atlassian environment.
The app meets the technical eligibility criteria for Atlassian’s Runs on Atlassian programme. Data is encrypted at rest by the Atlassian platform.
We cannot read your data. We have no access path to a customer’s Forge storage.
All of the following is stored per-installation in Forge storage:
| Data | When | Contents |
|---|---|---|
| Issue snapshots | On issue create/update (debounced) | Restore-relevant fields only: summary, description, project/type/status ids, priority, labels, assignee and reporter account ids, parent, due date, created date, non-empty custom fields. Compressed. |
| Comment mirror | On comment create/edit | Comment id, author account id and display name, created timestamp, body. Compressed. |
| Trash records | On issue deletion | The snapshot, plus deleted-by account id and deleted-at timestamp. |
| Attachment mirrors | On upload, while attachment capture is enabled. Capture is ON from installation. | Filename, size, uploader account id, created date, media id, and the file bytes in chunks. Files over the per-file cap or past the monthly budget: metadata only, no bytes. |
| Attachment usage counter | As files are mirrored | Per-month aggregate only: bytes stored, files mirrored, files skipped. No file content. |
| Audit log | On restore/purge | Timestamp, acting administrator’s account id, action, old and new issue keys. |
| Settings | On save | Retention days, restorer role, excluded projects, notification toggle, attachment capture settings. |
| Feedback bookkeeping | On first app open | A random install ID generated locally, when the app was first opened, and whether the feedback card was dismissed. No account ids, no issue data. |
Attachment capture is on from the moment you install the app. The app copies each attachment as a user uploads it, so that a file deleted later can be put back. The volume is bounded by a per-file size cap (default 10 MB) and by a monthly write budget (default 250 MB). A site administrator can switch capture off in Settings, or exclude individual projects from it.
The app stores Atlassian account ids — the platform’s pseudonymous identifier — for the user who deleted an issue, for comment authors, and for administrators who restore or purge. It also stores comment-author display names as they appeared at capture time.
Personal data inside captured issue content (descriptions, comments, attachments) is retained only for the retention window, and only so the issue can be restored.
Legal basis: we process this as a processor on the controller’s documented instructions, which are given by the administrator’s act of installing and configuring the app.
The app shows two links to a feedback form — one in Settings, one on a dismissible card in the Trash view. Both are optional.
The app never transmits anything. It builds a link and hands it to your browser. Your browser prompts you before opening it. If you do not click, nothing leaves.
If you do click, the link carries up to four values, all visible to you on the form:
| Value | What it is |
|---|---|
| Install ID | A random identifier generated by this installation. Not derived from your site name, cloud ID, or any account. Carries no site-identifying information on its own. |
| Days since first opened | How long ago the app was first opened here. |
| Attachment capture on | Whether attachment capture is enabled — 1 or 0. |
| Which link | Whether you clicked from Settings or from the card. |
If the app cannot read its own local storage when you click, the install ID and the days-since-first-opened are omitted rather than guessed at.
Nothing else travels. No site name or URL, no account ids, no display names, no project or issue keys, no issue content, no file names.
The form is hosted by Tally BV (Sint-Pietersnieuwstraat 11, 9000 Gent, Belgium), which stores form data on servers within the European Union. Tally’s own handling is governed by the Tally privacy notice.
Treat the form as you would any external form: do not paste customer data into it. Anything you type there is your own choice, and we use it only to act on your feedback.
The app has one sub-processor. It is the one that Annex III of our Data Processing Addendum lists.
| Sub-processor | Purpose | Location |
|---|---|---|
| Atlassian | Hosts all app compute and storage (Forge) | Per your Atlassian site’s data residency |
Atlassian hosts the app inside your own Atlassian environment. No other party receives data from the app.
Tally BV is not a sub-processor. It hosts only the optional feedback form (section 6). The form receives nothing unless a person at your organisation opens it and submits it. We are the controller of what a person submits there, not a processor for you (DPA clause 1.3).
Support email is covered in section 12. A support request is not data from the app. Section 12 tells how we handle it, and names Proton AG, which hosts the support inbox.
On uninstall, all Forge storage for the installation is deleted by the Atlassian platform under Forge data lifecycle policy. Nothing survives on our side, because there is no our side.
Note the flip side: uninstalling destroys the safety net and everything in the trash.
ADMINISTER), verified server-side on every call.For data the app holds in your Jira site, data subject requests should go to the controller — the organisation whose Jira site holds the data — not to us. That organisation’s administrator can satisfy a right-to-erasure request by purging the relevant trash items in the app, by shortening retention, or by uninstalling. For a support request you sent us, we are the controller; see section 12.
If you are a customer administrator and need our help with a request, contact us at the address in section 13. Where we act as processor we will assist the controller as required by Article 28 GDPR.
We will update this page if the app’s data handling changes, and change the “last updated” date. Material changes will be notified to customer administrators and to Atlassian, as required by the Atlassian Marketplace Partner Agreement.
This section covers a support request you send us. It does not concern data the app holds in your Jira site.
What we receive: your email address and the headers your email carries, your name if you give it, and what you write or attach — typically your Jira site URL, an issue key, a description of the problem and a screenshot of an error. For this data we are the data controller.
Why: to answer your request and fix the problem. The legal basis is our legitimate interest in supporting the users of the app (GDPR Article 6(1)(f)).
Where it is kept: support email arrives in an inbox hosted by Proton AG (Geneva, Switzerland). Switzerland has an adequacy decision from the European Commission.
How long: while the request is open, and afterwards for as long as we need it to handle follow-up questions about the same problem. Then we delete it.
Your rights: you can ask us for a copy of this data, to correct it or to delete it, and you can object to its use, by writing to the address in section 13. You can also complain to the Finnish Data Protection Ombudsman (tietosuoja.fi).
Do not send customer data. Issue keys and error messages are enough to start.
Email privacy@muhana.fi for any question about this policy or about data the app holds.
Muhana Vahverokuja 9, 70910 Vuorela, Finland Business ID 2642201-7