DigiRosary

Privacy Policy

Effective 13 August 2026

DigiRosary is a prayer app developed and operated by Sahil Sunny. This policy explains what the app keeps on your device, what is sent to the DigiRosary service at sahilsunny.com, why it is used, and how to delete it.

Data kept on your device

Prayer preferences, custom prayer content, saved progress, reminders, settings, and a local copy of prayer statistics are stored on your device. Foreground location may be used, only after you enable motion cues and grant permission, to derive travel speed on the device. Coordinates and derived speed are not sent to DigiRosary or stored by the DigiRosary service.

Deleting a cloud account does not erase this local data. Use DigiRosary's local reset controls, clear the app's storage, or uninstall the app if you also want to remove data held on the device.

Account and cloud statistics

Creating an account is optional. When you create one, the service stores your email address, a one-way password hash, hashed authentication tokens, server-keyed digests of verification or reset codes, whether the email is verified, and the prayer statistics you choose to synchronize. Plain-text passwords are never stored. Account records and cloud statistics remain until you delete the account; this includes unverified accounts. API sessions expire after 90 days, email-verification codes after 24 hours, and password-reset codes after 30 minutes. Expired credentials are removed by scheduled pruning.

Synchronized statistics are linked to your account and can record your exact Rosary practice. This information can reveal religious practice or belief.

Remote usage telemetry

Remote usage telemetry is optional and starts off. During onboarding, DigiRosary offers separate Don't share and Share usage data choices before any telemetry identifier, timer, or request is created. Declining does not limit the app. You can change the choice later under Settings → Help → Share pseudonymous usage data. Turning it off stops future DigiRosary telemetry requests and active-recitation heartbeats.

If you affirmatively choose to share, the app creates a random installation identifier and may send fixed events for app opening, Rosary start, Rosary completion, and active recitation. Each event may include the app version, platform, major operating-system version, device model, selected prayer language, interface language, and a text-size group. The service adds the coarse Fly.io server region that accepted the request. It does not add your name, email address, cloud-account ID, advertising ID, hardware serial number, precise location, prayer text, custom prayer content, or anything you type.

The random identifier links events from one app installation, so this data is pseudonymous, not anonymous. Rosary events and the selected prayer language can reveal religious practice or belief. DigiRosary uses this stream only to estimate how many opted-in readers are actively praying, understand recitation flow, and improve accessibility and the general prayer experience. Online counts include only readers who chose to share; they are estimates from recent pseudonymous active-recitation signals, not counts of every person using DigiRosary. The data is not used for advertising, cross-app tracking, or personal profiling. Pseudonymous event rows become eligible for deletion once they are older than 30 days, and the daily cleanup normally removes eligible rows within the following 24 hours. Withdrawing consent stops future collection but does not retroactively turn already received rows into account data; they remain subject to that short retention period. Clearing the app's storage or uninstalling it removes the local telemetry choice and identifier.

Separately, Google Play may provide Sahil Sunny with aggregated store and app-health reports, such as installs, active-user and retention summaries, device or app-version groupings, crashes, and application-not-responding events, under Google's own settings and policies. DigiRosary does not receive individual prayer activity, a DigiRosary analytics identifier, or per-install event histories through those aggregate reports.

Bug reports

Bug reports are sent only when you submit them. A report can contain your description and reviewed annotated screenshot; exact app, operating-system, device, display, language, and connectivity context; navigation history; active mystery; Rosary total and streak; saved-progress key names; sign-in and verification flags; relevant settings; recent fixed diagnostic categories; and an optional contact email. User-entered text, screenshots, and prayer-state context can contain personal information or reveal religious practice or belief. Screenshot attachments become eligible for deletion after 14 days, while the remaining bug-report fields become eligible after 60 days; the daily cleanup normally removes eligible data within the following 24 hours.

Network processing and service providers

sahilsunny.com processes requests over HTTPS. A request's raw network address is used transiently for security and abuse-rate limits but is not written to the DigiRosary application database. For consented telemetry, the stored region is only the coarse Fly.io server region that handled the connection, not a GPS coordinate or street address. Fly.io hosts the service. During an off-platform backup, a GitHub Actions runner temporarily processes a plaintext database copy, encrypts it immediately to an offline-held age recipient, deletes the plaintext, and stores only the encrypted artifact for up to 30 days. An email delivery provider processes account verification and password-reset mail, and Google Play operates the app-distribution platform and aggregated store and stability reporting described above. Data is not sold, used for advertising, or used for cross-app tracking by DigiRosary.

Deleting your data

In DigiRosary, open Settings → Help → Cloud sync → Delete cloud account. You can also follow the instructions on the account-deletion page. Account deletion removes the email, password hash, authentication tokens and codes, and synchronized cloud statistics from the active service. Optional telemetry is controlled separately by the Share pseudonymous usage data setting. Pseudonymous event rows are not linked to a cloud account or email address and follow the 30-day eligibility and daily-cleanup schedule above.

If you supplied an email address in a bug report, mention that in a manual deletion request so the report can also be located and removed. Routine encrypted disaster-recovery backups may retain deleted records for up to 30 additional days; they are isolated and used only for recovery.

Contact

DigiRosary is developed by Sahil Sunny. Questions and privacy requests can be sent to hello@sahilsunny.com.