Doxa Privacy & Data Protection Policy

Version 1.2 | Last updated: 9 October 2026 | First published: 23 January 2026

Plain Language Summary

  • Who is responsible. The Doxa Way Ltd, a company in England and Wales, is the controller of your personal data. Contact us at privacy@doxa.app.
  • The law we follow. Doxa follows the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations (PECR). We give everyone who uses Doxa, wherever they live, the same rights and protections as the EU GDPR. Where we have not yet fully met a requirement, this policy says so.
  • Where your data is stored.Doxa's database, sign-in and file storage are in the United Kingdom (London). Some of the providers that help us run Doxa are in the USA. Section 6 names where each provider processes data and the safeguard for each transfer, and Section 7 explains them.
  • Your faith is special category data. What you record can show your religious beliefs. We process it only with your explicit consent, which you give with a separate checkbox and can withdraw at any time (Section 5).
  • No sale, no ads from your records.We do not sell your data. Your records are not used for advertising. We do measure Doxa's own advertising, as Section 3 explains.
  • Your rights.You can get a copy of your data, correct it or delete it, and you can complain to the Information Commissioner's Office (Section 11).

What changed in version 1.2 (9 October 2026):

  • Correction: your data is stored in London, not the USA.Earlier versions said that our database (Supabase) is in the USA. That was wrong. It is in the United Kingdom, in Amazon Web Services' London region.
  • A clear statement of the data protection laws we follow, and a table of the lawful basis for each thing we do (Section 4).
  • Explicit consent for faith data. We now ask for your explicit consent, with a separate checkbox that is not ticked for you, before we process what you record (Section 5).
  • The provider list now says, for each provider, whether it acts for us (a processor) or for itself (a controller), where it processes data and which transfer safeguard applies (Section 6). We added Upstash, Fly.io, Discord, Google Workspace and Clarify. The web app's server functions and rate limiting now run in London, voice transcription runs on AssemblyAI's European servers, and Deepgram is turned off.
  • Corrected what our AI providers keep and whether they can train on data (Section 8).
  • New sections: international transfers (Section 7), churches (Section 9), children (Section 13), Data Protection Officer (Section 16) and contacts at churches we write to (Section 10).

Earlier versions and what changed in each are listed on our version history page.

1. Who We Are

The Doxa Way Ltd ("Doxa", "we", "us") provides the Doxa mobile app, the doxa.app website and web app, the Doxa bots on Telegram and Discord, and the Doxa connector for ChatGPT and other AI assistants (together, "the Service"). We are the controller of the personal data described in this policy, except where Section 9 says that a church is the controller.

  • Company number: 16744139 (registered in England and Wales)
  • Registered address: 108 Kings Road, New Haw, Addlestone, KT15 3BH, United Kingdom
  • Privacy contact: privacy@doxa.app (this reaches our privacy lead; see Section 16)
  • POPIA Information Officer (South Africa): Garth Hilton Watson, privacy@doxa.app

2. The Data Protection Laws We Follow

These laws apply to Doxa, and we follow them:

  • the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018;
  • the Privacy and Electronic Communications Regulations 2003 (PECR), which cover cookies, similar technologies and electronic marketing;
  • other laws that apply where you live, such as POPIA in South Africa and US state privacy laws (Section 18).

Doxa is a UK service. We also give everyone who uses Doxa, wherever they live, the same rights and protections as the EU General Data Protection Regulation (EU GDPR). Where this policy refers to an article, the UK GDPR and the EU GDPR use the same number.

In practice, this means that we:

  • use personal data only for the purposes in Section 4, each with a lawful basis;
  • process special category data, such as your religious beliefs, only with your explicit consent (Section 5);
  • collect only what we need, and keep it only as long as Section 12 says;
  • tell you who receives your data, where it is processed and how each transfer is protected (Sections 6 and 7);
  • keep data secure, and tell the regulator and you about serious breaches (Section 15);
  • respond to your rights requests within one month (Section 11).

Where we have not yet fully met a requirement, this policy says so in the section concerned, and we are working to close it. At the date of this policy these are: a provider without a valid transfer safeguard (Clarify, and Tenjin for UK law; Section 6), the Doxa bot on Discord, which does not yet ask for explicit consent (Section 5), and the mobile app, which does not ask before the Meta SDK on Android reads the advertising identifier or before PostHog stores an identifier on your device (Section 17).

3. What Data We Collect

