MyNamaz: Salat Learning — Privacy Policy

This policy explains how MyNamaz: Salat Learning and its publisher handle information when you use the app and its website. You can contact the MyNamaz team through our support form.

Your practice on your device

Prayer journal entries, selected city, prayer settings, reading position, bookmarks, saved readings, guide progress, dhikr counts, recall history and personal study collections are stored on your device. We do not upload these records to our practice service. You can export them from Settings → Your data. Files you choose to share then follow the privacy practices of the destination you select. Temporary export copies can be removed in the app; copies older than 24 hours are cleared the next time you open the export screen or export again.

Location permission is optional. Coordinates and compass readings are used on your device for Qibla direction and prayer calculations, without being sent to our practice service. You can select a city instead. Notification permission lets the app schedule prayer reminders on your device. You can change either permission in your device settings. The app checks whether WhatsApp is installed only to decide whether to show its first-launch rating invitation; it does not read your messages or contacts.

Optional AI explanations

The first time you request AI help, we ask permission to send the selected public prayer-guide step and the type of explanation you choose. We do not send your journal, precise location, bookmarks, personal study collection names or account credentials to an AI model. AI is optional; the core guides and other main tools remain available without it or a subscription.

With your permission, Firebase Authentication creates an anonymous account. Our service stores an anonymous owner identifier, an installation identifier, a public verification key, request identifiers, guide-step references, request status and usage counters. These records authenticate your requests, prevent replay and abuse, and enforce the free AI allowance. The private installation key stays in your device's secure storage. Firebase App Check uses Apple App Attest or Google Play Integrity to check that requests come from our app. These providers process app and device attestation information.

Our server sends the public guide text to OpenRouter, which routes it to an OpenAI model or a Google model when the configured fallback is available. Requests require zero-data-retention provider routing and prohibit provider training/data collection. The service returns an unavailable message if a compliant route cannot answer. This routing policy does not mean that our own request and abuse-prevention records are absent. See OpenRouter's retention explanation.

Ordinary request records are scheduled for removal after 30 days. If you report an AI answer, we store that answer, your selected reason and associated request metadata for review for up to 90 days. Cleanup runs hourly while the service is operating and catches up after interruptions. Usage counters expire after their period is more than 100 days old; replay records expire after one day.

Delete or export your AI data

Settings → Your data offers AI data export, withdrawal of AI permission and Delete AI account and data. Deletion requires a connection, deletes your service request/report records, deletes the anonymous Firebase account and clears the local AI identity. If a step cannot be confirmed, the app says so and lets you retry. Using AI afterward requires permission again and creates a new anonymous account.

We retain a minimal record of the retired installation, its public key and owner association to prevent old signed requests reopening deleted data. These security records remain while necessary to reject replay. Existing abuse counters expire on the schedule above. Withdrawing AI permission stops future requests but does not by itself delete previous records. Local reading and practice records are kept when you delete the AI account.

You can also request deletion without reinstalling the app. Open our support form, use “Delete MyNamaz account” as the subject, and include the install ID from your AI export if you have it. Never send a password or private key. We may need additional information to establish which anonymous account is yours. The same form accepts access, correction and other privacy requests. Deletion does not cancel a store subscription; manage billing in Apple or Google subscription settings.

Optional usage and crash reporting

Usage analytics and crash reporting are separate choices in Settings → Your data. Both start off. Neither is required for the app's main features, AI allowance or purchases. You can change each choice at any time. If the SDK cannot confirm the change, the app shows an error and a retry action.

When enabled, Google Analytics for Firebase receives general events such as opening a feature, completing onboarding, saving progress, viewing an offer and purchase or restore outcomes. Events use feature categories, not your reading selections, journal text, chosen city, AI text or transaction IDs. The SDK also processes app-instance identifiers, app/device information and automatic usage events; Google can derive an approximate region from an internet connection. Advertising identifier collection, advertising storage, advertising personalization and advertising-user-data consent are disabled. We do not use this information to target advertisements.

When enabled, Firebase Crashlytics receives technical crash information, stack traces, app/device details and diagnostic installation identifiers. App-authored error messages are reduced to error categories to avoid including private content. Google describes a 90-day retention period before removing Crashlytics records. Analytics data follows the linked Google Analytics retention settings. See Firebase's privacy information.

Turning usage sharing off stops our new events, disables SDK collection, denies analytics storage and resets local Analytics data. Turning crash sharing off disables collection and discards unsent reports. These actions do not retroactively remove already received provider records. Use the support form for questions or requests concerning those records. A small diagnostic history used to explain AI errors stays on your device and contains error codes and times, not credentials or AI content.

Purchases, online content and website support

Apple and Google process payments and manage subscriptions under their own policies. MyNamaz reads store product and entitlement information to show accurate terms, unlock optional study-collection editing and restore existing purchases. We do not receive your card number. Main app workflows remain free.

Playing or downloading Quran recitation contacts the Islamic Network audio CDN. Refreshing daily content contacts our service, which retrieves the existing content feed. Hosted onboarding, paywalls, public pages and our API are delivered through Cloudflare. Online services necessarily receive network information such as your IP address and user agent for delivery and security. This is separate from optional app analytics. Downloaded recitation can be removed without deleting Quran text or bookmarks.

If you submit our support form, we receive your message, reply address and any name or subject you enter. The form stores your submission and sends it to our support mailbox so our team can respond. Do not include sensitive information that is unnecessary for your request. You can request deletion of support correspondence through the same form, subject to records needed to resolve the request or comply with applicable obligations.

Service providers and your choices

We use the providers described above to operate, secure and improve the functions you choose. They may process information in countries outside your own. We do not sell your personal information. We may disclose information when necessary to comply with law, address abuse or protect users and the service. Your applicable law may give you rights of access, correction, deletion, restriction, portability or complaint to a data protection authority; contact us through the support form to exercise them.