We read everything that arrives. We answer everything that is answerable.
General enquiries, corrections, and disagreements
Good things to send us:
- A fact or number that looks wrong. Send the article link, what you think is wrong, and your source. This is the most useful mail we get. If you are right, we correct the article and say so.
- A factual error. Send the article link and the specific sentence.
- A topic you want explained. Tell us the question you want answered. “Which of these two plans is cheaper for X” is a better request than “please review Y”.
- A question about something we published. If a Test Setup section is not reproducible, that is a defect in our writing and we want to know.
We usually reply within a few days. One person reads this mailbox, so a slow reply means it is a busy week, not that the mail was ignored.
Privacy, data protection, and legal requests
Use this address for:
- Requests to access, correct, delete, restrict, port, or object to the processing of your personal data
- Withdrawing consent you previously gave
- Anything else arising from our Privacy Policy
Korean law sets this in two layers, and we state both. The Personal Information Protection Act itself requires us to investigate and act on a correction, deletion or suspension request without undue delay (지체 없이) — that is Article 36(2) for correction and deletion, and Article 37(2) for suspension of processing. The Enforcement Decree then fixes the deadlines that carry a number: access must be granted within 10 days, and you must be told the outcome within 10 days. Requests made under the GDPR are answered within one month, which is a different jurisdiction and a different clock. Where a request is complex we tell you before the deadline, not after it. We may ask for enough information to confirm the request is genuinely yours — that check protects you, not us.
The person responsible for privacy matters is named in section 11 of the Privacy Policy.
If you are not satisfied with our response, section 12 of that policy lists the regulators you can complain to, in Korea and in Europe. We would rather you complained to us first, but you are not obliged to.
What we do not respond to
We will not reply to these, and there is no point sending them:
- Guest post offers. We do not publish guest posts or outside submissions.
- Link insertion and “we noticed a broken link” outreach. We do not sell, swap, or insert links.
- Paid reviews and sponsored placements. Nobody has paid for an article here and nobody is going to. See About.
- SEO, design or traffic services. Thank you, no.
- Bulk press releases.
Sending these repeatedly will get the address filtered rather than answered.
If you represent a tool we wrote about
You are welcome, and you get the same treatment as everyone else.
- If we got something wrong, tell us what and why. We will check it against the sources and correct the article if we were wrong. Corrections are dated and visible, not silent.
- If your product has changed since we wrote about it, tell us what changed and we will update the article or mark its date more clearly. Software moves, and we would rather say when something was true than pretend it still is.
- We do not remove accurate criticism, and we do not offer favourable coverage in exchange for anything — access, licences, or otherwise. If we ever accept a product or any other consideration, it will be disclosed at the top of that article, before the content.
What we cannot help with
We cannot debug your specific setup, act as unpaid support for a vendor’s product, or advise on your architecture. We explain what changed and what it costs; turning that into your decision is your job, and we would be guessing.
If a tutorial here does not work for you, that is worth telling us — but tell us as a report (“step 4 fails with this error on this version”), not as a support ticket. Reports improve the article for everyone.