Security policy

How we keep our apps and your data safe, and what we do when something goes wrong. Effective date: 4 November 2026.

Report a vulnerability

Mail security@handig.app with the app, what you found and how to reproduce it. We acknowledge every report within 2 business days and keep you posted until it is fixed.

How the apps are built

  • Every app runs on Atlassian Forge, with no servers of our own and no Forge Remote. Handig Q&A, Handig Diagrams, Handig Approvals, Handig Markdown, Handig Numbered Headings, Handig Role Estimates and Handig Estimation Poker make no calls to outside hosts (Runs on Atlassian). Handig BDD calls only the Git host that a customer's project admin connects (api.github.com, gitlab.com or api.bitbucket.org), and receives CI test reports and push webhooks through Forge web triggers that check a key or a signature.
  • Data stays in your Atlassian site and in Atlassian's Forge hosted storage, which Atlassian encrypts at rest, within your site's data residency region. The one exception is your choice: the feature files Handig BDD writes to the Git repository your project admin connects. We store Atlassian account IDs only, never names or e-mail addresses, and we implement Atlassian's personal data reporting.
  • Each app asks for the fewest scopes it needs. User actions run with the user's own permissions; admin features check that the user is an admin before the app acts on its own.
  • The apps never ask for your Atlassian password or API tokens. Handig BDD keeps the Git access token a project admin enters in Forge's secret storage: never shown again and sent only to that Git host. A webhook secret per project is kept there too, shown only to project admins when they add the webhook by hand. Its CI upload key is kept only as a hash. The other apps hold no tokens or secrets.

How we work

  • Two-factor authentication on every account (Atlassian, GitHub, Cloudflare, e-mail), with unique passwords from a password manager.
  • The development laptop has full disk encryption, endpoint protection and automatic updates.
  • Source code lives in private repositories. Every change runs linting, type checks and tests, including tests of the license, permission and input checks, and an audit of the production dependencies. Dependabot reports vulnerable dependencies.
  • Only the owner deploys to production, after the checks pass and the change has been tried on a development site.

Fixing vulnerabilities

We follow Atlassian's Marketplace security bug fix policy: critical issues fixed within 10 days, high within 4 weeks, medium within 12 weeks and low within 25 weeks.

Incident response plan

When we learn of a security incident that may affect customer data, we follow Atlassian's incident guidelines:

  1. Investigate: find the cause, which data and which customers are affected, and since when.
  2. Tell Atlassian within 24 hours with a priority 1 ticket at ecosystem.atlassian.net: scope, data affected, containment and communication plan.
  3. Contain: switch off the affected feature, release a fix or ask Atlassian to hide the app until it is safe. We update Atlassian at least every 6 hours.
  4. Fix the cause and deploy the fix.
  5. Tell affected customers within 72 hours, with Atlassian's incident template, and the Belgian Data Protection Authority where the law requires it.
  6. Review: confirm it is resolved, record what we change so it cannot happen again, and report the outcome on the Atlassian ticket.

We review this policy every year and after every incident.