RoyFoundry · Firebrat

Data use & safety

A practical explanation of Firebrat’s data flows. The official Google Play Data safety label is a separate declaration in Play Console.

Account information

Email, user ID and provider-supplied profile information are processed by Firebase Authentication for sign-in/account management. Optional signed-in sync stores private library metadata, Drive backup references/hashes and reading checkpoints in Firestore for cross-device resume. Book bytes stay on the device or in user-owned Drive. Sync can be disabled in Menu → Sync & backup.

App activity, identifiers and coarse location

The Android Firebase Analytics SDK can collect interactions, device/installation or advertising identifiers, app/device information and coarse network-derived location. Messaging uses notification/installation tokens. These support analytics and notifications; there are no advertisements.

Documents, narration and pictures

Local conversion keeps book processing on Android when cloud helper is off. Server mode uploads the chosen document to your configured server. Enabling a cloud LLM helper sends relevant content to that provider. Optional Drive backup stores book packages in your Drive.

Downloaded models and voices

Initial setup contacts model distributors. Models and Kokoro voice data can then run locally. The PWA has no on-device conversion/model-download feature.

Encryption

Google services and the review server use HTTPS. Custom HTTP server addresses are permitted, so encryption cannot be guaranteed for every user-configured server connection.

Deletion

Local books can be deleted in the library. Account/cloud-data and hosted-file removal can be requested through the deletion page. Deleting a local copy does not delete remote copies.

Guest access

Android Continue as guest does not create an authentication account or require an email/password. Account/profile collection is optional because local features and public-shelf downloads work without login. SDK analytics, installation/device identifiers and network-derived approximate location are still covered by the disclosures above. Guest access does not make the app a “no data collected” app. Server conversion uploads remain authenticated. Signed-in cross-device resume uses private Firestore metadata/checkpoints; book transfer uses the user’s Google Drive backup or a shared server. Guests keep checkpoints locally.

Providers and sharing

Data may be processed by Google/Firebase, your chosen server operator, a configured LLM provider, model distributors, and Google Drive when enabled. These operational disclosures are broader than the specific “sharing” categories in Google Play’s form; the app’s published Play label must also account for SDK behavior and applicable service-provider exceptions.

Read the full privacy policy for retention, controls and contact details. This page does not assert that Google has reviewed or approved the app or its declarations.

Source disclosures

Firebase Android data disclosures · Firebase Analytics disclosures