Your book files and notes stay on your device. Usage measurement, ads, purchases and translation use third-party services.
Bunko eReader opens EPUB, PDF, Word, Excel and text files without an account. Book files, titles, notes, highlights and saved reading positions remain on your device unless you export content or request a translation.
The Android and iOS apps use Google Analytics for Firebase to measure feature usage, including reading duration and page transitions. The free version uses Google AdMob for ads. Purchases use the app store and RevenueCat; translation sends your selected text to Google Translate. These services process the data described below.
Bunko has no account registration or book-upload server. We do not send your book files, titles, authors, file paths, notes, highlights or search text to Analytics or AdMob.
Google Analytics for Firebase measures onboarding completion, screens viewed, document import and open attempts, document format, reading duration and page transitions, reader-setting changes, read-aloud starts and views of the Pro screen. These events help us understand which features are used and improve the app. They do not identify which book you are reading.
Analytics also collects installation identifiers, app and device information, session data and approximate location. Depending on platform permissions and device settings, device or advertising identifiers may be available. Bunko does not request GPS location. We do not assign a name, email address or account ID to Analytics events.
Analytics starts when the Android or iOS app starts, including for Pro users. The current app does not provide a separate Analytics opt-out switch. Advertising consent messages apply to ads; they are not an Analytics off switch.
More information: Google Analytics data collection and Google Privacy Policy.
The free version uses Google AdMob to load and show interstitial ads. Pro users are exempt from these ads. Google may process IP-derived approximate location, device identifiers, ad impressions and interactions, and diagnostic or performance information. Identifier availability and ad personalization depend on permissions, consent and device settings.
The app requests advertising consent information through Google's User Messaging Platform and shows a consent form when required by that service. See Google Mobile Ads data disclosures and How Google uses information for advertising.
Bunko does not use Firebase Crashlytics or Firestore. This does not prevent the advertising SDK from processing its own diagnostic data.
For the app to work, the following information is kept only on your own device, in the app's private storage:
Your book files, notes and detailed saved reading positions are not uploaded by Bunko. Separate usage events, such as reading duration and page transitions, are sent to Analytics as described in section 01. Data may also leave your device when you export or share it (section 06), request a translation (section 05), or use an operating-system backup such as iCloud or Google Drive. System backups follow the platform provider's privacy policy.
The app asks for access to your files so it can open the EPUB, PDF, Word, Excel, text and ZIP files you select from within the app. It uses the system file picker and only reads the files you choose; it does not scan your storage. Your book files are read, processed and stay on your device. They are never transmitted outside the app.
Read-aloud uses your device's built-in text-to-speech engine. The text is spoken by the operating system on the device. If the system engine you have chosen downloads voice data, that is handled by the engine's provider (for example Google or Apple), not by Bunko.
Bunko Pro is an optional in-app purchase. Payment is processed entirely by Google Play or the Apple App Store. Bunko never sees your name, payment method or card details.
To check whether a purchase is valid and to restore it on a new device, the app uses RevenueCat, a subscription management service. The purchase SDK is initialized at app startup to check Pro status. During initialization and when checking, purchasing or restoring Pro, RevenueCat may process:
Bunko uses RevenueCat to validate and manage Pro access. Bunko does not attach your book content or notes to purchase records. RevenueCat's handling of this data is described in the RevenueCat Privacy Policy.
Bunko Pro includes a tap-to-translate feature. When you tap a word or select a passage and open the lookup panel, only that selected text is sent to Google Translate so it can be translated and, for single words, given dictionary meanings.
Bunko does not store the translated text on any server. Results are shown on screen and kept only on your device.
Book viewing works locally. Internet connections are used for usage measurement, ads, purchase management and translation. Bunko does not sell your book files or notes.
Providers may process data on servers outside your country under their terms and privacy policies. Analytics event retention depends on the Firebase/Google Analytics project's configured retention settings; advertising and purchase records follow the applicable provider's retention practices. This policy does not promise a fixed deletion period for third-party records.
This policy and our Terms of Use are linked under Settings → About and on the Pro screen.
Bunko eReader is not directed at children under 13. If you believe a child has provided personal data through the app or its services, contact us using section 11. Purchases are subject to the device's app-store payment settings and parental controls.
You can remove local book files and reading records by clearing the app's storage or uninstalling it. Backups and exported files must be deleted separately from wherever you saved them.
Uninstalling the app does not itself delete data previously processed by Analytics, AdMob, RevenueCat or an app store. Device advertising privacy settings may restrict identifier use but do not remove previously collected records.
For questions about access or deletion of data processed through Bunko, email us using section 11. We will assess the request and coordinate with the relevant provider where records can be identified. Bunko has no account system, so locating a particular installation's records may require additional information. Do not send book contents or payment card details.
This privacy policy may be updated from time to time, for example when a new feature changes how data is handled. Any changes will be posted on this page and the "last updated" date at the top will be revised accordingly.
If you have questions about this privacy policy, you can reach us at: