What we store, and why

This site has no passwords and asks for no email address. You can use it without signing in; signing in with GitHub is optional and exists so anything you save can follow you to another browser. This page describes everything actually kept, which is not much.

The cookies

The first time something needs to be saved for you we set one cookie, app_uid, containing a randomly generated identifier. It is HttpOnly, SameSite=Lax, marked Secure in production, and expires after one year.

Until you sign in, that identifier is the only thing connecting you to what you have saved. It is not linked to your identity, and we do not use it to track you across other sites. There are no analytics, advertising, or third-party cookies, and no third-party scripts are loaded. Fonts are served from our own domain rather than fetched from Google at page load.

Signing in sets a second cookie, app_session, protected the same way. It holds your GitHub account number, the date it stops working, and a signature made with a key only this server has. It is not a GitHub token and is useless anywhere but here. It lasts thirty days, and signing out deletes it. A third cookie exists for ten minutes during sign-in and holds a random number used to check that you came back from GitHub and not from somewhere else.

Signing in with GitHub

If you sign in, GitHub tells us your account’s numeric id and nothing else. We ask for no permissions, so we never see your email address, your repositories, or anything private. We store that number as the owner of your data, in the form gh:1234567. The access token GitHub issues is used once, to read the number, and then thrown away — we do not store it and cannot act on your account with it.

GitHub learns that you signed in here; what you do afterwards is not reported back to them.

Where it is stored

The site is hosted by Vercel, and data is stored in a Postgres database Vercel provisions from a third-party vendor through its marketplace. Both run on servers in Frankfurt, Germany, inside the EU. We do not sell your data, and we do not share it with anyone except those providers, which process it only to run the site.

Deleting your data

There is no button for this, which we would rather be honest about than paper over. If you have not signed in, clearing your browser cookies makes anything saved permanently unreachable to you, but it does not erase it from the database — it only discards the identifier that pointed at it. If you have signed in, clearing cookies loses nothing: signing in again finds it.

To have it actually deleted, write to whoever runs this site and include nothing more than the request; we will need your GitHub account number, or the app_uid value from your browser, to find it.

Children

The site is not directed at children and is intended for people aged 16 or older.

Changes

If this policy changes we will update the date at the top of this page. Questions go to whoever runs this site.