privacy
allthings.dev needs no account and shows no ads. Here is what it keeps, and why.
Visiting the site
- Cloudflare runs the site. Its Web Analytics counts page views, where visitors came from and how fast pages load. It sets no cookie. See Cloudflare's privacy policy.
- For each request the site answers, we count the page, how it answered, how long it took, the data center, and whether it looked like a bot. Never your IP address, browser, cookies or the page you came from. We keep these counts for three months.
- Cloudflare's logs keep each request's URL for 7 days, so we can fix what breaks.
- The one cookie,
theme, holds Paper or Night, and only once you choose one.
Evenings
You say you're in, and subscribe to the calendar, on Luma, which keeps your details under Luma's privacy policy. This site never copies the guest list: from Luma it reads each evening's details, who hosts it, and how many people said they're in and checked in.
Hosts and speakers we invite to help plan an evening sign in with their email, through Cloudflare Access, to see that evening's draft.
People on the site
Everyone who organized, spoke at or co-hosted an evening has a page: their name, photo, job title, a short bio, links to their profiles, the talks they gave and a few of their posts on X. All of it is public, read from their own sites and profiles, their talks, Luma, and company or conference pages, and we keep where each fact came from. An evening's page shows photos from that evening, and posts people wrote about it once an organizer approves them.
The API, the MCP server and the command
/api, /mcp and the allthings command's reads show only what the pages already show. They need no account or key, and their requests are counted and logged like any page's. To answer quickly, the site keeps each answer under the question asked, never under who asked it.
At an evening that passes the aux, allthings aux sets the room's lights or music with the code on your card, which the command saves on your machine. The hub, on the host's laptop, logs each call by the code's id, never your name, with only the choices it knows (a scene, color, zone or track), never other text you type. The host can read the whole log, which stays on that laptop.
Our accounts elsewhere
We post about evenings from our own accounts on X, Bluesky, LinkedIn and Discord. Where we use a platform's API, it is to post as allthings and to read public data: posts about our evenings, and speakers' posts and follower counts on X, which order speaker lists.
Changes and questions
Email hello@allthings.dev to change or take down anything about you, a photo included, or to ask about any of this.