Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

This document describes our security policy. We cannot guarantee that no leak will ever happen, but we do our best to keep your data safe.

Your data

Please see our Privacy Policy concerning how we manage your data.

How we keep our communications secure

We make our best to use state-of-the-art techniques to keep the data safe:

  • We use SSH keys to access our servers,
  • We use HTTPS and SSL certificates to communicate between us and with you.
  • We don't transfer data in clear-text over the network, except in situations where we display a warning such as support requests through emails.

How we keep the data secure

Once again, we make our best to use state-of-the-art techniques to keep the data safe:

  • Our main servers are hosted by Digital Ocean, which has extremely good security procedures:
  • The hard drives of our personal computers are encrypted (for example with Apple's FileVault 2),
  • Our personal backup drives are encrypted (for example with Apple's FileVault 2 / Time Machine).

Where we host your data

Please see the Privacy Policy on where we store data.

How we develop secure software

  • We ensure that our plugins check Confluence and Jira permissions before exposing data to users,
  • We use peer-reviews to detect errors and security issues before releases,
  • We use Git to manage changes, so that any code that goes to production is easily auditable.

How we ensure continued security

Whenever we are aware of a leak affecting the software we use (for example Heartbleed or Shellshock), we halt the service in emergency and upgrade our systems.

If you notice a vulnerability, please contact us at Should you notice a vulnerability that affects security, please request us to use GPG (documentation from DO or Linode).

  • No labels