Skip to content
Ambo
  • Ambo Desktop
  • Ambo Bible
  • Follow along
Get the app

Privacy Policy

Ambo Bible app · Last updated 12 November 2026

This policy explains what personal data the Ambo Bible app for iOS and Android ("the app") processes, why, and what rights you have. We keep collection to what the app needs to work.

1. Who is responsible

The controller under the EU General Data Protection Regulation (GDPR) is:

Fadi Zgheib
Schiersteiner Str. 90
65187 Wiesbaden
Germany
Email: contact@fadi-zg.de

2. What stays on your device

Reading the Bible, commentary, cross-references, maps, reading plans, memory verses, prayer, quizzes and games, your reading progress and badges, and your settings are stored only on your device. We do not receive this data.

To read a translation, the app downloads Bible, commentary and song files from our content server. These downloads need no account. As with any internet request, the server receives your IP address in order to deliver the file.

3. Your account

To use the community features (feed, posts, reels, comments, groups, chat, churches, teams and service plans) you create an account. We process:

  • Email address and password. Used to sign you in. The password is stored by our authentication provider in hashed form; we never see it.
  • Profile: your display name and, if you add one, a profile picture.
  • A user ID that links your account to the content you create.

Legal basis: performance of the contract for using the app (Art. 6(1)(b) GDPR).

4. Content you create and share

Posts, photos, reels (short videos, which only accounts our moderators allow can post), comments, likes, follows, group and church memberships, chat messages, service plans and team rosters are stored on our servers so that the people you share them with can see them. Content you post publicly is visible to other users of the app. Messages in a group or church chat are visible to its members.

If you report content or a user, we store the report (who reported what, and when) so that moderators can review it. Moderators can block accounts that break the rules.

When you share a reel, only its caption and links to the app stores are shared, never the video itself.

Legal basis: Art. 6(1)(b) GDPR, and our legitimate interest in keeping the community safe (Art. 6(1)(f) GDPR) for reports and moderation.

5. Finding a church

Your location. When you tap “Use my location” in Find a church nearby, the app asks your phone for your approximate location (to about a kilometre). It is used on your phone to sort churches by distance. It is not sent to us or stored.

The church directory is public. Anyone can see each listed church's name, city, address, phone number, map position, service times, events, website and description, without an account. A church's admins decide what it shows.

Setting a church's position. When a church admin sets the church's position from their phone or from a typed address, the phone's own map service does the lookup: on Android, Google; on iPhone, Apple. It receives the address or coordinates. The resulting position is stored with the listing.

Suggesting a church. If your church is not listed, you can suggest it. We store what you enter (name, city, address, phone, position), when you sent it and your account, so that each person has at most one suggestion waiting. Our moderators see your username with it. You can withdraw it until it is reviewed. If it is approved, the church appears in the directory without your name and you get a message in the app. Approved or rejected, the suggestion itself is then deleted.

Claiming a church's page. If you are an admin of a church on Ambo, you can claim a page that someone in the community added, so that your church can keep it up to date. We store your account, the page, your church and when you sent it. Our moderators see your username with it. You can withdraw it until it is reviewed; approved or rejected, the claim is then deleted, and if it is approved you get a message in the app.

Legal basis: performance of the contract (Art. 6(1)(b) GDPR); for public church listings, the church's legitimate interest in being found (Art. 6(1)(f) GDPR).

6. “How do you feel today?” and care contacts

Your answers stay on your phone. We do not store or send them, and they are gone when you leave the screen. The questions themselves are downloaded from our servers.

If your answers suggest you may be in danger, the app shows a helpline for your country, chosen on your phone from its region setting. It can also offer to message a care contact, to open the support chat, or to post a prayer request. Nothing is sent unless you choose one of these; a message or prayer request is then stored like any other.

