Privacy Policy

Account data: your email address, the name you provide, and an optional profile photo, headline and location.

Activity data: the churches you follow, posts and comments you write, the interests you select during onboarding, and whether a sponsored event card was viewed or opened.

Church data: if you create a church page, the details you publish on it — name, address, service times, description and images.

Technical data: your IP address is used transiently for rate limiting, to derive a coarse city and region for relevant event promotion, and with your browser user-agent to initialize the signed promotion identifier. The promotion system does not store your IP address, user-agent, or precise coordinates.

Promotion measurement uses a first-party, server-signed pseudonymous browser identifier. We store only a salted one-way digest of that identifier, separately from any account, to count at most one impression and one click per campaign per UTC day. We do not use third-party advertising trackers.

We do not collect or store card numbers, bank account numbers, or tax identification numbers. Card details are entered into Stripe's own hosted fields in your browser and go straight to Stripe; they never reach oabba's servers, and we could not show them to you if you asked.

When you give, buy a ticket or book a room, we record what the payment was for and what happened to it: the amount and currency, the fee breakdown, Stripe's identifiers for the payment, the name and email address you gave at checkout, and the status — succeeded, failed, refunded or disputed. That is the ledger a church needs to reconcile its giving and a buyer needs to find their ticket.

Stripe is the processor and holds the card itself. A saved card is stored by Stripe against your customer record there; what we keep is a reference to it, not the card. Stripe's own privacy policy governs what it does with the data it holds.

Churches and organizers are paid through their own Stripe accounts, so a payment to them appears in their Stripe dashboard as well as in oabba. They can see the name, email and amount for payments made to them, which is what lets them issue a receipt or a refund.

Payment records outlive an account deletion. We are required to keep the financial record of a completed transaction, so deleting your account clears your profile, follows, posts and comments but leaves the payment ledger intact, with the purchase detached from a live account.

A published church page, its posts, events and follower count are public and indexed by search engines.

Your name and profile photo are visible alongside anything you post or comment publicly.

Your email address, your notification settings and the list of churches you follow are not shown to other users.

To operate the service: rendering your feed, delivering the notifications you opted into, and letting church staff manage their page.

To keep the service safe: rate limiting, abuse prevention and debugging.

To pace sponsored event delivery, limit repeat billing, report aggregate reach and clicks to organizers, and prefer relevant city or regional campaigns without building an individual interest profile.

We do not sell personal data, and we do not share it with advertisers.

Supabase provides database, authentication and file storage.

Vercel provides hosting.

Resend delivers transactional email such as verification codes and team invitations.

Stripe processes payments and holds the billing details a church submits when connecting a payout account.

Livestreams play from the church's own provider — YouTube, Facebook, Vimeo or Twitch. Pressing play loads that provider's player, which they may use to set cookies and record the view under their own privacy policy. Nothing is sent to them until you play a service.

You can edit or delete your posts and comments at any time, change your notification preferences in settings, and unfollow any church.

You can download a copy of your data and permanently delete your account yourself from Settings. Password accounts re-authenticate before sensitive changes; OAuth accounts use their active provider-backed session.

Account and activity data are kept while your account is open. Deleted posts and comments are retained in a hidden state so counts and threads stay coherent, then removed on account deletion.

Hashed promotion-impression and click records are removed after 13 months. Aggregate campaign totals and the financial credit ledger are retained as business and payment records.

Questions about this policy: support@oabba.com.