Your data is yours.
Clarity is your right.

1. Data stored on the device

Wird may locally store data needed to continue your experience, including:

• dhikr counts, session history, progress, and preferences;
• Quran reading position, markers, khatmah, Night Prayer progress, and Mushaf settings;
• adhkar, prayer, and memorization-practice progress;
• city, prayer-time settings, notifications, and saved mosques;
• Quran recitations and resources you choose to download; and
• audio recordings, imported audio, and video projects you create in the video editor.

Audio files used to create videos are stored in the app’s private area and are outside journey sync. Device backups may include data from this feature according to system settings. With your permission, an audio copy can be sent for external analysis, or to a destination you select when exporting or sharing; these files should therefore not be described as staying only on your device.

2. Optional iCloud sync

You may request a one-time sync or enable automatic sync. When enabled, Wird uses CloudKit to synchronize journey data in your private Apple iCloud database, including dhikr-session history; Quran reading sessions, positions, bookmarks, and markers; khatmah state, progress, and completions; memorization-recitation results and completed surahs; and saved mosques.

The developer cannot browse the content of your private iCloud database from the CloudKit dashboard. Sharing uses a separate Firebase Authentication identity; it is not your Apple Account and is not linked to that account in the counter server. Audio files and video projects are not included in journey sync.

Disabling automatic sync stops later synchronization but does not automatically delete a copy already stored in iCloud. From the iCloud section in the main menu, you can review managed data types, export a local JSON copy, or delete the iCloud copy while preserving on-device data and turning automatic sync off. You can also manage the app’s iCloud data in Apple Account settings on your device.

When you enable iCloud sync or request a manual sync, your private copy also includes your sharing link, last confirmed count, previously shown badges, sharing identity and recovery credential inside an encrypted CloudKit field. The recovery credential stays in Keychain on the device and is excluded from public JSON exports. Deleting the iCloud copy removes the cloud backup, not the sharing account or its counter-server record.

3. Usage analytics controls

Google Firebase Analytics stays off until you agree to usage sharing in the optional onboarding step, or enable it later in About Wird. Your saved explicit choice is preserved. No usage analytics are sent before you consent. The app may send categorized product-interaction events that help improve the product, such as opening a section or starting or completing a journey. You can disable or re-enable analytics from About Wird in the main menu at any time.

An event category can indicate interaction with a religious feature such as Quran, dhikr, or prayer, so Wird treats this data as sensitive information in App Store disclosures. Firebase may process a random app-instance identifier, app version, device model, operating-system version, interface language, limited diagnostics, and an approximate geographic region inferred from the internet connection. Wird does not use this data for advertising or tracking and does not link it to your sharing-account identity.

Analytics data is linked to Google’s identifier for this installation of the app, even though you are not asked to sign in. It is not anonymous or unlinked data. Wird does not send your name or email address to Analytics and does not use this data for advertising or cross-app tracking.

Wird does not send Analytics:

• audio, recordings, or speech transcripts;
• Quran text, surah or verse identifiers, or search queries;
• dhikr text, precise counts, or individual worship times;
• precise location, coordinates, or your selected city;
• mosque names or addresses; or
• your name, email address, phone number, or advertising identifier.

Disabling analytics stops subsequent collection and resets local Analytics data. Events that occur while analytics is disabled are not stored for later transmission, but disabling alone does not delete data previously received by Google. The service settings verified on October 24, 2026 retain event data for two months and user data for 14 months. Reset on new user activity is enabled, so the user identifier’s retention period can restart with continued use. Those limits may not apply to standard aggregated reports, according to how Google Analytics operates.

4. Microphone and speech recognition

Wird requests microphone access for voice dhikr, memorization review and spoken learning, search dictation, or when you deliberately record audio to create a video.

Memorization practice does not create an audio file or save your voice; speech is processed on your device during the session. Voice dhikr and search dictation use Apple speech-recognition services according to your device’s capabilities, settings, and Apple’s policies. Wird does not send audio or speech transcripts to Firebase Analytics.

Analyzing the clip’s audio to identify verses and create videos