Account and profile

  • Name and email address (needed to create an account)
  • Profile picture, bio and location, if you add them
  • Sign-in method (email and password, Sign in with Apple, or Google Sign-In). Passwords are stored only as a hash
  • The versions of our terms and this policy you accepted, your confirmation that you are 13 or older, and when and which version of the explicit consent in Section 5 you gave

What you record (special category data)

  • Prophecies, testimonies, encouragements, prayers and notes, with the tags, dates and other details you add
  • Voice recordings you make to transcribe a record, and images you upload
  • What you say or type in Doxa Engage, and short notes Doxa saves after a session to help later sessions (for example what encourages you, and facts you stated, such as a family name or a health condition)
  • Your Bible reading and Bible searches

This content can show your religious beliefs. It can also include other special category data, such as facts about your health, and information about other people. Section 5 explains how we handle it.

Groups and churches

  • Groups and church boards you belong to, your role, and invitations you send or receive
  • Content you choose to share with a group or a church board, and weighing notes written there

Subscriptions and payments

  • Your plan, its status and usage counts (for example Engage minutes)
  • In-app purchases are processed by Apple or Google, and web purchases by Stripe. We do not receive or store your full card number

Technical and usage data

  • Device type, operating system and app version
  • IP address, used for security, rate limiting and to deliver the Service
  • Error reports from Sentry, linked to your Doxa user ID. A small sample of app sessions is recorded as a session replay with all text, images and graphics masked. Earlier versions of the app also attached an unmasked screenshot of the screen when an error happened, which could show your own content; versions of the app after 3.1.0 do not
  • Product analytics from PostHog, linked to your Doxa user ID (and, in the mobile app, your email address): screens you open, features you use, and session replays. In the mobile app, session replay masks all text and images. In the web app, it masks what you type, but other text on the screen, including your records, can be recorded. Earlier versions of the mobile app could also send the text of an item you tapped; versions of the app after 3.1.0 do not
  • Page views and events from Google Analytics 4 on the doxa.app website and web app (see Section 17)

Advertising measurement

Doxa shows no ads. We do buy ads elsewhere, and we measure which of them bring people to Doxa. Your records, prophecies, testimonies, prayers, images, voice and anything you say in Engage are never part of this.

  • Mobile app (Meta).The Meta SDK reports the app install and a fixed list of milestones (sign-up completed, first record created, Engage gift unlocked, Engage session started, an Engage session that drew on a personal record, paywall viewed, subscription purchased) with your device advertising identifier and a few non-content details such as the plan and the amount. On iPhone this happens only if you allow tracking at Apple's App Tracking Transparency prompt. On Android, your device's ad settings are respected.
  • Android app outside the UK, the EEA and Switzerland (Tenjin and AppLovin).The Tenjin SDK reports the install and three milestone names (signed up, first record created, subscription started) with the Android Advertising ID, IP address and device details. Tenjin tells AppLovin only about installs that came from an AppLovin ad. Tenjin's probabilistic matching is off. The Tenjin SDK does not start on devices whose region or time zone is in the UK, the EEA or Switzerland, and the iPhone app does not include it.
  • Website (Meta Pixel and X pixel). The doxa.app marketing website can load the Meta Pixel and the X pixel, which set advertising cookies and tell Meta and X which pages a browser visited. The signed-in web app does not load them. Section 17 and our Cookie & Tracking Policy say when they load.
  • Web purchases. When you buy on the website, our servers can report the purchase to Meta (Conversions API) with a hashed email address and a hashed Doxa user ID, the plan and the amount, and to Google Analytics with an identifier made from your user ID.

Your control: on iPhone, turn tracking off in Settings, Privacy & Security, Tracking. On Android, reset or delete your advertising ID in Settings, Google, Ads. On the website, use Cookie settings in the footer, or block third-party cookies.

Bots and AI assistants

  • Doxa bots on Telegram and Discord: your platform user ID and username, and the messages you exchange with the bot
  • Doxa in ChatGPT and other AI assistants: what the assistant sends to Doxa's tools (Section 8)

When you contact us

  • Your emails to support@doxa.app or privacy@doxa.app and our replies

What we do not collect

  • Precise GPS location
  • Your contacts, or photos and files you have not chosen to upload
  • Biometric data. If you unlock Doxa with Face ID, Touch ID or a fingerprint, your device does this. We never receive the biometric data

4. Why We Use Your Data, and Our Lawful Basis

The law requires a lawful basis for each use of personal data (Article 6), and an additional condition for special category data (Article 9). This table shows ours.

