Privacy Policy

1. Controller and scope

This policy explains personal data processing in the Hanafi Guide app, its server services and hanafi-guide.ru. The controller is ООО «БЛЦ» (BLTs LLC), Russian taxpayer identification number (INN) 1658257832, primary state registration number (OGRN) 1261600023475. Contact: info@hayrat.digital.

This policy covers app and website users, associated account holders and people contacting us. The controller follows applicable Russian law, including Federal Law No. 152-FZ on Personal Data. This policy provides information and does not itself replace consent where consent is required by law.

2. Use without an account and on-device data

Prayer schedules, learning materials and many tools work without sign-in. Your device may store a selected locality, preferences, saved materials, downloaded audio, reading and dhikr progress, missed prayer and fasting records, and zakat calculations. The actual data depends on the features you use and the information you enter.

Calculation inputs may include your birth date, the date religious obligations began, missed and exempt periods, completion records, and amounts and categories of assets, liabilities and payments. Do not enter other people’s names, medical diagnoses or information unnecessary for a calculation. Uninstalling the app may not delete a previously synchronised server copy. Device backups are also governed by your Apple or Android settings and the selected backup provider’s terms.

3. Account and synchronisation

If you choose to sign in with UmmaID, the server receives a user identifier, name, email address and email verification status. These identify your records, display your profile and provide authentication and access protection. Hanafi Guide does not receive your UmmaID password.

When using synchronisation, account-linked documents for missed prayers, missed Ramadan fasts, zakat calculations and dhikr progress are sent to the server. These documents can directly or indirectly reveal religious beliefs; some periods or notes entered by you may reveal health information. Processing special categories of personal data requires a separate lawful basis. Where the law requires separate consent, it must be obtained separately. Accepting the Terms of Use does not replace that consent.

Signing out ends the current session; it does not delete an account or server records. UmmaID is a separate identity service and also processes data under its own documents. Deleting Hanafi Guide data does not itself delete an UmmaID account.

4. Separately enabling synchronisation

The controller configures the synchronisation mode. When separate consent is required, the app shows a standalone document with an initially unchecked control and the server blocks cloud documents until the current version is accepted. When that mode is disabled, account records synchronise after sign-in without a separate agreement prompt. This is not recorded as consent given by the user. A personal sync opt-out remains effective regardless of the global mode; local use remains available.

A consent record contains the account identifier, document version and SHA-256, time, platform and decision. Administrative policy changes and personal enable/disable actions without an agreement are recorded separately and never substitute for consent. Withdrawing consent in account settings deletes cloud documents while retaining local records. The sign-in profile remains until account deletion. Consent events are retained for the account lifetime and deleted with it. Technical electronic confirmation does not remove the controller’s obligation to establish the legally required form and lawful basis for special-category processing.

5. Notifications and technical data

After you permit notifications, the server may receive an APNs token on iOS or a Firebase Cloud Messaging (FCM) token on Android, installation identifier, language, delivery environment, selected locality and reminder preferences. Dhikr reminders also use the chosen schedules, time zone and completion information needed to suppress reminders for completed activities. A device subscription may operate without an account.

Network infrastructure processes an IP address, request time and path, technical headers, response status and error information as needed to deliver content, operate the service and prevent abuse. Session credentials are used to check access. Advertising personalisation and selling user data are not processing purposes.

6. Location, audio, enquiries and payments

Location and sensor readings are requested for Qibla direction with operating-system permission. The direction is calculated on-device; precise coordinates for this calculation are not sent to the Hanafi Guide API. Opening the map can involve processing coordinates and network information by Apple Maps on iOS or Google Maps on Android under their terms. You can withdraw location permission in iOS or Android settings.

Surah audio is downloaded from Yandex Object Storage. The provider can technically receive your IP address and request details, including the audio URL. Calculation documents and profile information are not included as audio URL parameters.

Requests for missing prayer schedules are stored on the server and may contain a locality, region, year, source URL, comment and technical installation identifier. The support form processes your name, email, optional phone, selected or custom subject and message. The database stores messages, staff replies, statuses, status changes and the version and date of consent for handling the enquiry. New tickets created after sign-in are account-linked; guest tickets are accessible through a protected installation credential. If you email us, we process your address and correspondence to respond and resolve the enquiry.

