Christian Widgets · iOS & Android

Privacy Policy

Effective and last updated: October 12, 2026

Christian Widgets does not require an account or display third-party advertising. Your faith preferences, saved and custom verses, reading activity, widget choices, reminders, and selected background media stay on your device. In iOS version 1.0.1 and later, Apple and Superwall process the limited purchase, subscription, technical, and interaction information described below to provide Premium access and measure how onboarding, the app tour, and the purchase experience work. Section 4 explains iOS advertising measurement by Meta and, in builds with TikTok measurement enabled, by TikTok only after you authorize Apple's tracking permission.

1. Scope and operator

This policy applies to Christian Widgets on iOS and Android (the “App”), with iOS bundle identifier and Android package name com.prizmaly.christianwidgets. Sections 2–14 describe the iOS application; section 15 describes the Android application, its different providers and data practices. The App is provided by PRIZMALY YAZILIM TICARET LIMITED SIRKETI (“Prizmaly,” “we,” “our,” or “us”). For privacy questions or requests, email info@prizmaly.com.

2. Information stored on your device

The App stores the information needed for its features in local app storage and in an Apple App Group shared only with the App's widget extension. Depending on how you use the App, this may include:

an optional profile name, denomination or faith preferences, motivations, struggles, moods, and onboarding choices;
selected categories, favorites, disliked verses, custom verse text and sources, collections, and recently seen verses;
reading goals, streaks and history, game progress, and other feature progress;
language, theme, font, appearance, widget, notification, and sound preferences; and
a photo or video you choose as a custom background.

Prizmaly does not operate an account or cloud-sync service for the App and does not receive this content. The App does not send this local faith, reading, or media information to Superwall. Local information may be included in device backups you enable with Apple; Apple and you control those backups.

3. Purchases, onboarding analytics, and Superwall

Apple processes App Store payments. The App does not receive or store your full payment-card details or Apple Account password.

Starting with iOS version 1.0.1, we use Superwall to display subscription offers, perform and restore Apple in-app purchases, manage Premium access, support purchases, and understand onboarding, app-tour, paywall, and subscription performance. Apple sends purchase and subscription status notifications directly to Superwall. Superwall may process the following information on our behalf:

automatically generated pseudonymous installation and user identifiers, including a Superwall alias and Apple's identifier for vendor;
app and SDK versions, operating system, device model, language, region, time zone, storefront, network type, display settings, and similar technical information. Internet requests expose an IP address, which may be used to derive an approximate country, region, or city; the App does not request precise location access;
product and transaction identifiers, purchase and restoration results, entitlement and subscription status, prices, currencies, and transaction timestamps; and
internal SDK events, including app sessions, paywall views and interactions, purchase or restore attempts and results, paywall assignments, and technical loading or error information; and
limited interaction events showing whether onboarding or an app-tour step was viewed, completed, skipped, or revisited; numeric step and completion counts; time spent in those flows; notification permission prompt results; fixed screen-source or purchase-flow status values; checkout outcomes and duration; allowlisted error categories and numeric error codes when checkout fails; and optional cancellation feedback selected from fixed reason categories. No free-form feedback or personal onboarding answers are included.

This information helps deliver the correct offers, validate and restore access, prevent purchase fraud, resolve errors, and measure the onboarding and subscription experience. The limited interaction events help us identify confusing steps and improve these flows. They are associated with Superwall's existing pseudonymous SDK identifiers; they are not fully anonymous. The App does not add a separate account identity or send profile attributes for this analysis. It limits its custom analytics to approved event names, numeric measurements and diagnostic codes, and fixed status, error-category, cancellation-reason, or screen-source values. Error messages, NSError userInfo, receipts, and arbitrary strings are not included in these custom diagnostics.

We do not supply Superwall with your profile name, email address, denomination, faith preferences, raw onboarding answers, motivations, struggles, saved or custom verses, reading history, game progress, selected background media, or reminder content. The pseudonymous SDK identifiers are not your Apple Account password or payment-card details. See the Superwall Privacy Policy and the Apple Privacy Policy for these providers' privacy information.

Earlier App versions: iOS version 1.0.0 used RevenueCat for purchase verification, restoration, Premium access, and subscription analytics. Devices still using that version may continue to send its pseudonymous purchase and technical information to RevenueCat, and earlier transaction records may remain there for support, restoration, or required retention. Version 1.0.1 and later use Superwall without the RevenueCat SDK or a RevenueCat purchase dependency. See the RevenueCat Privacy Policy for that earlier-version processing.

3a. Optional information for Apple refund requests