What we doLawful basis (Article 6)Special category condition (Article 9)
Create and run your account, sign you in, keep you secureContract (6(1)(b))Not applicable
Store, sync and search what you record; transcribe voice recordings; suggest titles, reminders and Scripture; run Doxa Engage; share with the people, groups and church boards you chooseContract (6(1)(b))Your explicit consent (9(2)(a)), Section 5
Show licensed Bible translations through YouVersionContract (6(1)(b))Your explicit consent (9(2)(a))
Reply to you through the Doxa bots and AI-assistant toolsContract (6(1)(b))Your explicit consent (9(2)(a)), given in the app or, on Telegram, in the bot (Section 5)
Publish a testimony you submit to The Grace RecordContract (6(1)(b))Your explicit consent (9(2)(a)); once published, data you made public (9(2)(e))
Take payments and manage your planContract (6(1)(b))Not applicable
Service emails (account, security, purchases) and support repliesContract (6(1)(b))Your explicit consent, where your message contains special category data
Find and fix errors (Sentry), and understand how Doxa is used so we can improve it and contact you about your account and the product (PostHog, in the app)Legitimate interests (6(1)(f)): a reliable, useful serviceYour explicit consent (9(2)(a)), where web app session replays or error screenshots from earlier app versions show your records; we use them only to find and fix problems
Analytics and advertising cookies on the doxa.app website and web app (Google Analytics, PostHog browser storage, the Meta and X pixels)In the UK, the EEA and Switzerland, and wherever we cannot tell where you are: your consent (6(1)(a)), given in the cookie banner. Elsewhere: legitimate interests (6(1)(f)), measuring and improving our website and ads, and you can reject them (Section 17)Not applicable: no record content is sent
Measure our own ads in the mobile app (advertising identifier)iPhone: your consent at Apple's tracking prompt (6(1)(a)). Android: legitimate interests (6(1)(f)), and you can reset or delete the identifierNot applicable: no record content is sent
Report web purchases to Meta and Google AnalyticsLegitimate interests (6(1)(f)): measuring our adsNot applicable
Follow-up emails about Doxa to people who use itLegitimate interests (6(1)(f)); for marketing email, the PECR rules on existing customers. You can stop them at any timeNot applicable
Emails you ask for on our website (for example a free resource)Consent (6(1)(a))Not applicable
Contact churches and their leaders about Doxa (Section 10)Legitimate interests (6(1)(f))Not applicable
Prevent fraud and abuse, rate-limit requests, check shared content for safetyLegitimate interests (6(1)(f))Your explicit consent, where the content is yours
Keep accounting records, answer lawful requests from authoritiesLegal obligation (6(1)(c))Legal claims (9(2)(f)), where needed
Contact emergency services if we learn of a serious risk to someone's lifeVital interests (6(1)(d))Vital interests (9(2)(c))

Where we rely on legitimate interests, we have balanced our interest against your rights, and you can object at any time (Section 11). Where we rely on consent, you can withdraw it at any time. Withdrawal does not make earlier processing unlawful.

5. Your Faith Data: Special Category Data and Explicit Consent

Doxa exists to help you record what God has said and done, and to remember it. What you record can show your religious beliefs. The law calls this special category data and protects it more strongly. We process it only with your explicit consent (Article 9(2)(a)).

How you give consent

When you create an account, and when you accept this version of the policy if you have not already given this consent, we show a separate checkbox. It is not ticked for you, and it is separate from accepting our terms. It says:

I agree that Doxa may process what I record, which can show my religious beliefs, to provide the app. I can withdraw this at any time in Settings.

We record when you gave this consent and which version of the wording you saw. The Doxa bot on Telegram asks for the same consent before it uses a message from you, and you can withdraw it there by sending /stop. The Doxa bot on Discord does not yet ask for this consent; until it does, please do not send it anything you do not want processed as this policy describes.

What the consent covers

  • Storing, syncing and searching what you record, and sharing it with the people, groups and church boards you choose
  • Sending it to the providers in Section 6 that help us run those features, including the AI providers in Section 8, in the way Section 8 describes
  • Session replays and error reports that can show your records on screen (Section 3), which we use only to find and fix problems in the app
  • Other special category data in your records, such as facts about your health, handled the same way

It does not cover advertising. Your records are not used for advertising, and we do not send them to advertising companies.

How to withdraw consent

In the app, go to Settings, then Legal, then Faith data consent. You can also email privacy@doxa.app. Doxa cannot keep or use your records without this consent, so withdrawing it means we delete your account and everything in it. Before you withdraw, you can ask us for a copy of your data from the same screen, and we will send it to you. Withdrawal does not make our earlier processing unlawful.

