How to report
Email sales@shichifukutekx.ae with "Security" in the subject. Please do not open a public issue.
Tell us:
- What you found, and what someone could do with it.
- The steps to reproduce it, with the version you tested if it is self-hosted.
- How we can reach you, and whether you would like to be named when it is fixed.
Please do not send real customer data, passwords or keys. If you came across any, tell us that you did and leave them out.
What is in scope
- The open source code in the Hivelock repository.
- The hosted service and this website, within the rules below.
Problems in another company's service, such as an AI provider or a connected app, belong with that company. If Hivelock handles such a service unsafely, that is in scope. A model being misled by prompt injection is a known risk, so it is in scope only if it gets past a control we describe in the security overview.
What we ask of you
- Use your own account or your own self-hosted copy, and test only data that is yours.
- Do not read, change or delete anyone else's data. If you reach it by accident, stop there and tell us.
- Do not attack availability: no denial of service, load testing or mass automated scanning of the hosted service.
- Do not use social engineering, phishing or physical attacks against us, our customers or our suppliers.
- Give us reasonable time to fix the problem before making it public.
What you can expect from us
- We aim to reply within 5 working days.
- We will tell you what we decide, and when a fix is out.
- We will agree a date with you before anything is made public.
- We will credit you if you want that.
- If you act in good faith and follow this page, we will not take legal action against you for your research.
We do not offer payment for reports.
More
A machine-readable version of this contact is at /.well-known/security.txt. To see how Hivelock is protected, read the security overview.
Checked on 7 November 2026.