Doxa Cookie & Tracking Policy
Effective Date: 23 January 2026 | Last updated: 9 October 2026
We believe in transparency. This policy explains what cookies and tracking technologies we use, why we use them, and how you can control them.
Key update (9 October 2026, second update): The returning visitor cookie, doxa_returning, is now a preference cookie, not an essential one. It follows your analytics choice: in the UK, the EEA and Switzerland (and wherever we cannot tell where you are), the web app sets it only after you accept cookies. If you reject them, we remove it. The website still works without it: when you are signed in, it shows Open Doxa.
Earlier update (9 October 2026): When you use the Doxa web app while signed in, it sets one more first-party cookie, doxa_returning. It remembers that you have signed in on this browser before, and whether you lead a church or ministry, so the doxa.app website can show you Log in, Open Doxa or Open your church instead of the sign-up button. It holds no name, email or account ID, and it is never used for analytics or advertising.
Earlier update (8 October 2026): In the UK, the EEA and Switzerland (and wherever we cannot tell where you are), the website and the web app now ask before they set analytics or advertising cookies. A banner offers Accept and Reject, with equal weight, and you can change your choice at any time with Cookie settings in the website footer. Until you accept, Google Analytics, the Meta Pixel and the X pixel do not load, and PostHog keeps no cookie or local storage, records no session replay, and is not linked to your Doxa account. If you reject, it stays that way and we do not ask again. Everywhere else these technologies load as before, and you can turn them off with Cookie settings.
Earlier update (7 October 2026):We checked this policy against what Doxa's code does today. The doxa.app marketing website runs the Meta Pixel and the X (Twitter) pixel, which set advertising cookies, and we said before that it set none. Google Analytics runs on the whole Doxa website, including the signed-in web app. PostHog and Sentry are linked to your Doxa account. The website has no cookie consent banner and does not respond to Do Not Track signals. The AI table now names the right providers. This version corrects all of these.
This Cookie & Tracking Policy forms part of our Privacy & Data Protection Policy and should be read alongside our Terms of Service.
1. Our Approach
We use cookies and similar technologies for four things: to run the Service (essential), to remember that you have signed in so the website can take you back to your account (preference), to understand how Doxa is used (analytics), and to measure Doxa's own advertising. In the UK, the EEA and Switzerland, the preference, analytics and advertising ones wait until you accept them (see Section 4). We do NOT:
- Show ads in Doxa
- Use your records, prophecies, testimonies, or prayers for advertising
- Sell your data to data brokers or advertising networks
We do use advertising technology to measure our own ads. The doxa.app marketing website runs the Meta Pixel and the X pixel, which set advertising cookies and let Meta and X see your visits to the website. The mobile app shares the device advertising identifier with Meta, and the Android app with Tenjin and AppLovin. See Advertising Cookies (Website) and Advertising Measurement (Mobile App) in Section 2 below.
2. Technologies We Use
Essential Cookies & Storage
Required for the Service to function. Without these, you cannot log in or use core features.
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Auth Session | Supabase | Keeps you logged in | Until logout/expiry |
| Secure Token | Supabase | API authentication | Session |
| Country (doxa_country) | Doxa | Your country from your connection, to show prices in your currency and to know whether to ask for cookie consent first | 1 day |
| Cookie choice (doxa_consent) | Doxa | Remembers whether you accepted or rejected analytics and advertising cookies | 12 months |
| Local Storage | Browser/App | App preferences, cached data | Until cleared |
Preference Cookies
Set when you use the web app while signed in, so the doxa.app website can show Log in, Open Doxa or Open your church instead of the sign-up button. They follow your analytics choice. In the UK, the EEA and Switzerland (and wherever we cannot tell where you are), we set them only after you accept cookies (Accept, or Analytics under Choose). Elsewhere we set them unless you reject analytics cookies with Cookie settings. If you reject them, we remove them. They are never used for analytics or advertising.
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Returning visitor (doxa_returning) | Doxa | Set when you use the web app while signed in. Remembers that you have signed in on this browser, and whether you lead a church or ministry, so the website shows Log in or a link back to Doxa. No name, email or account ID | 12 months |
| Returning visitor check (doxa_returning_chk) | Doxa | Lets the web app check the cookie above at most once a day for the signed-in account (10 minutes if the check fails). Your browser's scripts cannot read it | 1 day |
Analytics Technologies
Used to understand how the Service is used and improve the experience.
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Google Analytics 4 | Page views, events, traffic sources on the doxa.app website and the Doxa web app (including signed-in pages) | 2 years | |
| PostHog Analytics | PostHog (EU) | Product analytics linked to your Doxa account, funnel tracking, session replay in the web app (text inputs masked) | Persistent (PostHog default, up to 1 year) |
Google Analytics 4 runs on the doxa.app marketing website and on every page of the Doxa web app, including signed-in pages. In the UK, the EEA and Switzerland it loads only after you accept cookies; elsewhere it loads unless you reject it with Cookie settings. It records page views, events, and traffic sources. When you buy a subscription on the website, our servers can also send Google Analytics a purchase event with an identifier made from your Doxa user ID.
PostHogprovides product analytics (feature usage, funnel analysis) on the website, in the web app, and in the mobile app. It is not anonymous: when you sign in, the web app sends your Doxa user ID to PostHog, and the mobile app sends your user ID and email address. In the web app and the mobile app, PostHog can record a session replay. Text inputs are masked (and images too in the mobile app), but other text on the screen may be recorded. The marketing pages do not record replays. Data is hosted on PostHog's EU infrastructure (Frankfurt) and routed through our reverse proxy at insight.doxa.app. PostHog does not set cookies on mobile; on the web it stores an identifier in a cookie and in your browser's local storage. In the UK, the EEA and Switzerland, until you accept cookies (or after you reject them), PostHog on the web keeps its identifier in memory only, so nothing is stored in your browser, it records no session replay, and it does not link your visit to your Doxa account.
Advertising Cookies (Website)
Used on the doxa.app marketing website (for example the home page, the blog, and the Bible pages) to measure how well Doxa's own ads on Meta and X work. The signed-in Doxa web app does not load them.
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Meta Pixel (advertising cookies) | Meta Platforms, Inc. | Reports page views to Meta to measure Doxa's ads on Facebook and Instagram | Per Meta's cookie policy |
| X pixel (advertising cookies) | X Corp. | Reports page views to X to measure Doxa's ads on X | Per X's cookie policy |
These pixels send Meta and X the page you visited, your IP address, your browser information, and their own cookies and identifiers, which can link the visit to your Facebook, Instagram, or X account if you are signed in to them. Meta and X can use this data under their own privacy policies, including for their own advertising products. They never receive your records or anything you type in Doxa. In the UK, the EEA and Switzerland, these pixels load only after you accept cookies. Elsewhere they load unless you reject them with Cookie settings in the website footer. Separately, when you buy a subscription on the website, our servers can report the purchase to Meta (Conversions API) with a hashed copy of your email address and your Doxa user ID. Full detail is in the Advertising Measurement section of our Privacy & Data Protection Policy.
Advertising Measurement (Mobile App)
Used to measure how well Doxa's own advertising works. This subsection covers the mobile app, which uses no cookies for this. For the website, see Advertising Cookies (Website) above.
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Meta SDK (device advertising identifier) | Meta Platforms, Inc. | Attribute app installs and allowlisted milestones to Doxa's own ads | Per Meta's retention policy |
| Tenjin SDK, Android app only, outside the UK/EEA/Switzerland (Android Advertising ID, IP address, device info) | Tenjin, Inc.; reports on installs from AppLovin ads go to AppLovin Corporation | Attribute app installs and three milestone names to Doxa's own ads | Per Tenjin's and AppLovin's retention policies |
The Doxa mobile app uses the Meta (Facebook) SDK to attribute app installs and a short, fixed list of in-app milestones (such as signup and subscription) to ads a person previously saw. The reports include your device advertising identifier, which is the Android Advertising ID on Android and the Identifier for Advertisers (IDFA) on iOS. They never include your prophecies, testimonies, prayers, notes, images, voice, or anything you type or say in Doxa Engage. On iOS the identifier is used only if you grant permission at Apple's App Tracking Transparency prompt. On Android you can reset, limit, or delete your advertising ID in device settings, and Doxa honours that. Full detail and controls are in the Advertising Measurement section of our Privacy & Data Protection Policy.
The Android app also includes the Tenjin SDK, the measurement partner that AppLovin requires. On devices whose region is set outside the UK, the EEA, and Switzerland, it sends Tenjin the app install and three milestone names (signed up, first record created, subscription started) with the Android Advertising ID, IP address, and basic device and app information, and Tenjin tells AppLovin only about installs that came from an AppLovin ad. No content is sent, and Tenjin's probabilistic (IP and device) matching is off. The iPhone app does not include Tenjin: iOS installs are measured only through Apple's SKAdNetwork, with no device identifier.
Push Notification Tokens
Used to deliver push notifications to your device (if enabled).
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Expo Push Token | Expo (650 Industries) | Push notification delivery | Until app uninstall |
| APNs Token | Apple Inc. | iOS push delivery | Until app uninstall |
| FCM Token | Google LLC | Android push delivery | Until app uninstall |
Error Monitoring (Mobile App)
Used to identify and fix bugs. There is no in-app switch to turn it off; you can object by contacting privacy@doxa.app.
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| Error Reports | Sentry (Functional Software) | Crash and error tracking linked to your Doxa user ID, a screenshot when an error happens, masked session replays (1% of sessions, 5% of sessions with an error) | 90 days |
Website Hosting
Technologies used when you visit our website (doxa.app).
| Technology | Provider | Purpose | Duration |
|---|---|---|---|
| CDN/Edge | Vercel Inc. | Website hosting and delivery | Session |
| Access Logs | Vercel Inc. | Security and performance | 30 days |
3. AI Processing
Your content is processed by our AI partners when you use AI-powered features, and some processing runs automatically (the search index, reminder drafts, and titles for voice recordings):
| Feature | Provider | Data Processed | Retention |
|---|---|---|---|
| Audio Transcription | AssemblyAI (Deepgram as backup) | Audio files | Under the provider's retention settings |
| Title Generation (automatic for voice recordings) | Anthropic | Transcript text | Up to 7 days |
| Search Index (automatic) | OpenAI | Text of each record you save | Up to 30 days |
| Reminder Drafts (automatic) | OpenAI | Title and content of a saved record | Up to 30 days |
| Content Moderation | OpenAI | Text content you submit for sharing | Up to 30 days |
| Scripture Recommendations | OpenAI | Text content | Up to 30 days |
| Engage Text Sessions | Anthropic | Your messages and the records Engage reads | Up to 7 days |
| Voice Chat (Engage) | ElevenLabs | Voice audio streamed from your device, and Engage context from your Encouragement Vault | Under ElevenLabs' retention settings |
Your content is not used to train AI models per our agreements with these providers. Full detail is in Section 6B of our Privacy & Data Protection Policy.
Voice Chat (Engage): How It Works
When you use the Engage voice chat feature, here's exactly what happens with your data:
- Voice audio: Streamed in real time directly from your device to ElevenLabs (so ElevenLabs sees your device's IP address), not recorded or stored by Doxa
- Session metadata: Duration, voice preference, and topics are stored in your account to improve future sessions
- Conversation context: Your prophecies and testimonies may be referenced to provide personalized encouragement (this data already exists in your account)
- ElevenLabs records: Doxa does not keep the audio. ElevenLabs keeps a record of each session, which can include the audio and a transcript, under its own retention settings
You can use text-only mode if you prefer not to use voice features.
4. Your Choices & Control
You have control over how we use tracking technologies. Here are your options:
Push Notifications
You can disable push notifications at any time through your device settings (Settings → Notifications → Doxa). Disabling notifications does not affect other app functionality.
Error Reporting
Sentry error reporting helps us fix bugs and improve reliability. You can:
- Request deletion of your error data at privacy@doxa.app
- Error data is automatically deleted after 90 days
- We do not use error data for any purpose other than fixing bugs
Browser Cookies
When using our website, you can manage cookies through your browser settings:
- Block all cookies: Note that this will prevent login and essential functionality
- Delete cookies: Clear your browser cookies to remove session data
- Private/Incognito mode: Browse without persistent cookies
The website and the web app use essential cookies, preference cookies (the returning visitor cookies), analytics cookies (Google Analytics and PostHog), and, on the marketing pages, advertising cookies (the Meta Pixel and the X pixel). In the UK, the EEA and Switzerland, and wherever we cannot tell where you are, a banner asks you to accept or reject the preference, analytics and advertising cookies before they are set; Doxa works either way. Elsewhere they are set unless you reject them. To change your choice at any time, select Cookie settings in the website footer. Rejecting removes the preference, analytics and advertising cookies Doxa's website set. You can also block third-party cookies in your browser, use a tracker blocker, or use Google's Analytics opt-out browser add-on.
AI Features
Engage, voice recording, and the Doxa tools in AI assistants are optional. Some AI processing runs automatically when you save a record: its text goes to OpenAI for the search index, and its title and content go to OpenAI to draft its reminder. A voice recording's transcript goes to Anthropic for a title. You can avoid voice and Engage processing by typing your records and not using Engage.
Do Not Track
If your browser sends a Global Privacy Control or "Do Not Track" signal and you have not made a choice with Cookie settings, the website and the web app treat it as Reject: the preference, analytics and advertising cookies are not set. A choice you make with Cookie settings takes priority. In the mobile app, you control advertising measurement in your device settings (iOS App Tracking Transparency, or the Android advertising ID controls).
5. Third-Party Privacy Policies
For more information about how our partners handle data:
- Supabase: Privacy Policy
- Stripe: Privacy Policy
- Expo: Privacy Policy
- Sentry: Privacy Policy
- Vercel: Privacy Policy
- OpenAI: Privacy Policy
- AssemblyAI: Privacy Policy
- Apple: Privacy Policy
- Google: Privacy Policy
- PostHog: Privacy Policy
- Meta: Privacy Policy
- X: Privacy Policy
6. Data Retention Summary
- Authentication data: Until you log out or session expires
- Push tokens: Until you uninstall the app or disable notifications
- Error logs: 90 days, then automatically deleted
- Website access logs: 30 days
- Analytics data: Google Analytics: 2 years; PostHog: per PostHog's EU retention settings
- Website advertising cookies and web purchase reports: Held by Meta and X under their own retention policies
- Advertising measurement data (mobile app): Device advertising identifier and install/milestone events held by Meta, and for the Android app by Tenjin and (for installs from AppLovin ads) AppLovin, under their own retention policies; not stored in Doxa's database; resetting the identifier in device settings and reinstalling the app breaks the link
- AI processing data: Kept by each AI provider for its retention period (Anthropic up to 7 days, OpenAI up to 30 days; AssemblyAI and ElevenLabs under their retention settings)
- Voice chat audio: Not stored by Doxa; ElevenLabs keeps Engage session records under its retention settings
- Voice chat session metadata: Retained with your account until you delete it
- Payment/subscription data: Retained by Stripe; subscription records retained for legal/accounting purposes
7. Changes to This Policy
We may update this policy from time to time. Material changes will be communicated via the app or this page. The "Last updated" date at the top indicates when this policy was revised.
8. Legal Basis for Cookies
Under UK GDPR, ePrivacy Directive, and PECR, we rely on the following legal bases:
- Strictly necessary cookies: No consent required, as these are essential for the Service to function
- Preference cookies (returning visitor): Consent in the UK, the EEA and Switzerland, given with your analytics choice in the cookie banner before they are set. Elsewhere, legitimate interest (taking you back to your account), and you can reject them with Cookie settings
- Analytics/performance cookies: Consent in the UK, the EEA and Switzerland, asked for with the cookie banner before they are set. Elsewhere, legitimate interest (product improvement), and you can reject them with Cookie settings
- Advertising cookies (website): The doxa.app marketing website uses the Meta Pixel and the X pixel to measure our own ads. Consent in the UK, the EEA and Switzerland, asked for before they load. Elsewhere they load unless you reject them with Cookie settings. The mobile app sets no advertising cookies
- Advertising measurement (mobile app): Consent on iOS, given at Apple's App Tracking Transparency prompt; legitimate interest on Android, where you can reset or limit the advertising identifier in device settings
- Optional AI features: Consent (provided when you choose to use these features)
9. Disclaimer
While we take measures to limit tracking and protect your privacy, you acknowledge that:
- Third-party providers (Apple, Google, Supabase) may collect data according to their own privacy policies
- Your device and browser may transmit data that we cannot control
- We are not liable for tracking conducted by third parties outside our control
- You are responsible for managing your own device and browser settings
10. Contact Us
For questions about cookies or tracking technologies:
Email: privacy@doxa.app
Address: The Doxa Way Ltd, 108 Kings Road, New Haw, Addlestone, KT15 3BH, United Kingdom
See also our Privacy & Data Protection Policy and Terms of Service.
Our Commitment to Your Privacy
No ads in Doxa. We never sell your data, and your records are never used for advertising. We measure our own ads with advertising cookies on our website, which you can accept or reject, and the device advertising identifier in the app, and this policy tells you how to limit both. Your privacy matters.