Export My Requests for Jira Service Management

Security Policy — Export My Requests for Jira Service Management

Last updated: 10 November 2026

This policy describes how the Atlassian Marketplace app Export My Requests for Jira Service Management (the "App"), published by Jules Imbert (individual publisher, France, the "Publisher"), is built and operated securely, and how to report a security issue.

1. Hosting: Runs on Atlassian

2. Data handling

3. Access control and permissions

4. Encryption

Data read by the App stays in Atlassian's cloud and the user's browser. The export configuration is kept in Forge app storage, protected by the Atlassian platform, including encryption in transit (TLS) and at rest. The App stores no data elsewhere and keeps no credentials, passwords or API tokens.

5. Logging

When a server-side operation fails, the App writes only the operation name and the error message to the Forge logs, which are hosted by Atlassian. The App does not log request content and sends no logs to third parties.

Vulnerability disclosure

If you believe you have found a security vulnerability in Export My Requests for Jira Service Management, please report it by e-mail to contact@menuiserieestivale.fr with the subject “SECURITY”. Please include the affected feature, steps to reproduce, the potential impact and, if possible, your Atlassian site URL. Do not include passwords, API tokens or customer data in the report.

Incident response and customer notification

We follow Atlassian's guidance for Marketplace partners on preparing for and managing security incidents:

  1. Detect: Atlassian Marketplace and ecosystem notifications, customer and researcher reports, dependency audits (npm audit) and Forge platform logs.
  2. Triage (within 24 hours of acknowledgement): confirm the issue, rate its severity and identify affected versions and customers.
  3. Contain: disable the affected functionality or roll back to the last safe version with a new Forge deployment.
  4. Notify: for critical issues, notify Atlassian and affected customers without undue delay, using Atlassian's vulnerability notification process and within the deadlines of the Marketplace Security Bug Fix Policy.
  5. Fix and verify: patch, run the automated tests and dependency audit, deploy to production and verify.
  6. Review: write a short timeline and root-cause analysis and update this policy and our dependencies.

Security updates

Contact

Security contact: contact@menuiserieestivale.fr (subject “SECURITY”). General support: support page. Privacy: privacy policy.

Material changes to this policy will be published on this page with a new date.