Information about other people

A prophecy or testimony can name other people, for example the person who gave a word. Please record only what you are entitled to share. If you share a record with someone, or bring it to a church board, the people who can see it there can read it.

6. Who Receives Your Data

We do not sell, rent or trade your personal data. We share it only with the organisations below, and only for the reasons given.

Processors: providers that act for us

These providers act on our behalf, as processors. "DPF" means the EU-US Data Privacy Framework and its UK Extension (the UK-US data bridge). "SCCs" means the European Commission's Standard Contractual Clauses (2021) with the UK Addendum issued by the Information Commissioner.

ProviderWhat it does for usDataWhereTransfer safeguard
SupabaseDatabase, sign-in, file storage and server functions. Hosted on Amazon Web ServicesAll account data and everything you recordUnited Kingdom (London, AWS eu-west-2). Supabase support staff, including in the USA, can access it when needed to support the service, and Supabase keeps service logs with its logging provider (Google BigQuery)Storage: none needed (UK). Support access and logs: SCCs in the data processing agreement of Supabase Pte. Ltd. (with Supabase, Inc.)
Vercel Inc.Hosts the doxa.app website and the Doxa web app. Its server functions handle your account and your records when you use the web appIP address, request logs, account identifiers, and record content handled by the web appServer functions: United Kingdom (London). Pages and static files: Vercel's global edge network. US companyDPF; SCCs as a fallback
Upstash, Inc.Counts requests to the web app so we can limit abuseIP address, type of request, timeUnited Kingdom (London). US companyDPF; SCCs as a fallback
OpenAI OpCo, LLCSearch index, reminder drafts, Scripture suggestions, topics, safety checks, Engage session notes (Section 8)Record text and titles, search text, Engage session text, shared and Grace Record text. No name, email or account IDUSASCCs
Anthropic Ireland, LimitedClaude: Engage text sessions, encouragement in bots and AI assistants, drafting help, titles, content review (Section 8)Engage messages, records Engage reads, titles and remembered facts, voice transcripts, drafts. No name, email or account IDUSASCCs
Eleven Labs Inc.Engage voice: real-time voice conversation and text-to-speech (Section 8)Your voice (not recorded), your device's IP address, Engage context and records Engage reads, session transcriptsUSADPF; SCCs as a fallback
AssemblyAI Inc.Transcribes voice recordingsAudio of your recording and its transcriptEU (AssemblyAI's European servers). US companyStorage in the EU: UK adequacy regulations. Any access from the USA: DPF; SCCs as a fallback
Deepgram, Inc.Backup transcription. Turned off since 7 October 2026: no data is sent to Deepgram. We will update this policy before we use it againNone while turned offUSANot applicable while turned off
Expo (650 Industries, Inc.)Sends push notifications, and delivers app updatesPush token, notification text (general wording that does not quote your records; the weekly push can quote a testimony its author published in The Grace Record), device and app details, IP addressUSADPF
Functional Software, Inc. (Sentry)Error monitoring and masked session replaysDoxa user ID, device details, error details; from earlier app versions, screenshots that can show your contentEU (Frankfurt) for error data; Sentry's own account records in the USADPF; SCCs as a fallback
PostHog Inc.Product analytics and session replay, through our own address insight.doxa.appDoxa user ID (and email in the mobile app), events, screen views, device details, session replays (web app replays can show your records)EU (Frankfurt)DPF; SCCs as a fallback
Plus Five Five, Inc. (Resend)Sends our emailsEmail address, name, email content, delivery recordsSent from Ireland (AWS eu-west-1); stored in the USADPF; SCCs as a fallback
GoogleGoogle Analytics 4 on the website and web app; Google Workspace for our email (including privacy@doxa.app and support@doxa.app) and for adding Android testers; the Gemini API for research on public Grace Record testimoniesPage views and events with cookies; emails you send us; tester email addressesUSA and other countriesDPF; SCCs as a fallback
StripeWeb payments, the customer portal and Telegram paymentsName, email, billing and payment details, plan statusUSA and other countriesDPF; SCCs as a fallback. Stripe is also an independent controller for fraud prevention and its legal duties
Fly.io, Inc.Runs the Doxa Discord botDiscord user ID and username, messages you send the bot, logsBot servers in the United Kingdom (London); US company, whose own systems can be in the USADPF
GitHub, Inc.Receives short error summaries from Sentry so we can track bugsError title, place in the code, link to the reportUSADPF; SCCs as a fallback
Tenjin, Inc.Measures Android app installs from our ads, outside the UK, the EEA and Switzerland onlyAndroid Advertising ID, IP address, device details, install and three milestone namesUSATenjin's data processing agreement includes EU SCCs but not yet the UK Addendum, so we do not yet have a valid UK safeguard. Tenjin receives no data from people in the UK, the EEA or Switzerland
Clarify, Inc.Our contact manager for churches and partners (Section 10)Names, email addresses, organisations, notes, and the emails and calendar of our team's synced mailbox, which can include messages you send to support@doxa.app or privacy@doxa.appUSANone in place at the date of this policy: Clarify's Data Privacy Framework certification lapsed on 26 September 2026, and we have not yet signed its data processing agreement. We are reviewing this

Controllers: organisations that decide for themselves

These organisations receive personal data through Doxa but decide for themselves how to use it, under their own privacy policies. They are independent controllers, or, for Meta, a joint controller with us.

OrganisationWhy it receives dataDataRole and safeguard
AppleApp Store, in-app purchases, push delivery (APNs), Sign in with AppleDevice tokens, purchase data, Apple ID relay email, notification textIndependent controller. Apple transfers data to the USA under its own SCCs
Google (Google Play and Google Sign-In)Play Store, in-app purchases, push delivery on Android, Google Sign-InDevice tokens, purchase data, sign-in identifiersIndependent controller. DPF
Meta PlatformsMeasures our ads (mobile app SDK, website pixel, web purchase reports)Advertising identifier, milestone events, page visits, cookies, hashed email and user ID, plan and amountJoint controller with us for collecting and sending this data (Article 26), then an independent controller. EU-US DPF and SCCs; for UK users, Meta's UK data transfer addendum
X Corp.Measures our ads on X (website pixel)Page visits, IP address, browser details, X cookiesIndependent controller. DPF and SCCs
AppLovin CorporationAd network that runs our app-install ads; learns which installs its ads producedAndroid Advertising ID with the install and milestone names (via Tenjin); Apple SKAdNetwork reportsIndependent controller. DPF and SCCs
YouVersion, Inc.Supplies licensed Bible translations when you choose onePassage requested, Bible search text, IP address, app version. No account ID, name, email or recordsIndependent controller under its own privacy policy. Your device connects to YouVersion in the USA directly
TelegramCarries your messages with the Doxa bot on TelegramTelegram chat ID, username, messagesIndependent controller of its platform. We control what our bot stores
DiscordCarries your messages with the Doxa bot on DiscordDiscord user ID, username, server and channel IDs, messagesIndependent controller of its platform. We control what our bot stores
OpenAI (ChatGPT)Runs ChatGPT when you use Doxa inside ChatGPTYour ChatGPT conversationIndependent controller under OpenAI's own terms (Section 8)
OpenStreetMap FoundationTurns a place name in a public Grace Record submission into a map locationThe place name only, sent from our serversIndependent controller of its server logs. UK and Netherlands

Meta joint controller arrangement.For the Meta SDK, the Meta Pixel and the Conversions API, Doxa and Meta are joint controllers for collecting the data and sending it to Meta, under Meta's Controller Addendum. In short: Doxa is responsible for telling you about this collection (this policy) and for its lawful basis; Meta is responsible for its own processing after it receives the data, including your rights over that data. You can contact either of us. If you contact us, we will pass your request to Meta where needed.

Other disclosures

We may disclose personal data where the law requires or allows it: to comply with a court order or a legal obligation, to protect someone's life, to prevent fraud or crime, or to establish or defend legal claims. If we sell or merge our business, the buyer would receive your data under this policy, and we would tell you first. Where the law allows, we will tell you about a request from an authority.

Changes to our providers

We update this page when we add or change a provider. For an important change we also tell you in the app or by email. You can object by writing to privacy@doxa.app.

7. International Transfers

Doxa's database is in the United Kingdom. When a provider in Section 6 processes data in another country, the law calls this a restricted transfer. We make each transfer under one of these safeguards:

  • Adequacy. Transfers between the UK and the EEA rely on adequacy decisions. The European Commission renewed its decisions for the UK in December 2025, valid to December 2031.
  • Data Privacy Framework.For a US company certified under the EU-US Data Privacy Framework and its UK Extension, transfers rely on that certification. We keep the SCCs in place as a fallback where the provider's contract includes them.
  • Standard Contractual Clauses.For other providers, transfers rely on the European Commission's Standard Contractual Clauses (2021) with the UK Addendum, in the provider's data processing agreement.

Where we rely on Standard Contractual Clauses, we carry out a transfer risk assessment, following the Information Commissioner's guidance, and keep it on record. It looks at the data sent, the laws of the destination country, and the extra protections we use: encryption in transit, sending no name, email or account ID to AI providers, and short retention where the provider offers it.

Some providers are US companies, so the data they process can be subject to US law. Section 6 lists which providers process data in the USA. You can ask us for a copy of the safeguard for any transfer at privacy@doxa.app.

8. AI Providers and Your Records

Some Doxa features use AI providers. We want you to know exactly what they receive. Your Encouragement Vault is not sent to any AI provider as one export. We do not send your name, email address or Doxa account ID with your content. Most requests come from Doxa's servers, so the AI provider sees our server's IP address, not yours. The exception is Engage voice: your voice goes from your device to ElevenLabs, so ElevenLabs sees your device's IP address.

What happens automatically

  • When you save or update a record, its text goes to OpenAI to build your search index (an embedding).
  • When Doxa prepares a reminder of a saved record, the record's title and content go to OpenAI to draft it.
  • When you record by voice, the audio goes to AssemblyAI in the EU to be transcribed, and the transcript goes to Anthropic to suggest a title.

What happens when you use a feature

  • Engage voice (ElevenLabs). At the start: the titles of up to 10 prophecies and 8 other records, facts and concerns Doxa remembers from earlier sessions, and lines from your last session. During the session, Engage can look up a whole record, one at a time.
  • Engage text (Anthropic). Your messages, record titles, remembered facts, and the records Engage reads to answer you. When a session ends, its text goes to OpenAI so Doxa can save short notes for later sessions.
  • Search, sharing and The Grace Record. Search text goes to OpenAI. Text you share goes to OpenAI for a safety check. Testimonies submitted to The Grace Record go to OpenAI and Anthropic for themes, summaries and review.
  • Bible reading stays out of AI. Licensed translations from YouVersion are not sent to any AI provider. Our AI features read and quote only the public-domain Berean Standard Bible.

Training and retention

ProviderUsed to train AI models?How long the provider keeps it
OpenAINo. OpenAI's business terms exclude API data from training, and we have not opted inUp to 30 days, for abuse monitoring
AnthropicNo. Anthropic's commercial terms do not allow it to train on our dataDeleted within 30 days; content flagged for a policy breach can be kept for up to 2 years
ElevenLabsElevenLabs' terms allow it to use content to improve its models unless the customer opts out. We have not yet opted outYour voice is not recorded. Session transcripts are deleted after 7 days. Doxa checks this setting every day
AssemblyAINo. AssemblyAI does not use data sent to its European servers for trainingDoxa deletes the audio and the transcript from AssemblyAI as soon as it has saved the transcript

Doxa's staff do not read your records unless you ask us to (for example in a support request) or we must, to keep the Service safe or meet a legal duty. Inside a provider, access is limited by that provider's own controls, which we cannot see. No online service can promise that nothing will ever go wrong. If a provider weakens how it protects your data, we will tell you and give you time to get a copy of your data and delete your account.

Your choices

  • Type instead of speak: no audio goes to AssemblyAI.
  • Do not use Engage: nothing goes to ElevenLabs, and less goes to Anthropic.
  • The minimum: the text of each saved record still goes to OpenAI for your search index, and its title and content when Doxa drafts a reminder.

Doxa in ChatGPT and other AI assistants

  • When you use Doxa inside ChatGPT, OpenAI processes your conversation under its own terms. Doxa receives only what ChatGPT sends to Doxa's tools: a verse reference or quote, the situation you describe when you ask for encouragement, the topic you search, and anything you ask Doxa to keep or give.
  • Sign-in is optional. If you sign in, you approve the connection on a Doxa page, and ChatGPT can then save to, search and share from your Encouragement Vault through Doxa's tools. You can revoke it in ChatGPT's settings or by writing to privacy@doxa.app.
  • For each tool call, Doxa logs the tool, the time, the request's IP address and app name (in ChatGPT, normally OpenAI's server), and your Doxa user ID if you signed in. For requests from ChatGPT, Doxa logs the length of what you typed, not the text; for a quote check, the first 500 characters; and the first 200 characters of Doxa's reply. Through the connector for other assistants (doxa.app/mcp/v1), the situation you describe is logged in full.
  • ChatGPT sends an anonymous identifier for your ChatGPT account. Doxa stores it only as a one-way hash, to count free use. Without it, Doxa counts free use by IP address.

