We read everything sent to us. Corrections and factual challenges are the most useful messages we receive.
Last updated: September 21, 2026
Where to write
| What it is about | Address | What to include |
|---|---|---|
| Corrections and factual errors | editor@ecomtoolshed.com | The article URL, the claim you believe is wrong, and the source you are relying on |
| General enquiries and feedback | contact@ecomtoolshed.com | Anything that does not fit the other rows |
| Privacy requests and data rights | privacy@ecomtoolshed.com | See the section below for what we need to verify your request |
| Copyright and DMCA notices | dmca@ecomtoolshed.com | See our Editorial Policy for the required elements of a notice |
| Affiliate and disclosure questions | contact@ecomtoolshed.com | Which page and which link you are asking about |
We aim to acknowledge messages within a few business days and to resolve substantive matters promptly. Please write in English.
Corrections: how to make one land
A correction request is acted on fastest when it contains three things:
- The exact claim. Quote the sentence or table cell, and give the article URL.
- Why it is wrong. A stated reason, not just a disagreement.
- A primary source. The vendor’s current pricing page, plan comparison table, help-centre article, or published documentation. A competing blog post is not a primary source, though it may point us to one.
Pricing and plan limits change constantly, so a screenshot or the URL and date you checked it is especially useful. We verify against primary sources before changing published figures. If you are right, we correct the article and note what changed under the correction policy in our Editorial Policy.
Privacy and data rights requests
You can ask us to access, correct, or delete personal information we hold about you. Email privacy@ecomtoolshed.com with the words “Privacy request” in the subject line and tell us:
- what you are asking for (access, correction, deletion, or another right);
- the email address or other identifier you used when you contacted us;
- the state or country you reside in, where a specific law applies to your request.
We will verify the request by confirming you control the email address associated with the data, and we will respond within the deadlines set out in our Privacy Policy — one month under the GDPR, 45 days under the CCPA and CPRA, extendable as those laws allow.
You do not need an account to make a request, because we do not have accounts.
What we cannot help with
We are not the vendor, and we are not a reseller or a support channel for any tool we cover. We cannot:
- cancel, pause, or refund a subscription;
- recover access to your account with a vendor;
- fix a billing error or reverse a charge;
- change a plan, raise a limit, or apply a discount;
- escalate a support ticket or a deliverability problem;
- confirm whether your setup is compliant with any law or standard;
- perform a migration, or advise on your specific data.
For all of those, contact the vendor directly. They are the only party who can act on your account, and writing to us only adds a delay to your problem.
We will never ask you for your login credentials, API keys, or access to your account with any vendor. If a message claiming to be from us asks for them, it is not from us — do not reply to it. See section 2.1 of our Privacy Policy.
What we cannot do with a link request
We do not sell links, we do not accept guest posts, and we do not add commercial links to articles in exchange for payment. Messages offering either are discarded without a reply.
How we handle your message
Messages are read by the site operator and kept only as long as needed for the purpose you sent them — see section 9 of our Privacy Policy for retention. We do not add you to a mailing list because you wrote to us, and we do not pass your message to third parties except as described in that policy.