Vulnerability disclosure policy
This policy states how to report a security vulnerability in our service to techtropy GmbH (“we”) and what we commit to in return.
This English version is a translation. Where it differs, the prevails.
1 Scope
1.1 This policy covers the website and the service at techtropy.com and the interface at api.techtropy.com.
1.2 Every other system is excluded, including other hosts under techtropy.com, the systems of our providers and the systems of our customers. If you notice a vulnerability there, report it without testing it further.
1.3 An instance we run for a single customer is covered only with that customer's approval. Ask us first.
1.4 Missing security headers or email records and the output of automated scanners count as a vulnerability only where you show an attack.
2 Report
2.1 Send your report in English or German to security@techtropy.com.
2.2 Name the affected address, the steps to reproduce and the effect you observed.
2.3 We offer no end-to-end encrypted channel. Send no passwords, access tokens or personal data of others, and describe only where they are found.
2.4 You may report under a pseudonym.
3 Rules
3.1 Test only with accounts and organizations that are your own or that we set up for you.
3.2 Do not open, change or delete data of other organizations or users.
3.3 Attacks on availability, load tests, social engineering of our team or our customers, phishing, spam, malicious software and physical access are not permitted.
3.4 Do not set up lasting access, and do not move on from a system you reached to further systems.
3.5 A report tied to a demand is outside this policy.
4 Personal data
4.1 If you come across personal data or a customer's data, stop testing and report the finding at once. Do not store this data and do not pass it on.
4.2 Delete data you could not avoid storing as soon as we have confirmed receipt of your report, and confirm the deletion to us.
4.3 Access to personal data through a vulnerability can be a personal data breach (Article 4 (12) GDPR). We then inform the customers concerned and, for data we are the controller of, the supervisory authority where Article 33 GDPR requires it and the people concerned where Article 34 GDPR requires it.
4.4 We process your name, your email address and the content of your report in order to handle it (Article 6 (1) (f) GDPR). We pass your name on only with your consent or where a law requires it. The privacy notice has the details.
5 Our commitments
5.1 We confirm receipt of your report within 5 business days.
5.2 On request we set up a test organization for you.
5.3 We tell you our assessment, and we inform you once the vulnerability is fixed.
5.4 We aim to fix a confirmed vulnerability within 90 days of your report. If we need longer, we tell you the reason and a date.
5.5 On request we name you on this page as the reporter once the vulnerability is fixed.
5.6 We pay no reward.
6 Legal position
6.1 We regard testing that keeps to this policy as permitted by us, as far as it concerns our own systems and data.
6.2 We neither request prosecution (Strafantrag) nor file a criminal complaint (Strafanzeige), and we assert no civil claims against you for such testing. We do not treat it as a violation of our terms of service.
6.3 This commitment binds only us. It does not bind public prosecutors, authorities, our customers or other third parties, and we cannot permit access to our customers' data.
6.4 Conduct outside this policy is not covered. Ask us first if you are unsure whether a step is permitted.
7 Publication
7.1 Keep the vulnerability confidential until it is fixed, and for no longer than 90 days after your report.
7.2 After that you may report on it. Leave out personal data and our customers' data, and tell us the date in advance.