Skip to content

Privacy policy

BookPocket keeps your reading life and the people behind it. This page says what we store, who can see it, who helps us run the service, and how to delete it all.

Last updated 12 November 2026.

Who runs BookPocket?

BookPocket belongs to BookPocket LLC, a company in Washington State run by one person, R.J. LaCount. "We" on this page means BookPocket LLC. For any question about your data, email privacy@bookpocket.app.

We may change this policy as BookPocket grows. If a change affects what we do with your data, we email you before it takes effect.

What do we store about you?

  • Your account: your email address, your display name and full name if you give them, your picture if you add one, your time zone, and your preferred format. We store your password only as a one-way hash, so nobody can read it.
  • If you sign in with Google or Apple: the identifier that account gives us so we can recognise you, and the email address it shares. If Apple shares a private relay address, that is the address we have. If you sign in with Apple, we also keep a token Apple gives us, locked so only we can read it. We use it for one thing: telling Apple to remove BookPocket from your Apple account when you delete yours. We never see your Google or Apple password.
  • Your books: what is on your shelf, statuses, reading dates, ratings, reviews, private notes, pause notes, tags, and the sources you credit.
  • Your imports: the Goodreads or StoryGraph file you upload, and what we read from it. We keep the file in private storage that is not publicly readable, and delete it as soon as we have read it.
  • Where you are signed in: for each signed-in device, the IP address and browser it signed in from, so the session can be checked and ended.
  • Your phone, if you turn on notifications in the iOS or Android app: a device token Apple or Google gives us, which is how a notification finds your phone. Turning notifications off in your phone's Settings stops them.
  • Your friends: who you are friends with, and friend requests you have sent or received.
  • Your votes and comments on the roadmap, if you have Pro: which cards and comments you voted for, and what you wrote and when.
  • Reports you send: who you reported, the review or roadmap comment if you reported one, the reason you chose, anything you added, and when. We email each report to ourselves so we can act on it quickly.
  • Who you block, and when.
  • A message you send us through the contact form: your email address, your name if you give one, and what you wrote. It is emailed to us and kept in our inbox so we can reply. BookPocket itself does not store it.
  • The waitlist: your email address, your name if you give one, and, if the link you followed had one, a short word saying where the link was shared, like a flyer or an event.

We count how many times each page of this website is opened each day, and which website linked to it. The count holds nothing about you: no IP address, no browser details, and no cookie.

We use no advertising or tracking tools, and we do not sell or rent your data to anyone.

What do we store about other people?

Recording who recommended a book is the point of BookPocket. So you can store details about people who have not signed up and have not agreed to anything. We treat that data with extra care.

  • Sources you record: a name, what kind of source it is, how you know them, your note about them, a link, and a picture. Only you can see them.
  • When you share who recommended a book, a person shows only as "someone they know", unless they have linked their own BookPocket account to your source, and then by the name they chose. Podcasts, publications, bookshops, and videos are shown by name. Your notes about a source, and their picture, are never shown.
  • When you save a book from a bookshop's list, that shop becomes its source. The shop sees how many readers saved books from each of its lists. Once five readers have finished books from a list, it also sees how many finished one and their average rating. It never sees who, and books you've locked are never counted.
  • Pictures of sources are kept in private storage that is not publicly readable. Your own picture is in public storage, at an address nobody can guess.
  • Pictures and covers you upload are made smaller before we store them, and we keep only the image. Anything else in the file, such as where a photo was taken, is removed.
  • Email addresses you send books or invitations to. The person gets one email, which names you, the book, and your note. They can accept it or ignore it.

A source is only connected to someone's BookPocket account if that person agrees. Nobody can link your account to their source without you.

