Quran / أقرأ

Operator and contact

ASR Technology Solutions. Privacy and support: info@seshatnews.com.

Effective date: 2 October 2026.

Recitation checking and artificial intelligence

When you start recitation checking, microphone audio is processed in memory on your iPhone or iPad using the Moonshine speech-recognition model. Recognized words are compared with the selected Quran verses locally. This recitation feature does not upload your microphone audio or recognized text to Moonshine or another AI service, and it has no cloud recognition fallback. It does not save an audio recording of the checking session.

The app downloads the model from download.moonshine.ai. The download host receives your IP address and normal connection/request information to deliver the model files. The download does not contain recitation audio or recognized text. Once installed, recognition works offline. You can delete the downloaded model in recitation options. In build 160 and later, before microphone capture, the app explains local recognition, identifies Moonshine and its download host, and asks whether to start on this device. Declining leaves the microphone off. Microphone capture begins only when you choose to start and grant system permission; you can stop capture and revoke microphone access in iOS Settings.

Account and cloud features

Google Firebase provides authentication, database storage, audio storage, server functions, and push delivery. Account identifiers, available email/name information, sign-in provider, platform, and account activity timestamps are used to operate accounts. Apple or Google sign-in supplies the account information authorized through that provider. Signed-in memorization data is backed up to Firebase to support synchronization across devices. Shared Aqra khatma features use Google Firebase to process membership, reading assignments, and progress. Separately, legacy group invitation routes and group screens may contact the app backend at seshatnews.com for invitation codes, group details, membership, assignments, and reading progress, along with normal network information. These legacy routes do not offer separate Seshat account registration or sign-in within Aqra.

Dua recordings and sharing

Dua recording is separate from recitation recognition. Audio you record or import is stored locally, with recording metadata. Saved recordings sync to Google Firebase when signed in with an Apple or Google account, including previously unsynced recordings. Guest recordings stay on the device unless you choose to share them; signing in later can sync saved recordings. In build 160 and later, a notice explains this before recording starts, and you can decline without granting microphone access. Choosing to share a recording creates access for recipients through a sharing link. Family recording requests allow invited people to submit audio and the associated information entered in that flow. Shared audio is delivered through the app's Firebase services; it is not submitted to an AI recognition service. Recipients may retain copies of recordings they receive. You can use the recording deletion controls to remove recordings you manage.

Reading settings and location

Reading preferences and progress are stored to provide the reader, bookmarks, memorization, and reminders. With permission, location and device-heading information support prayer times and Qibla. Prayer-time calculations use the device location; displaying a place name can use the operating system's geocoding service. Location access can be revoked in iOS Settings.

Notifications and diagnostics

Push notification tokens are sent to Firebase to deliver notifications. Production builds use Firebase Crashlytics to report crashes and errors, including diagnostic information such as app/device details and stack traces, to diagnose failures and improve reliability. Notification permissions can be changed in iOS Settings.

Content downloads

Requests for Quran reciter audio, Mushaf images, and other remotely delivered content disclose network information such as IP addresses and the requested resource to the relevant content host. Hosts include everyayah.com and files.quran.app. These downloads are separate from microphone recognition and do not include your recitation audio.

Protection and service providers

We require service providers that process personal data for us to provide protection equal to or greater than the protections in this policy, restrict processing to the services they provide, and apply appropriate security safeguards. Google Firebase publishes its data-processing and security terms at https://firebase.google.com/terms/data-processing-terms and privacy information at https://firebase.google.com/support/privacy. We do not sell personal data or submit recitation audio or transcripts to an external AI service.

Retention, deletion, and choices

Local recitation audio is processed for recognition without recording it to an audio file. Local model files remain until removed through recitation options or app-data removal. Cloud-synchronized data is separate from data on the device; uninstalling alone does not delete a cloud account or cloud backups.

In iOS version 1.0.20 build 160 and later, open Settings → Profile → Delete account to delete a signed-in account or an automatically created guest account. The app asks for confirmation; Apple or Google accounts also require a fresh sign-in to verify ownership. You do not need to email support. Deletion removes the authentication account, profile, memorization backups, saved cloud recordings and their metadata, recording share links, family-recording requests, and personal membership and attribution in Firebase-backed Aqra khatmas from active systems. Shared Aqra khatma data belonging to other members is preserved. Personal reading history, memorization data and saved recordings on the device are cleared, and the app confirms completion. Recipients may retain copies of recordings already delivered to them. A temporary deletion receipt expires after 30 days so an interrupted request can confirm completion; it contains no email address, name, recording or reading history and is removed using automatic expiry. Limited security and diagnostic records follow the relevant provider retention schedules. Deleting the app alone does not delete a cloud account or send a deletion request.

The account deletion flow described above covers the Aqra Firebase account and its Firebase-backed data. It does not delete an independent account or data maintained by the legacy Seshat group service; this app does not offer separate Seshat account registration or sign-in. Contact info@seshatnews.com for privacy questions or help. Contacting support is not required to delete the Aqra account.

Policy changes

We will update this policy when data practices change and provide any notice or permission required before introducing new data sharing.