Your practice is personal.

1. Who is responsible

Noor Technologies Ltd, trading as Mus’haf, is responsible for information received through its support and services.

Unit 404, Daisyfield Business Centre, Appleby Street, Blackburn, United Kingdom, BB1 3BL

Company number: 17520809

There is no Mus’haf account system or server holding your reading or memorisation profile. Google, Apple where applicable, audio providers and website hosts process information under their own terms when you use their services.

2. Information on your device

The app stores bookmarks, favourites and groups, reading position, settings/layout, Hifz statuses, planner/revision history, notes where present and practice recordings you choose to make. These records provide the features you request. Microphone permission is used for your recording action, not passive listening.

Downloaded recitations are stored separately. Reading selections, Hifz activity and personal usage are not sent to Mus’haf for behavioural analysis. Local records can be edited or deleted through relevant app controls. Clearing app storage or uninstalling may remove local data, subject to system backup/device-transfer behaviour; this does not revoke a purchase or necessarily delete a Drive backup.

3. Trial and store purchases

The 14-day trial begins on the first successful launch. Local first-launch and elapsed-time records help prevent casual clock resets. A trial anchor may be included in Android system backup/device transfer. No IMEI, device serial, advertising identifier or tracking account is used for trial administration.

Google Play handles Android checkout and payment details. The app receives purchase status and signed purchase information needed to verify and acknowledge the one-off unlock. Confirmed entitlement is stored locally with encryption so it can work offline; ownership is refreshed with Play when available. The app does not receive your payment-card number.

The planned iOS version is intended to use App Store purchases. Apple would handle checkout and account ownership; the final receipt/entitlement implementation and policy will be confirmed before iOS launch. There is no claim that an Android purchase transfers to iOS.

Trial and purchase state are excluded from Drive backups. Restoring a backup does not restart the trial or transfer a purchase to a different account. Reading, navigation, bookmarks, basic favourites, settings and last-read restore remain free after trial expiry.

4. Optional Google Drive backup

Drive sign-in is optional, not a condition of reading, starting the trial or purchasing. If you choose backup, the app requests access to its private application-data area in your own Google Drive. It does not use a shared Mus’haf database or request general access to browse your other files.

Lightweight reading data comprises bookmarks, favourites/groups, Hifz progress, planner/history, notes where present, settings, layout and last-read position. Archives contain a schema version, app version, timestamps, device model and integrity checksums.

Practice recordings are stored locally by default. The recordings-backup option is off by default; enabling automatic backup does not enable it.

Practice recordings are excluded from Drive backups by default. You can explicitly enable Back up practice recordings in Settings → Access, backup & privacy. This choice is separate from automatic backup. If enabled, saved practice recordings are included with the backup in your own Google Drive and may use significant space from your Google Drive allowance. The app shows an approximate size for recordings on your device. Leaving this option off keeps backups lightweight. Turning it off does not delete recordings already on your device or remove recordings from earlier Drive backups.

Downloaded recitation audio, reciter cache, trial state, purchase entitlement, diagnostics and review/test data are excluded. Manual backup runs when requested. Optional automatic backup runs while the Android app is open, after changes and subject to a six-hour attempt interval; it is not continuous background sync. Successful backups are retained separately.

Backups are limited to 512 MB before compression. If a recording-inclusive backup is too large, you can turn recording backup off and back up normal app data. A failed backup does not delete your local recordings.

The app offers the latest matching backup. Before downloading it, you choose whether to restore normal app data only or also practice recordings, where the backup contains them. Recording restore is off by default. The app shows the archive download size when available; older backups may have an unknown size. A combined archive is downloaded in full even if you skip restoring recordings, so it may be large. You can cancel before downloading. A further confirmation is required before replacing local app data, with a warning if local data is newer. Skipping recording restore preserves your existing local recordings and recording settings. Choosing recording restore replaces local recordings with those in the backup; records are not silently merged. Authorisation, network or full-Drive failures do not remove local data or recordings.

Google Drive sign-in and backup are optional. Normal app use does not depend on Drive. Network failure, full Drive storage, authentication failure or Drive errors do not remove local app data or recordings. You can continue using local data and recordings without Drive, including after a failed backup.