When you add a recitation audio or video file, or record a recitation to create a video, online audio analysis requires separate permission from microphone access. If permission is not already saved, you can agree, choose Add verses manually, or cancel. The manual route extracts or records audio, trims and adjusts it on your device, and lets you use the editor and export without sending this audio to QUD. You may select canonical ayahs and set their timing yourself, or export without ayah captions. Cancelling closes the initial flow; it does not prevent reading or on-device memorization review. Online-analysis consent is saved for later automatic requests and can be withdrawn in About Wird.

After you choose automatic analysis and agree, an audio copy is sent to QUD, a third-party AI service at https://aligner.qud.dev/api/v1/, hosted on Hugging Face, to match the recitation to verses and time the words. Analysis of imported audio starts as soon as its audio copy is ready, while you choose the excerpt and adjust its sound. External analysis of a microphone recording starts after you stop recording. The copy may include the entire recording before trimming, including other audible speech and sounds. If you later request automatic recognition from the editor, the full current audio asset may be sent, even when only part is selected in the timeline. Video images, the original filename, the recording title, and a Wird user identifier are not sent. The verse-matching results are used in a follow-up word-timing request. The service also receives ordinary connection data, such as your IP address. Omitting a Wird user identifier does not make the request anonymous to the provider.

Trimming and sound enhancement take place on your device. For supported connection or service-availability failures during automatic analysis, it can fall back to the on-device model. A local retry is available when the app displays it. Choosing manual creation does not start automatic online or on-device verse recognition. In the editor, you can request automatic recognition separately; declining or cancelling that request preserves your current edit and does not start another external request. The manual route does not make unrelated services or resource downloads work offline.

5. Location, camera, and notifications

• Location is used when you request prayer times, Qibla direction, or nearby mosques. Wird sends the selected location’s coordinates to Apple WeatherKit to retrieve weather. Selecting a city manually uses that city’s coordinates; for current location, coordinate accuracy depends on what iOS allows. Apple Maps services are also used for city and mosque search and resolving a location name. You can select a city manually without allowing access to your device location. Wird does not track your location in the background.
• When scanning a Mushaf page, Wird processes the image on the device to identify its ayahs. Wird does not retain the scan or send it to the developer.
• Notifications provide local reminders you choose and can be disabled in Wird or iOS Settings.

6. External services

Wird may use Apple system, Maps, speech-recognition, iCloud, and WeatherKit services; Google Firebase Analytics only after you explicitly enable usage sharing; and Quran audio or resource providers for playback or downloads you request. It also uses QUD at aligner.qud.dev, hosted on Hugging Face, to analyze audio for video creation after the separate permission explained above. Processing by these services is subject to their policies. Ordinary internet connections may expose an IP address and technical information needed to connect. Excluding audio and precise location from Firebase Analytics does not mean they are never processed by services needed for the features you choose.

When you type an online-library search to obtain suggestions or submit a search, Wird sends the search terms to Shamela (old.shamela.ws) and Arabic Wikisource (ar.wikisource.org) to obtain results. These providers also receive ordinary connection information, such as your IP address and technical request details. The query is not sent to Firebase Analytics. Search providers may retain request logs and use them to operate and secure their services and analyze usage under their policies; Wird does not promise that these logs are deleted when results appear. You can read downloaded books and search their contents on your device without performing a new online-catalog search.

Wikimedia privacy policy · Wikimedia data-retention guidelines · Shamela

Optional Mushaf editions, tafsir and translation databases, and Nawawi text are downloaded through Apple-Hosted Background Assets. Apple handles these download requests under its privacy policy. These asset downloads do not send your recordings or reading history to Apple.

When you create a supplication video, Wird may download the audio recording from the IslamicAPI library hosted on GitHub. The host receives ordinary connection data, such as your IP address, to complete the download. The video is created on your device; your photos and recordings are not uploaded to this source.

Apple Privacy Policy · Google Privacy Policy

QUD — service and documentation · QUD — processing API documentation · Hugging Face privacy policy

7. Sharing and contact

When you choose to share a recording or file, iOS presents available destinations and you select the recipient. Contact us opens an available email app addressed to our support email. Wird does not automatically attach device details, diagnostic logs, or screenshots to that message. You choose what to write, attach, and send in your email app.

