1 Data Controller
The Application is developed and managed by the developer of Seb7a. For any questions related to this policy, you can contact us using the address provided at the end of this document.
2 Data Collected
Automatically Collected Data
| Data | Source | Use |
|---|---|---|
| App Instance ID (unique per installation, anonymous) | Firebase Analytics | Functional Analytics |
| Usage statistics (screens visited, sessions, events, duration) | Firebase Analytics | Analytics Promotional |
| Device type, OS version, language, country | Firebase Analytics | Analytics |
| IP address (truncated by Google, used only to infer country) | Firebase Analytics | Analytics |
| Anonymous app-open counter increment (no user ID or device ID attached) | Firebase Firestore | Analytics |
| FCM topic subscription (public broadcast channel, managed by Firebase) | Firebase FCM | Functional |
| Crash reports and error traces | Firebase Crashlytics | Technical |
| Application integrity signal | Firebase App Check | Security |
Data Stored Locally on Your Device
The Application uses GetStorage (a local key-value store) to persist data on your device only. This includes:
- App preferences and settings (theme, language, notification schedules)
- Dhikr counters and session history
This data never leaves your device and is not transmitted to any server. It is deleted when you uninstall the Application.
Data NOT Collected
- First name, last name, email address, or phone number
- Precise GPS location
- Contacts, photos, or files on your device
- Payment data
- User account or authentication credentials (no login system)
- Individual FCM push token (not stored by the developer)
3 Services and Libraries Used
Firebase services are operated by Google LLC (United States). Data may be processed on servers located outside your country of residence.
4 Purposes of Processing
Technical and Functional Purposes
- Ensure proper functioning and stability of the Application
- Detect and fix errors and crashes (Crashlytics)
- Protect the Application against fraudulent use (App Check)
- Store app preferences and dhikr data locally on your device (GetStorage)
- Schedule and display local dhikr reminders (flutter_local_notifications)
- Display a floating overlay for quick dhikr access without leaving your current app (flutter_overlay_window)
- Send reminders and notifications related to app usage (dhikr) via FCM
Promotional Purposes
- Send broadcast push notifications to all subscribers via an FCM public topic (e.g., feature announcements, seasonal reminders)
- Analyze aggregated usage statistics (Analytics) to understand global usage trends and improve promotional messaging
- Measure the effectiveness of broadcast notification campaigns
5 Legal Basis for Processing
| Processing Activity | Legal Basis |
|---|---|
| Stability, security, Crashlytics, App Check | Legitimate interest |
| Usage statistics (Analytics) | Legitimate interest (data is anonymous and aggregated, no individual profiling) |
| Local notifications and reminders (flutter_local_notifications) | Consent (notification permission, requested at first use) |
| Broadcast push notifications via FCM public topic | Consent — revocable via Android notification settings or by uninstalling |
| Sharing aggregated anonymous statistics with advertising/analytics partners | Legitimate interest (data is strictly anonymous and aggregated, no individual can be identified) |
| Overlay window (flutter_overlay_window) | Consent — user explicitly grants "Draw over other apps" permission in Android settings |
6 User Rights
The Application does not use any authentication system and does not store any user identifier (UID, FCM token, or account) on its servers. Because no individual user data is held by the developer, there is nothing to access, rectify, or export on a per-user basis.
Analytics data collected by Firebase is anonymous and aggregated.
Uninstalling results in:
- Invalidation of your FCM token (push notifications will no longer be sent)
- Cancellation of all locally scheduled notifications (dhikr alarms)
- Deletion of all locally stored data (GetStorage: preferences, dhikr counters, settings)
- Removal of any active overlay window
Note: Anonymous analytics data (App Instance ID, usage events) may persist on Firebase servers after uninstall, as it is managed by Google/Firebase. Since no personally identifiable data is stored, there is nothing further to delete from the developer's side. For Firebase data managed by Google, refer to Firebase's privacy policy.
7 Data Sharing and Transfer with Third Parties
Usage and crash data is transmitted to Firebase services operated by Google LLC (United States) for the purposes described above. This data is subject to Google's privacy policy.
Aggregated and anonymous statistics — such as total app opens, feature usage frequency, country distribution, and device types — may be shared with or sold to third-party advertising or analytics partners for commercial and promotional purposes.
This data is strictly aggregated and anonymous: it reflects population-level trends and cannot be used to identify, contact, or track any individual user. No UID, FCM token, device identifier, name, email, phone number, or precise location is included in this sharing.
8 Permissions Requested
- INTERNET — required for Firebase synchronization (Analytics, Firestore, FCM, Crashlytics, App Check).
- POST_NOTIFICATIONS (Android 13+) — for both locally scheduled reminders (flutter_local_notifications) and server-sent notifications (FCM), including functional and advertising messages. You may refuse or revoke this permission at any time from your device settings.
- SYSTEM_ALERT_WINDOW ("Draw over other apps") — to display the floating dhikr overlay while using other apps (flutter_overlay_window). This permission is optional and must be explicitly granted by the user via Android settings. Denying it disables the overlay feature only.
- SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM (Android 12+) — to schedule precise dhikr reminders using the local notification system.
- RECEIVE_BOOT_COMPLETED — to reschedule local notification alarms after the device restarts, so reminders are not lost.
9 Data Retention Period
Anonymous analytics data (App Instance ID, usage events, device info) is retained by Firebase according to its own retention policies (typically up to 14 months for Analytics). The developer does not store any user data on its own servers, so there is no developer-side retention period to report.
Firebase may apply its own retention periods in accordance with its privacy policy.
10 Changes to This Policy
We reserve the right to update this privacy policy at any time. In case of changes, the “Last updated” date at the top of this document will be modified. We encourage you to review this page regularly. Continued use of the Application after any change constitutes acceptance of the updated policy.
📬 Contact Us
For any questions:
Application: Seb7a
Email: fahdboudakim@gmail.com
Data deletion request: fahdboudakim@gmail.com
Developer: Fahd BOUDAKIM
See also: Terms of Service