Project support is voluntary. The SBP button opens an external payment page. Bank details, authorisation and payment information are processed by the payment infrastructure and your bank under their documents. The app does not request a card number, bank password or authorisation code. Opening the link does not confirm a payment.

7. Purposes, legal bases and operations

Processing purposes are to provide requested features and synchronisation, authentication and notifications, respond to enquiries, maintain operation and security, and meet legal obligations. Bases include performing the user agreement, complying with law, consent where required, and other applicable grounds under Article 6 of Federal Law No. 152-FZ.

Processing is automated and, for enquiries, may be manual. Operations include collection, recording, organisation, accumulation, storage, updating, retrieval, use, disclosure to authorised providers, restriction, deletion and destruction. Data is not intended for public dissemination. Refusing optional permissions may limit the related feature without requiring you to stop using the entire app.

8. Recipients, retention and security

Individual functions use UmmaID, Apple (APNs, permissions and maps on iOS), Google (Firebase Cloud Messaging, location services and maps on Android), Yandex Object Storage, hosting and payment providers. They receive the information necessary for the relevant function. Data may be provided to public authorities upon a lawful request. Using providers does not remove the controller’s personal data protection obligations.

The Hanafi Guide server database is hosted in Russia. External services apply their own processing rules; data localisation and cross-border transfer requirements must be observed separately. This policy does not imply that every external service processes all data exclusively in Russia.

Account data and synchronised records are retained while necessary for the selected functions, until a justified deletion request, or until another legal ground for stopping processing arises. Sessions expire, and sign-out revokes the relevant session. Enquiries and technical records are retained within their response, security and statutory purposes. When a purpose or lawful basis ends, processing stops and data is deleted or anonymised within statutory deadlines; a legal retention obligation takes priority.

Measures include access controls, authentication, HTTPS, restricted database network access and backups. Backup copies may retain data until the relevant copy is deleted or overwritten and are not intended for routine processing. Data subject to deletion must not be restored to active processing after recovery. Absolute security of any information system cannot be guaranteed.

9. Your rights and deletion

You may request information about processing, correction, restriction or deletion, withdraw consent where it is the basis for processing, and complain to Roskomnadzor or a court, subject to statutory limitations.

Email info@hayrat.digital with the subject “Hanafi Guide personal data”, your account email and your request. Explicitly state if you want your Hanafi Guide account and its server records deleted. Proportionate account ownership verification may be requested; do not send passwords, login codes or banking information. Responses and action are provided within applicable statutory deadlines.

On-device content can be removed through available app controls, including downloaded audio management. Notification and location permissions can be changed in iOS or Android. These actions alone do not delete server data or your separate UmmaID account.

10. Changes and contact

The current version is published on this page with its update date. Where the law requires separate consent or notice for a material change, merely publishing a revision does not replace it. Controller contact: ООО «БЛЦ», INN 1658257832, OGRN 1261600023475, info@hayrat.digital.

11. Deletion in the app and on the web

In Settings, Account, Delete Hanafi Guide account, confirm deletion without contacting support. The server deletes the Hanafi Guide profile, cloud documents, consent events, account-linked support threads and all server sessions. Following server acknowledgement, the current device removes this account’s local copy. While acknowledgement is pending, synchronisation is paused and deletion can be retried. An irreversible digest of the used access token, without name, email or account identifier, allows acknowledgement retries for 60 days. Expired digests are cleared on subsequent deletion operations.

The separate UmmaID identity, guest records, shared downloaded materials and offline copies on other devices are not deleted by this action. Anonymous notification subscriptions and guest support requests belong to an installation and may be managed or requested separately. System permissions can be withdrawn in device settings.

If the app is unavailable, visit https://hanafi-guide.ru/en/delete-account/ and email info@hayrat.digital with your account email. Support verifies ownership without disclosing account existence to third parties and fulfils verified requests without undue delay within statutory deadlines. Restricted backups may retain data until deletion or overwrite and are not available to the app. Recovery must reapply completed deletion requests; a backup is not a basis to resume processing deleted data.