The modern web is built, by default, to take from the people who use it. Not maliciously, most of the time — just by accumulation, one reasonable-seeming decision at a time, until the ordinary website is hauling a heavier load of surveillance and lock-in than it carries of actual content. We've all stopped noticing. The taking became the texture of the thing.
But none of it is load-bearing. The trackers, the data harvested in exchange for "free," the proprietary formats you can't leave with, the words chosen to keep the real terms out of view — none of it is required for a website to work, to be useful, to make a living. Every piece of it was added. Which means every piece of it was a choice. And a choice can be made differently.
If a thing can be done without taking from the people it's done for, then doing it with taking was never necessity. It was a decision — usually one nobody told them they were making.
That sentence is the whole of it. Everything else on this site is just that idea, applied. When we say your fonts are phoning home, or that a cookie banner is a confession, or that "unlimited" means "until you matter" — we're pointing at the same thing each time. Someone built a taking into a place it didn't need to be, and called it normal.
Two kinds of taking, one root
The guides here split into two streams, and at a glance they look like different subjects. One is about privacy — what leaves your site without permission. The other is about plain dealing — how services are sold to you with the real terms hidden. But they're not two topics. They're the same act, wearing two costumes.
The Field Guide
Taking from your visitors
Trackers, fingerprinting, fonts that phone home, banners that perform consent while the data already flowed. The extraction points outward — at the people who came to read your page.
↳ the same act
Plain Terms
Taking from you
"Unlimited" that throttles, "managed" that isn't, "free" billed in data, renewals that triple, lock-in that holds your own site hostage. The extraction points at you — the person buying the service.
↳ the same act
Outward at your visitors, inward at you — but always the same move: a cost moved somewhere the person wasn't looking, a value taken without a clear yes. Surveillance and sharp-dealing are siblings. Both work by keeping you from seeing the full price until you've already paid it.
The opposite of extraction isn't generosity. It's sovereignty — the plain state of being able to see what's happening and free to walk away.
What we build for
If extraction is the default, the alternative has to be built on purpose. It isn't complicated — it's mostly the older, plainer way things worked before everything became a funnel. These are the tenets every guide here is quietly arguing for, and every thing we build is made to honor.
Take nothing that isn't given
No surveillance baked in, no data harvested as the silent price of admission. If something is collected, it's because it was needed and offered — not extracted because the visitor didn't know to object.
The price is the price
What you're paying should be visible, named, and whole — in money, not in data or attention or a bill deferred to month six. No fine print doing the work that plain words wouldn't survive.
You hold the exit
Ownership is measured at the door. If you can't leave with everything intact — your code, your data, your domain, your work — you never owned it. Sovereignty is the freedom to walk away.
Plain over clever
The words should mean what they say. No term chosen to obscure, no number that hides its own scale, no reassurance that quietly admits the opposite. If it can't be said plainly, it's probably hiding something.
Less is the discipline
Things only ever get added — another script, another tracker, another tier. The harder, better practice is subtraction: the clean site is faster, safer, and freer precisely because there's less in it taking from the person on the other side.
Why this is worth the trouble
It would be easier to take the defaults. The extractive web is the well-paved road — the templates ship with the trackers, the hosts bundle the lock-in, the words come pre-fogged. Building the other way means doing more by hand and saying no to convenient things. So why bother?
Because on the other side of every one of those takings is a person. The visitor who came to read about your services and left a data trail sold to strangers. The owner who got quietly overcharged because a word was chosen to confuse them. Non-extraction is just refusing to treat those people as inventory. It's the old, plain idea that you can run something successful without making the people who trust you into the product.
And the quiet surprise is that it's better, not just kinder. The clean site is faster. The honest price is easier to plan around. The thing you fully own is the thing you can never be locked out of. Sovereignty and decency turn out to be the same direction as quality. The taking was never even buying you much.
Build it clean. Own it completely. The taking was always optional — and so is refusing it.
Where this leads
These aren't abstractions. They're the standard behind every guide on this site, and behind every thing built on the other one — clean static sites, hosting you actually own, privacy hardening that removes what was never load-bearing.
The guides are how you learn to see the taking for yourself. The services are for when you'd rather have it built without the taking in the first place.
The guides · two ways to see the taking, and one way to undo it
The Field Guide · taking from your visitors
01Your fonts are phoning home 02Measure traffic without surveilling people 03The cookie banner confession 04Who owns your website? 05Fast is a privacy feature 06Your site should let everyone in 07Your email is someone else's filing cabinet 08The CDN that watches everyone 09What your keyboard sends home 10Consent isn't a contract you sign oncePlain Terms · taking from you
01What "managed hosting" should include 02What "unlimited" bandwidth really means 03The real cost of "free" 04Uptime guarantees & what they don't cover 05Domain vs. hosting — not the same thing 06What "SSL included" actually covers 07The renewal price trap 08Who actually backs up your site? 09What "SEO included" actually means 10"No setup fee" — and the math that hides 11What a CDN actually doesThe Field Manual · and then, the undoing
01How to actually leave a platform 02Make your forms keyboard-accessible 03Set up privacy analytics in an afternoon 04Get your domain into your own hands