Privacy Policy

Last updated: June 10, 2026

Diya is a Hindu daily practice and reflection app. This policy explains what information Diya may collect, process, use, and share when you use the iOS app and related hosted services.

Information Diya Collects Or Processes

Diya does not require an account. Some information is stored locally on your device, including saved verses, Gita reflections, practice progress, reminder settings, onboarding completion state, and the name you choose to enter for in-app personalization.

When you complete onboarding, Diya may send an onboarding response record to Diya's backend. That record may include the name you entered, selected goals, prayer experience, prayer reasons, prayer time or reminder preference, silence-time preference, faith-struggle response, temptation response, age group, and gender. Diya may also process related identifiers, such as a Diya install identifier, a PostHog analytics identifier when analytics are enabled, and hashed or masked RevenueCat subscription identifiers when available, to operate the app, support subscriptions, understand product usage, and measure advertising performance when enabled.

If you use Ask Diya, your chat messages and related context are sent to Diya's backend and AI service providers so the assistant can respond. This may include free-form text you choose to enter and context from the app, such as a selected verse or lesson prompt.

If product analytics are enabled for a release, Diya may collect app interaction data, such as onboarding step views, onboarding completion summaries, content categories, feature usage, message length, feature flag events, purchase-flow events, and app lifecycle events. Analytics events are used to understand and improve the app. They do not include chat message text, saved verses, or Gita reflections.

If advertising attribution or measurement is enabled for a release, Diya may use the Meta/Facebook SDK, including Meta SDK App Events, to measure app activation, ad attribution, subscription trial starts, and purchase-related conversion performance. Diya may send app activation and trial-start events, including Meta's StartTrial App Event, after RevenueCat confirms an active free-trial subscription entitlement. Trial-start and purchase-related Meta events may include limited technical and purchase-related information, such as app activation, product identifier, package identifier, price, currency, subscription entitlement status, and a store transaction identifier when available. They do not include chat message text, prayer or spiritual responses, onboarding answers, names, email addresses, or phone numbers.

Diya may also use Supabase to store onboarding response records, RevenueCat trial webhook records, and Meta App Event records so that Diya can operate onboarding, support subscription access, and verify whether app activation, trial-start, or purchase-related conversion events were attempted, skipped, or sent. These records may include product identifiers, package identifiers, price, currency, subscription status, hashed or masked RevenueCat identifiers, hashed or masked App Store transaction identifiers when available, product interaction information, and the onboarding response fields described above. Meta App Event records do not include chat message text, prayer or spiritual responses, onboarding answers, names, email addresses, or phone numbers.

If you contact us for support, we collect the information you choose to provide, such as your email address, phone number, and message contents.

How Information Is Used

We use this information to operate core app features, including chat, daily practice tracking, saved progress, and optional reminders. We also use information to troubleshoot issues, provide support, maintain security, prevent abuse, improve Diya, and comply with legal obligations. We do not sell personal information.

Third-Party Services

Diya shares the content needed to answer your request with AI providers such as Anthropic or OpenAI. This can include chat messages and related request context. These providers process information only as needed to provide the requested assistant response, operate the service, troubleshoot issues, maintain safety, and comply with legal obligations.

The Listen experience uses YouTube API Services, including the embedded YouTube player, to open or play YouTube-hosted media. YouTube and Google may receive information from your device or browser when a YouTube player loads or when you play YouTube content, including information needed to render the player, determine playability, prevent abuse, and apply content restrictions. YouTube content is governed by Google's policies, including the Google Privacy Policy and YouTube Terms of Service.

If product analytics are enabled, Diya may use a product analytics provider such as PostHog to process app interaction data. If advertising attribution or measurement is enabled, Diya may use the Meta/Facebook SDK and Meta SDK App Events to measure ad performance, attribute installs or app activations, and report trial-start or purchase-related conversion events. Diya may use Supabase to process onboarding response records, subscription records, attribution records, and RevenueCat trial webhook records. Diya also uses cloud hosting and infrastructure providers to operate the app and hosted web services. Service providers that process user data are expected to protect user data as described in this policy and as required by applicable law.

Local Data

Practice progress, reminder preferences, onboarding completion, the name you enter, saved verses, and Gita journey reflections are stored locally on your device. Local data is not used for advertising or tracking. Most local data is not available to Diya unless it is sent as part of an Ask Diya request, support request, analytics event, or onboarding response record described above. Deleting the app removes locally stored Diya app data from your device.

On iOS, Diya stores limited widget state locally, including Daily Diya streak date keys and a widget sync timestamp, in the app's shared App Group container. The Daily Quote widget reads this local App Group data so it can display your current streak alongside the bundled daily quote outside the main app. This widget state is not transmitted to Diya's servers or third parties unless described elsewhere in this policy.

Notifications And Purchases

Notification permission is optional and is used for local practice reminders. Diya does not use remote push notifications in this version.

Diya offers in-app purchase subscription flows through Apple and RevenueCat. Apple processes payment and billing information; Diya does not receive or store your payment card information.

To provide, restore, and support subscription access, Diya may receive purchase-related information such as product identifiers, entitlement status, transaction or subscriber identifiers, purchase dates, renewal, cancellation, expiration, and refund status from Apple or RevenueCat. This information is used for subscription administration and support. When advertising attribution or measurement is enabled, Diya may send limited trial-start or purchase-related conversion event data to Meta/Facebook SDK App Events after RevenueCat confirms subscription or trial state. Diya's app-owned conversion event may include the Meta StartTrial App Event after a confirmed active free-trial entitlement; Diya does not send payment card information to Meta.

Tracking

Diya may use the Meta/Facebook SDK and Meta SDK App Events for ad attribution and advertising measurement, including app activation, trial-start, and purchase-related conversion measurement. During onboarding, Diya may ask for permission under Apple's App Tracking Transparency framework. If you grant permission, iOS may allow access to advertising identifiers that help measure ad performance and attribute ads. If you deny permission, Diya will not access the IDFA, and you can still use the app. Diya does not sell personal information, share personal information with data brokers, or use chat, prayer, scripture, or reflection content for advertising attribution or measurement.

Data Retention And Deletion

Diya's app backend is not designed to maintain a permanent chat history in this version. Chat requests may be processed by AI providers and infrastructure providers according to their retention and security practices. Onboarding response records, analytics records, subscription records, attribution records, RevenueCat webhook records, and support communications may be retained as long as reasonably necessary to operate Diya, understand and improve the app, administer subscriptions, respond to support requests, maintain records, prevent abuse, or comply with legal obligations.

You may request access to or deletion of information associated with a support request or backend record by contacting us. Because Diya does not require accounts in this version, we may need information from you to locate backend records associated with your app installation, support request, or subscription. Most in-app practice data is stored locally and can be deleted by deleting the app from your device.

Data Security

We use reasonable safeguards designed to protect information, including encryption in transit where supported and access controls for service infrastructure. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Children's Privacy

Diya is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can review and delete it as appropriate.

Your Choices

You can decline notification or tracking permissions in iOS Settings. You can choose not to start Ask Diya, YouTube playback, or optional reminders. You can also delete the app to remove locally stored app data from your device.

Changes To This Policy

We may update this policy as Diya changes. The updated policy will be posted with a new "Last updated" date.

Contact

For privacy or support questions, contact hello@tryhoudiniapp.com.