Skip to main content

Privacy

Your recitation is not our data

AyahClip uses private account storage and an isolated cloud worker to recognise recitation across your devices. Your media is not used for advertising or model training.

Last updated 9 August 2026

Private processing

When you ask AyahClip to recognise an uploaded recitation, the source is sent over HTTPS to tenant-isolated private account storage and processed by AyahClip’s isolated cloud recognition worker. Durable jobs continue if a tab closes; checkpointed Bulk Create recognition can also resume from another signed-in device. Timeline editing, previews and final video rendering remain in your browser.

Saved projects, templates, Bulk Create collections, uploaded B-roll, sources and rendered clips are synced privately to the signed-in account so they can reopen across devices. AyahClip does not send imported media, detected transcripts, Quran text, translations, project names or file names to the diagnostics endpoint.

A local desktop installation may also offer an explicit save-to-folder action. Choosing a share sheet, download or third-party stock asset is an action you control.

Anonymous diagnostics

To understand whether creators reach a successful export, AyahClip can record a small set of milestones such as source loaded, Quran range confirmed, template chosen, Studio opened and export succeeded or failed.

Each browser session receives a random temporary journey identifier. Reports include only a coarse device class, browser family, duration band and fixed error category. They do not contain account identifiers, advertising identifiers, precise device details or free-form error messages. Request addresses may be held briefly in memory to limit abusive request bursts, but AyahClip does not add them to product-event records. Accepted records are retained for up to 90 days. AyahClip honours the browser Do Not Track setting.

Anonymous product diagnostics

Share coarse workflow milestones and fixed error categories. Your media, Quran text, transcript, file names and project names are never included.

Services AyahClip contacts

The app may request Quran text and translation data from Quran.com, reciter audio and timing data from EveryAyah or MP3Quran, optional stock media from Pexels, and application assets from AyahClip hosting. Quran recognition uses AyahClip’s own pinned model on privately managed hosting. Those providers receive ordinary network information such as an IP address when your browser contacts them.

If server-assisted caption writing is configured, AyahClip sends the platform, tone, Surah name, verse reference, exact translation excerpt and selected reciter name to OpenAI. It does not send imported media, files or detected transcripts. Starting a donation sends the chosen amount and frequency to Stripe so Stripe can host the checkout.

AyahClip runs on privately managed hosting infrastructure. Signed-in account records and private media are stored there, and the configured email provider delivers verification and password-reset messages. Hosting, network and email providers may process the information needed to provide those services. AyahClip does not add request IP addresses, raw user-agent strings or referrers to its product-event records.

Storage and deletion

Device-only projects, source blobs, templates and library clips remain in browser storage until you delete them or clear the site’s data. Signed-in account records and private media remain until you delete the item or account. Removing an account item creates a deletion record so it does not reappear on another signed-in device.

Recognition jobs store progress and results so they can recover from worker or network interruption. Finished job records expire after 30 days; the account source media remains with the saved work until you delete that item or account.

Account settings let you download a JSON copy of account records and the private-media manifest. Deleting an account removes its active server records and private media. Encrypted disaster-recovery backups expire within 35 days, so deleted data may remain inaccessible in a backup until that backup expires. Existing browser copies are separate and remain on that device until you delete them or clear site data.

Files already downloaded or shared must be removed from their destination separately. Keep original media and completed exports in storage you control.

Your choices

You can turn anonymous diagnostics off above, enable Do Not Track, delete individual projects, download or delete your account, or clear AyahClip’s site data in your browser. The troubleshooting report is created locally and is copied only when you press its button.

Questions about this policy can be raised through the support page. Do not include recitation recordings, private links, credentials or unpublished project content in a support request.

How to contact us

Email support@ayahclip.com with any question about this policy or to ask for privacy help. For a signed-in account, use Account settings first to download or delete the account. Clearing browser site data removes device copies but does not delete a signed-in account.