For an App Store purchase, Apple may request limited purchase and access information from us to assess a refund. Where supported and enabled for the app, we or its billing provider may respond through Apple's refund-consumption-information service. The purpose is to help Apple assess delivery and use of the purchase and our refund recommendation. Apple makes the final refund decision; an automated response does not guarantee that a refund will be declined or granted.

The response can include transaction or product references needed to match the request, purchase or Premium-access delivery status, availability of a trial or sample, the extent of purchased content consumed where applicable and actually known, a record that you agreed to the sharing, and a recommendation to grant, decline or leave the refund to Apple. Fields depend on the app, provider and type of purchase. A purchase alone is not evidence that you used a particular feature. For auto-renewable subscriptions, Apple can calculate consumption from elapsed subscription time. This refund response does not include private app content, messages, photos, contacts, health information, faith answers or listening history.

Before this optional sharing, we require a separate, informed, affirmative choice describing its purpose, the information and Apple as the recipient. Agreeing to general terms or this policy, making a purchase, continued use, analytics settings and App Tracking Transparency authorization do not by themselves provide that choice. Publishing this notice does not activate the feature or establish consent for existing customers. Declining does not prevent core app use, purchase restoration or requesting a refund.

To decline or withdraw, contact info@prizmaly.com and identify the app. Where the app offers a dedicated control, you may also use it. Once recorded, your choice applies to future optional refund-information responses. Withdrawal does not undo prior sharing; Apple and billing providers may retain required purchase and refund records under their own policies and applicable obligations. We use only purchase information available for the relevant app, and its product-specific privacy notice continues to control its provider and data practices. Do not send passwords, full card details or unnecessary private content.

4. Advertising and tracking

The App does not display third-party advertising. Current builds include the Meta iOS SDK to measure app activation, onboarding completion, paywall views, and automatically detected Apple purchase events for advertising campaigns. Meta may receive pseudonymous app-instance identifiers, product and transaction details, price, currency, event times, device/app/SDK metadata, and network information. Meta observes purchases but does not initiate or finish them; Superwall remains the purchase, restore, and entitlement authority. The App does not also send manual Meta purchase events.

The App requests Apple's App Tracking Transparency permission for advertising measurement. IDFA collection is enabled only when permission is authorized. Meta App Events starts after ATT has an authorized or denied result, so non-IDFA app events may still be sent after permission is denied. Apple's SKAdNetwork may also provide aggregate campaign attribution without IDFA. Purchase processing, restoration, and the limited Superwall analytics described above do not depend on ATT permission. We do not send profile names, personal onboarding answers, faith preferences, reading activity, verses, or media content to Meta. Tracking permission can be changed in iOS Settings.

In iOS builds with TikTok measurement enabled, the native TikTok App Events SDK measures app installation and opening, generic onboarding completion, paywall views, checkout starts, and verified initial free trials, subscriptions, or lifetime purchases for advertising measurement. TikTok may receive pseudonymous app-instance and event identifiers, IDFA when authorized, app/device/SDK and network information, event times, product and transaction identifiers, and the actual transaction price and currency. This information is not anonymous.

Unlike the Meta behavior described above, the App initializes TikTok and permits TikTok event transmission only while Apple's App Tracking Transparency permission is authorized. TikTok is not initialized while permission is undecided, denied, or restricted. If you revoke permission in iOS Settings, the App disables TikTok transmission and clears its own pending checkout and conversion records when it next synchronizes that permission. This does not delete information already received by TikTok.

TikTok events do not include profile names, email addresses, phone numbers, personal onboarding answers, denomination or faith preferences, reading activity, verses, or media content. The App disables TikTok enhanced-data postbacks, automatic retention events, automatic purchase detection, and TikTok SKAdNetwork support. Initial purchase events are sent only after Apple's transaction verification; restores and renewals are not reported by the App as new TikTok conversions. Superwall continues to own purchasing, restoration, and Premium access. These TikTok events are sent directly through the native iOS SDK; no Superwall-to-TikTok server connector is enabled. See the TikTok Partner Privacy Policy for TikTok's processing.

5. Apple diagnostics

Apple may process standard App Store, operating-system, purchase, and diagnostic information under its own privacy terms and your device settings. For example, Apple may make aggregated usage or crash diagnostics available to developers when you have chosen to share such information. We use any information Apple makes available only to operate, secure, and improve the App and to support purchases.

6. Notifications and widgets

If you grant notification permission and enable reminders, the App schedules Bible verse reminders through Apple's local notification system. Notification schedules and selected verse categories stay on your device. Notification text may be visible on your Lock Screen or to anyone who can view your notifications, depending on your iOS settings.

