jeereemiassb

Privacy policy

Last updated: 24 September 2026

1. Who we are

jeereemiassb ("we", "us") develops the apps listed on this website for Atlassian Jira Cloud and Confluence Cloud. Contact: support@jeereemiassb.atlassian.net.

2. In short

  • The apps are built on Atlassian Forge and run on Atlassian's cloud. Except Telegram Notifications, which sends messages to the Telegram chats you set up, they do not send data to any server outside Atlassian.
  • We, the developer, cannot see the content of your Jira or Confluence site.
  • We do not sell data, show ads or build profiles.

3. Data the apps process

Data stored by an app is kept in Atlassian's Forge hosted storage, linked to your site. Data read but not stored is used only while the app is running, with the permissions of the person using it.

AppStored by the appRead but not stored
Excel & CSV Table ExporterNothing.Page and blog post content, to build the file in your browser.
Attachment Checkout & LockLocks and activity log (last 50 events per page): page ID, attachment ID, file name, version number, account IDs, dates.Attachments of the page (to restore a locked version).
Bulk ActionsNothing.The selected pages, their labels and watchers.
Read & UnderstoodPage settings (required account IDs and group IDs, rule) and confirmations (account ID, page version, date).Page title and version, group members.
Activity Stream by Filter & JQLNothing (the gadget settings are stored by Jira).Issues matching the query, their history, comments and work logs.
Trash CanCopies of issues in protected projects: summary, description, comments, main fields and the reporter, assignee and comment author account IDs; for deleted issues, who deleted it and when.The issues of the protected projects.
Admin ToolkitNothing.Jira configuration (projects, fields, workflows, screens and similar).
JSON Viewer & FormatterNothing (the JSON stays in the page).The JSON of the macro, to parse it.
Inline TooltipsNothing (the tooltip text is saved in the page).Nothing.
Telegram NotificationsBot token (encrypted), saved chats (ID and name), rules and reports (projects, JQL).Issues that match a rule or report and the names of the people involved, sent to the Telegram chats you choose.
OpenAPI & Swagger ViewerNothing (the API description stays in the page).The API description in the macro or attached to the page, to show it.
Notebook ViewerNothing (the notebook stays in the page).The notebook attached to the page, to show it.
CSV Table ViewerNothing (the CSV stays in the page).The CSV in the macro or attached to the page, to show it.

Closed Atlassian accounts. The apps that store account IDs (Attachment Checkout & Lock, Read & Understood and Trash Can) report them to Atlassian once a week through Atlassian's personal data reporting API, as Atlassian requires. When Atlassian reports that an account has been closed, the app deletes that person's account ID and any copy of their name, such as an @mention in a Trash Can copy. It keeps only a one-way hash of the closed account ID, so that it does not ask about that account again.

4. Data we receive

  • Licensing. When your organisation evaluates or buys an app, Atlassian shares license information with us under the Atlassian Marketplace terms, such as the company name, license details and technical and billing contacts. We use it to manage licenses, provide support and meet legal obligations.
  • Support. When you contact us, we receive your name, email address and whatever you send us.
  • Operations. Atlassian may give us technical information about the apps, such as installation counts and error reports. Our apps do not write page, file or issue content to logs.

5. How and why we use it

We use the data above only to provide the apps and support (performance of a contract), to manage licensing and billing (contract and legal obligations), and to keep the apps secure and working (legitimate interest).

6. Who we share it with

  • Atlassian, which hosts the apps and runs the Marketplace.
  • The provider of our support tool, only for support requests.
  • Public authorities, when the law requires it.

7. How long we keep it

App data stays in your site while the app is installed, as described in each app's documentation. When an app is uninstalled, Forge marks its data as deleted: reinstalling within 21 days can recover it, and after that it is disposed of under Atlassian's data retention policy. Your site administrators control the data: for example, Trash Can copies can be deleted from the app at any time. We keep support and licensing records only as long as needed for the purposes above and for legal obligations such as tax records.

8. Your rights

Under the GDPR and similar laws you can ask us to access, correct, delete, restrict or port your personal data, and object to its processing. Write to support@jeereemiassb.atlassian.net. You can also complain to a data protection authority; in Spain, the Agencia Española de Protección de Datos (aepd.es). For data that an app stores inside your site, contact your site administrator first: your organisation controls that data.

9. Security

The apps run on Atlassian's infrastructure, request only the permissions they need, and check permissions on the server. We fix security issues within the deadlines of Atlassian's security bug fix policy. Report a vulnerability through the support page.

10. This website

This website uses no cookies, analytics or third-party resources. It is hosted on GitHub Pages, and GitHub may log visitors' IP addresses for security; see GitHub's privacy statement.

11. Changes

We will update the date above when this policy changes, and describe important changes on this page.