/
Privacy Policy

Privacy Policy

Last updated - Mar 4, 2026

1. Introduction

This Privacy Policy describes how Amoeboids Technologies Pvt Ltd (“Amoeboids”, “we”, “our”, or “us”) processes data when providing the Roadmap & Idea Portal for Jira Service Management application (the “App”).

The App is available through the Atlassian Marketplace and integrates with Jira Service Management Cloud.

The App enables organizations to create public or internal portals that allow users to:

  • View product roadmaps

  • Submit ideas and feature requests

  • Vote on roadmap items

  • Post comments and feedback

Amoeboids processes customer data solely for the purpose of providing the functionality of the App.

By using the app Roadmap & Idea Portal for JSM, you acknowledge that you have reviewed the terms of our End User Licence Agreement (EULA) and this Privacy Policy, and that you have the authority to act on behalf of any person or organization for whom you are using the Product. You agree that we may collect, use, and process your Data as described in this policy.

If you are using the Product on behalf of a company, you confirm that the company is bound by this Privacy Policy.

This Privacy Policy applies to our direct customers (“Customers”). It is the responsibility of the Customer to ensure their own end users are informed of how their data is processed via this app.

2. Roles & Responsibilities

For the purposes of applicable data protection laws:

  • The customer organization using the App is the Data Controller.

  • Amoeboids Technologies Pvt Ltd acts as the Data Processor, processing data on behalf of the customer.

3. Categories of Data Processed

The App processes only the data necessary to deliver its functionality.

3.1 Data from Atlassian Accounts

For authenticated users, the App may process:

  • Atlassian account ID

  • Display name

  • Email address

  • Avatar URL

  • User permissions within Jira/JSM

This information is provided by Atlassian when users interact with the App.

3.2 Portal Interaction Data

When users interact with the portal, the following information may be stored:

  • Votes on roadmap items

  • Comments on roadmap entries

  • Submitted ideas or feature requests

  • User identifiers associated with those interactions

3.3 Anonymous Portal Interaction Data

If the portal is configured to allow anonymous access, users may be able to:

  • View roadmap items

  • Submit ideas

  • Vote on roadmap items

  • Comment on roadmap entries

In such cases, the App may store the IP address of the user for the limited purpose of preventing duplicate votes.

3.4 Jira/JSM Issue/Work item Data

The App may process data retrieved from Jira Service Management issues when rendering roadmap entries, including:

  • Issue summaries

  • Descriptions

  • Custom fields

  • Comments

  • Status and metadata

This data remains within the customer’s Jira/JSM environment.

4. How the App Processes Data

The App uses the above information solely to provide roadmap portal functionality, including:

  • Displaying roadmap information

  • Allowing users to submit feedback and ideas

  • Recording votes and comments

  • Preventing duplicate votes

  • Rendering portal pages for users

The App does not perform profiling, automated decision-making, or AI-based analysis of users.

5. Data Storage & Hosting Architecture

5.1 Forge Storage

The App is built on Atlassian Forge.

All persistent application data is stored within Atlassian’s infrastructure using Forge storage, which resides within the Atlassian cloud environment associated with the customer’s Jira/JSM site.

5.2 Portal Rendering Infrastructure

To render the portal interface, the App uses a rendering service hosted on AWS (EU – Paris region).

When the portal page is generated:

  • Jira and Forge data may be transmitted to the rendering service

  • The service uses this data to generate the portal page

  • The service does not persistently store or log this information

The rendering service functions only as a temporary processing layer.

6. Anonymous Portal Access

Customers may configure their portal to allow anonymous access.

When enabled, anonymous users may:

  • View roadmap entries

  • Submit ideas

  • Vote on roadmap items

  • Post comments

For duplicate vote prevention, the App may temporarily store IP addresses associated with voting activity.

This data is used solely for vote validation purposes.

7. Cookies and Analytics

The portal interface may use browser cookies to maintain user session information required for the proper functioning of the portal interface.

These cookies are used for purposes such as:

  • Maintaining active user sessions

  • Ensuring secure interaction with the portal

  • Supporting normal portal functionality

These cookies are necessary for the operation of the portal and do not track users across websites.

The App itself does not use cookies for advertising or behavioral tracking.

Customers may optionally configure their portals to use Google Analytics or similar analytics tools. If enabled by the customer, those services may place analytics cookies and collect usage information in accordance with their respective privacy policies.

Amoeboids does not control or manage data collected by such third-party analytics services.

8. Data Retention

Data processed by the App is retained as follows:

  • Votes, comments, and submitted ideas are retained until the user deletes or modifies the action or until the customer removes the associated content.

  • If the App is uninstalled, data may remain in Atlassian Forge storage for up to 60 days.

  • During this period the data is not actively processed and is retained only for potential recovery if the App is reinstalled.

  • After the retention window expires, the data is permanently deleted.

9. Security Measures

Amoeboids implements reasonable administrative, technical, and organizational measures designed to protect data processed by the App.

These include:

  • Secure API communication with Atlassian services

  • Infrastructure hosted within reputable cloud providers

  • Encryption in transit using HTTPS

  • Access controls for internal systems

  • Secure handling of application credentials

Because the App primarily uses Atlassian Forge storage, the majority of application data benefits from the security controls implemented by Atlassian’s cloud infrastructure.

10. Sub-Processors and Infrastructure Providers

Amoeboids may use third-party service providers to support operation of the App, such as infrastructure and email delivery providers.

These providers process data only as necessary to provide their services and under appropriate contractual safeguards.

A current list of sub-processors is maintained separately here - Data sub-processors

11. International Data Transfers

The App may process data in infrastructure located in the European Union (Paris region) and within Atlassian Cloud infrastructure.

Where personal data is transferred internationally, appropriate safeguards are applied in accordance with applicable data protection laws.

12. Data Subject Rights

Because Amoeboids acts as a Data Processor, requests related to personal data should generally be directed to the customer organization that administers the Jira site.

Data subjects may have rights under applicable data protection laws, including the right to:

  • Access personal data

  • Correct inaccurate data

  • Request deletion of personal data

  • Restrict processing

  • Object to certain processing activities

Amoeboids will assist customers in responding to such requests where required.

13. Changes to this Policy

Amoeboids may update this Privacy Policy from time to time to reflect changes in the App, legal requirements, or operational practices.

Updated versions will be published with a revised Last Updated date.

14. Contact Information

For questions regarding this Privacy Policy or security practices, contact:

Amoeboids Technologies Pvt Ltd
303, Archway, Sopanbaug
Balewadi, Pune – 411045
India
Email: security@amoeboids.com