Alkhaliq / MSX

Privacy Policy

Last updated: 2026-10-18

This policy explains how the Alkhaliq / MSX service team handles information for Quran reading and listening, device identity, optional audio sharing and official package sharing on supported platforms.

Device identity and compatible accounts

New versions can use a device identity without an email or Apple account. We register the public key, derived node identifier and platform to authenticate the device and account for verified sharing. The private key stays on your device. The account methods below describe legacy versions and compatible sessions. Email registration sends your username, email and password over HTTPS to msx.muslimwww.com to create and authenticate your account. Sign in with Apple provides an Apple account identifier, authentication information and, when Apple makes them available, your name and email or relay email. Our services process account IDs, authentication tokens, a device identifier and platform to sign you in, verify sessions and prevent unauthorized access. Do not send passwords in support messages.

Optional Quran audio sharing

Sharing has its own opt-in and can be switched off in Settings. When enabled and the app can run, verified Quran audio may be sent to another user through a direct WebRTC connection or an audio relay when needed. This uses data, battery and storage. Peer discovery processes device identifiers, audio/chunk identifiers, hashes, availability and connection addresses. Other participating peers may learn your connection IP address. Coordination and relay services process connection information. Signed contribution records contain participating device IDs, audio/chunk IDs, verified byte counts, timestamps and signatures; a leaderboard shows a generated contributor alias and contribution totals. These records can be linked to your service account. Sharing does not give other users access to your photos, contacts or arbitrary files. On supported Android versions, optional official APK sharing processes package hashes, chunk availability and session information. APK transfers have no relay, and APK result reports are not treated as signed audio contribution credit.

Local features and permissions

Downloaded audio, reading preferences, bookmarks and favorites are stored on your device. Location and compass information support prayer times and Qibla. Prayer calculations run locally; Apple's geocoding service may process your location to show a place name. Notification permission is used for local prayer reminders. This release does not capture camera images or microphone recordings, although included libraries require related permission descriptions. You can manage permissions in iOS Settings. Local data can be included in device backups according to your Apple settings.

Payments, service providers and international processing

Apple processes optional in-app support purchases; we do not receive your payment card details. Account services, our coordination infrastructure and audio hosting/CDN services process the requests needed for their respective functions. Audio hosts receive network information such as your IP address and requested resource. Apple sign-in, geocoding and purchases are also subject to Apple's privacy policy. Services may process information outside your country. The app has no advertising or cross-app tracking function. We do not sell personal information or use Quran reading or sharing activity to create advertising or religious-belief profiles. Separate audio sharing exposes the connection information described above only as necessary for the transfer you choose.

Retention and security

Account, enrolled-device and contribution records remain while needed to operate your account, until deletion or where retention is legally required. Peer availability becomes inactive when its validity expires; that does not mean the database row is immediately erased. Expired or closed signaling sessions are cleaned up when later sessions are created. Operational access/error logs can contain IP addresses, request paths, timestamps, status codes and diagnostic information. They are retained for troubleshooting and security; server system logs are configured for a 30-day retention window. Other infrastructure logs, including the website ingress reverse proxy, follow their own rotation settings and are not covered by this server’s cleanup rule. We do not promise a zero-log service. HTTPS and device key storage help protect information, but no system is completely secure. Deleting a device identity removes its public key and associated contribution records; a key fingerprint is retained to prevent the revoked key from registering again.

Your choices and deletion

You can turn sharing off and revoke location or notification permissions. Settings → Delete device identity removes this node’s public key and associated contribution records; a revoked-key fingerprint remains to prevent re-registration. For a linked legacy account, other devices and the external account are not automatically deleted. Contact us for access, correction or account deletion. Uninstalling alone does not delete server records. Local downloads/bookmarks require separate cleanup; Apple manages purchase records.

Privacy contact

For privacy questions, access, correction or deletion requests, contact: wanghui32026@outlook.com. Include only the account email or identifier needed to locate your record; never include your password or private keys.

Changes and this website

We update this page when our practices change, and request a new choice in the app if the scope of an optional service materially changes. This policy page uses no advertising, analytics scripts or tracking cookies. Loading it still sends an ordinary web request to the hosting server and may create an operational access log. The language versions describe the same practices.

Legacy connection: supplementary data notice

Only if you use the optional legacy VPN connection, the service processes account/device identifiers, a connection public key, source and assigned addresses, handshake/activity information and traffic counters for authentication, transmission and security. The connection private key stays on your device. A separate in-app notice and choice are provided before use; you can disconnect or remove the profile. We do not sell this feature’s user data, use it for advertising or profiling, or disclose it to third parties for any purpose.