This Cookie Policy explains how Tiger LLC uses cookies, web-storage, and similar SDK-level identifiers across divineapp.io (this website) and the Divine mobile application. It supplements our Privacy Policy.
1. What is a cookie?
A cookie is a small file written to your browser by a website to remember you across pages, sessions, or visits. Cookies set by the site you are visiting are first-party; cookies set by other domains (such as Google) are third-party.
Mobile applications typically do not use browser cookies but rely on equivalent on-device identifiers (e.g., values stored by an SDK, the Apple Identifier for Advertisers, or the Android Advertising ID) which serve a similar purpose. We treat both consistently in this Policy.
Cookies and identifiers fall into four categories:
- Strictly necessary — required for the website or App to function.
- Functional — remember your preferences so you don’t have to re-set them.
- Analytics & performance — help us understand how Divine is used so we can improve it.
- Advertising — show ads in the free tier of the App and record your consent for personalized advertising.
Several adjacent technologies do similar work and are covered by this Policy on the same terms:
- Web beacons (also called tracking pixels) — tiny images or scripts that record that a page or email was opened.
- SDK identifiers — values that mobile-app SDKs store locally on the device (e.g., in iOS Keychain, Android Keystore, or the App’s sandbox storage). These are not cookies but serve similar identification functions.
- Local-storage and IndexedDB — browser storage mechanisms that persist data on your device.
This Policy treats all of the above consistently — what we do with each is described per surface below.
2. Cookies and storage used by the marketing website
We do not run analytics scripts, ad-tech tags, A/B-testing trackers, chat-widget sessions, or any third-party advertising pixels on the marketing site.
| Name / type | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
next-route-announcer (ARIA live region) | Tiger LLC (first-party) | Announces route changes to screen readers. No personal information stored. | Strictly necessary | Session |
HTTP preconnect to fonts.googleapis.com and fonts.gstatic.com | Google LLC | Loads the Special Gothic Condensed One typeface used for the Divine wordmark. No cookie is set by the preconnect; Google’s servers log the IP address that requests the font under Google’s own privacy practices. | Strictly necessary | Per request |
| Local-storage keys written by Next.js framework | Tiger LLC (first-party) | Remember the page you came from for back-navigation. Not tied to your identity or shared. | Functional | Persistent until cleared |
Because the marketing site is informational and does not require accounts, most pages can be viewed without any cookie or storage being set at all.
3. Identifiers used by the Divine app
The Divine mobile application does not use browser cookies. It does use on-device identifiers and SDK storage to make features work and to keep your account secure.
3.1 Strictly necessary
| Identifier | Provider | Purpose | Duration |
|---|---|---|---|
| Session token | Tiger LLC (first-party) | Keeps you signed in to your Divine account. Stored in encrypted Keychain on iOS or Keystore on Android. | Until sign-out, account deletion, or token rotation |
| Per-call session token | Stream.io, Inc. | Authenticates the device with Stream’s real-time audio infrastructure during voice match or Spaces. Issued at call start. Not used for tracking; only valid for the duration of the call. | Per call (token expires when the call ends) |
| Device identifier | Tiger LLC (first-party) | A randomly generated identifier we associate with your account to prevent abuse. Does not identify your physical device to anyone outside Divine. | Until account deletion or device reset |
| APNs / FCM push token | Apple Inc. / Google LLC | Allows Apple Push Notification service and Firebase Cloud Messaging to deliver incoming-call, message, and follower notifications. | Rotated by platform; refreshed automatically |
| DeviceCheck token | Apple Inc. | Two bits of information per device, set by Tiger LLC to prevent a single abusive device from spawning many accounts. | Persistent device-bound |
| RevenueCat customer identifier | RevenueCat, Inc. | Attributes App Store / Play Store receipts to your account for subscription and entitlement. | Until account deletion |
| App Store / Play Store transaction ID | Apple Inc. / Google LLC | Records in-app purchases and is required for refunds, restorations, and entitlement validation. | Permanent (transaction record) |
| UMP consent string | Google LLC | Records your consent or rejection of personalized advertising under GDPR. | Until you change it |
3.2 Functional
| Identifier | Provider | Purpose | Duration |
|---|---|---|---|
| Locale / region preference | Tiger LLC (first-party) | Remembers your language and regional settings. | Until changed |
| Accessibility preferences | Tiger LLC (first-party) | Remembers text size, reduced motion, and similar accessibility-related preferences. | Until changed |
| Last-used filters / discovery preferences | Tiger LLC (first-party) | Remembers your most recent discovery filters so they persist between sessions. | Until changed |
3.3 Analytics & performance
| Identifier | Provider | Purpose | Duration |
|---|---|---|---|
| Sentry installation ID | Functional Software, Inc. (Sentry) | Crash reporting and error monitoring. Helps us link a stack trace to the install instance that produced it. Does not see your name or contact information. | Persistent install-bound |
| PostHog distinct ID | PostHog, Inc. | Product analytics. We pass PostHog an account-scoped identifier so we can analyze flows and funnels without exposing your raw account information to PostHog. | Until account deletion |
| Build version and OS metadata | Tiger LLC (first-party) / Sentry / PostHog | Used to associate diagnostic information with the App build that produced it. | Per session |
3.4 Advertising
| Identifier | Provider | Purpose | Duration |
|---|---|---|---|
| Apple Identifier for Advertisers (IDFA) | Apple Inc. | Personalized in-App advertising via AdMob. Used only when you grant App Tracking Transparency permission. You can reset or disable it in iOS Settings → Privacy & Security → Apple Advertising. | Until reset or revoked |
| Android Advertising ID | Google LLC | Personalized in-App advertising on Android. Used only with your consent. Reset or delete it in Android Settings → Google → Ads. | Until reset or deleted |
| Non-personalized ad identifier | Google LLC (AdMob) | A randomly generated, non-resettable on-device identifier limited to ad serving and limited to non-personalized ads when you have not granted ATT consent. | Until app reinstall |
| AdMob session/imp tokens | Google LLC (AdMob) | Operational identifiers AdMob uses to serve and count individual ad impressions. | Per ad request |
Ad creatives served by AdMob inside the App can write their own short-lived storage during the rendering lifecycle for ad measurement and frequency-capping purposes. This storage is governed by Google’s policies and is outside Tiger LLC’s direct control.
4. How long we keep cookies and identifiers
Cookies are either session (deleted when you close your browser) or persistent (stored on your device until they expire or you delete them). Each entry in the tables above includes its duration. Generally:
- Strictly necessary cookies and identifiers are kept as long as the App or website needs them to function.
- Functional preferences are kept until you change them.
- Analytics identifiers are kept until account deletion or app reinstall.
- Advertising identifiers are kept until you reset them or revoke consent.
5. Your controls
5.1 Browser (this website)
You can clear local-storage keys and cookies for divineapp.io at any time through your browser settings. Most browsers also let you block cookies for specific sites or globally. There is very little to clear — we don’t use third-party tracking on the marketing site.
5.2 iOS
- App Tracking Transparency. Settings → Privacy & Security → Tracking. Toggle Divine off to prevent personalized-ad identifiers.
- Apple Advertising. Settings → Privacy & Security → Apple Advertising. Reset the advertising identifier.
- Push notifications. Settings → Notifications → Divine. You can disable notifications without disabling other features.
- Location. Settings → Privacy & Security → Location Services → Divine.
- Camera, microphone, photos. Same place. Toggle individual features.
5.3 Android
- Ad personalization. Settings → Google → Ads. Toggle off personalized ads or delete the advertising ID.
- Notifications. Settings → Apps → Divine → Notifications.
- Permissions. Settings → Apps → Divine → Permissions.
5.4 Analytics opt-out
If you wish to opt out of product analytics, email support@divineapp.io with the subject line “Analytics Opt-Out.” We will exclude your account from PostHog ingest going forward.
5.5 Account deletion
Deleting your account removes the on-device session, push token, and all SDK identifiers we hold. Some platform-level identifiers (the IDFA / advertising ID) are owned by the operating system and persist until you reset them through OS settings or reinstall the App.
6. Cross-context behavioral advertising
When you grant ATT permission on iOS or do not opt out of personalized advertising on Android or via UMP, Google AdMob may use device-level signals to deliver personalized ads. Under the California Privacy Rights Act and similar state laws, this may constitute “sharing” of personal information for cross-context behavioral advertising. You have the right to opt out at any time using the device-level controls above or by emailing us with the subject line “Do Not Sell or Share.”
7. IAB Transparency & Consent Framework (TCF v2.2)
Tiger LLC is not a registered Consent Management Platform (CMP) or a registered TCF vendor.
Google AdMob uses the TCF v2.2 framework for EEA/UK consent signaling via Google’s User Messaging Platform (UMP). When you respond to the UMP prompt inside the App, your choice is encoded in a TCF consent string and passed to AdMob for ad-personalization decisions.
The marketing website does not use the TCF because it does not load any vendor that participates in TCF.
8. IAB Global Privacy Platform (GPP)
We observe the IAB GPP string on the marketing site where supplied by your browser, as part of our handling of Global Privacy Control signals (see §10).
The App relies on the OS-level controls — App Tracking Transparency on iOS, Android Ad Personalization on Android — rather than GPP, because those are the controls the platforms surface to users.
9. EU/UK cookie consent on the marketing website
The marketing website does not display a cookie-consent banner because we do not set any non-strictly-necessary cookies on the site. The Google Fonts preconnect described in §2 transmits a request to Google’s servers and may result in Google logging the IP address that requested the font under Google’s own privacy practices, but it does not write a cookie to your browser.
If we later add analytics, advertising, or other non-strictly-necessary tracking to the marketing site, we will add an IAB TCF-compliant consent banner before doing so.
10. Do Not Track and Global Privacy Control
Our marketing website honors Do Not Track signals where supported. For users in states whose laws give the Global Privacy Control (GPC) signal legal effect (e.g., California, Colorado, Connecticut), we treat a GPC signal received from your browser as a valid opt-out of sale and targeted advertising on divineapp.io.
The mobile App does not respond to browser-based DNT signals; instead, the same intent is expressed through the App Tracking Transparency prompt on iOS and the ad-personalization toggle on Android, which we honor.
11. Changes to this Policy
We may update this Cookie Policy from time to time. When we do, we update the “Effective date” at the top and, for material changes, notify you through the App.
12. Contact
Tiger LLC
California, United States
Email: support@divineapp.io