CONTACT
Contact CodeRook
Pick the address that matches what you need. Separate routes mean the urgent things are seen as urgent rather than queued behind whatever arrived first.
Everyday
Product and account help
support@coderook.com — how something works, an account you cannot get into, something behaving oddly.
Billing
billing@coderook.com — a charge you do not recognise, a failed payment, a refund, or changing a subscription.
If money has come out wrongly — a duplicate charge, a charge after you cancelled, a charge you never authorised — say so here and we aim to reply within 24 hours with how it is being put right. That is faster than everything else on this page on purpose: it is your money sitting somewhere it should not be.
Rights and safety
Privacy
privacy@coderook.com — to see what we hold about you, correct it, delete it, or make a privacy complaint. See our privacy policy for what happens then.
Copyright
copyright@coderook.com — to report material that infringes your copyright, or to challenge a removal. The procedure is on the copyright page.
Abuse
abuse@coderook.com — malware, phishing, harassment, or a project being used to attack somebody. What is and is not allowed is set out in the acceptable use policy.
Security
Reporting a vulnerability
security@coderook.com — scope, what we ask while you are testing, and what you can expect back are in the vulnerability disclosure policy.
Legal
Legal notices and formal correspondence
legal@coderook.com — notices, court orders, and correspondence from a legal representative.
CodeRook is operated by ACCA Gaming Productions, a business name registered to a sole trader in NSW 2259, Australia, under ABN 80 173 545 848. A postal address is provided on request where one is needed for a legal purpose.
What to expect
Everything sent to these addresses is read. We answer in order of what it costs you to wait, not in the order it arrived — a security problem, money that has moved wrongly, or anything touching somebody's rights goes to the front.
Where we have committed to a time, it is written down rather than implied: 24 hours for a billing error, and three days for a vulnerability report. If one of those passes without a reply, assume it went astray and send it again.