Drive transfers use HTTPS and Google authorisation. The archive is not separately end-to-end encrypted by Mus’haf. Google applies its own security and processing terms. Recording backups may consume significant space from your Drive allowance.

Turn automatic backup off to stop future automatic uploads. Revoke access through Google Account connected-app controls. To remove hidden app data, use Drive’s app-management controls where available. Revoking access or uninstalling alone should not be relied upon to delete remote backups. Mus’haf cannot remotely delete a copy held only in your Drive.

5. Audio streaming, downloads and fallback

Streaming and downloading sends a request to the selected approved audio provider. Technical information includes your IP address and requested file; a URL may identify a reciter and Surah. Providers may keep operational logs under their policies. Mus’haf does not use these requests to build a reading profile.

Verified downloads stay in app-private storage and can be removed using audio storage controls without deleting personal reading data. Partial files are not treated as ready for offline playback. An internet connection is needed for streaming or unfinished downloads.

A Cloudflare R2 fallback is planned for when a primary provider fails. It would serve an exact verified copy of the recording; it is not yet configured as a live service. Cloudflare may process request/IP/security information when enabled. Personal backups and purchase data are not uploaded to that audio bucket. Hosting and log-retention details must be confirmed before activation.

6. Diagnostics and support

No third-party behavioural analytics or automatic third-party crash reporting is included at launch. Local diagnostics contain app version, Android version, device model and recent non-sensitive technical error codes/timestamps. They exclude reading selections, Hifz activity and personal usage fields.

Diagnostics are transmitted only when you choose to share them and select a destination. That service handles the shared information under its own terms. If you contact support, the publisher receives what you send: your contact details, message and voluntary attachments. Do not send passwords, payment-card information or private recordings unless necessary and intentional.

7. Retention, purposes and your rights

Local records are kept to provide the requested app features until you remove them or app data is removed. Downloads persist until removed. Diagnostics use a small rolling record. Drive backups may accumulate and remain until you delete them or Google removes them under its terms. Google and Apple control retention of their billing/account information.

The support-message and attachment retention periods are still being finalised and will be stated in the effective policy.

The final policy will identify applicable lawful bases for requested services, optional disclosures and necessary support/security, following review by the publisher. These pre-launch details are not yet finalised.

Subject to applicable law, you may have rights to access, correct, delete, restrict or object to processing, withdraw consent and receive portable copies. You may object to applicable processing of your personal information. Contact the publisher about information it holds. Device and personal Drive data may need to be managed locally or through Google because Mus’haf has no central copy.

In the UK, you can raise a concern with the Information Commissioner’s Office. The final policy must reflect the launch regions and actual processing. Using an optional service does not waive your data-protection rights.

8. Third-party services, transfers and children

Android uses Google Play Billing, optional Google Drive authorisation/storage and Play delivery of essential Mushaf artwork. Audio uses approved external routes, including MP3Quran and the approved Fatih Seferagic sources. Cloudflare provides website hosting and would also apply when audio fallback is activated; Apple applies to a future iOS release.

Providers may process information outside your country. Publisher-controlled service locations, contracts and applicable transfer safeguards remain to be confirmed before launch. See the Google Privacy Policy, Apple Privacy Policy and Cloudflare Privacy Policy.

The app does not ask for a date of birth. The public target audience and children’s privacy statement will be finalised alongside the store declarations before launch. No advertising profiles of children are intentionally collected. Purchases and optional external services are subject to provider account rules.

9. This website

This static website has no account system, database, behavioural analytics, advertising trackers or support form. Its help search runs only in your browser. It does not set analytics cookies or store a reading profile.

This website uses Cloudflare static hosting. Cloudflare may receive ordinary connection information such as IP address, browser details and requested pages to deliver and secure the site. Cloudflare processes hosting and security information under its privacy policy. The publisher’s applicable log-retention arrangements remain under review; no fixed retention period is claimed here. Store and other external links take you to services with their own policies.

10. Changes to this policy

The effective date and published policy will be updated when practices change. Material changes will be explained through an appropriate notice. For support and privacy enquiries, use the contact address shown on this page.