9. Churches: Who Is Responsible for What

A church can use Doxa to record, weigh and hold the words spoken over it, on a private church board. Data protection law asks who decides why and how the data is used. On Doxa:

  • The church is the controller of its church board. This is what the church records there: the words, who spoke them and when, weighing notes, held words, and who has which role. The church decides what to record and who can see it. Doxa processes this content for the church, only to provide the board.
  • Doxa is the controller of each member's own accountand personal Encouragement Vault. A personal word stays in that person's own Encouragement Vault. It appears on a church board only if they bring it there.
  • Doxa is also the controller of what it needs to run the Service for everyone: accounts, sign-in, billing, security, legal records and product analytics.

A church that uses a board is responsible for its own lawful basis for what it records, and for telling its members about it. A church can ask us for Doxa's Data Processing Terms for Churches (the Article 28 terms under which we process church board content) by writing to privacy@doxa.app. The same providers, locations and transfer safeguards in Sections 6 and 7 apply to church boards. A church can ask us at any time for a copy of its board, or to delete it.

10. Churches and Leaders We Contact

We write to churches, church leaders and partners about Doxa. We find their work contact details on public sources, such as church websites and directories, or receive them when they write to us. We keep their name, role, organisation, contact details and our emails with them in our contact manager (Clarify, Section 6). Our lawful basis is legitimate interests: telling churches about a service that can help them. If you are one of these contacts, you can ask us to stop at any time by replying or writing to privacy@doxa.app. We will then stop contacting you and delete your details, keeping only what we need to make sure we do not contact you again.

