Privacy & proof
You probably got here by clicking “this ad respects your privacy” under an ad. This page is the receipt: a plain-language, complete description of what these ads do, and everything they don't.
What is measured
Impressions
When an ad is shown, a counter for that ad on that day goes up by one. The request carries no cookies and no identity.
Clicks
Clicking an ad routes through this site to the advertiser's URL, incrementing a per-ad daily counter on the way. Nothing about the clicker is recorded.
What is never collected
✗ Cookies or localStorage on the host site
✗ IP addresses (not even hashed)
✗ User agents, screen sizes, or fingerprints
✗ Browsing history or interests
✗ Anything that could identify a visitor
How ads are chosen
There is no targeting. Within a tier, the ad you see is simply the active ad that has been shown the least today, a fair round-robin across the (at most five) advertisers in that tier. The selection uses only those aggregate counters; it knows nothing about you and doesn't want to.
How the embed behaves on the host site
The widget is a few kilobytes of dependency-free JavaScript, served from this domain. It makes exactly one request to fetch an ad (and one beacon to count the impression), sets no cookies, reads no storage, and touches nothing outside its own container. If this server is down, it renders a quiet fallback and never breaks the page.
Who is behind the ads
Every advertiser is a real person or indie project whose creative I reviewed and approved by hand before it went live, and can remove just as quickly if it misbehaves. There is no programmatic exchange, no auction, and no third party between the advertiser and this page.
Data retention
The only ad data that exists is the daily counter table (ad × date × impressions × clicks) used to show advertisers how their slot is doing. There is nothing about visitors to retain or delete.
Don't take my word for it: the embed script is short and open at /embed/ad.js on this domain, and you can watch the network tab while an ad loads. Two requests, no cookies. That's the whole story.