Data safety at a glance
This page gives a simple explanation of Mimber's current data practices. The Google Play Data safety form must always match the exact app version and every third-party SDK included in that release.
Mimber currently works without creating a user account.
No third-party advertising or behavioral ad profiling.
Mimber does not sell or rent personal information.
Notes, bookmarks, downloads, and progress stay on the device.
What may be processed
| Information | Where it goes | Why it is used |
|---|---|---|
| Notes, bookmarks, highlights, reading progress and settings | App-private storage on your device | To provide reading and study features |
| Book or audio download requests and routine technical logs | Content hosting infrastructure | To deliver files, maintain security and diagnose service problems |
| Support message, email address, screenshots or device details you voluntarily submit | Imam & Science support systems | To answer questions, investigate bugs, or process reports |
Permissions and device access
Mimber is designed to use only access needed for reading, downloading content, playing recitations, and storing app data. Android and iOS display permission prompts when an optional device permission is requested. You can review or revoke permissions in your device settings.
Important Play Console note
Before every release, the development team must review the final app bundle, including Flutter packages and native SDKs, and then complete the Google Play Data safety form accurately. Website wording alone does not replace the Play Console declaration.
Questions
For questions about Mimber's data practices, use the Imam & Science support page.