Requesting your personal link in Share Wird creates or restores a random Firebase Authentication identity in the separate service project. Cloudflare D1 retains the sender ID, link code, short numeric alias, creation time, active status, aggregate Store-opening attempts and latest attempt time. The owner-only dashboard displays these sender records and totals. This counter does not upload your voice, photos, contacts or reading position. The sharing identity, link and count are not sent to Firebase Analytics.

The link is stable and may include the app language. Opening it loads the Wird landing page, which automatically attempts to open the App Store and retains a download button as a fallback. The total represents opening attempts, not verified downloads or distinct people, and cannot prove eligibility for monetary rewards. Reopening the page may count again.

We do not create a persistent recipient identifier, use measurement cookies or persistent browser storage, or fingerprint a device to recognize returning visitors. A random short-lived ticket exists only in the page memory. The ticket expires within ten minutes, and its receipt prevents double-counting automatic navigation and the fallback button on that page. Stored expired receipts are removed when later attempts are processed. Hosting providers may process normal connection information, such as IP addresses, to operate and protect the service. A transient request-rate limit uses the connection address to prevent abuse; our counter ledger does not retain it or use it to identify visitors or count distinct people.

The counter refreshes when a participant enters Share Wird or pulls to refresh, not on every app launch. An earned badge appears after a successful refresh inside that section. Sharing is independent of optional usage Analytics; it does not enable Analytics or override a saved refusal.

Wird has no App Clip or pause-count control. Historical measurement-test records remain separate and do not increase the current counter; account deletion includes records associated with that identity in those tests. iCloud recovery does not silently merge different identities.

8. Controls, deletion, and retention

You can delete recordings, downloads, markers, and histories where the app provides management tools; revoke permissions in iOS Settings; and disable analytics from About Wird or sync from the iCloud section in the main menu. The iCloud section also lets you export local journey data and delete its iCloud copy without deleting on-device data.

Deleting the app removes local data subject to iOS behavior. Some Keychain or iCloud items may remain until you manage them in Apple Account settings. Google’s retention settings govern Analytics data received while analytics is enabled, as described above.

You may send a privacy or deletion request to the contact address below. Google uses an app-instance identifier; without that identifier, we may be unable to locate historical Analytics data associated with your installation. Turning analytics off resets local Analytics data but does not itself delete data already received by Google.

Retention of audio and connection information by QUD and Hugging Face is governed by the provider’s and host’s policies. Wird does not promise a fixed deadline for deletion of every copy or service log, and does not assume that the request is anonymous. Cancelling stops the app’s requests but cannot retrieve audio already sent. Deleting a recording from your device does not send a deletion request to the provider.

You can withdraw permission for future requests in About Wird by choosing Withdraw online audio permission. This does not withdraw a copy already sent. For questions about processing or deletion by an external service, contact us at the privacy address below. Deleting a local copy is not confirmation of deletion by the service.

The sharing identity, link and totals are retained to preserve progress; uninstalling alone does not delete them. In About Wird, choose Delete sharing data when a sharing identity exists. After confirmation, we delete the random Firebase account and its link, count and badge records, and remove its recovery data from the associated iCloud backup if present. This is permanent and does not delete your reading position, bookmarks, khatmas or other journey data. Disabling Analytics or deleting the iCloud copy alone does not delete the sharing account.

If deletion is interrupted, the request remains securely stored on your device and can be resumed from the same control; completion is not reported until the required stages succeed. Access to the same iCloud account may be necessary to clean its backup. The server retains a random deletion-retry receipt; after completion it contains no account ID, and completed receipts older than seven days are removed on later deletion requests. A deleted short-code reservation remains without an account association so an old link cannot be assigned to someone else. iCloud may retain a marker containing no sharing identity or profile data to prevent an old backup from being restored; deleting the iCloud copy also removes that marker. These statements do not cover connection logs retained by service providers under their own policies.

9. Children, security, and changes

Wird does not target the collection of children’s personal data and contains no ads or advertising trackers. Reasonable safeguards are used, but no electronic storage or transmission method is completely risk-free. This policy may change when features or store requirements change; the revision date will appear at the top.

10. Contact

For privacy or support questions, contact:

Aboutmuslimapp@gmail.com