The widget extension reads the limited preferences and verse content placed in the App Group shared container so it can display the widget you configured. This is local communication between the App and its widget extension, not transmission to Prizmaly.

7. Photos, videos, saving, and sharing

When you choose a custom photo or video background, Apple's system photo picker gives the App access only to the item you select. The selected copy is stored locally for the background feature and is not uploaded by Prizmaly. If you ask the App to save a generated verse image, iOS may ask for permission to add it to your photo library.

The App opens the iOS share sheet only when you choose to share verse text or an image. A shared item leaves the App only through the person, app, or service you select. That destination handles the item under its own privacy terms.

7a. Optional iOS AI chat

When you choose to allow AI sharing and send a message, the app sends that message, the recent conversation and your selected reply language through our Cloudflare-hosted server and OpenRouter to Alibaba Cloud (Qwen) to generate a reply. Questions you choose to type may contain religious or other personal information. Your stored profile, denomination or faith preferences, saved verses and app activity are not automatically included. Our server also receives Apple’s device-attestation information and verified purchase information to check that the device and Premium access are valid; these proofs are not sent to OpenRouter or the model provider. Network requests expose technical information, such as an IP address, to the receiving service.

The app keeps the current conversation in memory and allows you to clear it or withdraw AI sharing permission in AI privacy. Our AI gateway does not store chat messages or replies in its security and usage ledger. It retains pseudonymous device-verification records and usage or spending counters to protect access, prevent abuse and enforce limits. Clearing the conversation removes the app’s current copy. Withdrawing permission stops future AI sharing. Neither action erases information already processed by service providers. Provider retention and deletion practices apply to their copies, and processing may occur in countries other than yours. Contact the app’s privacy contact for requests involving records we hold.

8. Retention and deletion

Profile-related local information remains until you change or delete it in the App. The Delete Profile control removes the local profile record and cancels its reminders. Some device-local settings, cached content, or selected media files may remain until you remove the App. Removing the App clears its local container subject to device and backup behavior. Removing local information does not cancel a subscription or delete purchase-provider transaction records.

Apple and Superwall may retain purchase, entitlement, and related technical records as needed to operate purchases, restore access, measure service performance, prevent fraud, comply with accounting or legal requirements, and provide support. Earlier RevenueCat records may be retained for the earlier-version purposes described above. To request help with a provider record associated with an installation, email info@prizmaly.com and include the Christian Widgets installation or user identifier if it is available to you. We may ask for limited app, installation, or transaction details needed to locate the record. Do not send payment-card or bank-account details.

For TikTok measurement, the App keeps a small device-local queue of consented checkout intents and verified conversion events. Checkout intents are valid for up to seven days, and pending conversion events are eligible to be sent for up to seven days; expired events are not sent. A bounded set of hashed transaction identifiers is retained locally to avoid reporting the same conversion twice. Revoking tracking permission clears the App's pending checkout and conversion records when the App next synchronizes permission. TikTok's retention and deletion practices for information it has already received are described in its Partner Privacy Policy linked in section 4.

9. Sharing, sale, and international processing

We do not sell personal information. We disclose the limited purchase, interaction, and technical information described above to Apple and Superwall for App Store payments, Premium access, fraud prevention, support, onboarding, app-tour, subscription and paywall analytics, and service operation. Apple processes its purchase and system information; the App sends the custom interaction events described in section 3 to Superwall. The limited app and purchase event information described in section 4 is also sent to Meta and, only with authorized tracking permission, to TikTok for advertising measurement. RevenueCat applies only to earlier-version processing and records as described in section 3. These providers may process information in countries other than yours and apply their own safeguards for international transfers. We may also disclose information when required by law or to protect users, the App, or our legal rights.

10. Your choices and rights

You can manage notifications and photo-library permission in iOS Settings, choose whether to share Apple diagnostics, delete local App data, and manage or cancel subscriptions in your Apple Account settings. Depending on where you live, you may also have rights to request access, correction, deletion, restriction, objection, or portability for covered information. Contact us to make a request. Because the App has no Prizmaly account and the purchase providers use pseudonymous identifiers, we may need limited installation or transaction information to find a provider record.

11. Security

The App relies on iOS app sandboxing, device security, and encrypted HTTPS connections for Apple and Superwall purchase services. No system can guarantee absolute security. Protect your device with a passcode and review the destination before sharing content.

12. Children

The App does not create a Prizmaly account. A parent or guardian should supervise a child's purchases and any use of sharing features. If you believe a child has provided covered information to a purchase provider or Prizmaly in connection with the App, contact us so we can investigate and respond where required.

13. Changes

We may update this policy when the App, its providers, or applicable requirements change. The date above identifies the latest version. A revised policy will be posted at this address.

