Security

This page explains how to report a security vulnerability in one of my apps or on this website, and what happens after you report it. I develop the apps on my own, so your report reaches the person who wrote the code.

What this policy covers

Not covered, please report these to the provider instead:

How to report

Email service@aaronwst.de and start the subject with “Security”. You can write in English or German. Please include:

Please include other people’s personal data only where it is needed to understand the vulnerability.

Email is not encrypted. If the details are very sensitive, send a short message without them first, and we agree on another way to pass them on.

What happens next

Publishing your findings

Please give me time to fix the vulnerability before you publish anything about it. We agree on a date together. Unless we agree otherwise, you can publish once the fixed update is available, or 90 days after your report, whichever comes first.

Research in good faith

If you keep to these rules and report what you found to me first, I consider your research authorised, and I will neither take legal action against you nor file a criminal complaint about it. This commitment binds only me. It cannot bind public prosecutors, courts or other parties such as Apple or Google, and it does not cover research that breaks these rules.

Your data

I use your name, your email address and the content of your report only to handle the report and, if you agree, to name you in the note on the fixed vulnerability. When I report an actively exploited vulnerability to the authorities, I pass on your contact details only with your agreement. More in the privacy policy.

Rewards

There is no bug bounty: I don’t pay for reports. With your consent, I name you in the note on the fixed vulnerability.

Machine-readable contact

The same address is published in security.txt, as described in RFC 9116.

Last updated: 15 November 2026