11. Your Rights

Under the UK GDPR, and wherever you live, you have the right to:

  • Access a copy of your personal data
  • Correct data that is wrong or incomplete
  • Delete your data
  • Restrict how we use your data in some cases
  • Take your data with you in a machine-readable format (portability)
  • Object to processing based on legitimate interests, and to direct marketing at any time
  • Withdraw consent at any time, where we rely on consent (Section 5 for faith data)
  • Not be subject to decisions made only by automated means that have legal or similar effects (Section 14)

How to use your rights

  • Get a copy of your data: email privacy@doxa.app and we send you your records in a machine-readable format
  • Delete your account: in the app, Settings, Account, Delete Account; or at doxa.app/delete-account
  • Anything else: email privacy@doxa.app from the address on your account

We reply within one month. If a request is complex, we can extend this by up to two more months, and we will tell you why within the first month. We do not charge, unless a request is clearly unfounded or excessive. We may ask you to confirm your identity.

Complaints

Please contact us first, so we can try to put things right. You also have the right to complain to the Information Commissioner's Office (ICO), the UK regulator: ico.org.uk/make-a-complaint, telephone 0303 123 1113. You can also complain to the data protection authority where you live.

12. How Long We Keep Data

DataHow long
Your account and recordsWhile your account exists. After you delete it: removed within 30 days, and from encrypted backups within 90 days
Engage session notesWith your account; deleted when you delete your account
Data held by AI providersSee the table in Section 8
Error reports and session replays (Sentry)Up to 90 days
Product analytics (PostHog)Events up to 7 years and session replays up to 90 days, under PostHog's retention for our plan. You can ask us to delete your analytics data at any time
Website analytics (Google Analytics)Up to 14 months
Emails we send (Resend)About 30 days at Resend
Rate-limit counters (Upstash)Minutes to hours; each counter expires on its own
AI-assistant tool-call logsWith Doxa's service records; you can ask us to delete the entries linked to your account
Advertising measurementHeld by Meta, X, Tenjin and AppLovin under their own retention. Doxa does not store your advertising identifier
Messages with the Doxa botsUntil you withdraw consent in the bot (on Telegram, send /stop) or ask us to delete them
Payment and accounting recordsUp to 7 years, as tax law requires
Contacts at churches we write toWhile we are in contact; deleted when you ask us to stop

