1. Who we are
DinoReader is an ebook reading app from FBReader.ORG Limited, registered in England and Wales under company number 08579768. We are the controller of personal information processed for DinoReader. This policy covers the DinoReader Android app, the dinoreader.app website and the support services described below.
You can contact us about privacy at [email protected].
2. Reading on your device
You do not need an account to open your own books. DinoReader accesses the files and folders you select or allow it to scan, reads book contents and metadata, and keeps library information, reading positions, bookmarks and preferences on your device so you can organise your books and continue reading.
You can manage file access in DinoReader’s library settings and in Android’s app permissions. Removing access can prevent DinoReader from finding or opening affected books.
Online features can send information off your device as described below. Enabling cloud synchronisation is a separate choice from opening a local file.
3. Online services
Cloud synchronisation
If you connect DinoReader to the FBReader Book Network, you can synchronise books, reading positions and bookmarks across devices. The Book Network uses Google sign-in and Google Drive for book storage. Information needed for the features you enable is transferred to those services and linked to your account.
The Book Network is also operated by FBReader.ORG Limited. Its terms and privacy information and Google’s privacy policy explain the services involved.
Bookshops, libraries and catalogues
When you browse, search, sign in, save a book or download from an online catalogue, your requests go to that catalogue’s provider. The provider receives connection information, such as your IP address, and the information needed to carry out the request. Signing in connects those actions to your account with that provider.
Readino is operated by FBReader Books Limited. Its handling of accounts, saved books, purchases and payment processing is explained in the Readino privacy policy. Purchases take place in a browser through Readino’s checkout. Other bookshops and libraries have their own privacy policies.
Protected books
Opening or managing a Readium LCP-protected book can require communication with the book provider’s licence service. That service handles the licence information needed to authorise access or manage a loan under the provider’s terms.
Reading aloud
When you use reading aloud, DinoReader passes text to the text-to-speech engine selected on your device. Some engines process text locally; others use an online service. The engine’s settings and privacy policy determine how it handles that text.
4. Feedback and support
If you send feedback, we receive your message and any email address you choose to provide. Feedback can also include your DinoReader version, device model and operating system version to help us understand the problem. You can send feedback without providing an email address; without one, we cannot reply directly.
Feedback is delivered to our support mailbox through Zoho, our email provider, which processes these messages to provide the email service. Message text and email addresses are not saved in the website’s feedback database, but are included in the email we receive. Please avoid including passwords or other information we do not need to resolve your enquiry.
Our support mailbox is hosted in Zoho’s United States data centre.
To limit spam and repeated submissions, the feedback service stores a keyed hash derived from the connection’s IP address, a submission time and, for app submissions, a request identifier. These records are used for abuse prevention.
5. Website and connection data
Visiting the website, downloading an update or requesting the default catalogue list makes a connection to our servers. Handling these requests involves your IP address and technical request information. Hosting and network providers may also process this information to deliver the service and protect it from abuse.
DinoReader and fbreader.org are hosted by Linode on servers located in London, United Kingdom.
The website’s feedback form uses a security cookie to protect submissions against forged requests. Website pages load fonts from Google Fonts, which causes your browser to connect to Google. See Google’s privacy policy for information about Google’s processing.
We use HTTPS to protect connections to the DinoReader website. The feedback service also includes protection against forged form submissions and excessive requests.
International transfers
Using Zoho for email involves transferring support correspondence to the United States. Our Sentry organisation stores crash-event data in the European Union. These storage locations do not necessarily cover all processing by a provider or its service providers.
We have accepted data processing agreements with Zoho and Sentry. These agreements set out their obligations when handling data on our behalf, including security and international transfers. They provide contractual transfer safeguards, including standard contractual clauses where applicable. Sentry’s agreement includes the UK Addendum for relevant UK transfers.
Further details are available in Zoho’s privacy information and Sentry’s data processing agreement. Contact us if you would like information about, or a copy of, the safeguards applicable to your data.
6. Crash reports and usage data
Crash reports
DinoReader uses Sentry to report crashes so we can investigate faults and improve the app’s reliability. Reports contain technical crash information, including error details and exception messages.
Crash reporting is enabled by default. You can switch it off in Main menu → About → Details → Privacy. Switching it off stops future crash reporting; it does not itself delete reports already sent.
We do not deliberately include book titles or file paths in crash reports. However, an exception message can sometimes contain a file path. If that happens, the path is included in the report and may reveal a filename or other information contained in the path.
Sentry receives and processes these reports as our crash-reporting provider. Its published data processing terms describe how it handles customer-submitted data.
Our Sentry organisation uses the European Union region to store crash-event data.
Usage data
DinoReader asks for your explicit consent before sending usage data to fbreader.org. This reporting is separate from Sentry crash reporting. Declining usage reporting does not require you to stop using DinoReader.
As described in the FBReader statistics collection policy, reports may include:
- Operating system, app version, interface language, whether synchronisation is enabled, library size, book formats and session duration.
- Book titles and authors, book language and format, reading progress, and the provider of a protected book.
- Actions such as opening or downloading books, using the contents or bookmarks, and navigation interactions.
A persistent generated device ID links reports from the same device. We retain reports grouped by that ID for the period described below. Statistics exclude email addresses, account names, purchase lists and bookmark text. The statistics service derives country and region from the connection’s IP address, then discards the address without logging it.
We use statistics to understand app use, improve features and fix faults. We may publish aggregated results, not individual reports. If you decline, the app sends a single refusal notice and stores your choice locally.
You can withdraw consent at any time in Main menu → About → Details → Privacy. This stops future usage reporting; it does not itself delete reports already sent. Contact us about deletion using the details below.
7. Why we process personal information
Where UK or EU data protection law applies, the legal bases for processing personal information are:
- Consent: optional usage reporting. You can withdraw consent through the privacy settings described above.
- Legitimate interests: responding to support enquiries, protecting our services against abuse, keeping security logs and investigating crashes. These interests are supporting readers and maintaining reliable, secure services.
- Providing a service under an agreement: processing necessary to provide optional account services you request, such as Book Network synchronisation, under that service’s terms.
You can object to processing based on legitimate interests by contacting [email protected]. You can also switch off crash reporting in the app’s privacy settings.
8. Keeping and deleting data
You can clear DinoReader’s app data through Android settings. Book files saved in shared storage may remain and can be deleted separately with your device’s file manager. Clearing local data or uninstalling DinoReader does not delete information already stored in a connected online account.
To delete information held by the Book Network, Readino or another catalogue, use that service’s account controls or contact its operator. You can also contact us at [email protected] about information we hold in connection with DinoReader.
Server logs are retained for 14 days. As explained above, the statistics service does not record IP addresses in its logs.
Feedback abuse-prevention records become eligible for cleanup after one day. The current service removes older records when it next processes a feedback attempt; cleanup is not a fixed 24-hour deletion guarantee.
Support emails: there is no fixed retention period. A member of our team decides when correspondence is no longer needed and deletes it.
Usage data: we retain each usage report, linked to its generated device ID, for up to two years from collection, then delete it. We delete reports sooner if they are no longer needed. You can request earlier deletion of personal information in these records by emailing [email protected].
We use Sentry’s free Developer plan, which provides a 30-day history of crash events. This period applies to the event history held in Sentry, rather than to support correspondence or usage data sent to fbreader.org.
9. Your privacy rights
Depending on the law that applies and the circumstances, you may have rights to access your personal information, correct it, request deletion, restrict or object to processing, and receive a portable copy. Where processing relies on consent, you can withdraw it without affecting the lawfulness of processing before withdrawal.
To make a request, email [email protected] and describe the information or service concerned. We may need enough information to verify that the request relates to you. You can also raise a concern with the UK Information Commissioner’s Office or your local data protection authority.
10. Children
DinoReader is intended for a general audience and is not specifically directed at children. It provides access to Readino and other online catalogues, whose content, account requirements and privacy practices are governed by their respective providers.
11. Changes to this policy
We will update this page when the way DinoReader handles information changes and show the date of the updated policy. Where required, we will provide an additional notice or ask for consent before a new use of personal information begins.