One inbox, and it is read by the people who build ClusterHack: info@clusterhack.dev. Below is what to send so the first reply is a fix rather than a question.
A few things answer themselves faster than we can reply:
Whatever you send, these four lines save a round trip:
Never send us your password. We will never ask for it.
| Topic | Send to | What helps |
|---|---|---|
| Bug or something broken | info@clusterhack.dev | The four lines above. |
| Running an event | info@clusterhack.dev | Event link, what you are trying to set up, and by when. |
| Billing and plans | info@clusterhack.dev | Account email and the date of the charge. Never card numbers. |
| MCP / API / connected apps | info@clusterhack.dev | Which client, which tool, and the error it returned. Start from the MCP docs. |
| Privacy request — access, correction, deletion, opt-out | info@clusterhack.dev | Say which right you are exercising. See the Privacy Policy. We answer within 45 days. |
| Security vulnerability | info@clusterhack.dev | Steps to reproduce. Please tell us before disclosing publicly — we will work with you and credit you if you want. |
| Abuse, harassment or stolen work | info@clusterhack.dev | Links to the content and what is wrong with it. |
| Legal notices | info@clusterhack.dev | See the Terms. |
We aim to answer within two business days, and faster when an event is live — say so in the subject line if yours is running today and we will jump it. Privacy requests get the statutory answer within 45 days, usually sooner.
We are a small team, so this is a target rather than a contractual guarantee. Paid plans do not currently carry a separate service-level agreement; if you need one, write to us.
Event organizers can see participant details in order to run their event, and they are responsible for handling them properly. If an organizer misuses your data, spams you, or does not honour the rules or prizes they published, tell us — we can revoke their access and remove the event. Include the event link and what happened.