Divine Mercy Chaplet Privacy Policy

Android · com.gigafishapps.divinemercy · Version 1.0.0 · Updated October 18, 2026

Divine Mercy Chaplet is provided by GigafishApps IT. You can use its prayer texts without an account or an internet connection. Your saved place and prayer completion are stored on your device. The app uses Google advertising services and offers separate, optional choices for usage statistics and crash reports.

Information kept on your device

The app stores your selected language, privacy choices, position in an unfinished chaplet, the time of your most recent completion and a completion count. This lets it offer Continue and show whether you have prayed today. These records, dates and counts are not sent to GigafishApps or Firebase. Android cloud backup is disabled. Clear the app’s storage in Android settings or uninstall the app to remove its locally stored information; this also removes your saved progress.

The free app uses Google Mobile Ads and Google’s User Messaging Platform. An App Open advertisement may appear at startup and an interstitial may appear after you save a completed chaplet. No advertisements appear inside the prayer reader. Availability depends on connectivity, advertising availability and your applicable privacy choices.

Where required, Google’s consent form appears before advertisements are requested. You can revisit available advertising controls through Privacy options and Advertising choices. Google determines the choices available in your region. Advertising choices are separate from optional usage statistics and crash reports.

Google’s advertising SDK may collect and share your IP address, approximate location derived from it, advertising or other device identifiers, app and advertising interactions, and technical performance information. Google uses these for advertising, measurement, fraud prevention and security. The app does not request precise GPS location. Android settings let you reset or delete the advertising ID where supported.

See the Google Privacy Policy and Google Mobile Ads data disclosure.

Optional usage statistics

Usage statistics are off by default. If you enable them, Google Analytics for Firebase processes general app-use measurements, including screen openings, time in the reader, scrolling milestones, ad-report screen openings, advertising loading and display results, and advertising revenue values. These help us improve the app and understand its operation.

These measurements can include a randomly generated app-instance identifier, app and device information, timestamps and session information. They are not anonymous. Because this is a prayer app, information about use of its reader may indicate an interest in religious content. We do not attach prayer names, prayer text, saved completion dates or counts, or the text and images of your ad reports to Analytics events.

Firebase Analytics advertising-ID collection is disabled. We do not enable Analytics advertising-personalisation or remarketing signals. AdMob processes advertising information separately under the advertising choices described above.

You can decline usage statistics and still use the app. To withdraw consent, open Privacy options, clear Share usage statistics and save. This stops future Analytics collection and resets its local Analytics identifier; it does not automatically delete data already received by Google.

Optional crash reports

Crash reports are also off by default. If you enable them, Firebase Crashlytics can receive technical error reports containing stack traces, app and device details, application state and a randomly generated installation identifier. If both statistics and crash reporting are enabled, reports may include recent general app events to help diagnose a problem.

Reports are sent on a subsequent launch while crash reporting remains enabled. Changing this choice removes pending reports from the device. We do not add prayer history, prayer text or ad-report contents to crash reports. You can withdraw this choice in Privacy options without losing access to the app. Withdrawal stops future reporting; it does not automatically delete previously sent reports.

See Firebase privacy and security and Firebase Android data disclosures.

Reporting an advertisement and contacting us

During the current app session, the app keeps details of the most recently displayed ad: its format, response ID, advertising SDK version and whether it is a test ad. These details help identify a reported advertisement.

Report an ad lets you add a description and optionally choose a screenshot. Prepare email opens your email application with a draft addressed to gigafishapps@gmail.com, including the description, selected screenshot, recent ad details and app version. Nothing is sent automatically. If you send the message, we receive your email address and the information you include. We use it to respond and investigate, and may share relevant ad details with Google to investigate the advertisement. Do not include unrelated personal information in your report or screenshot.

Retention, security and your requests

Local progress and preferences remain until you clear the app’s storage or uninstall it. The recent ad details described above are held in memory during the app session. Google SDK services encrypt data in transit. Your email provider applies its own transport and security arrangements to messages you choose to send.

Google Analytics retains user-level and event-level information according to our Analytics property settings; standard aggregated reports have separate retention arrangements. Firebase Crashlytics generally retains crash traces and associated installation identifiers for 90 days. Advertising data is subject to Google’s retention policies.

We retain support correspondence for the time needed to handle the issue and related follow-up, or longer if required by law. Email gigafishapps@gmail.com with the subject “Divine Mercy privacy request” to request access, correction or deletion of information we hold or to ask about your choices. Depending on your location, you may also have rights to restrict or object to processing, request portability, withdraw consent and complain to a data protection authority. Withdrawing consent does not affect processing carried out before withdrawal.

Some SDK records are linked to a random installation identifier rather than your email address. We may need enough information to identify the records concerned. There is no GigafishApps account to delete. Google’s privacy tools and policies describe controls over information Google handles in its own capacity.

Google and its service providers may process information outside your country. Their privacy documentation explains processing locations and safeguards for international transfers. External websites and email applications have their own privacy practices.

Children and policy changes

