Readerly Privacy Policy

Effective date: February 9, 2026

Developer

Readerly is developed by Jamie Fury. If you have any questions about this policy, you can reach us at contact@pulseratalent.com.

Information Collected

Account data

• Email address
• Display name
• Password (stored only as a bcrypt hash; we never store your plain-text password)

Library data

• Book titles, authors, and ISBNs
• Cover image URLs and descriptions
• Page counts
• Reading status

How Data Is Used

All collected data is used solely to provide the Readerly service—authenticating your account and storing and displaying your personal library. We do not sell, rent, or share your data with any third party for advertising or analytics purposes.

Third-Party Services

Readerly queries the Google Books API to retrieve book metadata (titles, authors, cover images, etc.). No user data is sent to Google as part of these requests; only book search terms are transmitted.

Data Storage & Security

• Data is stored in a MySQL database on a secured virtual private server.
• Passwords are hashed using bcrypt before storage.
• All communication between the app and the server is encrypted over HTTPS.
• Session authentication is handled with JSON Web Tokens (JWT).

Data Retention & Deletion

Your data is retained for as long as your account remains active. You can delete individual books from your library at any time within the app. To request full account deletion, please email contact@pulseratalent.com.

Children's Privacy

Readerly is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal data, please contact us so we can remove it.

Changes to This Policy

We may update this privacy policy from time to time. Any changes will be posted on this page with a revised effective date.