Who can see your data?

  • Anyone: book pages are public. They show the reviews readers write, with the reader's name, and an average of readers' ratings with how many there are. To hide your review of a book, press the lock on it.
  • Anyone: a comment you post on the public roadmap, with your display name and picture beside it, or "A BookPocket reader" if you haven't set a display name. Votes on cards and comments are counted and never show who cast them.
  • Anyone with the link to your page sees your name and any part of your reading you set to Public. Nothing is Public unless you choose it.
  • Your friends see your name, that you are friends, and the parts of your reading you share with them. By default that is what you're reading, the books you've finished with your ratings, your To be read list, and who recommended each book. Change it on your profile's Friends tab, for every friend or for one. Books you've locked are never shown. If you decline a friend request, the person who sent it is not told.
  • Only you: your reading dates, private notes, pause notes, tags, the sources you record, and anything you haven't shared.
  • If you make lists for a bookshop, the shop's page and lists are public, and the shop's other members see your name. When you join, we email your display name to the shop's own address. Each book you pick shows your display name and profile picture, on the list and its printed shelf talker. If you haven't set a display name, or you leave the shop, your picks show the shop's name instead.
  • People you send a friend request to see your full name, or your display name if you haven't given one.
  • People you send a book to see your name and your note. You see whether they accepted it and whether they have finished it, and nothing more.
  • People you block no longer see your reviews or your page, and you no longer see theirs. If you were friends, you stop being friends. We don't tell them they were blocked.
  • People you report are never told who reported them. The Owner reads each report, with your name, to decide what to do.
  • Anything you give an API token to can read everything on your account: your books, notes, sources, and stats. It can't change anything. We store only a scrambled copy of each token, so we can't show it again. Revoke one on your profile's API tab and it stops working at once.
  • Support: if you ask for help, a support account can look up counts and states on your account, such as how many books you have or whether an import failed. It cannot see titles, notes, reviews, tags, or sources, and every lookup is logged. A support account can also ban an account that breaks the terms.
  • R.J. can reach the database to keep the service running and fix problems, and only does so for that.

Who else handles your data?

We use a few services to run BookPocket. Each one gets only what it needs.

  • Hetzner hosts the servers and the database.
  • Cloudflare R2 stores pictures, book covers, import files, and nightly database backups.
  • Apple delivers notifications to the iOS app, so it receives the device token and the notification's text.
  • Google delivers notifications to the Android app, through Firebase Cloud Messaging, so it receives the device token and the notification's text. Firebase also receives the app's version and the phone's make, model, and Android version.
  • Google's barcode scanner, in the Android app, reads a book's barcode on your phone. The picture never leaves your phone. The scanner sends Google the phone's make and model, the app's name and version, and how the scan went, so Google can check it works.
  • Google and Apple, if you sign in with them, learn that you signed in to BookPocket. They send us your name and email address, and nothing else about your account there.
  • Resend delivers our emails, so it receives the address and the message.
  • Open Library and the Library of Congress receive the words you search for and book identifiers such as ISBNs. They never receive your name or email address.
  • Penguin Random House receives the words you search for, when the other catalogues do not have the book, and book identifiers such as ISBNs, so we can fill in details about their books. Wikidata receives one general question a week about which books belong to a series. Neither receives your name or email address.
  • A cover address you paste is fetched once by our server. That website sees a request from BookPocket, never from you.

What do we keep in your browser?

  • A cookie that keeps you signed in.
  • A cookie that tells this site you have signed in before, so a button can say "Dashboard". It cannot sign you in.
  • A cookie that remembers whether you view My Books as a list or a grid.
  • A cookie that remembers you hid the "Start with a few books you loved" list on your dashboard.
  • Your theme and motion choices, stored in your browser only.

None of these track you across other websites.

How long do we keep it, and how do you delete it?

  • Your account stays until you delete it. To delete it, open your profile and use Delete your account, as Delete your account explains step by step. Everything goes, including the sources you recorded and their pictures. If you signed in with Apple, we tell Apple to remove BookPocket from your Apple account too.
  • Books you typed into the catalogue stay for everyone else, without your name on them.
  • An application to be a librarian, and what we decided, stays until you delete your account.
  • A ban records when it was placed and by which account, until it is lifted. While it lasts, your account can't be signed into and nothing from it is shown to anyone. If we delete an account instead, everything goes, as it does when you delete it yourself.
  • A review we remove for breaking the terms is deleted. We keep when it was removed and by which account, and your rating stays.
  • A roadmap comment stays until you delete it from its card, or delete your account. If we remove one for breaking the terms, nobody sees it again, and we keep it with when it was removed and by which account until your account is deleted. Your votes stay until you take them back or delete your account.
  • A report stays until the account that sent it, or the account it is about, is deleted. When we deal with it, we also keep when and by which account.
  • A block stays until you unblock, on your profile's Friends tab, or until either account is deleted.
  • Deleted data can remain in nightly backups for up to 30 days, until those backups are deleted.
  • An account whose email address is never confirmed is deleted a week after sign-up, if nothing was added to it.
  • An unconfirmed waitlist signup is deleted once its confirmation link expires. To leave the waitlist, use the link in the email that confirmed your signup.
  • To get a copy of your data, or to ask us to correct or delete something, email privacy@bookpocket.app.