When you delete your account, we also ask our processors to delete your data. We may keep data longer only if the law requires it or to establish or defend a legal claim.

13. Children and Young People

You must be at least 13 years old to use Doxa. If the law where you live sets a higher age for consenting to online services on your own (in some European countries it is up to 16) and you are under that age, you need your parent's or guardian's permission to use Doxa. We do not knowingly collect data from children under 13. If you think a child under 13 has an account, write to privacy@doxa.app and we will delete it.

Young people aged 13 to 17 can use Doxa, so the ICO's Age Appropriate Design Code (the Children's Code) applies to us. Doxa shows no ads, does not collect precise location, keeps records private unless you choose to share them, and does not sell personal data or use records for advertising.

14. Automated Decision-Making

We do not make decisions about you by automated means alone that have legal effects or similarly significant effects (Article 22). Our AI features help you: they transcribe, suggest titles, draft reminders and offer encouragement. They do not decide anything about your rights. An automated safety check can stop a piece of content from being shared; if this happens and you disagree, write to us and a person will review it.

15. Security and Data Breaches

  • Encryption in transit (HTTPS/TLS) for all connections
  • Encryption at rest (AES-256) for the database and file storage
  • Row-level security in the database, so each account can reach only what it is permitted to see
  • Rate limiting against abuse and brute-force attempts
  • Access to production data limited to the people and systems that need it

