A check records a short, silent clip or a single frame, sends it — encrypted — to be judged once, and destroys it: the media is never written to a server disk, never stored, never used to train anything, and never shared. Only the verdict — pass or fail — is kept. We don't sell data, we don't run ads, and we don't track you across other apps. Delete your account any time and your record goes with it.
1. Who we are
Mashhud ("Mashhud," "we," "us") is the Fajr alarm application published by Dynamic Dev Solutions LLC, a limited liability company registered in Florida, USA. This policy describes what we collect, why, and the choices you have when you use the Mashhud app or website (together, the "Service"). If you do not agree with it, please don't use the Service.
2. What we collect
Account (optional). An account is optional — the alarm, prayer times, and checks all work signed out. If you do sign in, you use email and a 6-digit code (no password); we receive your email address and an authentication token. There is no Apple or Google sign-in.
Prayer-time settings. Your coordinates, calculation method, Asr convention, and alarm offset. Times are computed on your device (see Location below).
Check results. For each alarm: the check type (Wudu or Steps), pass/fail/bypass, and timestamps. This is your record — the lit and unlit days.
Tasbih (optional). If you sign in, your all-time tasbih tallies — and any zikr you add in your own words (its text and count target) — are saved to your account so they follow you to a new phone. Counts only: we never record when you counted, and nothing syncs while you're signed out.
Purchases. Whether you hold the one-time "Founding lifetime" purchase, from the App Store or Google Play. We never see your card number.
Diagnostics & anonymous usage. Crash reports and a short log of what the alarm did and which of Mashhud's own screens were reached (device model, OS and app version, true/false alarm events, and fixed status words — never anything you typed, never a photo, never your name) — used to keep the alarm reliable and to understand which parts of the app work. It is labeled by a random install identifier that is linked to no account, and it all turns off with one switch in Settings.
3. What we never collect
4. Camera & checks
The Wudu and Steps checks use your camera, with your permission, solely at the moment you run a check — there is no background access and no access to your photo library. The Wudu check records a silent clip of up to fifteen seconds; the Steps check takes a single frame. In both cases the file is deleted from your device before it is sent, then transmitted over an encrypted connection (HTTPS) to our verification service, which passes it once to a vision model (Google's Gemini API) to answer one question — did a wash happen, or is this your mat with your feet in frame. The media is held only in memory for that one request, judged, and destroyed; it is never written to a server disk or database (there is no image or video column), never used to train anything, and never shared. Only the verdict is kept — a pass/fail and, if it didn't clear, a one-word reason so the app can coach you — and it is written to your account only if you are signed in.
If our service can't be reached — no network, a timeout, an error on our end — the check passes you automatically rather than trapping you; an outage never locks your alarm. Revoking camera permission disables camera-based checks. No microphone is ever used.
5. Location
Prayer times require a location. Location is requested at your device's coarse ("Low") accuracy, only when you grant permission or tap refresh — never tracked continuously or in the background — and is used to compute prayer times on your device. If you are signed in, an approximate, rounded location (to about a kilometre, not a precise point) is saved with your account so your times follow you to a new phone; signed out, nothing leaves the device.
6. How we use data
To run the alarm and your record; to sync your record and your tasbih across your devices if you sign in; to provide support when you write to us; to fix crashes; and to compute aggregate, anonymized statistics (for example, a community "dawns witnessed this week" count, if we publish one — a count, never who). We do not use your data for advertising, and we do not use it to train models.
8. Retention & deletion
We keep your account data while your account exists. Delete your account in Settings → Account → Delete, or email us — your record, tasbih, settings, and identifiers are erased from our systems within 30 days (backups age out within 90). Diagnostics are retained at most 18 months. Purchase records are kept as long as tax law requires.
9. Security
Data is encrypted in transit (TLS) and at rest. Access inside the team is limited and logged. No system is perfect; if a breach ever affects your data we will notify you and the relevant authority without undue delay.
10. Children
Mashhud is not directed to children under 13 (or the equivalent minimum age where you live), and we don't knowingly collect their data. If you believe a child has created an account, contact us and we'll delete it.
11. Your rights
Depending on where you live (GDPR, UK GDPR, CCPA/CPRA, and similar laws), you may have the right to access, correct, export, restrict, object to the processing of, or delete your personal data — and to complain to your local supervisory authority. Email services@mashhud.app; we respond within 30 days and never discriminate for exercising a right.
12. International transfers
Our servers are in the United States. If you use Mashhud from elsewhere, your data is processed in the US; where data crosses borders we rely on recognized safeguards such as Standard Contractual Clauses.
13. Changes to this policy
If we change this policy we'll update the date above and, for material changes, tell you in the app before they take effect. The promise in section 4 is load-bearing — that a check's clip or frame is judged once and destroyed, never stored and never used to train anything: if that ever changed, we would ask for your explicit consent first — silence would not be consent.