Privacy Policy — AMAL.in

Djie Development Studio built the AMAL.in ("the App", "we", "us") is a daily worship companion Free app for Muslims. This policy explains what data we collect, why we collect it, and what rights you have over it This SERVICE is provided by Djie Dev Studio at no cost and is intended for use as is. 

By using the App, you agree to this policy.

1. Quick Summary

• The App is fully usable without an account (Guest mode). In Guest mode, all your data stays on your own device.

• We do not sell your data to anyone.

• We show no ads and use no advertising trackers.

• We use Firebase Analytics and Firebase Crashlytics to see which screens people use and to be told when the App crashes. We do not use them to build an advertising profile of you.

• Your location is used only to calculate prayer times and Qibla direction.

2. Data We Collect

2.1 Account data (optional — only if you sign in)

If you choose to sign in with Google Sign-In, we receive the following from Google:

• Display name

• Email address

• A unique account identifier (User ID)

We never receive or store your Google password.

2.2 Worship and activity data

The App stores data you create yourself inside the App, including:

• Amal/habit list and its completion history

• To-do list

• Daily prayer checklist

• Prayer notification settings

• Qur'an bookmarks and favourites

• Daily activity log

• Tasbih counts and dhikr progress

• Nickname, language preference, Arabic font, chosen reciter, and week start day

Guest mode: this data is stored only locally on your device and is not sent anywhere.

2.3 Location data

The App requests location permission (while the app is in use) in order to:

• Calculate prayer times for your position

• Determine the Qibla direction

Your coordinates are sent to a third-party prayer time provider (see Section 5) solely to retrieve prayer times. We do not store location history and do not track your location in the background.

You may decline the location permission. The App remains usable, but prayer times and Qibla direction will be unavailable or must be set manually.

2.4 Device data

For prayer reminders, the App reads your device time zone and uses notification and scheduled-alarm permissions. All notification scheduling happens on your device.

2.5 Data we do NOT collect

• Contacts, calendar, photos, microphone, or camera

• Passwords or payment information

• Browsing history outside the App

• Biometric data

2.5 Analytics and crash reporting

The App includes two Google Firebase SDKs that report back to us:

Firebase Analytics records which screens you open and Google's standard automatic events (app opened, app updated, first open, session start). We do not log any custom event and never attach the content of your worship data — your amal entries, to-do items, dhikr counts, and bookmarks are never sent to Analytics. Analytics identifies your installation with a randomly generated app-instance ID, not your name or email. On Android, the Google Analytics SDK may also read your device's advertising ID (GAID); we do not use it for advertising, profiling, or audience targeting.

Firebase Crashlytics sends us a report when the App crashes or hits an unexpected error. A report contains the error message, the stack trace of the code that failed, and technical device information (device model, operating system version, app version, language, available memory and storage, and whether the app was in the foreground). It also carries a randomly generated Crashlytics installation ID. We do not attach your name, email, or account ID to crash reports, and the content of your worship data is not included.

Both are used only to keep the App working and to decide what to improve. Neither is used for advertising, and neither is shared with a data broker or ad network.

2.6 Data we do NOT collect

• Contacts, calendar, photos, microphone, or camera

• Passwords or payment information

• Browsing history outside the App

• Biometric data

• The content of your worship data in analytics or crash reports (see Section 2.5)

• Advertising identifiers on iOS (IDFA) — the App never asks for App Tracking Transparency permission and does not track you across other apps or websites

3. Log Data

We do not maintain our own application log of your activity. Two other kinds of log exist:

Analytics and crash logs. As described in Section 2.5, Firebase Analytics and Firebase Crashlytics send screen-view records and crash reports to Google's Firebase servers, where we can read them. They are tied to a random installation identifier, not to your identity.

Server logs at our providers. Whenever the App makes a network request, the server that receives it keeps standard technical logs. This is normal server behaviour and applies to any internet-connected app. These logs may include:

• Your device's IP address

• The date and time of the request

• The endpoint requested (for example, "prayer times for these coordinates")

• Basic client information such as operating system and app version

• Error and diagnostic information if a request fails

Requests are made to the services listed in Section 5. These logs are held by those service providers under their own retention policies, not by us, and we do not use them to build a profile of you.

4. Cookies

The App is a native mobile application. It does not use cookies, web beacons, or similar browser tracking technologies inside the App itself.

The App stores small settings values locally on your device (for example, your chosen language, reciter, and Arabic font) using the operating system's own preference storage. This is local device storage, not a cookie, and it is never transmitted to us or to anyone else.

5. Service Providers