14. Contact

PRIZMALY YAZILIM TICARET LIMITED SIRKETI
Christian Widgets Privacy Support
info@prizmaly.com
Christian Widgets Support

15. Christian Widgets on Android

This section applies to the Android application with package name com.prizmaly.christianwidgets, provided by Prizmaly using the contact details above. It describes the Google Play release using Superwall, beginning with version 1.0.1. Earlier Android releases used RevenueCat as explained below. The Apple purchase, App Group, iOS notification, Meta iOS SDK, and App Tracking Transparency descriptions in sections 2–14, including the optional iOS AI section, do not describe the Android application.

Local content and permissions

Android does not require an account. Your optional profile name, denomination or faith preferences, onboarding choices, selected or saved verses, reading and game progress, language and appearance preferences, selected background media, and widget data remain in local app storage. Prizmaly does not operate an account or cloud-sync service for this content, and it is not sent to Superwall or advertising services. The release disables Android app-data backup. Its verse, story, image, and audio resources are bundled with the app.

This Android release does not request precise or approximate device location, microphone, broad photo or video library, or advertising-ID permission. If you choose a custom background, Android's system picker grants access only to the photo or video you select. The app copies it into its private local storage for use as your background; it is not uploaded. Replacing or removing a custom background deletes the previous app-owned copy. The Delete Profile control also removes these copies. User-started story narration can continue in the background and provides Android media controls. Narration files are bundled and no microphone recording is used. If you enable verse reminders, it requests Android notification permission and schedules local verse notifications on your device. The selected categories, delivery count and sounds stay in app storage. Notification text can appear on your lock screen according to your Android settings. Disabling reminders cancels scheduled verse notices. The app does not register for remote push notifications; Firebase messaging auto-initialization and data collection are disabled. Widgets use local content and preferences. If you choose a sharing action, the content goes to the app or recipient you select, under that destination's privacy practices.

Google Play purchases and Superwall

Google Play processes Android payments. The App does not receive your full payment-card details or Google Account password. Superwall supports subscription offers, purchase and restoration handling, Premium access, and measurement of the purchase experience. It processes the following information on our behalf:

purchase history and related data, including product and purchase identifiers, prices, currencies, purchase or restoration results, transaction times, and subscription or entitlement status;
automatically generated pseudonymous installation, user, vendor, or device identifiers used by the SDK; these do not reveal the local profile name or your Google Account password;
app interactions such as automatic SDK installation, app-open and session events, and purchase or restore attempts and outcomes;
technical and diagnostic information, such as app and SDK versions, operating system, device model, language, region, network and display properties, SDK loading or billing errors, SDK error codes, and SDK crash logs or stack traces; and
the IP address exposed by network requests and approximate country, region, or city derived from it. This occurs through the SDK's IP enrichment even though the App does not request Android location permission; no GPS or precise location is requested.

These records are associated with pseudonymous SDK identifiers and are not fully anonymous. They support app and purchase functionality, access restoration, offer delivery, subscription and paywall analytics, troubleshooting, service security, and fraud prevention. The SDK collects its internal events automatically; the Android release does not send our custom onboarding, faith, reading, or game analytics to Superwall. The SDK data collection is not optional within this release and is not limited to temporary processing in memory.

Superwall acts as our service provider for these purposes. Google processes Google Play purchase and platform information under its own terms. See the Superwall Privacy Policy and the Google Privacy Policy. Earlier Android releases used RevenueCat for purchase verification, restoration, Premium access, and subscription analytics; installations still running those releases may continue that processing, and earlier transaction records may remain for support, restoration, and required retention. The current Superwall release has no RevenueCat SDK or RevenueCat purchase dependency. See the RevenueCat Privacy Policy for earlier-version processing.

Optional Android AI chat

Android AI chat is available only when the service is enabled and configured for this App. Before sending a message, you must separately allow AI sharing. If you allow sharing and send a message, your current message, selected chat language, and a bounded recent conversation context are sent through Prizmaly's Cloudflare-hosted gateway to OpenRouter and Alibaba Cloud's Qwen model service to produce the reply. The context is limited to the latest five exchanges and the current message, subject to an overall size limit. The language selection is sent with each request. This optional service requires network access and verified Premium access or separately authorized AI reviewer access.

The App does not automatically attach your local profile name, denomination, faith or onboarding answers, saved verses, reading or game activity, or advertising-measurement data to AI requests. Anything you choose to type, including religious beliefs or personal details, becomes part of the message and may appear in later conversation context or in the generated answer. Avoid including information you do not want these providers to process. The providers process messages under their own applicable terms; provider retention may apply. We do not promise zero data retention, anonymity, or end-to-end encryption. See the Cloudflare Privacy Policy, OpenRouter Privacy Policy, and Alibaba Cloud Privacy Policy.

