Advertising & affiliate disclosure
Two revenue sources, both disclosed. Neither has ever changed what a guide recommends, and this page explains the controls that make that claim checkable.
Effective
The short version
DevToolSDK makes money from display advertising and from affiliate links. We do not sell guides, recommendations, or placement inside a technical instruction. If we ever did, this page would say so, because the alternative is lying to you.
Display advertising
We serve display ads through Google AdSense. Google sells the inventory and places the ads. We cannot see which advertisers bought space on a given page, and advertisers cannot see what we are writing or influence it.
That separation is the point. A vendor unhappy with what a guide says about their tool has no lever to pull — they are not our customer, Google is. Every ad slot on this site is labelled "Advertisement", and we deliberately keep no ads above the fold, none on the contact page, and the ad load below the level where it starts degrading page performance.
Affiliate links
Some links to the tools we cover are affiliate links. If you click one and later sign up or buy, we may receive a commission at no additional cost to you.
Specifically:
- Affiliate links carry
rel="sponsored nofollow"in the page source, so they are machine-identifiable, not just disclosed in prose. - A minority of the tools we cover have affiliate programmes at all. Most do not, and we cover them identically.
- No affiliate link ever appears inside a technical instruction. If a guide tells you to install something, that link goes to the official source, always.
- We write the guide before anyone checks whether an affiliate programme exists. The commercial question is deliberately asked last.
- Commission rates vary between vendors and are never taken into account when choosing which tool to write a guide about, or what that guide says.
What we refuse to do
This list exists so you can hold us to it. We do not:
- Publish sponsored guides, paid tutorials, or vendor-written copy under our byline
- Sell placement in a guide, or a "featured partner" slot
- Steer a reader toward a paid tier that the task does not require
- Change what a guide says because a vendor asked, complained, or threatened
- Accept payment for a link, or add an affiliate link to a tool we did not independently choose to cover
- Remove a criticism in exchange for anything
Vendors get exactly one privilege: they can tell us a command is wrong or a feature was described incorrectly, and we will check it and fix it. That is the same privilege every reader has.
How the guides are produced
Every guide follows the same seven chapters, every command is run on a clean machine before publication, and each chapter states the tool version it was verified against. The full editorial process is on our about page.
Which tools we cover is decided by what readers ask for and by what we are using ourselves. It has never been decided by which vendor has an affiliate programme.
Regulatory note
This disclosure is made in accordance with the United States Federal Trade Commission's 16 CFR Part 255 guidance on endorsements and testimonials, and with equivalent advertising standards in the EU and UK requiring commercial relationships to be disclosed clearly and conspicuously.
If you think we broke this
Tell us. Email hello@devtoolsdk.com or use thecontact form and select "Report a factual error". If you are right, we publish the correction and say what happened. A disclosure policy nobody can challenge is decoration.