Last updated: October 8, 2026
This policy explains what data is used in the public release of Kav Siddur.
If you allow it, the app reads your device location to calculate local prayer times (zmanim). The zmanim calculation happens on your device, and the coordinates are kept only on your device. To show a city name, the app asks Apple’s (or Google’s) geocoding service to translate the coordinates once; we never receive, store, or share your location.
Location permission is optional. If you decline it, you can still use the prayer library, Tehillim, and study tools.
If you turn on Daven together in the reader, the app uses your local network (peer-to-peer Wi-Fi and Bluetooth, no internet) to find nearby phones that enter the same four-digit code. The only thing sent is your place in a service (which prayer and section), so others can follow along. No names, no device names, and no prayer text are sent. Nothing is stored, nothing is sent to us or any server, and the session ends when you stop it or close the app. iOS asks for Local Network permission the first time you use it. Please consult your rabbi about using a phone on Shabbat.
Kav Siddur stores settings such as nusach, font choices, display preferences, reminder toggles, and local reading progress on your own device so the app can remember your setup between launches.
This information stays on your device and is not uploaded to us in the public release.
The app may occasionally ask Apple to show its standard App Store rating prompt after you finish a service. To decide when, it keeps a count of finished services on your device; the count is never uploaded.
To show “Your prayer life” (your days with prayer, streaks, the prayers you open most, reading time, psalms and Omer days this year), Kav Siddur keeps a history of your activity in the app on your device: which prayers and psalms you open, for how long, what you finish, which features and settings you use, and when. It never includes anything you type (no names, notes or search words) and never your location.
This history stays on your device and is never sent to us or anyone else. You can delete it at any time in Settings (“Clear my activity history”) or on the Your prayer life page; deleting the app deletes it too. If we ever offer to share anonymous totals for community statistics, it will be a separate, clearly explained choice that is off unless you turn it on.
If you share a passage, the app draws the image on your device and hands it, together with a link, to your device’s share sheet. Nothing is sent to us. If you choose “Save Image”, iOS asks your permission to add that one image to your photo library; the app never reads your photos.
Shared links open a page on this site. That page makes no requests of its own, sets no cookies, and records nothing; if you have the app, it opens the passage there.
If you choose to use the Pray For feature, the following applies:
A prayer request consists of a Hebrew name, a category, an optional short note, and a duration. All of these are visible to every user of the app. Do not include health details about an identifiable person without their consent, and do not include contact information — notes containing links, email addresses, or phone numbers are rejected.
You can also share a prayer request as a candle card with a short link. A request stores: the name as you entered it (full, first name only, or initials — the app sends only what you chose to show), the request type (healing, memorial, safe return, or other occasion), an optional note of up to 280 characters, when it expires, a count of prayers, and a once-per-day marker for each person who taps “I prayed” so the same person is not counted twice in a day. Requests are unlisted by default: they do not appear on the Pray For board unless you choose to list them, and are reachable only through their link. Anyone with the link can read the name, note, and any updates you post, and can open the link in a web browser without the app.
You choose how long a request lasts, up to 30 days for healing and safe return, 90 days for other occasions, and 365 days for a memorial; closing a request as recovered shortens what remains to 3 days. Expired requests are purged on the schedule above. You can delete a request at any time, and the link then shows nothing.
The link page loads the request from our backend provider (Supabase), sets no cookies, and has no analytics. When you tap “I prayed” on the page, it stores a random code in your browser’s local storage to count one prayer per day; it is not linked to your identity. If you tap “Report this request” on the page, we store the request’s id, that same random browser code, and the short reason you may type (up to 200 characters, optional) so we can review it by hand and count one report per browser; web reports alone never remove a request. Prayer and report requests are also rate-limited per request, using the request’s id. To slow down guessing of links, looking up a link that never existed is counted against one of 4,096 coarse groups derived from your network address (the address itself is not stored); these counters are deleted after about two hours.
Opening a request link in the app never creates an account: the app reads the request with the same public key the link page uses. When you tap “I prayed” or report the request in the app, it sends a random code made once for your copy of the app, so each person is counted once per day and one report is counted per phone, and we store it the same way as the browser code above. The code is kept only inside the app (deleting the app deletes it), is not linked to your identity, and is never sent anywhere else. If you already have the anonymous identity described below, the app uses that instead, so it can show which requests are yours.
When you open the Pray For feed (even just to read it), post on it, or create a prayer request with a link, the app creates an anonymous account with our backend provider and keeps its session credentials on your device. Opening, praying for, or reporting a request someone sent you never creates one. We never ask for your name, email, or phone number, and the account carries no personal information. This anonymous identity links your own requests to your device so you can delete them; it is not connected to any real-world identity.
Requests expire automatically after at most 48 hours and are permanently deleted from our systems within 30 days of expiry. “I prayed” interactions are stored against the anonymous identity (or, without one, the random code described above) for counting and abuse prevention, and are deleted on the same schedule.
You can delete any of your own requests immediately, and you can delete all data associated with your anonymous identity at any time from the Pray For screen (“Delete my Pray For data”).
Users can report and block content. Reported content is hidden automatically after multiple reports and reviewed. Abuse can also be reported through our support page.
Pray For data is stored with our backend provider (Supabase) and is not sold, shared with advertisers, or used for any purpose other than operating the feature.
If the app offers an optional subscription (“Kav Siddur Chai”), payment is handled entirely by Apple’s App Store or Google Play — we never see or store your payment details. Subscription status (an anonymous purchase record, with no name or email) is processed by RevenueCat, our subscription-management provider, solely to unlock content you have purchased and to support purchase restoration. When subscriptions are enabled, RevenueCat’s software also receives basic device information (device model, operating-system version, app version, and locale) needed to operate the service. Builds without subscriptions do not contact RevenueCat. Core prayer content remains free and requires no purchase.
| Category | Behavior in public release |
|---|---|
| Location | Optional. Used on-device only for zmanim. |
| Daven together | Optional. Local network only; shares just your place in a service with phones that enter your code. Nothing stored or sent to us. |
| Preferences | Stored locally on the device. |
| Progress | Stored locally on the device. |
| Activity history | Kept only on the device for Your prayer life; never sent. You can clear it in Settings. |
| Shared passages | Created on the device; sent only where you choose in the share sheet. |
| Accounts | No named accounts. Pray For (optional) creates an anonymous backend account with no personal data when the feed is opened or a prayer request is created. Opening a request link someone sent you creates none; praying for or reporting it sends only a random per-install code. |
| Prayer requests (Pray For) | Optional. Board posts are publicly visible in the app and expire within 48h; link requests are unlisted, visible to anyone with the link, last up to 7 to 365 days by type, and can be deleted by you at any time; purged ≤ 30 days after expiry. |
| Purchases | Handled by Apple/Google; anonymous subscription status via RevenueCat. |
| Analytics | Not included. |
| Crash telemetry | Not included. |
The public release does not rely on third-party analytics or advertising services. The optional Pray For feature stores its data with Supabase; optional subscriptions are managed through RevenueCat (see above).
Apple may process standard App Store download, payment, and device information under Apple’s own privacy policy. We do not receive payment card details.
Kav Siddur does not knowingly collect personal information from children under 13. The public release is designed to avoid collecting personal information from users of any age.
If our data practices change, we will update this policy and revise the effective date above before those changes ship publicly.
If you have questions about this privacy policy or the app’s data practices, please contact us at:
Support: https://ronrefael.github.io/kav-siddur-site/support.html