Privacy policy

Last updated: November 18, 2026

In short

Most of what hud.place shows is already public: records on people's PDSes, the servers that host their atproto accounts, which anyone can read. hud.place keeps a little more to sign you in, keep your canvases and remember your theme. It shows no ads, sells nothing, runs no analytics or error tracking and sends no email. This page says what it keeps, who else is involved and how to remove things.

What is public by design

On atproto, your account is named by a DID, a permanent identifier, and shown by a handle such as alice.example.com. Its records live on your PDS, and public records there can be read by anyone, not only hud.place. A like, a repost, a post or a theme HUD writes for you is one of these records, in your own repository. Removing something from hud.place does not remove it from your PDS or from other services that read it.

What hud.place keeps

Cookies. Signing in on the web sets two, both HttpOnly, Secure and SameSite=Lax:

The workspace's page also keeps the theme it drew last in your browser's local storage, so it draws in it before it asks the server. The iOS app keeps its sessions in the device's Keychain.

Sessions. When you sign in, hud.place keeps your atproto OAuth session (its tokens and its DPoP key) on the server, to act for you. HUD's own tokens and web cookies are kept only as their SHA-256 hashes. An MCP client's access token lasts an hour and its refresh token 30 days, replaced each time it is used.

Canvases. Your canvases (their names, their members, and their tiles: each a tool call with its arguments, its place and width) and your tabs are kept on hud.place's disk, or, where the server has it on and your PDS offers it, in your PDS's spaces. Your chosen theme is kept on the server.

Caches. hud.place keeps public data it read in memory for a while, and audio blobs and apps' icons on disk.

Feed interactions. Signed in, when you scroll or open posts in a feed, what you saw and opened is sent to that feed's generator, through your PDS, so it can tune the feed.

Logs. The server logs what it does: each request's path, status, client name and how long it took, each MCP tool call's name, whether it failed and how long it took, the services it called on your behalf by host and path, its errors, and events of sign-in and of canvases, some of them with the DID of the account involved. It never logs tokens, cookies, request bodies, tools' arguments or results, or IP addresses. Its operators keep these logs on the server for at most 30 days.

What hud.place never does

Who else is involved

Your PDS, wherever it is, holds your records and your login. Its operator's policy covers what it keeps.

How to remove things

Your rights

Depending on where you live, laws such as the GDPR give you the right to ask what data is held about you, to have it corrected or deleted, to object to its use, and to complain to a data protection authority. Most of your data is in your own account, where you can read and delete it yourself, and what hud.place keeps you can delete as above. For anything else, ask on the issue tracker. An issue there is public, so say what you need without posting the data itself.

Children

hud.place is not for anyone under 16. If you learn that a child under 16 is using it, tell the maintainers on the issue tracker.

Changes to this policy

When this policy changes, the date at the top changes too.

Contact

hud.place is run by HUD's maintainers. Reach them on the HUD issue tracker. There is no email address. See also the terms and the community guidelines.