Overview
Bloox is an audiobook player for iOS. Your privacy is important to us. This policy explains what data the app accesses, how it is used, and what is shared with third parties.
Data Collection
All core app data (your library, playback progress, listening sessions, and transcriptions) is stored locally on your device. Bloox does not collect your name, email, or Apple ID. The exceptions are crash reporting, analytics, and the optional feedback feature described below.
Speech Recognition
Bloox offers an optional transcription feature that converts audiobook speech to text. This processing is performed entirely on your device using Apple’s on-device speech recognition. No audio or transcription data is sent to any server.
Google Drive Access
If you choose to import audiobooks from Google Drive, the app will request access to your Google Drive account. This access is:
- Initiated only when you explicitly sign in
- Used solely to browse and download audiobook files you select
- Handled through Google’s official Sign-In SDK
Bloox does not access, read, or modify any files other than those you explicitly choose to import. Your Google credentials are managed by Google’s SDK and are never stored by the app.
Third-Party Services
Bloox uses the Google Books API to fetch cover art for your audiobooks. Only the book title is sent in these requests — no personal information is included.
Bloox also uses an external service to identify characters in your audiobooks. When this feature runs, the book title and author name are sent to a server to retrieve character data. No audio, transcription content, or personal information is included in these requests.
Feedback
Bloox includes an optional feedback feature that lets you send us comments or suggestions. When you submit feedback, the text you typed and your app version are sent to Firebase Firestore (provided by Google). No personal identifiers (name, email, Apple ID, or device ID) are attached — feedback is completely anonymous. Feedback is only sent when you explicitly tap “Send”; the app never collects or transmits text without your action.
Crash & Error Reporting
Bloox uses Firebase Crashlytics (provided by Google) to collect crash reports and non-fatal error logs. This helps us identify and fix bugs quickly. The data sent to Crashlytics may include:
- Device model, OS version, and app version
- Stack traces and error messages generated at the time of a crash or error
- A random installation identifier (not tied to your identity)
- Audiobook titles associated with the error (e.g., which book was being processed when a failure occurred)
This data is used solely for diagnosing and fixing bugs. It is anonymous — Crashlytics does not collect your name, email, Apple ID, playback history, or any other information that identifies you personally. Book titles are included only to help us reproduce and fix errors affecting specific content. You can learn more about how Google handles Crashlytics data in Firebase’s privacy documentation.
Analytics
Bloox uses Firebase Analytics (provided by Google) to collect anonymous usage data that helps us understand how the app is used and improve it. The data collected includes:
- Feature usage patterns (e.g. which playback controls are used, import sources, transcription usage)
- Aggregate engagement metrics (session duration, screen flows)
- A random device identifier (IDFV — not tied to your identity or shared across apps)
This data is anonymous and aggregated. It does not include your name, email, Apple ID, audiobook content, transcription text, or any information that identifies you personally.
Analytics collection is enabled by default. You can disable it at any time in Settings → Privacy → Share Analytics. When disabled, no usage data is sent to Firebase Analytics.
Bloox does not include any advertising SDKs or cross-app tracking. You can learn more about how Google handles Analytics data in Firebase’s privacy documentation.
Data Sharing
We do not sell, trade, or share any user data with third parties.
Children’s Privacy
Bloox does not knowingly collect any personal information from children.
Changes to This Policy
We may update this privacy policy from time to time. Any changes will be reflected on this page with an updated effective date.
Contact
If you have questions about this privacy policy, please visit our Support page to submit a request.