Email Hello@dev.cooking for general enquiries, editorial corrections, privacy requests, copyright or licensing questions, and responsible security reports.
Corrections and website issues
Include the affected public URL, a clear description and a supporting reference. Public technical issues can also be reported through the Dev.Cooking GitHub issue tracker, which may require an account.
Keep sensitive information private
GitHub issues are public. Send privacy and rights requests to Hello@dev.cooking, rather than posting personal information in an issue. Never send seed phrases, private keys, passwords or other credentials. Include only information needed to explain your request; we may ask for proportionate verification when necessary.
Historical newsletter removal
If you previously saved a secure newsletter removal link, use that link directly. Do not publish its token in an issue. The privacy policy explains what a successful removal clears and what metadata may remain.
Reporting responsibly
Email Hello@dev.cooking with a concise description of a technical vulnerability. Avoid publishing an exploit against other readers or sending credentials. We do not promise a fixed response time or bounty program that is not in place.