We read everything that comes in. Whether you have a story tip, a correction, a question about something we published or a business proposal, the fastest way to reach the team is email.
Email: contact@geekblog.net
To help your message reach the right person quickly, please put one of the subject lines below at the front of your email.
What to write about, and how to label it
| Subject line | Use it for |
|---|---|
| Correction | A factual error in an article. Include the URL, the passage, and a source if you have one. |
| Story tip | News, a document, a leak or something you think we should look into. |
| Feedback | Comments on our coverage, a topic you want covered, or a problem with the site. |
| Press | Press releases, embargoed briefings, review unit offers, interview requests. |
| Partnership | Advertising, sponsorship, guest contributions, commercial proposals. |
| Privacy | Access, correction or deletion requests under GDPR, CCPA or another privacy law. |
| Copyright notice | Copyright complaints and takedown requests. See section 9 of our Terms. |
| Security | Responsible disclosure of a vulnerability affecting this site. |
Corrections come first
Accuracy matters more to us than speed. If you spot a mistake, a broken step in a guide, an outdated price or a misattributed quote, tell us and we will check it. Substantive corrections are made on the article and noted there. Our full process is set out in the Editorial Policy.
Story tips
If you work at a company we cover and want to share something, say clearly whether you are speaking on the record, on background or not for attribution, and we will honour it. We protect the identity of sources who ask for confidentiality, but please do not send us anything that would put you at legal or professional risk, and do not use a work device or a work account to contact us.
Press and PR
Journalists, analysts and communications teams are welcome to get in touch. Please send the substance in the body of the email rather than as a password protected attachment or a link to a login walled portal. We cannot promise coverage of any pitch, and we do not publish press releases as articles. Accepting a review unit or a briefing never guarantees a positive verdict, and never guarantees a review at all.
Advertising and partnerships
We are open to advertising, sponsorship and clearly labelled commercial content. We do not sell links inside editorial articles, we do not accept payment to change or remove published coverage, and we do not run undisclosed sponsored posts. Proposals that involve any of those will not receive a reply.
Security disclosure
If you find a security issue affecting geekblog.net, report it to us privately and give us reasonable time to fix it before publishing anything. Please do not run automated scanners, denial of service tests or any activity that degrades the site for other readers, and do not access, modify or exfiltrate data that is not yours. We are grateful for good faith reports and will credit you if you want us to.
Response times
We aim to reply within two business days. Corrections, privacy requests, copyright notices and security reports are prioritised and, where the law sets a deadline, we answer within it. Volume can slow us down around major product launches, so please allow a little extra time before following up.
A few things we cannot help with
- Individual technical support. We are a publication, not a help desk, and we cannot troubleshoot your device or your account. For that, contact the manufacturer or your service provider.
- Account recovery. We have no connection to any company we write about and cannot restore, unlock or refund anything.
- Giveaways and review units. Devices we test are returned or disclosed, and we do not pass them on to readers.
Before you hit send
Please do not include passwords, payment card numbers, government identifiers or other sensitive personal data in your message. Email is not a secure channel, and we do not need that information from you. Anything you send us is handled in line with our Privacy Policy.
More about the team and how we report: About us, Editorial Policy, Terms and Conditions.