Legal / Cookie Policy

Cookie Policy

Last updated: April 22, 2026

This policy explains what cookies and similar tracking technologies Divine Connect uses, why we use them, and how you can control them.

What are cookies?

Cookies are small text files stored on your device when you visit a website or use an app. They help services remember you between visits, keep you logged in, and understand how you use the product. On mobile, we use similar technologies such as local storage and device identifiers.

Strictly Necessary

Always active

Required for the service to function. These cannot be disabled.

  • ● Authentication tokens
  • ● Session identifiers
  • ● Security tokens (CSRF)
  • ● User preference cache

Functional

Optional

Enable enhanced features like remembering your language preference and deity selection.

  • ● Language preference
  • ● Last viewed deity
  • ● Notification settings
  • ● Theme preference

Analytics

Optional

Help us understand how users interact with Divine Connect so we can improve the experience. We use PostHog with IP anonymisation.

  • ● Page views & session duration
  • ● Feature engagement
  • ● Crash reports
  • ● Funnel analysis

Marketing

Optional

Used to show relevant advertisements and measure campaign effectiveness. We use these only in limited circumstances.

  • ● Ad frequency capping
  • ● Conversion tracking
  • ● Retargeting pixels

How to manage cookies

You can manage your cookie preferences at any time via the Settings → Privacy menu in the Divine Connect app.

For browser cookies on our website, you can also use your browser's built-in controls. Note that disabling strictly necessary cookies will prevent you from using core features of Divine Connect.

To opt out of analytics tracking across the web, visit posthog.com/privacy.

Third-party cookies

Some third-party services integrated into Divine Connect may set their own cookies. These include Razorpay (payment), PostHog (analytics), and YouTube (embedded content). We do not control these third-party cookies; please refer to their respective privacy policies.

Questions? Contact us at [email protected]