Version 1.2 | Last updated: 9 October 2026 | First published: 23 January 2026
Plain Language Summary
What changed in version 1.2 (9 October 2026):
Earlier versions and what changed in each are listed on our version history page.
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.
These laws apply to Doxa, and we follow them:
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:
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).
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.
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.
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.
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 do | Lawful basis (Article 6) | Special category condition (Article 9) |
|---|---|---|
| Create and run your account, sign you in, keep you secure | Contract (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 choose | Contract (6(1)(b)) | Your explicit consent (9(2)(a)), Section 5 |
| Show licensed Bible translations through YouVersion | Contract (6(1)(b)) | Your explicit consent (9(2)(a)) |
| Reply to you through the Doxa bots and AI-assistant tools | Contract (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 Record | Contract (6(1)(b)) | Your explicit consent (9(2)(a)); once published, data you made public (9(2)(e)) |
| Take payments and manage your plan | Contract (6(1)(b)) | Not applicable |
| Service emails (account, security, purchases) and support replies | Contract (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 service | Your 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 identifier | Not applicable: no record content is sent |
| Report web purchases to Meta and Google Analytics | Legitimate interests (6(1)(f)): measuring our ads | Not applicable |
| Follow-up emails about Doxa to people who use it | Legitimate interests (6(1)(f)); for marketing email, the PECR rules on existing customers. You can stop them at any time | Not 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 safety | Legitimate interests (6(1)(f)) | Your explicit consent, where the content is yours |
| Keep accounting records, answer lawful requests from authorities | Legal obligation (6(1)(c)) | Legal claims (9(2)(f)), where needed |
| Contact emergency services if we learn of a serious risk to someone's life | Vital 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.
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)).
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.
It does not cover advertising. Your records are not used for advertising, and we do not send them to advertising companies.
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.
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.
We do not sell, rent or trade your personal data. We share it only with the organisations below, and only for the reasons given.
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.
| Provider | What it does for us | Data | Where | Transfer safeguard |
|---|---|---|---|---|
| Supabase | Database, sign-in, file storage and server functions. Hosted on Amazon Web Services | All account data and everything you record | United 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 app | IP address, request logs, account identifiers, and record content handled by the web app | Server functions: United Kingdom (London). Pages and static files: Vercel's global edge network. US company | DPF; SCCs as a fallback |
| Upstash, Inc. | Counts requests to the web app so we can limit abuse | IP address, type of request, time | United Kingdom (London). US company | DPF; SCCs as a fallback |
| OpenAI OpCo, LLC | Search 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 ID | USA | SCCs |
| Anthropic Ireland, Limited | Claude: 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 ID | USA | SCCs |
| 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 transcripts | USA | DPF; SCCs as a fallback |
| AssemblyAI Inc. | Transcribes voice recordings | Audio of your recording and its transcript | EU (AssemblyAI's European servers). US company | Storage 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 again | None while turned off | USA | Not applicable while turned off |
| Expo (650 Industries, Inc.) | Sends push notifications, and delivers app updates | Push 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 address | USA | DPF |
| Functional Software, Inc. (Sentry) | Error monitoring and masked session replays | Doxa user ID, device details, error details; from earlier app versions, screenshots that can show your content | EU (Frankfurt) for error data; Sentry's own account records in the USA | DPF; SCCs as a fallback |
| PostHog Inc. | Product analytics and session replay, through our own address insight.doxa.app | Doxa 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 emails | Email address, name, email content, delivery records | Sent from Ireland (AWS eu-west-1); stored in the USA | DPF; SCCs as a fallback |
| Google 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 testimonies | Page views and events with cookies; emails you send us; tester email addresses | USA and other countries | DPF; SCCs as a fallback | |
| Stripe | Web payments, the customer portal and Telegram payments | Name, email, billing and payment details, plan status | USA and other countries | DPF; SCCs as a fallback. Stripe is also an independent controller for fraud prevention and its legal duties |
| Fly.io, Inc. | Runs the Doxa Discord bot | Discord user ID and username, messages you send the bot, logs | Bot servers in the United Kingdom (London); US company, whose own systems can be in the USA | DPF |
| GitHub, Inc. | Receives short error summaries from Sentry so we can track bugs | Error title, place in the code, link to the report | USA | DPF; SCCs as a fallback |
| Tenjin, Inc. | Measures Android app installs from our ads, outside the UK, the EEA and Switzerland only | Android Advertising ID, IP address, device details, install and three milestone names | USA | Tenjin'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.app | USA | None 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 |
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.
| Organisation | Why it receives data | Data | Role and safeguard |
|---|---|---|---|
| Apple | App Store, in-app purchases, push delivery (APNs), Sign in with Apple | Device tokens, purchase data, Apple ID relay email, notification text | Independent 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-In | Device tokens, purchase data, sign-in identifiers | Independent controller. DPF |
| Meta Platforms | Measures our ads (mobile app SDK, website pixel, web purchase reports) | Advertising identifier, milestone events, page visits, cookies, hashed email and user ID, plan and amount | Joint 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 cookies | Independent controller. DPF and SCCs |
| AppLovin Corporation | Ad network that runs our app-install ads; learns which installs its ads produced | Android Advertising ID with the install and milestone names (via Tenjin); Apple SKAdNetwork reports | Independent controller. DPF and SCCs |
| YouVersion, Inc. | Supplies licensed Bible translations when you choose one | Passage requested, Bible search text, IP address, app version. No account ID, name, email or records | Independent controller under its own privacy policy. Your device connects to YouVersion in the USA directly |
| Telegram | Carries your messages with the Doxa bot on Telegram | Telegram chat ID, username, messages | Independent controller of its platform. We control what our bot stores |
| Discord | Carries your messages with the Doxa bot on Discord | Discord user ID, username, server and channel IDs, messages | Independent controller of its platform. We control what our bot stores |
| OpenAI (ChatGPT) | Runs ChatGPT when you use Doxa inside ChatGPT | Your ChatGPT conversation | Independent controller under OpenAI's own terms (Section 8) |
| OpenStreetMap Foundation | Turns a place name in a public Grace Record submission into a map location | The place name only, sent from our servers | Independent 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.
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.
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.
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:
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.
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.
| Provider | Used to train AI models? | How long the provider keeps it |
|---|---|---|
| OpenAI | No. OpenAI's business terms exclude API data from training, and we have not opted in | Up to 30 days, for abuse monitoring |
| Anthropic | No. Anthropic's commercial terms do not allow it to train on our data | Deleted within 30 days; content flagged for a policy breach can be kept for up to 2 years |
| ElevenLabs | ElevenLabs' terms allow it to use content to improve its models unless the customer opts out. We have not yet opted out | Your voice is not recorded. Session transcripts are deleted after 7 days. Doxa checks this setting every day |
| AssemblyAI | No. AssemblyAI does not use data sent to its European servers for training | Doxa 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.
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:
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.
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.
Under the UK GDPR, and wherever you live, you have the right to:
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.
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.
| Data | How long |
|---|---|
| Your account and records | While your account exists. After you delete it: removed within 30 days, and from encrypted backups within 90 days |
| Engage session notes | With your account; deleted when you delete your account |
| Data held by AI providers | See 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 logs | With Doxa's service records; you can ask us to delete the entries linked to your account |
| Advertising measurement | Held by Meta, X, Tenjin and AppLovin under their own retention. Doxa does not store your advertising identifier |
| Messages with the Doxa bots | Until you withdraw consent in the bot (on Telegram, send /stop) or ask us to delete them |
| Payment and accounting records | Up to 7 years, as tax law requires |
| Contacts at churches we write to | While 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.
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.
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.
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.
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.
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).
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.
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.