Seb7a
Privacy Policy
Last updated: June 23, 2026
This privacy policy applies to the Seb7a mobile application (hereinafter the “Application”) published on the Google Play Store. It describes what data is collected and how it is used. The Application does not require any user account, does not store any user identifier on its servers, and does not perform individual user targeting.

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

🔒 No user account required. The Application has no login or authentication system. No name, email address, phone number, or individual identifier is collected or stored by the developer.

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
No user identity stored on our servers. The Application does not use Firebase Authentication. No user identifier (UID), FCM token, or personal data is written to Firestore or any database by the developer. Notifications are sent to a public broadcast topic — not to individual users.

Data Stored Locally on Your Device

The Application uses GetStorage (a local key-value store) to persist data on your device only. This includes:

This data never leaves your device and is not transmitted to any server. It is deleted when you uninstall the Application.

Data NOT Collected

3 Services and Libraries Used

📊 Firebase Analytics
Collects anonymous usage statistics (screens visited, sessions, events, duration, device type, OS version, country). This data is used to understand how the Application is used and to inform promotional strategy (e.g., which features to highlight, when to send broadcast notifications). No individual user profiling or behavioral ad targeting is performed.
Firebase Privacy Policy →
🗄️ Firebase Firestore
Cloud database used to store app content and configuration (e.g., dhikr texts, app settings) and to record an anonymous app-open counter. Each time the app is launched, a single number is incremented in Firestore with no user identifier, device ID, or any personal data attached. This counter is used solely to track the total number of app opens for statistical purposes.
Firebase Privacy Policy →
🔔 Firebase Cloud Messaging (FCM)
Sends push notifications using a public broadcast topic. The Application subscribes to a shared topic; notifications are sent to all topic subscribers at once — not to individual users. The individual FCM device token is managed entirely by Firebase/Google and is never stored or accessed by the developer.
Firebase Privacy Policy →
💥 Firebase Crashlytics
Automatic detection of crashes and technical errors. Reports include device model, OS version, app version, and a stack trace. Used exclusively to improve app stability — no use for promotion or targeting.
Firebase Privacy Policy →
🛡️ Firebase App Check
Verifies that requests to Firebase services come from the genuine Seb7a app, protecting against abuse. No personal data is collected and no use for promotion or targeting.
Firebase Privacy Policy →
🔔 Flutter Local Notifications
Schedules and displays notifications locally on your device (e.g., dhikr reminders). No data is sent to any server. All scheduling logic runs entirely on-device.
🪟 Flutter Overlay Window
Displays a small overlay (floating widget) over other apps, allowing you to access dhikr features without switching apps. Requires the "Draw over other apps" permission granted by you. No data is collected through this feature.

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

Promotional Purposes

No individual targeting. Promotional notifications are sent to a public topic shared by all users — not based on individual behavior, profile, or stored token. No user segmentation is performed by the developer.

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:

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

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