Last updated: October 2026
Sajda (“we”, “our”, or “us”) respects your privacy. This policy explains information handling in the Sajda mobile application, including the services used to operate subscriptions, measure app use and measure campaign referrals.
You do not need to provide an email address or other contact details to use Sajda. An optional onboarding name and your prayer-related answers are stored by the app locally. Sajda uses assigned account, app-installation and device identifiers for service operation and measurement. These identifiers need not contain your name, but they can link activity and purchases to the same account, app instance or device; they should not be understood as completely anonymous.
The app's service and analytics processing includes:
Sajda's app-authored event schema no longer includes individual-prayer names, prayer-history entries, completion or missed-prayer records, prayer streaks, selected calculation methods, prayer-notification interactions, or answers/progression for the prayer-difficulty, missed-prayer and religious-goal questionnaire stages. This describes the reviewed app instrumentation, not a guarantee about arbitrary externally supplied campaign text; separate conditional SDK processing is explained in Section 4. Updating the app does not erase data previously processed by a service or change older installed versions automatically.
The app stores prayer history and editable prayer records on the device. Individual prayer identity, completion/missed state, streak information, prayer/calculation preferences and sensitive onboarding answers remain in the app's local storage; they are not written by Sajda to its Firestore account documents or sent by its app-authored analytics.
Apple's Screen Time, Family Controls and Managed Settings APIs support temporary restrictions on your selected apps. Sajda stores the selection tokens locally, including in the App Group shared with its extensions. The app-authored analytics report selected-app/category counts, not app names or the selected tokens. Sajda does not read the content inside other apps.
Location is used to calculate appropriate prayer times. Sajda stores the calculation coordinates locally and uses Apple's location/geocoding services where applicable. It does not include precise coordinates in its app-authored Firebase, RevenueCat, TikTok or GoMarketMe event/attribute payloads. Apple's own service processing is separate from Sajda's analytics and approximate network-derived geography. The absence of app-authored uploads is not a promise about every conditional third-party screen/text capture path.
Optional subscription plans and any eligible introductory offer are shown in the app before purchase. Apple handles the payment process; Sajda does not receive your payment-card or bank-account details.
RevenueCat processes store purchase/receipt or transaction information, product identifiers, subscription lifecycle and entitlement/customer status so the app can verify purchases, provide access and restore eligible subscriptions. Purchase and subscription information also supports analytics and campaign measurement as described below. A recorded trial checkout or a product's displayed price is not necessarily a paid charge. Cancelling renewal does not necessarily end access immediately.