Where to report
Please send security concerns to support@davoniumtech.com with a concise description and the affected public URL. We review the message and direct it to the appropriate project owner.
Our public site does not promise a formal bug bounty or a fixed response deadline.
- Include the page or product and the time the issue was observed.
- Use a subject line such as “Security concern — [brief area]”.
What helps us investigate
A useful report explains the steps needed to reproduce the issue, what you observed, what you expected, and whether the result can be repeated. Screenshots can help when they do not expose private information.
We may ask follow-up questions to determine scope and impact.
- Keep test data non-sensitive and under your control.
- Do not attach passwords, one-time codes, private keys, or full payment details.
Safe boundaries
Please do not access, alter, download, or delete other people’s information; disrupt availability; run broad automated scans against unrelated systems; or publish an unverified exploit that creates risk.
We can investigate a report without receiving a copy of someone else’s private data.
- Stop testing when you encounter information that is not yours.
- Share the minimum evidence needed to explain the behaviour.
Our response and limits
We review reports in good faith, validate the issue, assess impact, and decide on a proportionate response. We may clarify scope or ask for a safer reproduction path.
We do not guarantee a reward or a specific timeline. We update the reporter when we can do so responsibly.
- We avoid making absolute claims about security.
- We coordinate public disclosure when it could reduce risk to visitors or product users.
How we handle a report
We review reports based on the detail supplied and the affected public route. We do not promise a bug bounty or a fixed response deadline.