Account and Data Deletion

Emam (Emam App / Emam AI) is an Islamic companion app for iOS and Android. We give you two ways to delete your account and associated data. The first is built directly into the app. The second is by email. Both methods are described below. As explained in the What gets deleted section, the email request is currently the path that achieves complete server-side erasure, including your stored profile photo and server-side records. Both methods are subject to a small set of items we are required or permitted to keep, which are explained below.

If you used Emam without creating an account (guest mode), you do not have an account to delete, but there is still some device-based data you can clear. See the Guest data section.

You can start deleting your account from inside the Emam app while you are signed in. Follow these steps:

1. Open the Emam app and make sure you are signed in to the account you want to delete.
2. Go to the Account or Settings area.
3. Open Personal Information.
4. Tap Delete Account.
5. Confirm that you want to permanently delete your account when prompted.

For your security, you may be asked to re-authenticate before the deletion can be completed. If you signed in with Google or Apple, you will be asked to sign in again with that provider to confirm it is really you. If you signed in with email and password, you may be asked to enter your password again. This re-authentication step is a safety measure that protects your account from unauthorized deletion.

Once you confirm, the app removes your Firebase Authentication account and your user profile record. Your sign-in credentials stop working, and you will be signed out of the app.

Important: the current in-app Delete Account flow may not remove every item on its own. In particular, it may not delete your profile photo stored in our file storage or call our backend to erase your server-side records. If you want everything removed, including your stored profile photo and server-side records, please use the email request in Method 2, which we treat as the path to complete server-side erasure. We are working to make the in-app flow remove all of these items directly. If, after an email request, you wish, you can confirm full erasure with us at support@emamapp.com.

If you cannot access the in-app option, for example because you can no longer sign in, or if you want to be sure that all of your data is removed, you can ask us to delete your account by email. This email route is the path that achieves complete server-side erasure.

1. Send an email to support@emamapp.com from the same email address you used to register or sign in to Emam.
2. Use the subject line: Delete my account.
3. In the message, briefly confirm that you want your account and associated data deleted.

Sending the request from your account email helps us verify your identity. If we cannot confirm that the request comes from the account owner, we may ask you for additional information before we proceed, so that we do not delete the wrong person's data. After we verify your identity, we will delete your account and associated data within 30 days, and email you to confirm when it is complete.

When your account is deleted, we remove the personal data associated with it, including:

• Your Firebase Authentication account and sign-in credentials (email/password, Google, or Apple link).
• Your profile information stored in our database record for your account (users/{uid}), including your name, email address, phone number, gender, and date of birth.
• Your profile photo stored in Firebase Storage (profile_pictures/{uid}.jpg).
• Your in-app activity tied to your account, such as prayer tracker history, dhikr counts attributed to you, Dua Board posts, saved khutbah summaries, and any Tajweed or voice samples linked to your account.
• Other server-side records linked to your account on the Emam backend (pathway.emam.ai).

A truthful note about how this works today: the in-app Delete Account flow removes your Firebase Authentication account and your database profile record, but it may not yet delete your profile photo in Firebase Storage or call our backend to erase your server-side records. To have those items fully removed, please send the email request described in Method 2. We treat the verified email request as the route that completes erasure of your profile photo and server-side records, and we are updating the app so the in-app flow removes them directly as well.

After deletion, you will need to create a new account if you wish to use account-based features in Emam again. Your previous data will not be recoverable.

In a few limited cases, some information may remain after your account is deleted. This is normal and is kept only for specific reasons:

• Aggregated or anonymized statistics, such as community totals in the global dhikr counter. These figures no longer identify you and cannot be linked back to you.
• Content you already shared publicly that has been de-identified, such as Dua Board posts where your name has been removed (see the next section).
• Records we are required to keep for legal, accounting, safety, or security reasons, for example to comply with the law, prevent abuse, or resolve disputes.

Any data we retain is kept only for as long as the relevant purpose or legal obligation requires, and then it is deleted or further anonymized. We do not keep your personal data longer than necessary. Copies of your data held in routine backups by our service providers are removed on the normal backup cycle after deletion, after which they are overwritten or purged.

The Global Dua Board is public community content. Dua requests you post there (up to 200 characters) are visible to Emam users around the world, who can tap Ameen and share them. Because others may have already seen, responded to, or shared these duas as part of the shared community experience, your Dua Board posts are not automatically removed when you delete your account. Instead, they are de-identified, meaning your name and account link are removed so the post is no longer connected to your identity.

If you want a specific Dua Board post fully removed rather than only de-identified, email us at support@emamapp.com with details that help us locate the post (for example the text of the dua and roughly when you posted it). We will review the request and remove the post where appropriate, in line with our moderation policy.

If you use Emam as a guest, without signing in, you do not have an account. To attribute guest activity such as contributions to the global dhikr counter and Dua Board participation, the app uses a device ID that is generated and stored only on your device (in local storage).

Because this identifier lives on your device, you can clear guest data by clearing the app's local storage or uninstalling the app, which removes the stored device ID. Note that contributions already reflected in community totals (such as the aggregate dhikr count) stay part of those anonymized totals and cannot be individually removed, because they no longer identify you. If you posted a dua to the Global Dua Board and want it removed, contact support@emamapp.com as described above.

Both in-app deletions and verified email deletion requests are completed within 30 days. In-app deletions begin as soon as you confirm and complete any required re-authentication. Email deletion requests are processed within 30 days after we verify your identity, and we will send you a confirmation when the deletion is complete. Copies held in routine backups by our service providers are removed on the normal backup cycle, after which they are overwritten or purged. Remember that the verified email request is the route that completes erasure of your profile photo and server-side records.

If you have any questions about deleting your account or about what happens to your data, you can contact us at support@emamapp.com or through the in-app live chat support (Crisp).

Important: deletion is permanent. Once your account and data are deleted, they cannot be restored. If you are not sure, consider signing out instead of deleting. Emam is not directed to children under 13, or under the minimum age of digital consent in your region if that age is higher. This page is provided by [LEGAL ENTITY — to be confirmed by Emam] and is governed by the laws of [GOVERNING-LAW JURISDICTION — to be confirmed by Emam].