Privacy

Data and Privacy

Last updated: June 2026

This plain-language page summarizes what Readr stores, why it stores it, and how users can control or delete data.

What Readr stores

Readr may store account details, profile details, profile photos, club memberships, club content, messages, book suggestions, votes, meeting details, saved books, reading progress, completed books, notification tokens, support requests, analytics, diagnostics, and performance data.

Why Readr stores it

Readr stores data to provide book club organization, personal library tracking, account access, notifications, support, safety review, moderation, diagnostics, reliability, and product improvement.

How users can control or delete data

Users can update some account, profile, club, and library information in the app. Users can request account deletion help through support and, when available, start account deletion from Readr Settings.

Shared club content may need special handling because it can affect other club members and shared club history.

Notification data

If notifications are enabled, Readr may store device tokens and preferences so it can send club, meeting, message, voting, suggestion, and account notifications. Device settings may also control whether notifications are delivered.

Profile photos

Profile photos may be uploaded by users and stored through cloud storage or related image services. Users should only upload images they have the right to use.

Profile photos may be visible to other members in clubs or app areas where profile identity is part of the experience. Deleting an account may delete or de-identify profile photo data, subject to safety, legal, backup, or operational retention needs.

Club content

Club content can include club names, descriptions, member lists, current reads, suggestions, votes, meetings, messages, and related activity. Club content may be visible to members of that club depending on the feature.

Analytics and diagnostics

Readr may collect analytics, crash, diagnostic, and performance signals to fix bugs, understand reliability, improve features, and protect the service from misuse.

Analytics and diagnostics should avoid passwords, authentication codes, private message text, and other unnecessary sensitive content.

Third-party services

Readr may use Firebase or Google Cloud services to operate accounts, database, storage, notifications, analytics, diagnostics, and hosting. Readr may also use book metadata providers to search and display book information.

Third-party providers may process information only as needed to provide, secure, monitor, and improve Readr or to show book information requested by users.

Data and privacy contact

Use this email for data questions, privacy requests, and account deletion help.

hello@readrofbooks.com