1. Introduction

Welcome to Haseen, an app locker designed to help protect access to selected applications on your device.

This Privacy Policy explains how the app handles information related to its functionality and your use of the service.

2. Data Handling

Haseen does not collect or transmit personal data to external servers.

All data related to the app’s core functionality is processed and stored locally on your device only.

• PIN Code: Stored locally in encrypted form.
• Recovery Code: Randomly generated and securely stored on the device.
• Protected Apps List: Used only to provide app-lock functionality.
• Security Event Log: Such as failed unlock attempts, stored locally only.
• User Preferences: Such as language and certain internal settings.

3. Internet Usage & Third-Party Services

The app does not rely on internet access for its core lock functionality. However, it uses the following services that may require internet access:

• Google AdMob: Used to display ads (banner, interstitial, rewarded, app open). Google may collect non-personal information such as the advertising ID to personalize ads. You can manage ad preferences in your device's Google settings.
• Firebase Crashlytics: Used to automatically report technical crashes to improve app stability. No personal data is sent — only technical error info and device type.
• Firebase Analytics: Used for general usage insights (e.g., app opens). No protected app names or sensitive data are transmitted — apps are classified by category only (social, finance, etc.).
• Firebase Remote Config: Used to update app settings remotely without requiring a full update.

4. Permissions Used

The app may request certain permissions directly related to app protection:

• Usage Stats: Used to detect which app is currently in the foreground so the lock screen can be triggered when needed.
• Display Over Other Apps: Required to securely display the lock interface over protected applications.
• Query All Packages: Used only to display installed apps so the user can choose which apps to protect.
• Accessibility Service: Used only as a support or backup protection layer for protected apps. It is not used to read user content, collect personal data, or track user activity.
• Boot Completed: Used to restart protection after device reboot.
• Foreground Service: Used to keep the protection service running.
• Biometric Authentication: Used to provide fingerprint-based unlock if enabled by the user.
• Device Admin: An optional feature used to help prevent app removal without verification. It can be disabled at any time from system settings.

5. Data Sharing

Lock data, passwords, and protected app lists are never shared with anyone.

The app uses the following Google services that may collect non-personal technical data:

• Google AdMob — to display ads (advertising ID, device type)
• Firebase Analytics — general usage statistics (no sensitive data)
• Firebase Crashlytics — technical crash reports only

6. Data Security

The app uses strong local security measures, including:

• Local AES-256-GCM encryption
• Key management through Android Keystore
• Hardware-backed protection where supported
• Code hardening using R8 / ProGuard

7. User Rights

• You can delete app data by uninstalling the app.
• You can revoke permissions at any time from device settings.
• You may review or clear the security log from داخل التطبيق if that feature is available.

8. Children’s Privacy

The app is not directed to children under the age of 13 and is not designed to collect data from children.

9. Compliance

This policy is written to support compliance with Google Play requirements and Android security best practices.

10. Contact

• 📧 Email: eissa.developer@gmail.com
• 💬 WhatsApp: +967 775 346 074
• 💼 LinkedIn: Eng. Eissa Al-Gumaei

11. Changes to This Policy

This Privacy Policy may be updated from time to time. Any updates will be posted on this page along with the revised last updated date.