‹ Back to Shelfmark

Privacy

Last updated November 4, 2026

Shelfmark is a catalog for the books in your house. Your catalog stays in your browser and, if you turn on sync, in one file in your own Google Drive. Shelfmark has no server, no accounts, no analytics and no cookies, so there is nowhere else for it to go.

Where your catalog is kept

What Shelfmark does with your Google account

Drive sync asks Google for one permission: drive.file, “see, edit, create, and delete only the specific Google Drive files you use with this app”. With it, Shelfmark can reach only the folder and file it made itself. It can't see, open or list anything else in your Drive.

After you sign in, Shelfmark asks Drive which Google account it's saving to and keeps that account's email address in your browser, with the sign-in, so that Settings can show which account it saves to and signing back in skips Google's account chooser. It doesn't ask for your name or contacts.

Shelfmark uses this access only to read your library file, merge it with the copy on your device, and write it back. The sign-in token Google gives your browser lasts about an hour and is kept in your browser so a reload doesn't sign you out. Shelfmark has its own address, so the token and the email address are its own: the other junkdrawer.works projects can't read them, and signing in to one of them doesn't sign in Shelfmark. Neither is ever sent anywhere except to Google.

Shelfmark's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Your Drive data is used only to show you your own library. It isn't transferred to anyone, used for advertising, or read by any person.

Other services the page talks to

Removing your data

Questions

Shelfmark's code is open at github.com/markjf99702/shelfmark, so you can check all of this. Questions or problems can go to the issue tracker.