Short version. BookHive is a reading app that runs almost entirely on your device. The books you import, your reading progress, highlights, notes, and settings are stored locally on your phone and encrypted at rest. Nothing is sent to us. If you choose to sign in with Google Drive, your data syncs to your own Google Drive account — we don't see it.
We don't sell, share, or monetize your data. We don't track you. We don't show ads. We don't have analytics.
BookHive ("the app") is developed and published by Eassist ("we", "us", "our"), based in the Philippines. This policy explains what data BookHive handles, how it handles it, and what choices you have. It applies to the BookHive Android application distributed under the package name com.bookhive.app.
When you import an EPUB, PDF, TXT, DOCX, or MOBI file into BookHive, the file is processed and stored on your device. We use Android's IndexedDB storage, and book content is encrypted at rest using AES-256-GCM (the Web Crypto API). The encryption key is derived on your device and is not transmitted anywhere.
We do not upload your books to any server controlled by us. We have no servers that receive book content.
BookHive records, locally on your device:
All of this is stored on your device. None of it is transmitted to Eassist.
If you sign in with Google Drive from inside the app, BookHive uses Google's OAuth 2.0 flow to obtain permission to read and write files in your Google Drive. When sync is enabled:
drive.file, which limits access to files BookHive itself creates. We cannot see your other Drive files.Google's use of any data you sync to Drive is governed by Google's Privacy Policy, not ours.
BookHive includes an optional crash reporting feature, off by default. If you enable "Send anonymous crash reports" in Settings, the app may send technical error details (stack traces, app version, Android version) when something crashes. These reports contain no book content, no personal identifiers, and no reading data. You can turn this off at any time.
At the time of writing, crash reports are buffered locally and not transmitted to any external service. If we ever enable transmission to a third-party error tracking service (such as Sentry), this policy will be updated and the feature will remain opt-in.
android.permission.INTERNET): Required only for optional Google Drive sync and OAuth sign-in. The app works fully offline if you never enable sync.BookHive does not request any other sensitive permissions.
BookHive is a general-audience reading app and is not directed to children under 13. We do not knowingly collect personal information from children. If you believe a child has used the app and you'd like data removed, contact us — though because all data is local to the device, uninstalling the app or clearing its data removes everything we'd otherwise be unable to reach.
Because BookHive stores data locally and (optionally) in your own Google Drive, we have nothing to retain. You can delete all BookHive data at any time by:
If you used Drive sync, you can additionally delete the BookHive folder from your Google Drive at drive.google.com.
Under the Philippines Data Privacy Act (Republic Act No. 10173), you have the right to be informed, to object, to access, to rectify, to erase or block, to data portability, to file a complaint, and to damages for inaccurate or unauthorised processing of your personal data. Because BookHive does not transmit personal data to us, most of these rights are exercised directly on your own device (by uninstalling, clearing data, or revoking Google permissions).
If you believe your rights have been violated, you may contact us using the details below, or file a complaint with the National Privacy Commission of the Philippines.
If you use BookHive outside the Philippines: the app's local-only design means the same protections apply regardless of jurisdiction. EU users (GDPR), California users (CCPA/CPRA), and others retain the right to access, correct, and delete their data — all of which can be done on-device without contacting us.
BookHive uses AES-256-GCM (a widely-reviewed authenticated encryption algorithm) to protect book content at rest. The app verifies its own JavaScript code at launch using SHA-256 hashes to detect tampering. No system is ever 100% secure, however; you remain responsible for the physical security of your device and the credentials of any Google account linked to the app.
If we materially change how the app handles data, we'll update this policy and bump the "Last updated" date at the top. For significant changes (e.g. introducing a server we control), we'll notify you in-app before the change takes effect.
Eassist
Email: oneshop.laoang123@gmail.com
Website: eassistph.com
For privacy-related questions, please include "BookHive Privacy" in the subject line.