Security
Vulnerability disclosure policy
We want to hear about security problems in Holarch. This policy says how to report one, what you may test, what we do with your report and how we protect you when you research in good faith.
How to report
Email [email protected]. Include:
- the address or feature affected;
- the steps to reproduce the problem, with any requests, scripts or screenshots that show it;
- what an attacker could do with it;
- how to reach you for questions, and the name you want us to use.
Write in English. Do not include other people’s personal data or project content in the report; if you came across some, say so and delete your copy. The contact is also listed in security.txt.
Scope
In scope:
- holarch.app, the website;
- app.holarch.app, the hosted Holarch service, including its API and MCP endpoints.
Out of scope:
- any other Holarch address, including test and staging services;
- denial of service, load or stress testing, and anything that degrades the service for others;
- social engineering or phishing of Holarch staff, customers or users, and physical attacks;
- accounts, projects and data that are not yours: create your own accounts to test, and stop as soon as you reach data that belongs to someone else;
- the services of our providers, such as Cloudflare, DigitalOcean, Paddle, Google, Microsoft and Anthropic: report problems in them to the provider;
- spam, and high-volume automated scanning.
Reports that usually need more to be accepted: a missing header or cookie flag without a way to exploit it, clickjacking on a page with no action to trigger, email settings of domains that send no mail, software version disclosure, and rate limits that are only slower than you would like.
Rules for testing
- Use only accounts you own or have permission to use, and keep test data in your own projects.
- Do the least needed to show the problem. Do not download, change or delete data that is not yours, and do not keep access longer than needed.
- Do not use a problem to reach other systems, and do not leave anything running, such as a backdoor.
- Keep the details confidential until we have fixed the problem, or until 90 days after your report, whichever comes first. If a fix needs longer, we tell you why and agree a date with you.
Safe harbor
If you research and report in good faith and follow this policy, we consider your research authorized: this policy is the written permission for security testing that the Terms of Use ask for. We will not take legal action against you or report you to law enforcement for it, and if someone else does, we will say that you acted under this policy. If you are unsure whether something is allowed, ask us first at the address above.
This does not cover research that breaks the law, harms others, or goes outside the scope and rules above, and it cannot give permission on behalf of anyone else, such as our providers.
What we do with your report
| Step | Target |
|---|---|
| First reply, confirming we received it | Within 1 business day |
| Our assessment: whether we can reproduce it and how serious it is | Within 5 business days |
| Progress updates until it is fixed | At least every 10 business days |
| Fix of a serious problem | As soon as possible, normally within 30 days |
Business days are Monday to Friday, US Central time, except US public holidays, as for support. These are targets, not guarantees. When the fix is live, we tell you, and the changelog notes the fix without the details that would let someone repeat the attack. If the problem exposed users’ data, we notify the affected users as described on the Security page.
No bounty
Holarch does not run a bug bounty and does not pay for reports. Reporting under this policy is voluntary, and a report is not a request for payment.