Legal
What data the church website and mobile app collect, what it is used for, and how to ask for it to be deleted. Written to be read in full in five minutes.
Effective as of November 4, 2026
First Baptist Church of Marion Oaks (558 Marion Oaks Lane, Ocala, FL 34473, United States) is responsible for the data described in this policy. For any question or request, write to iglesiadeamor@cfl.rr.com or call 352-347-8777.
This policy covers three things: the church website, the "Primera Iglesia Bautista" mobile app for Android and iOS, and the administration panel used by church staff.
Browsing the website requires no account. We use no tracking cookies. To know how many people visit the site we use Cloudflare Web Analytics, which Cloudflare adds to the pages: it counts visits in aggregate, without cookies, without identifying anyone and without following you across other sites. The only cookie that exists is the staff panel session cookie, created only when signing in to it.
Videos and the live stream are played through YouTube. When you play a video, Google may set its own cookies under its privacy policy.
When you submit a prayer request form, the data you enter (name, contact details, request) is delivered to the church and used only to attend to your request. If you tick the private request box, only the pastor will see it.
Our hosting provider, Cloudflare, temporarily logs technical data about each visit, such as IP address and browser type, to keep the service secure and running.
As a guest. You can use the whole app without an account. In that case the app only requests public content from the church server (schedules, calendar, videos, blog) and stores no personal data about you. The app does not access your location, contacts, photos or microphone.
Notifications. If you turn notifications on, the app registers on the church server a notification identifier generated by the Expo service (it is not your phone number or email), the platform (Android or iOS), the chosen language and the sign-up date. It is used exclusively to send you the church's notices. You can turn them off at any time from the app itself: the identifier is marked as unsubscribed and is no longer used. If you uninstall the app, the identifier stops working and is marked inactive as soon as the service reports it.
Prayer requests. If you send a request from the app, the church server stores what you write (the request and, if you add them, your name and a way to contact you), whether it is private, the language, the date and, if notifications are on, the notification identifier so we can let you know when the church prays for it. The request is delivered to the church by email. Your phone keeps a copy of the text and a private code the app uses to check its status; from "My prayer requests" you can withdraw it, and it is then deleted from the server. Closed requests are deleted after one year. They are never published and no one outside the church staff sees them; private ones, only the pastor.
Staff account. People authorized by the church can sign in to the app with the same account they use in the panel (email and password). The password is never stored in plain text; the session is kept in the phone's secure storage and expires after ninety days. Accounts for congregation members do not exist yet; if they are enabled, this policy will be updated first.
The app contains no advertising and no analytics tools (unlike the website, which counts visits in aggregate), and sends no data to any third party other than the technical providers listed below.
The church keeps in its panel the contact details of its members (name, email, phone, groups) that they themselves provided, to organize congregation life and communicate with it. Only authorized staff can see that data.
Emails to the congregation are sent only to those who have given the church their authorization, through the provider Brevo. Each one carries an unsubscribe link, and unsubscribing is immediate and automatic: it applies to that email address, even if several members of a family share it in the church records.
When you ask to subscribe on the website, we store your email address, the language of the page and the date, only to send you an email with a link that confirms the address is yours. To stop abuse we also keep how many requests come from each connection, with its IP address, for up to two days after the last one.
If you do not confirm, the link expires after 48 hours and the request is deleted within three days at most. If you confirm it, the request is deleted after one month.
You confirm by pressing the button on the page that link opens. Once you confirm, your address joins the church's records with the date and the way you gave your consent: if you had no record, one is created with your email and language, and if your address was already in the records, those records receive the permission. The panel's activity log notes the confirmation with your email address and the IP address you confirmed from, and that entry is deleted after one year.
Every newsletter carries a link to unsubscribe at any time.
Online offerings are paid on Stripe's secure page or, for as long as it remains in use, on the platform the church uses today (Emmaus/GrpLife). Your card or bank details are received by Stripe (or that platform) and never pass through our website or the app.
The church keeps your name, email, the amount, the fund you give to, the date, the frequency (one-time or recurring), the language, whether there was any refund and the Stripe references, for its accounting records and to be able to issue the donation statements used for taxes. The receipt for each payment is sent to you by Stripe, if you leave your email. Stripe handles your data under its own privacy policy: stripe.com/privacy.
These records may have to be kept for as long as tax law requires, even if you ask for your data to be deleted; in that case we will delete everything else.
These providers process only the data needed to deliver their service, following our instructions and their own policies. We share data with no one else, except where required by law.
All traffic is encrypted (HTTPS). Passwords and sessions are stored irreversibly (hashed). Notification identifiers are only used while active: those that are turned off or stop working are marked inactive and never used again. Closed prayer requests are deleted after one year; app sessions expire after ninety days; form and member data is kept for as long as the church needs it for the purpose it was collected for, or until you ask for it to be deleted, except donation records, which may have to be kept for as long as tax law requires.
Every month a backup of the database is saved, and administrators can make another one whenever they need to. Backups are kept in a private Cloudflare storage space, encrypted at rest, that only administrators can access: the administrator accounts of the church panel and whoever maintains the website. They contain the data in the database (members' details, prayer requests, donations and the panel's activity log, among others), but not passwords, service keys or the unsubscribe links of emails; nor newsletter subscription requests, the record of which phone each notice reached, or the record of phones that have notifications turned off. Backups are not deleted automatically.
The website and the app are not directed at children under 13 and we do not knowingly collect data from them. If you believe a child has provided us with data, write to us and we will delete it.
You can ask us at any time to access, correct or delete your data by writing to iglesiadeamor@cfl.rr.com. To stop receiving app notifications, just turn them off in the app; to stop receiving emails, use the unsubscribe link in the email itself. If you want us to delete all data associated with the app (notification identifier and session), request it by email and we will do so within thirty days at most. Donation records may have to be kept under tax law, as explained above. Backups are not deleted automatically: if you ask us to delete your data, you can also ask us to remove it from the stored backups. The exact steps are in Delete your account and data.
If this policy changes, we will publish the new version on this same page with its effective date. Effective as of November 4, 2026.