Responsible Disclosure
Last updated: October 31, 2026
We welcome reports from people who find security problems in OwlXBrowser. If you think you found one, please tell us privately first so we can fix it before anyone can misuse it.
How to report
Use the contact form with the topic "Security issue". Please include:
- what you found and what it affects (the website, the dashboard, billing and payments, the API, the desktop app or its updates);
- the steps to reproduce it, and the app version or page address;
- how we can reach you if we have questions.
Leave out other people's data. If you saw any by accident, tell us, don't keep a copy and don't share it.
What we promise
- We confirm that we received your report within 3 working days.
- We keep you informed while we look into it, and tell you when it is fixed.
- We don't take legal action against research done in good faith under the rules below.
- With your permission, we thank you by name when the fix is out.
We don't pay rewards at the moment.
In scope
- owlxbrowser.com and api.owlxbrowser.com
- The desktop app on Windows, Linux and macOS (beta), including its update feed and engine downloads
- Fingerprint leaks: a profile showing the real computer's address, location or hardware where the app says it hides them
Please don't
- touch accounts, profiles or data that aren't yours (use test accounts you create yourself);
- run denial-of-service tests, flood the forms or send spam;
- use social engineering, phishing or physical attacks against us or our users;
- run automated scanners that send large numbers of requests;
- share the problem publicly before we have fixed it, or for 90 days after your report, whichever comes first.
Out of scope: reports that only list missing security headers without showing a problem, clickjacking on pages without actions, rate limits on non-sensitive pages, outdated-version banners without a working issue, and problems in websites or services we don't run.
Our machine-readable contact details are in security.txt.