We take great care in handling any data that comes through our systems. Security is critical to every product and service we deliver and we view it as our top priority.

This page will address some details about how we work and the safeguards we use.

Handling data and secrets

  • All our services run and communicate via TLS (SSL), data is never sent as plain text.
  • Passwords and other sign in credentials are stored using one-way PBKDF2 hashes, generated with 100k iterations and salted.
  • External account credentials (API keys and tokens) that need to be accessed by our automated integration systems are stored and encrypted with AES. These credentials are read only just-in-time by automated processes and decryption keys are stored separately.
  • Human MindsUnited employees have access to HTTP, database and transaction logs to enable support. We keep passwords, tokens and secrets out of the logs, they are not visible to humans.

Our Policies

  • We always apply principles of least privilege.
  • We follow OWASP best practices.
  • All code is peer-reviewed before deployment.

Responsible Disclosure

At the MindsUnited, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

Please do the following:

  • E-mail your findings to . Encrypt your findings using our PGP key to prevent this critical information from falling into the wrong hands,
  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data,
  • Do not reveal the problem to others until it has been resolved,
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and
  • Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.

What we promise:

  • We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date,
  • If you have followed the instructions above, we will not take any legal action against you in regard to the report,
  • We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
  • We will keep you informed of the progress towards resolving the problem,
  • In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise)

We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved. Our policy is based on an original text written by Floor Terra, published with a Creative Commons Attribution 3.0 Unported license and the guideline Coordinated Vulnerability Disclosure (responsible disclosure) published by the Dutch National Cyber Security Centre (NCSC).


ID: 5532FD4E -Get PGP Key

Bug bounty

We currently do not have a formalized bug bounty program, nor do we have predefined bounties. We hope this does not discourage you from reporting any vulnerabilities you may have encountered. For substantial vulnerabilities we will always consider appropriate compensation for the use of your time.