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
- Every app I publish on the App Store or through TestFlight, as listed under Apps, in its current version.
- This website, aaronwst.de, including the enquiry form and the way I have configured its hosting.
Not covered, please report these to the provider instead:
- The App Store, TestFlight, iOS, iPadOS, macOS and watchOS: Apple Security Research.
- Firebase Hosting and Google Cloud themselves: Google Bug Hunters.
How to report
Email service@aaronwst.de and start the subject with “Security”. You can write in English or German. Please include:
- the app and its version, or the address of the page
- your device and system version
- what the vulnerability is and what an attacker could do with it
- the steps to reproduce it, or a proof of concept
- whether you know of anyone exploiting it already
- whether, and under which name, you would like to be credited
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
- I confirm that your report has arrived within five working days.
- Within 14 days of that, I tell you whether I can reproduce the vulnerability and how I plan to fix it. If I don’t consider it a vulnerability, I tell you why.
- I keep you informed until the fix is out. Security fixes come as an update in the App Store and are free of charge.
- After the update is available, I publish a short note on the fixed vulnerability with the version that fixes it and, if you agree, your name.
- If a vulnerability in one of my apps is being actively exploited, I report it through the EU’s single reporting platform to ENISA and the German Federal Office for Information Security (BSI), as the Cyber Resilience Act requires, and I inform the people using the app.
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
- Test only on your own devices, with your own copy of the app and your own data.
- Do not access, change or delete other people’s data. If you come across any, stop and tell me.
- Do not test whether the website or the enquiry form can be overloaded, and do not send automated submissions: each submission sends real emails.
- Do not try to trick me or anyone else into giving out information or access.
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