Reporting a security problem
If you have found a security problem in the OPAX website, the OPAX app or OPAX's research tools (its MCP service), please tell us privately first, so it can be fixed before it is made public.
How to report
- On GitHub, privately: report a vulnerability. Only OPAX's maintainers can see the report. You need a GitHub account.
- By email: support@opax.com.au, with "Security" in the subject line.
Please do not open a public GitHub issue for a security problem.
Tell us what you found, where (the address or the part of the app), how to reproduce it, and what you think it allows. Leave out other people's personal information; say that you saw it, not what it was.
What to expect
- OPAX is a small independent project, so replies are not instant. We aim to acknowledge a report within 5 working days and to tell you what we plan to do.
- We will tell you when it is fixed, and credit you if you would like.
- OPAX has no bug bounty and does not pay for reports.
Testing in good faith
We will not take action against anyone who looks for problems in good faith and follows these rules:
- test only against OPAX (opax.com.au and the OPAX apps), not its providers or other sites;
- do not read, change or delete other people's accounts or data; use your own account;
- do not overload the service: no denial-of-service testing and no high-volume automated scanning;
- no social engineering of OPAX's maintainers or members, and no physical attacks;
- give us reasonable time to fix a problem before you publish it.
OPAX's code is open source, so most testing can be done on your own copy: the repository.
Not security problems
Wrong records, wrong answers and account help go to Support. Questions about your personal information go to Privacy. The terms of use cover using OPAX.