Chat messages, draft text, and replies are held in the App's current session memory rather than saved as a chat history on your device. Prizmaly's gateway does not store or log ordinary chat prompts or replies. The separate, voluntary report process below is an exception for an answer you explicitly choose to submit for review. Network providers can see technical connection information, including your IP address, and their own retention practices may apply.

Android AI access and abuse prevention

To protect AI access, the native Android module sends purchase proof and Google Play Integrity information to Prizmaly's gateway for verification with Google. This can include the package, app signing certificate and version, app-recognition and licensing verdicts, device-integrity verdicts, request hash and time, and the purchase token and product identifier needed to verify access. These proofs are used by Prizmaly and Google for access verification and fraud prevention; they are not included in requests to OpenRouter or Alibaba Cloud.

A private key kept in Android Keystore signs requests. Prizmaly uses pseudonymous installation and purchase references, protected by keyed hashing where applicable, request counters, quota and cost records, and short-lived authorization for approved AI review access to prevent replay and enforce service limits. These security records do not contain the ordinary chat text, but they are not fully anonymous and can outlast a chat session. Private signing keys, purchase and Integrity proofs, and server or model-provider credentials are not exposed to the App's JavaScript chat interface. A reviewer code you enter is processed to request limited access; it is not sent to the AI model providers.

Reporting an Android AI answer

When Android AI reporting is available, use the in-app Report control beside an answer, select a reason, and review and confirm the submission. With your AI-sharing consent and this separate confirmation, the App sends only the selected AI answer, selected reason, chat language, and a signed response receipt, together with the technical information needed to authenticate and protect the submission. It does not automatically attach your question, the full conversation, or your local profile. An answer may itself repeat information you typed; check the selected text before confirming.

Reports go to Prizmaly's private moderation inbox hosted on Cloudflare, not to the AI model providers for another inference request. We use them to investigate objectionable answers and improve safety and moderation. Reports have a 30-day expiry and automated cleanup. The report service applies separate abuse-prevention limits. Reporting a previously received answer does not require renewing Premium or AI reviewer access, but the response receipt must still be valid. This description does not mean the service is enabled in every App version.

Advertising and disclosures to others

The Android release does not display third-party advertisements. It includes a dedicated native TikTok measurement SDK, which is disabled by default and remains inactive without this App's separately verified configuration and your explicit advertising-measurement consent. AI-sharing consent does not grant advertising-measurement consent. If enabled with consent, the integration is limited to generic onboarding and purchase-experience events and verified initial-purchase events; it does not send your local faith/profile choices or AI chat and report contents. The App does not include a Meta or Firebase advertising or analytics SDK. Its current Superwall configuration has no active Meta advertising integration or configured event webhook. We do not send its SDK purchase or interaction data to advertising partners for advertising measurement through Superwall. We do not sell personal information. Limited purchase, interaction, identifier, location, and diagnostic data is processed by the providers described above to operate and support the App; service providers may process it in countries other than yours. Information may also be disclosed when required by law or to protect users or our legal rights.

Retention, deletion, and your choices

You can clear the App's storage in Android settings or uninstall it to remove local app data, subject to device behavior. This does not cancel a subscription or erase provider transaction records. Manage or cancel subscriptions in Google Play. Google and Superwall may retain purchase, entitlement, identifier, interaction, location, and diagnostic records as needed to provide and restore access, measure service performance, resolve errors, prevent fraud, provide support, and meet legal or accounting requirements. Earlier RevenueCat records may be retained for the earlier-version purposes described above.

Clear chat removes the current on-device conversation. Revoking AI sharing stops further AI chat and report submissions until you allow sharing again and clears the displayed conversation. These controls do not erase provider-held records, access or quota records, or a report you previously confirmed. For help with an AI privacy request or report, email the contact below without sending unnecessary conversation text.

To request access, correction, deletion, or other available privacy rights for provider records, email info@prizmaly.com. Include the Christian Widgets installation or user identifier if available, or a Google Play order identifier so that we can locate the relevant record. Do not send payment-card details or your Google Account password. Some records may need to be retained to meet legal obligations or preserve transaction integrity.

Security and children

Android app sandboxing and device security protect local app storage. Network communication with Google Play, Superwall, and the optional AI gateway uses encrypted connections. No system can guarantee absolute security. A parent or guardian should supervise a child's purchases and sharing. Contact us at the address above if you believe a child has supplied covered information so we can investigate and respond where required.