Commonplace
DRAFT, NOT YET APPROVED This page is a draft for Devin to approve. It is not in force yet. Points to settle before it is:
  • The contact address privacy@commonplace.computer must exist and be read.
  • The operator-access paragraph follows the plan (KTD13). Align it with U18's final wording.
  • The provider-key sentence describes a feature that ships after the beta's launch (the paid plan). Keep it, or hold it until that ships.
  • The PostHog lines are DRAFT wording (U19 sets the event list).
  • Whether Fly.io's edge keeps request paths in its logs is not yet verified (U1). The "private address" paragraph says so.

Privacy note

Draft of 23 October 2026

Commonplace keeps what your AI agents learn about you in one home that you own. This note says what we store, where it lives, who can read it, and how you take it with you or delete it. It is written to be read in full.

Who runs it

Commonplace is a Pilgrim Technologies product, run during the beta by Devin Halladay. Write to privacy@commonplace.computer about anything on this page.

What we store

Where it lives

Your home runs on its own small server with its own disk, at Fly.io in Ashburn, Virginia, in the United States. Nothing is shared between homes: each has its own server, disk, private network and keys, and has no address on the public internet. Your agents and your browser reach it through our front door, which passes each request to the right home and keeps none of it.

Encrypted copies of your home (backups) are kept at Tigris. The web app's pages, and this site, are served by Vercel; Vercel sees which page was asked for and from which address, and never sees your home's contents or your agents' traffic. Sign-in and the waitlist are run by Clerk; our own email is sent by Resend; product analytics go to PostHog. The subprocessor list names each of them with what they get.

Who can read your home

Your agents read what their keys allow, and the apps behind them (Claude, ChatGPT and others) handle what they read under their own privacy policies.

We can. Your home is not end-to-end encrypted: search, the start context your agents get and the sensitive-place rules all need the plain text, so the person who runs Commonplace can technically open any home. We don't, unless you ask us to, there is a security problem with your home, or the law requires it, and we tell you when we have.

When we open a console on your home or run a command in it through our own tools, a line naming the reason is written to your home before the session opens, and it shows in your feed. That is enforced by our tooling, not by cryptography: a direct console through our hosting provider, a disk snapshot, or a backup decrypted on our own computer can bypass it. We say this plainly so you can decide what to keep in your home.

Sensitive places you mark are hidden from your agents' start context and search, and each opening is logged. They are protected from your agents, not from us.

What we don't do

On your own computer

Cookies and tracking

This site sets no cookies and runs no analytics. Signing in to the web app uses Clerk's cookies, which are needed to keep you signed in. Since there is no tracking to turn off, we treat every visitor as if Do Not Track were on.

The private address

Some apps connect with a private address that carries the app's key. Treat it like a password. Requests pass through Fly.io's network on their way to your home, and we have not yet confirmed whether Fly.io keeps the address in its own logs, so you can make a new key on the Agents page at any time and the old address stops working.

Taking it with you, and deleting it

If something goes wrong

If we confirm a security incident that affects your home, we tell you within 72 hours, with what happened and what was exposed.

Age

Commonplace is for people aged 18 and over.

Changes

We'll email you before any change to this note that affects what we store or who can read it.