Last updated: 19 November 2026
Interim document for the closed alpha. Not yet reviewed by a lawyer.
We wrote this ourselves by going through the app's own source code, so it is an accurate and good-faith description of what ShelfTalk actually does today. It is not a professionally drafted legal document.
Before ShelfTalk is released publicly, this will be replaced by a version drafted and reviewed by a qualified lawyer. We are telling you that up front rather than letting you assume otherwise. If anything here is unclear, or turns out not to match what the app does, please tell us at wspublished@gmail.com — during the alpha we would genuinely rather be corrected than be trusted.
Applies to: the ShelfTalk app (Android and iOS) and the ShelfTalk website, including join.shelftalk.com and its waitlist, closed alpha
Contact: wspublished@gmail.com
1. The short version
ShelfTalk is a book discovery and social reading app. We collect what we need to run it: your account, your reading activity, what you post, and, if you ask for an invite, the details on the waitlist form. We do not sell your data, we do not show ads, and we do not track you across other apps or websites.
This is a closed alpha. The app is under active development, data may be reset, and features change frequently.
2. Who we are
ShelfTalk is made by Steve and Wes, two readers in Canada. It is an independent app in pre-release development. For anything in this policy — questions, corrections, or a request to delete your data — write to wspublished@gmail.com.
We are a very small team, so please allow a few days for a reply.
3. What we collect in the app
Account
- Email address and password, or a Google or Apple account if you sign in with one. These are held by Firebase Authentication, our sign-in provider. If you sign in with Apple and choose to hide your email, we receive Apple's private relay address instead.
- Your email is deliberately not copied into your public profile record. When the app needs it, it reads it from your active sign-in session.
Profile
Display name, profile photo, bio, favourite genres, reading moods, your "currently reading" book, your top reads, your friends / following / blocked lists, and your experience points and rank.
Reading activity
- Books you like, skip, or mark as read on the Discover deck
- Your shelves and the books on them
- Your reading log: ratings, moods, pace, content ("spice") rating, and finish dates
- Reading progress (your bookmark) in book clubs
Things you write and share
Posts, captions, photos and videos you upload, comments, book club discussion, direct messages, reviews, and reports you file.
Hidden information in photos and videos. Photos and videos can carry hidden details alongside the picture, such as where they were taken (GPS location), the phone model and the time. Photos: before a photo you post or use as your profile picture leaves your phone, the app makes a resized copy and uploads only that copy, which does not contain the location, phone model or time. If the copy cannot be made, the photo is not uploaded. Videos: we upload videos exactly as they were recorded, so a video can still contain the phone model and, depending on your phone and camera settings, where it was recorded. On the Android phones we have tested, the system removes the location from a video you pick from your gallery before ShelfTalk receives it; we have not yet confirmed this on iPhone. Anyone who can view your video can download the file. If you do not want a video to show where it was recorded, turn off location tagging in your camera before recording.
Library imports
If you import a library from Goodreads or StoryGraph, we read your CSV file to create your shelves. The uploaded file is deleted from our storage as soon as it has been processed. The book data from it stays on your shelves.
Technical
- A push-notification token for your device, so we can send you notifications
- Crash and error reports (via Sentry), which may include device model, OS version, and the technical state of the app when it crashed
- Usage analytics (via Firebase Analytics) — see §7
4. The waitlist and invites
When you ask for an invite on join.shelftalk.com we store:
- your email address, and your first name if you give it
- which phone you use (iPhone or Android), because that decides which invite we send
- how you found us, if the link you followed says (for example a friend's share link)
- when you asked
To stop floods of fake requests, the website also turns your network address into a one-way fingerprint (a salted hash) and counts requests from it for a short time. We never store the address itself, and the fingerprint can't be turned back into it.
A person reads every request. If we invite you, we give your email to Apple (TestFlight, for iPhone) or Google (Firebase App Distribution, for Android), which send the invite and the install link. We use your waitlist details only to decide on and send your invite. We do not send marketing emails, and the form doesn't sign you up for any.
To have your waitlist entry removed at any time, write to wspublished@gmail.com.
5. The website
The website shows the waitlist, lets members sign in to see or delete their account, and holds these documents. It uses no advertising or tracking cookies. It stores two things in your browser: your light or dark display choice, and, if you sign in, the session that keeps you signed in (handled by Firebase Authentication). Book covers on the front page are shown for illustration.
6. What we do not do
- We do not sell or rent your personal data.
- We do not show advertising, and we do not share your data with advertisers.
- We do not track you across other apps or websites.
- We do not store your email address in the profile record other users can read.
- We do not read your direct messages routinely. See §10 for the one exception.
7. Analytics
We record app events to understand whether features work — for example that a book was swiped, a post was created, a club was joined, or a bookmark was moved.
These events carry book identifiers, titles, genres, and counts. They do not carry the text of your posts, comments, or messages. Analytics are processed by Google Firebase Analytics.
8. AI book recommendations
Some recommendations are generated by Google's Gemini AI. When that happens we send:
- your favourite genres, reading moods, and pace preference
- the titles and authors of books you have liked, skipped, or are currently reading
We do not send your name, email, profile photo, posts, comments, or messages to the AI service.
9. Who else processes your data
We use these providers to operate the app. Each only receives what it needs:
- Google Firebase — Sign-in, database, file storage, notifications, analytics, server functions, website hosting
- Google Sign-In — Optional sign-in method
- Sign in with Apple — Optional sign-in method
- Apple TestFlight — Sends iPhone invites and installs the alpha (receives your email)
- Firebase App Distribution (Google) — Sends Android invites and installs the alpha (receives your email)
- Google Books, Open Library — Book search, metadata and covers (we send the search text, not your identity)
- KLIPY — GIF search in chat (we send the search text, never your identity; GIF images load from KLIPY's servers when a chat shows them)
- Google Gemini — AI recommendations (see §8)
- Sentry — Crash and error reporting
- Agora — Live video for book club meetings, if you join one
10. Reports, moderation, and your messages
If someone reports a post, comment, club message, direct message, or account, the report is sent to us for review.
A report includes a copy of the reported content at the time it was reported — including the text of a direct message, if a direct message is what was reported.
We do this deliberately, for two reasons: we otherwise have no way to read a reported private message and therefore no way to judge the report, and because content can be deleted between being reported and being reviewed. Reports are readable only by the small number of people who operate the app.
Outside of a report, we do not read your direct messages.
11. Who can see what you share
- Public posts — any signed-in ShelfTalk user
- Friends-only posts — only people you are friends with
- Private posts — only you
- Stories — any signed-in user, and they expire after 24 hours
- Book club discussion — other members of that club
- Direct messages — you and the person you are messaging
- Your profile — any signed-in user, unless you turn on Private Profile in Settings
Blocking someone stops them messaging you and hides your content from each other.
12. Keeping and deleting your data
You can delete your account from Settings → Delete Account in the app, or on the website (Account → Delete account). You type DELETE to confirm. In the app, if you sign in with an email and password, you also re-enter your password. We complete every deletion within 30 days. In practice, deleting in the app or on the website happens straight away. Deletion cannot be undone.
When you delete your account we remove your profile, your posts and comments, your shelves and reading log, your uploaded photos, the feedback you sent us, and the messages you sent. Conversations you took part in remain for the other person, with your messages removed and your name replaced. We do not keep backups of the database, so deleted records cannot be restored. Deleted photos stay in our storage provider's recovery area for 7 days, then are gone for good.
A few things are kept for a limited time:
- Abuse reports and the evidence attached to them are kept for up to 12 months after the report is resolved, so that a banned account cannot simply be recreated and so we can handle appeals.
- Crash reports held by Sentry are deleted automatically within 90 days.
- Usage analytics held by Google Analytics are deleted automatically within 14 months.
You can also write to wspublished@gmail.com from the email address on your account and ask us to delete it. We will confirm your request and complete the deletion within 30 days.
13. Security
Access to your data is enforced on our servers, not just in the app — the database rejects requests for data you are not entitled to. Sign-in is handled by Firebase Authentication and we never see your password.
No system is perfectly secure, and this is alpha software. Please do not put anything in ShelfTalk that would be damaging if it were exposed.
14. Age
ShelfTalk is not intended for children under 13, and we do not knowingly collect data from them. If you believe a child under 13 is using the app, contact wspublished@gmail.com and we will remove the account.
15. Where data is stored
Your data is stored on Google Cloud infrastructure, which may be located in the United States and other countries. By using the alpha you accept that your data may be processed outside your own country.
16. Your rights
Depending on where you live you may have the right to access, correct, export, or delete your personal data, and to object to certain processing. In Canada, these rights come from federal privacy law (PIPEDA). To exercise any of these, write to wspublished@gmail.com.
17. Changes
We will update this policy as the app changes. During the alpha, expect it to change often. The date at the top always reflects the current version.