Privacy Policy

Last updated: September 30, 2026

We're a small tool built to serve masjids, not a data company. This policy is written in plain language for exactly that reason: to tell you clearly what we collect and why, not to bury it. It is a good-faith description of the system as built, not a substitute for a lawyer's review before you rely on it for a specific legal situation.

What we don't collect

If you simply open the public caption screen (the plain page, or a masjid's /m/<slug> link) without signing in:

We never receive or store your microphone audio. Speech recognition happens inside your own browser (or, for Urdu specifically, is streamed directly to Deepgram — see below) — our server only ever sees the resulting short text segments it sends for translation.
Captions are not saved anywhere. Refreshing or closing the page clears them. There is no "session history" stored on our servers tied to you.
No account, no cookies, no tracking are created just by viewing captions.

What we do collect

If a masjid creates an account (the dashboard)

Data	Why
Email address	Used only to send a one-time sign-in link and account-related notices. Never sold, never used for marketing, never shared with other masjids.
Masjid name & a generated URL slug	To label the account and build its public caption-screen link.
Aggregate daily usage counts	A count of translation calls per day, used to enforce a fair-use limit and show usage on the dashboard — not the caption content itself, just a number per day.
A session cookie	Keeps you signed in. `HttpOnly` (invisible to page scripts), sent only over HTTPS, and not used to track you across other sites.
Sign-in link tokens	Only a one-way cryptographic hash of the token is stored, never the raw link — a stored row can't be used to sign in even if the database were exposed. Each link expires in 15 minutes and works once.

Feature requests you submit through the dashboard's request box are stored with your masjid's account so we can follow up on them.

Server logs

Like virtually every web service, our hosting provider (Cloudflare) generates standard operational logs (IP address, timestamp, requested path) for security and abuse prevention. We don't build any separate analytics or advertising profile from these.

Third-party services we rely on

Each of the following sees only what's strictly needed to do its job, and each has its own privacy policy governing what it does with that — we encourage you to read the ones relevant to you:

Anthropic — receives the short speech-transcript segments to translate them. Does not receive your email, account, or identity.
Deepgram — receives live microphone audio only when a khutbah is set to Urdu mode on a device whose browser can't recognize Urdu itself (see our accessibility statement for why). Arabic and English khutbahs never send audio anywhere outside your own browser.
Resend — delivers the sign-in link emails; receives the recipient email address and the email content.
Cloudflare — hosts the entire application, its database, and this page.
Al Quran Cloud and a public hadith API — looked up to verify a recited āyah or hadith citation; only the reference number is sent, never anything about you.

Data retention

We keep account data for as long as the account is active. Expired or used sign-in-link records and old sessions are not yet automatically deleted from the database — only a cryptographic hash and an expiry timestamp are stored in them, never a usable credential, but if you'd like your account and its records fully deleted, contact us (below) and we will do so.

Your rights

You can ask us, at any time, to see what data we hold about your masjid's account, correct it, or delete it entirely. For most requests, we expect to complete this within a few days.

Children's privacy

This tool is intended for masjid administrators and congregations generally, not marketed to children, and we do not knowingly collect account data from children.

Changes to this policy

If this policy changes in a meaningful way, we'll update the date at the top of this page.

Contact

[Add a contact email or phone number here before publishing]

Accessibility Statement · Terms of Service · Privacy Policy