If a personal data breach happens, we will tell the ICO within 72 hours of becoming aware of it, where the law requires this. If the breach is likely to put your rights and freedoms at high risk, we will tell you without undue delay, explain what happened, and say what you can do. We record every breach, its effects and what we did about it.

You can help: use a strong password, keep your device locked, and tell us at once if you think someone has accessed your account.

16. Data Protection Officer

We have not appointed a Data Protection Officer. The law requires one when an organisation's core activities include processing special category data on a large scale (Article 37). Religious-belief data is central to Doxa, but at Doxa's current size this processing is not large scale, using the factors in the regulators' guidance (the number of people, the volume of data, how long and how widely it is processed). We review this decision as Doxa grows. Our privacy lead handles all data protection matters at privacy@doxa.app.

17. Cookies and Similar Technologies

The doxa.app website and web app use cookies and similar technologies for sign-in (essential), analytics (Google Analytics and PostHog) and advertising measurement (the Meta Pixel and the X pixel, on the marketing website only). In the UK, the EEA and Switzerland, and wherever we cannot tell where you are, a banner asks you to accept or reject analytics and advertising cookies before they are set. Until you accept, Google Analytics and the Meta and X pixels do not load, and PostHog stores nothing in your browser, records no session replay and is not linked to your Doxa account. Elsewhere these load unless you reject them. You can change your choice at any time with Cookie settings in the website footer. The website does not respond to Do Not Track or Global Privacy Control signals. The mobile app uses PostHog (no cookies) and the Meta SDK, and the Android app outside the UK, the EEA and Switzerland also uses the Tenjin SDK. The app does not yet ask before PostHog stores an identifier on your device, or, on Android, before the Meta SDK reads the advertising identifier; on iPhone, the Meta SDK uses the identifier only if you allow tracking. See our Cookie & Tracking Policy.

18. Rights Under Other Laws

South Africa (POPIA)

You can access, correct or delete your personal information, object to processing, and complain to the Information Regulator. We transfer data outside South Africa under contracts that give an adequate level of protection (section 72 POPIA).

United States (state privacy laws, including California)

  • You can ask to know, delete and correct your personal information, and to opt out of the sale or sharing of it. We do not sell personal information.
  • Our advertising measurement (the advertising identifier in the app, the Meta and X pixels on the website, and web purchase reports to Meta) may count as "sharing" for cross-context behavioural advertising under California law. To opt out: turn off tracking for Doxa on iPhone, reset or delete your advertising ID on Android, reject or block cookies on the website, or write to privacy@doxa.app. The website does not respond to Global Privacy Control signals.
  • Categories we collect: identifiers (name, email, user ID, advertising identifier, cookies), internet activity (usage and analytics), audio (voice recordings), sensitive information (religious beliefs in your records), and inferences (AI-generated suggestions). We use sensitive information only to provide the Service.
  • We do not discriminate against you for using these rights.
  • The Service is not directed at children under 13, and we do not knowingly collect their data (COPPA).

19. Changes to This Policy

We update this policy when what we do changes. The version number and date at the top show the current version. When we make an important change, we tell you in the app or by email before it applies, and the app asks you to accept the new version. If a change needs new consent from you, we ask for it and do not assume it. Earlier versions are listed on our version history page.

20. Contact Us

  • Privacy and data protection: privacy@doxa.app
  • Post: The Doxa Way Ltd, 108 Kings Road, New Haw, Addlestone, KT15 3BH, United Kingdom
  • Supervisory authority: Information Commissioner's Office, ico.org.uk

This policy sets out obligations of The Doxa Way Ltd as a company. It creates no personal guarantee by any director, officer, employee or agent. Nothing in it limits any right you have under data protection law.