Reebo: EPUB & TXT Reader
Privacy policy
Last updated October 14, 2026 · Reebo 0.27.2
Your books live on your device. This page explains the usage data Reebo sends to help improve the reading experience.
1. Books and data on your device
Reebo is a local EPUB and TXT reader provided by FlowManga Studio. It stores copies of imported books, reading positions, bookmarks, highlights, notes, collections, imported fonts, reading activity, and settings in the app’s private storage on your device.
Reebo does not automatically upload book files, book titles, authors, book text, highlights, notes, search terms, collection names, file locations, or imported fonts to its analytics services. You do not need to create an account to read. Reebo does not provide cloud synchronization.
2. Usage analytics and the upload-policy service
Reebo uses its developer’s upload-policy service and Amplitude to understand where people encounter interruptions, failures, or difficulty using the app. Reading does not require an internet connection.
Usage analytics is off until you choose to allow it. When analytics is enabled and the app process starts, Reebo requests an upload decision from the developer’s service. This request includes:
- A randomly generated installation identifier, shared with Amplitude as a device identifier if analytics is enabled.
- Device brand, Android version, app version, startup count, and whether this is the installation’s first app-process start.
- Language and country/region from the device’s locale settings. These are not GPS coordinates.
If the service permits analytics, Reebo sends Amplitude a limited set of usage events, such as screens and tools opened, book format, import/open outcomes, operation timing, coarse error categories, reading duration, and progress grouped into broad ranges. Amplitude also receives standard app, device, operating-system, and language metadata. Random identifiers distinguish installation and reading sessions; they are not your email address or an account name.
Advertising IDs, App Set IDs, GPS coordinates, screen recording, automatic text capture, and book content are excluded from Reebo’s analytics configuration. Analytics is not used for advertising in Reebo. You can turn off future usage analytics in Library options → Privacy & about. The setting is stored on your device. When it is off at startup, Reebo does not request an upload decision or start Amplitude. Requests already in transit may finish. Re-enabling analytics after turning it off takes effect after restarting Reebo. Reading and your local library remain available.
The developer’s network service and Amplitude can observe your connection’s IP address when requests reach them, even though Reebo disables the IP-address property in its analytics events. Their infrastructure may process request logs.
If the upload-policy service refuses analytics, cannot be reached, or returns an invalid response, Reebo does not initialize the analytics SDK for that process. The policy request itself may already have reached the developer’s service. Pending events are held in bounded memory rather than saved as analytics event files on the device.
Amplitude processes analytics for the developer. Learn about its general practices in Amplitude’s privacy notice. The developer remains responsible for the data sent by Reebo.
3. Actions you choose and system services
When you import a file, Android’s file picker or the source app grants access to the selected document. Reebo does not request broad access to all device storage.
If you choose Share, a text-processing tool, an annotation export, or a web link, the chosen destination receives the text, file, or URL needed for that action. The recipient’s own privacy practices apply. Reebo does not perform those actions automatically.
Read aloud uses installed voices identified by Android as available for offline speech. The system speech service receives the text needed to speak it. Reebo does not request microphone access or record your voice.
4. Data handling and security
Reebo’s upload-policy and analytics requests use HTTPS. Books and annotations are stored in Android’s app-private storage. Reebo does not claim to provide separate encryption of local book files or end-to-end encryption for analytics.
Books selected from other apps, exports, messages sent to support, and external tools may be subject to those services’ separate storage and privacy practices.
5. Retention and deletion
Your local reading data remains in the app until you remove the relevant record or remove the app’s data. Uninstalling normally removes the app’s private storage. Keep your original book files. Original files and exports outside Reebo’s private storage are managed separately and are not removed by uninstalling Reebo.
Removing the app does not delete analytics already delivered to the developer’s service or Amplitude. Removing app data may create a new installation identifier when you next use the app.
Upload-policy request logs are retained for up to 7 days. Amplitude event data uses a 90-day Time to Live (TTL) setting measured from when events reach Amplitude. Cleanup runs on a schedule; deletion processing, including the initial cleanup after a retention change, may take additional time.
The event TTL does not itself delete installation profiles or associated user properties. Those records can be removed through the installation-linked deletion process described below. This app does not have user accounts.
To request deletion of installation-linked analytics, contact gsprin999@gmail.com. In Reebo 0.27.2 or later, open Library options → Privacy & about → Copy installation ID and include that identifier in your request. Do this before uninstalling or clearing app data, because the old identifier may no longer be available afterward. We use it to locate matching backend records and the corresponding Amplitude installation. If more information is needed to identify the records, we will explain what is needed.
Verified deletion requests are handled for Reebo’s backend and Amplitude project, and deletion jobs are tracked to completion. Amplitude runs scheduled deletion jobs, so removal is not instantaneous. Turn off usage analytics before requesting deletion if you also want to stop new collection. Deleting analytics does not delete your books or notes on the device; deleting those local records is a separate action.
6. Contact and policy changes
This static policy page contains no analytics scripts, forms, or third-party fonts. If you visit it on Cloudflare Pages, Cloudflare processes the requests needed to deliver it under its own privacy policy.
For questions about Reebo or its data practices, contact the Reebo developer at gsprin999@gmail.com. Do not send book files or private reading notes unless they are needed for a support request and you choose to provide them.
This policy should be updated when Reebo’s data practices change. The date above identifies this version. Reebo’s Android package is com.nw.ttreader.
7. Adult readers
Reebo is intended for readers aged 18 and over and is not directed to children. We do not ask for your date of birth or use age verification to collect additional personal information. If you believe a child has provided personal data through Reebo, contact us so we can investigate and handle an appropriate deletion request.