Care contacts are people our moderators list, with their agreement, as someone to talk to. A moderator first invites you; we keep the invite (your account, the name and role it would show, the moderator's account and when) until you answer. You are listed only if you accept in the app, and you can stop at any time in Settings. A listing shows your display name, an optional role such as “Pastor”, and their account. Anyone signed in may be shown them. You can report a care contact to our moderators from the same screen; the report stores your account, theirs and what you wrote.

Legal basis: for care contacts, their consent (Art. 6(1)(a) GDPR); for reports, our legitimate interest in keeping the community safe (Art. 6(1)(f) GDPR).

7. Notifications

If you allow notifications, the app registers a push token with Firebase Cloud Messaging so that we can tell you about new messages, activity and reminders you set up. Activity notifications (someone liked or commented on your post, followed you, or your suggested church was listed) carry the other person's username and what they did. On iPhone they are delivered through Apple's Push Notification service. We delete the token when you sign out. Daily verse and reading reminders are scheduled on your device. You can turn notifications off at any time in your phone's settings.

Legal basis: your consent (Art. 6(1)(a) GDPR), given through the system permission prompt.

8. Crash reports

When the app crashes, Firebase Crashlytics sends us a crash report: the technical error, device model, operating system and app version, and an installation identifier. Crash reports do not contain your posts or messages. We use them only to fix bugs. Crashlytics keeps crash reports for 90 days.

Legal basis: our legitimate interest in a working, stable app (Art. 6(1)(f) GDPR).

9. Camera, microphone, photos, location and local network

  • Camera: used to scan the QR code shown by Ambo on your church's screen (the image is not stored or sent anywhere), and, for accounts allowed to post reels, to record a reel.
  • Microphone: used only to record the sound of a reel you film.
  • Approximate location: used only to sort churches by distance, on your phone (see section 5).
  • Photos: used to pick a picture for a post or profile, and to save verse images you create to your photo library.
  • Local network: used to find Ambo on your church's Wi-Fi so your phone can follow the service. This connection stays inside the local network and does not reach our servers.

10. Service providers

We use Google Firebase (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) for authentication, the database, file storage, push notifications, remote configuration and crash reporting. Google processes this data on our behalf under a data processing agreement. Our database is located in the EU (Belgium). Some Firebase services may process data in the United States; such transfers are covered by the EU–U.S. Data Privacy Framework and the EU Standard Contractual Clauses.

On iPhone, Apple (Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) delivers push notifications and looks up church addresses on the map; on Android, Google does the address lookup.

We do not sell your data, do not show advertising and do not track you across other apps or websites.

11. How long we keep data

We keep your account and content for as long as you have an account. When you delete your account, we delete your account data and the content linked to it, except where we are legally required to keep it. Crash reports are deleted after 90 days.

12. Deleting your account

You can delete your account in the app at any time: Settings → Delete account, then confirm with your password. This deletes your account, profile, posts, photos, reels, comments, likes, messages, group and church memberships, any church suggestion or page claim you have waiting, any care-contact invite, your listing as a care contact, your push token and your Ambo School data, straight away and permanently. Reports you made about other content are kept for moderation, without your account.

If you can no longer sign in, email contact@fadi-zg.de from the email address of your account and we will delete it within one month.

13. Your rights

You have the right to access your data (Art. 15 GDPR), to have it corrected (Art. 16) or deleted (Art. 17), to restrict its processing (Art. 18), to receive it in a portable format (Art. 20), and to object to processing based on legitimate interests (Art. 21). Where processing is based on consent, you can withdraw it at any time with effect for the future. To exercise any of these rights, email us at the address above.

You also have the right to complain to a data protection supervisory authority. The authority responsible for us is the Hessian Commissioner for Data Protection and Freedom of Information (HBDI), Postfach 3163, 65021 Wiesbaden, datenschutz.hessen.de.

14. Children

If you are under 16, please use the community features only with the consent of a parent or guardian.

15. Changes

We will update this policy when the app changes. The date at the top shows the latest version.

Ambo © 2026 Ambo
Ambo Desktop Ambo Bible Download Privacy Support