Privacy policy
Updated on October 13, 2026
This policy explains, in plain language, what Antioquia stores, where that data goes and what you can do about it. It describes the app as it works today.
The essentials, in three sentences
Most of what you do in Antioquia stays on your device: the Bible works offline, and your notes, highlights and chat conversations are saved locally.
Because the app works with your Google account, a copy of that data goes to our server so you do not lose anything when you change phones.
We do not sell your data, we do not use it for advertising and we do not build an advertising profile about you.
Your account
Sign-in is handled by Google, through Firebase Authentication, and the app asks for it on first use. We receive your name, e-mail and profile picture from your Google account — we never receive or see your password.
We use this to identify you, sync your data across devices and show who is who to the people you take part in something with. On a board, in a prayer room or in a friends ranking, the other members see your name and picture; in a ranking, also your points and how many devotional steps you completed.
If you publish a review of a series, your name, picture, rating and text are visible to anyone who uses the app.
In the giveaway, each participant gets an invite code. When someone joins the app through that invite, we record the invited account and the account that invited it, and the inviter sees, on the Giveaway page, the name and picture of the invited account and on how many days it has used the app, until the invite counts. To validate the invite, the server counts on how many different days the invited account used the Bible or the devotional: it looks only at the dates of the synced readings and devotional steps, never at what is in them. Giveaway data is deleted with the account; the record of an invite, when either of the two accounts is deleted.
What gets synced
With your account we sync:
• notes (including attached audio, photos and drawings) and note lists • favorite and highlighted verses, pinned books and the reader background • reading progress and plans • search history and your preferences, such as language • chat history: each conversation's title, the text of questions and answers, the names of attached files and the images the chat generated for you (presentation photos and requested images) • your personal prayer requests • tithe records: the church, the amount and the date • outlines, cell studies and presentations • devotional progress • the profile you chose at the start (pastor, leader or member) and, if you tell us, your church's tradition
This data lives in a database on Google Cloud, and attached files in storage private to your account. Our server stores this content without opening it for analysis, with one exception: to add up the points of a friends ranking, it reads the date, the course and the duration of the devotional steps you completed.
Syncing happens in the background and never blocks your use of the app.
AI-powered features
Some features rely on specialized providers, which receive the request, process it and return the answer:
• Bible chat, sermon outlines, cell studies, presentations, images requested in the chat, verse study translation, version comparison, visitor sheet reading and Library: OpenAI • Studio images and verse backgrounds: Google (Gemini) • Bible and devotional narration: ElevenLabs • AI search: Perplexity • Voice conversation and guided prayer: OpenAI
These providers are outside Brazil, mostly in the United States, and that is where the request is processed.
With every chat question, the conversation text goes to OpenAI with storage turned off: the provider does not keep the conversation for later use, only the records its own policy requires to prevent abuse. The history stays on your device and, like the rest of your data, synced on our server (previous section).
Photos and files you attach to a question are different: they are sent to OpenAI and stored there, tied to your account, until you delete it.
In voice conversation, the audio goes through our server, which relays it to OpenAI while you speak and does not record it. In guided prayer, OpenAI also transcribes what you say, only to notice when you said “amen”; that text is not kept.
Documents you upload to the Library stay in our storage and in a search index at OpenAI, so the assistant can consult your material; from them we build a summary of how you write. This is lookup, not model training. Deleting a document removes it from the Library, the index and the provider.
The visitor sheet photo travels inside the request itself and is not stored at the provider.
Studio images and verse backgrounds stay in our storage for 7 days and are then deleted automatically. Images requested in the chat do not go through our storage: they go straight to the conversation on your device.
Other people's data
The visitors tool, the board and the prayer room store third-party data: names, phone numbers, prayer requests, photos.
That data belongs to your church or ministry, not to us. You decide what to register, and it is your responsibility to have those people's consent and to treat their data with the care the law requires.
We only store and transmit this content so you and your team can see it. Whoever is a member of a group sees what is in it.
Events and registrations
Anyone who registers for an event through the organizer's link gives a name, an email address and a WhatsApp number. Those three stay with us, and they are what the organizer sees in the attendee list.
The WhatsApp number is erased 90 days after the event date — it exists so the organizer can reach you before and during the event, and has no use afterwards. Name and email stay: they are your ticket and the record of who was there.
The email is also what links a registration made on the website to the app: sign in with the Google account using that same address and your tickets appear under My tickets. We never send you email — here the address is an identifier, not a contact channel.
Payment happens on the Mercado Pago page, not on ours. We never see or store a card number, security code or Pix key. From the payment we keep only whether it was approved, the amount and the method used (Pix, card or balance). The money goes into the organizer's Mercado Pago account, never into an account of ours.
If you are the organizer, two things of yours become PUBLIC on the event page. The cover photo you upload sits at an open address — that is what lets it show up for whoever gets the link on WhatsApp. And the nickname of the Mercado Pago account that will receive the money is shown to whoever registers: it is what lets them check that the organizer's name and the payment destination match, and whoever sells in a consumer relationship has to be identifiable. Deleting the event deletes its cover; deleting your account deletes all of them.
Still as the organizer, the data of the people who register is yours, not ours — the same responsibilities from the previous section apply. And if you delete your account, your events and their registrations go with it.
Subscription
Payment is handled entirely by Google Play. We do not receive, see or store card numbers or banking details.
From Google Play we receive only the confirmation that an active subscription exists, which plan it is and how long it is valid — enough to unlock the paid features.
Notifications and crashes
If you allow notifications, we register a device identifier with Firebase Cloud Messaging so we can notify you about prayer requests, rosters, updates from your groups and news. You can revoke this at any time in your system settings.
When the app closes unexpectedly, or when an error is worked around without closing the app, we send a technical report to Firebase Crashlytics — device type, Android version, where the error happened and an installation identifier. That report exists to fix the problem and does not carry the content of your notes or conversations.
How we measure app usage
To learn what works and what needs improving, we record in Firebase Analytics which screens you visit, which features you use, subscription events (reaching the plans screen, starting a purchase, subscribing or cancelling), your plan, the app language and the profile you chose at the start (pastor, leader or member, and the ministry, when there is one).
Nothing you write goes into that measurement: not the text of your notes, not your conversations with the artificial intelligence, not what you type into search. We record, for example, that a search happened and how many results it returned — never what you searched for.
Like any service of this kind, Firebase receives the device's IP address and derives an approximate location from it, at city or country level. We do not collect precise location.
We do not collect an advertising identifier: that permission is removed from the app, so there is no way to build an advertising profile or target ads with this data.
Permissions we ask for
• Microphone: to record audio in a note, dictate a question in the chat, and for voice conversation and guided prayer. Used only while you are recording, dictating or talking. Dictation uses Android's own speech recognition (on most devices, Google's), which receives the audio to turn it into text. • Notifications: for the alerts you choose to receive.
We do not ask for camera or gallery permission: when you attach a photo, Android itself opens the camera or gallery, and we receive only the image you picked.
How long we keep it
Your data stays with us for as long as your account exists.
Whatever you delete inside the app is removed from our servers within 30 days — that window exists so the deletion can propagate across your devices before becoming final.
Studio images and verse backgrounds are deleted after 7 days. Chat attachments stay at OpenAI until you delete your account. Narration audio is kept because it is shared across all users and identifies no one.
Deleting your account
In Profile, under Danger zone, you can delete your account and everything tied to it: synced data, attached files (including chat and Library files stored at OpenAI), usage counters and the account itself.
Deletion is permanent and immediate, and does not require asking us for anything. Without access to the app, request deletion at antioquia.app/en/delete-account or write to the e-mail at the bottom of this page.
Your rights
You may request confirmation that we process your data, access to it, correction of anything wrong, portability and erasure.
Most of this is already in your hands inside the app. For anything that is not, write to the e-mail below and we will answer.
Children and changes to this policy
Antioquia is not intended for children under 13, and we do not knowingly collect children's data. If you know of such an account, let us know at the e-mail below and we will delete it.
If this policy changes in a relevant way, we will let you know inside the app before the change takes effect. The date at the top of this page shows the last revision.