The app is intended for adults. We do not knowingly collect personal information from children through support correspondence. Contact gigafishapps@gmail.com if you believe a child has supplied personal information.

We update this notice when the app or its data practices change. The date and version above identify the release covered. Contact: gigafishapps@gmail.com. Developer: GigafishApps IT.

Divine Mercy for iPhone and iPad — version 1.1.10

iOS · com.gigafishapps.divinemercy · Updated October 25, 2026

This section describes version 1.1.10 and supersedes the iOS version 1.0.0 section below for this release. The contact, support, advertising-provider and retention information in this notice continues to apply where relevant.

Prayer progress and calendar

Your saved place, completed prayers and settings are stored on your device. This version does not synchronize prayer history through CloudKit. Existing local completions from the previous iOS version are imported into the new local calendar, without deleting the previous local record. This release does not delete records previously stored in your private iCloud database. Local files may be included in device backups managed by iOS. No GigafishApps account is required.

Offline audio

English recordings and word-timing files are included in the app. Listening does not send your prayer text or listening position to a voice service.

Optional measurements

Usage statistics and crash reports have separate choices, both off by default. With your permission, Google Analytics for Firebase receives general app events such as screens, reading duration, progress milestones and advertising outcomes. These events may indicate engagement with religious content. We do not include prayer text, saved prayer dates, calendar totals or ad-report messages. Analytics advertising storage, advertising user data and ad personalization remain denied by the app. With diagnostic permission, Firebase Crashlytics receives technical crash information on a subsequent launch. Granting permission discards older pending reports. Withdrawing permission stops future optional reporting.

Advertising and reports

Google AdMob may show an ad when the app opens and after a completed prayer is saved. Its advertising data processing is separate from the optional measurement switches. Google UMP and applicable iOS permissions manage advertising choices. Reporting an ad prepares a message to gigafishapps@gmail.com with what you write, available ad-response details and an optional screenshot you select using the system picker. You confirm sending in your mail app or share sheet. Nothing is sent automatically.

External app links

App Store links open Apple's store. Apple's privacy policy and the other app's privacy policy apply to those services.

Divine Mercy for iPhone and iPad

iOS · com.gigafishapps.divinemercy · Version 1.0.0 · Updated October 19, 2026

This section supplements the notice above. Where platform descriptions differ, this section applies to iPhone and iPad.

Prayer and local history

The app stores your reading position and saved prayer completions on your device. You can read the prayer texts and save completions without creating an app account.

iCloud history

If iCloud is available for the Apple Account on your device, the app can synchronize saved prayer history between your iPhone and iPad. It uses a private CloudKit database associated with your Apple Account. Each completion has a random record ID and a completion date. The completion date is encrypted on the device using CloudKit before it is saved to the server. The app does not put this history in a public database or send it to Firebase Analytics or AdMob.

Your local history remains available when iCloud is offline or you are not signed in. The calendar shows the current synchronization status. When the app detects that the iCloud account has changed, it stops synchronization rather than automatically moving the existing history to the new account.

Optional usage statistics

Usage statistics are off until you choose to share them in Privacy options. Google Analytics for Firebase receives generic app events, such as screen views, return visits, reading duration and progress milestones, and ad outcomes and revenue. Its reports may include app and device information, a random app-instance identifier and approximate geographic information derived from the connection. These statistics are used to improve the app and its advertising performance. They are not used by this app to create personalized advertising audiences.

Because this is a prayer app, generic usage statistics may indicate engagement with religious content. The app does not send prayer names, prayer text, saved prayer dates, calendar totals, iCloud account identifiers, or anything you type in an ad report to Analytics. You can withdraw the usage choice at any time in Privacy options. Withdrawing it disables further usage collection and resets the local Analytics data and app-instance identifier.

Optional crash reports

Crash reporting has a separate choice, initially off. Firebase Crashlytics processes technical error information, app and device information, and a random installation identifier to help fix failures. If usage statistics are also enabled, reports may contain recent generic app events. Automatic crash-report upload is disabled. Reports from a previous session are sent on a subsequent launch only when the saved diagnostic choice allows it. Granting diagnostic permission does not send older reports gathered before that choice. You can withdraw this choice in Privacy options.

Advertising choices

The app uses Google AdMob. An ad may be shown when the app opens and after you save a completed prayer. There are no ads inside the prayer reader. Ad availability, personalization, and measurement depend on your choices, region, device settings and the advertising provider. Google's User Messaging Platform manages advertising choices where a consent form applies. On iOS, the system App Tracking Transparency permission is requested before access to the advertising identifier for tracking. Declining optional measurement or tracking does not prevent prayer, local saving or access to the calendar.

Ad reports

You may choose to report an ad by writing a description and optionally selecting a screenshot. The app prepares a message in your mail app or the system share sheet; you confirm whether and where to send it. The report can include technical ad-response information. It is not sent automatically and is not included in Analytics events.

Contact

For support and privacy questions, contact hello@gigafishapps.com or use https://gigafishapps.com/supportpage.html#send-message . Ad reports prepared by the app use gigafishapps@gmail.com.