Privacy Policy — Field & Screen Rules, Behaviors & Templates
Privacy Policy — Field & Screen Rules, Behaviors & Templates
Draft for Marketplace publication. Final legal review is recommended before publication. Technical claims marked by product behavior must remain aligned with the current security review and Atlassian Forge documentation.
1. Overview
This Privacy Policy explains how Field & Screen Rules, Behaviors & Templates (the App), provided by iDev Solutions, handles data when used with Atlassian Jira and Jira Service Management.
The App is built on Atlassian Forge and uses Atlassian-hosted Forge services for applicable application processing and storage.
2. Data processed by the App
Depending on the features used, the App may process configuration and contextual data necessary to create, validate, publish and execute Behaviors, including information such as:
project identifiers;
issue type or work type identifiers;
request type identifiers where applicable;
Jira screen or view context;
field identifiers and field metadata;
rule, condition, branch and action configuration;
tab configuration;
publication state and version information;
supported user, group or role identifiers where these are part of configured conditions, rule initiators, publication records or administrative audit records;
technical lifecycle and operational metadata required for application functionality.
The App is not intended to store the full contents of Jira issues as a separate external copy merely for execution of Behaviors.
3. Personal data and user references
Some App configurations and administrative records may reference Atlassian account identifiers, groups, roles or other user-related identifiers where these are necessary for identity-aware rules, administrative attribution, publication accountability, audit or security purposes.
The App may persist Atlassian accountId values as stable user references in Atlassian Forge-hosted storage. Depending on the purpose, these identifiers may be retained for longer than 24 hours, including for the life of an active Behavior or for bounded publication, audit or security-retention periods.
This persistence does not mean that the App creates a separate copy of the user's Atlassian profile. Display names and email addresses associated with these references are not intentionally persisted with the stored accountId values for normal App operation. Where user-facing identification is needed in the Builder, profile information may be retrieved from Atlassian on demand under the current user's applicable permissions.
The App should process only the personal data necessary for the requested feature and applicable support or administrative purpose.
Customers are responsible for ensuring that their use of identity-aware configuration complies with applicable privacy law and internal policies.
4. Storage location
Applicable App configuration and persistence use Atlassian Forge-hosted storage, including Forge SQL and other Forge-hosted storage services where applicable.
For normal App operation, iDev Solutions does not currently maintain an independent external customer datastore that copies these persisted Jira user references or Behavior configuration outside Atlassian Forge-hosted storage.
The App does not currently provide an independent external customer backup or restore service.
Any statement about absence of external storage or egress must remain consistent with the current App architecture and security review.
5. Data residency
Forge-hosted data residency follows Atlassian's applicable Forge and Atlassian Cloud data residency capabilities and policies.
The App does not independently promise a specific geographic storage location beyond the options and guarantees provided by Atlassian for the relevant Forge services.
6. Data retention while installed
While the App remains installed, application data required for active configuration, publication, operation, audit or administration may be retained for as long as necessary to provide the applicable App capability or satisfy a documented operational requirement.
This can include Atlassian accountId references used as rule operands or administrative attribution. Some such references are retained for longer than 24 hours. For example, a user reference that forms part of an active Behavior may remain for the life of that Behavior, while audit, publication and security records follow bounded retention schedules defined by the App's operational and security policies.
The App applies data-minimization controls so that user references are retained without unnecessarily persisting copied profile data such as display names or email addresses.
Edition-specific audit or governance features may apply different documented retention periods for their own records.
7. What happens after uninstall
After the App is uninstalled, Forge-hosted App data follows Atlassian's hosted storage lifecycle.
At the time of publication of this draft, Atlassian documents that hosted storage data is retained for 28 days after uninstall before deletion according to the Forge storage lifecycle.
Reinstalling the App does not automatically reconnect or restore data from a previous installation.
In limited circumstances, Atlassian may provide a recovery process during its documented recovery window. Any recovery request is subject to Atlassian's then-current process and may require customer consent.
The App does not independently maintain a separate backup copy outside this process.
8. Deletion and personal-data references
Customers may remove App configuration through the functionality made available in the product where supported, or uninstall the App to terminate normal application access.
Deleting a Behavior removes the active configuration and associated App records according to the product's deletion and retention rules. Some bounded audit records may retain a stable technical user reference for accountability until the applicable retention period expires.
Deletion of Forge-hosted data following uninstall is ultimately governed by Atlassian's hosted storage lifecycle.
Requests relating to personal data should be handled according to applicable law, Atlassian platform capabilities and the App's technical ability to identify and remove the relevant data.
9. Logs and operational data
The App may generate technical logs and operational metadata necessary for troubleshooting, security, reliability and support.
The App is designed to avoid including unnecessary account identifiers, customer-authored content or copied profile data in operational telemetry.
Customers should avoid intentionally entering unnecessary sensitive information into configuration names, descriptions or support materials.
Atlassian infrastructure logs may have separate retention behavior governed by Atlassian rather than by iDev Solutions.
10. Support data
When customers voluntarily provide screenshots, logs, exported configuration, issue examples or other materials to iDev Solutions for support, those materials are processed separately from normal Forge runtime storage.
Support data should be limited to what is necessary to investigate the request and handled according to iDev Solutions' applicable privacy and support practices.
Customers should remove or redact unnecessary sensitive information before submitting support materials whenever practical.
11. Third-party access and disclosure
The App relies on Atlassian services necessary to operate Forge, Jira and Jira Service Management.
The App does not sell customer personal data.
Any additional third-party processing introduced in the future must be reflected in this Privacy Policy and applicable Marketplace disclosures before or when that processing becomes part of the product.
12. Security
The App is designed to use Atlassian Forge security and hosting controls together with application-level authorization, validation and least-privilege principles appropriate to its functionality.
No security statement in this policy should be interpreted as a guarantee that UI behavior such as field hiding, read-only state or requiredness constitutes a confidentiality or access-control mechanism.
For sensitive information, customers must use appropriate Jira or Atlassian security controls designed for that purpose.
13. Customer responsibilities
Customers are responsible for:
configuring Jira permissions and access controls appropriately;
deciding what data is referenced by Behaviors and templates;
ensuring lawful use of personal data in configured rules;
avoiding unnecessary sensitive information in configuration metadata;
protecting sensitive Jira data through proper Jira security controls.
14. Children and prohibited sensitive use
The App is intended for organizational use with Jira and Jira Service Management and is not designed as a service directed to children.
Customers should not use App configuration fields as a repository for sensitive personal data that is not necessary for the App's intended functionality.
15. Changes to this Privacy Policy
This Privacy Policy may be updated to reflect changes to App functionality, editions, Atlassian Forge services, data handling practices or legal requirements.
Material changes will be published through the appropriate product or Marketplace documentation channels.
16. Contact
Privacy and data handling questions should be directed to the iDev Solutions privacy or support contact published in the Marketplace listing or corporate privacy documentation.
17. Related documents
Terms of Use
Support and Maintenance Policy
Marketplace Privacy & Security information
Product documentation