Security Policy

Catapult Labs, LLC · Last updated: Oct 14, 2026

Catapult Labs builds apps for the Atlassian Marketplace. Protecting our customers' data is a core part of how we design, build and operate our apps. This page explains how to report security issues to us, how we handle security incidents, how we manage vulnerabilities, and the main security controls we have in place.

Scope

This policy applies to all Catapult Labs apps on the Atlassian Marketplace:

  • Agile Retrospectives for Jira (Cloud and Data Center)
  • Agile Retrospectives for Confluence (Cloud and Data Center)
  • Task Boards for Confluence (Cloud)
  • Scrum Poker Estimates for Jira (Cloud)
  • Scrum Poker Estimates for Confluence (Cloud)
  • Standbot – Slack stand-up bot for Jira (Cloud)

1. Reporting a security issue

If you believe you have found a security vulnerability or a security incident affecting any Catapult Labs app, please contact us right away:

  • Email: hello@catapultlabs.com (subject: "Security")
  • Security researchers: through our bug bounty program on Bugcrowd, part of the Atlassian Marketplace Bug Bounty: https://bugcrowd.com/engagements/catapultlabs. The program covers Agile Retrospectives for Jira and for Confluence (Cloud and Data Center), Scrum Poker Estimates for Jira and for Confluence, and Standbot. The current scope and rules are published on the program page.
  • Customers: through our support portal

Please include the affected app, a description of the issue, steps to reproduce it, and any evidence (screenshots, requests, logs). Please do not access, modify or delete other users' data, and give us reasonable time to fix the issue before disclosing it publicly. We acknowledge security reports as soon as possible and keep the reporter informed of our progress.

2. How we handle security incidents

We maintain a documented Incident Response Plan that is reviewed and tested at least once a year. When a security event is reported or detected:

  1. Triage: our Head of IT, acting as Incident Manager, assesses the report and assigns a severity.
  2. Response: for high and critical incidents, a dedicated response team investigates, contains the issue, removes the cause, and restores normal service.
  3. Notification to Atlassian: security incidents involving our Marketplace apps are reported to Atlassian promptly, and no later than 24 hours after we become aware of them, following Atlassian's App Security Incident Management guidelines.
  4. Notification to customers: if an incident affects customer data, we notify affected customers without undue delay, aiming to do so within 72 hours of identifying the incident, and in line with our contractual and legal obligations.
  5. Post-incident review: we perform a root cause analysis for high and critical incidents and use the lessons learned to improve our controls.

3. How we manage vulnerabilitie

  • We receive vulnerability reports from security researchers (Atlassian Marketplace Bug Bounty), Atlassian security tooling (Atlassian Marketplace Security), customers, and our own testing.
  • Vulnerabilities are rated using the Common Vulnerability Scoring System (CVSS) and tracked until resolved.
  • We fix vulnerabilities within the timeframes of the Atlassin Marketplace Security Bug Fix Policy. For cloud apps: Critical within 10 days, High within 4 weeks, Medium within 12 weeks, and Low within 25 weeks. For Data Center apps: Critical, High and Medium within 12 weeks, and Low within 25 weeks.
  • We respond to Bug Bounty reports within the two-week triage period set by Atlassian.
  • Third-party libraries are reviewed and updated regularly, and immediately when a relevant vulnerability is published.
  • When a critical vulnerability is fixed, we notify affected customers using Atlassian's vulnerability notification guidelines.

4. Key security controls

Where your data lives

App

 

Platform

 

Where End-User Data is stored

 

Agile Retrospectives for Jira (Cloud)

Atlassian Forge, with a Forge Remote backend hosted by Catapult Labs

Heroku and Amazon Web Services, with data stored in MongoDB Atlas

Agile Retrospectives for Confluence (Cloud)

Atlassian Forge, with a Forge Remote backend hosted by Catapult Labs

Heroku and Amazon Web Services, with data stored in MongoDB Atlas

Agile Retrospectives for Jira and for Confluence (Data Center)

Installed in the customer's own Jira or Confluence Data Center

In the customer's environment

Task Boards for Confluence

Atlassian Forge

Atlassian Forge storage only. The app does not store or process End-User Data outside of Atlassian and follows your Confluence page and space permissions.

Scrum Poker Estimates for Jira

Atlassian Forge

Atlassian Forge storage only. The app does not store or process End-User Data outside of Atlassian.

Scrum Poker Estimates for Confluence

Atlassian Forge

Atlassian Forge storage only. The app does not store or process End-User Data outside of Atlassian.

Standbot – Slack stand-up bot for Jira

Hosted by Catapult Labs, with an API on Heroku that integrates with Jira and Slack

MongoDB Atlas

 

For apps with a backend hosted by Catapult Labs, our infrastructure providers maintain their own SOC 2 reports, which we review every year.

Encryption

  • Data in transit is encrypted with TLS 1.2 or higher.
  • For apps with a backend hosted by Catapult Labs, data at rest is encrypted with AES-256 using keys managed by our cloud providers.

Access control

  • Access to production systems is limited to authorized personnel based on the principle of least privilege.
  • Multi-factor authentication is required for access to our code repositories, cloud infrastructure and business systems.
  • Access is reviewed periodically and removed within 3 days when a person leaves the company.

Secure development

  • Every code change is peer reviewed before it is merged, and authors cannot approve their own changes.
  • Changes are tested by QA in a separate staging environment before release and verified again in production.
  • Customer data is not used for development or testing.

People and devices

  • All personnel accept our information security policies and complete security awareness training when they join and every year.
  • Background checks are performed before granting access, as permitted by local law.
  • Devices used to access company systems are monitored for security settings such as screen lock and operating system updates.

Monitoring and continuity

  • We monitor our apps and infrastructure for errors and availability issues.
  • For apps with a backend hosted by Catapult Labs, production data is backed up daily, and we maintain a Business Continuity and Disaster Recovery Plan.

Governance

  • Our security program is owned by our Head of IT and overseen by the company's Board of Managers.
  • Our security policies are reviewed and approved at least once a year.
  • We are preparing for a SOC 2 Type II audit.

5. Contact

For any security questions, contact us at hello@catapultlabs.com.