๐Ÿ”’ Privacy Policy

Behold Privacy Policy

Last updated: September 4, 2026

This Privacy Policy describes how Behold ("Behold", "the app", "we", "us", or "our") handles information when you install and use the Behold applications for Android and iOS. Behold shows one Bible verse a day from a translation you choose, with the complete text of both translations bundled inside the app. We operate no server of our own, and no information Behold stores about you is ever sent to the Developer. The app does now connect to the internet, for one purpose: to request ads from Google AdMob for readers who have not bought Behold Pro.

Summary in plain language. Behold shows ads to free readers, through Google's AdMob. That means the app connects to Google's ad servers, and that Google's ad SDK can use your device's advertising identifier โ€” see Advertising for exactly what that involves. In the EEA and the UK you are asked for consent first, and Settings has a row that reopens that form so you can change your answer. Buying Behold Pro removes the ads, and a Pro reader is never asked for consent at all โ€” there is nothing to consent to. Everything else is as it was: no account, no sign-in, no sync, no analytics, no crash reporting, and no server of ours. Scripture is bundled in the app and works offline, and your favourites, reading position and settings stay in a database and a preferences file on your own device.

1. Who we are

Behold is developed by EJ Frias ("the Developer") as a personal project. If you have questions about this Privacy Policy, you can reach us at ejsfrias@gmail.com.

2. Scope

This Privacy Policy applies to the Behold Android application, distributed through Google Play, and the Behold iOS application, distributed through Apple's App Store. They are two separate native applications that behave the same way; wherever a platform genuinely differs, it is named explicitly below. This policy does not apply to any third-party websites, products, or services โ€” including Google Play and the App Store themselves, each governed by its own privacy policy.

3. Data we handle

Behold itself handles only the small amount of information below, and all of it stays on your device. None of it is ever transmitted to the Developer, and none of it is passed to the ad SDK: what you have favourited, what you are reading and what you have chosen in Settings are never used to select an ad. Separately, Google's ad SDK collects its own data under Google's policies once ads are enabled โ€” Advertising covers that, because it is a different thing from the list below and should not be mixed into it.

Category Examples Where it lives
Favourites Verses you have favourited, and when On your device (local database)
Reading position The book and chapter you last had open in the Read tab, so it can be reopened there On your device (local database)
App preferences Theme, font size, typeface, which translation (King James or World English Bible) you last chose, and your daily reminder setting On your device (preferences file)
Behold Pro status Whether you have bought Behold Pro โ€” a single true/false flag, cached from Google Play so the app knows to hide the ads even when it is offline On your device (preferences file)

The Developer collects nothing: we never receive your name, email address, phone number, location, contacts, photos, microphone audio, browsing history, or any form of account credentials, because there is no server of ours for any of it to reach. Behold never asks you to create an account or sign in.

An advertising identifier is involved. For free readers, Google's ad SDK can read your device's advertising identifier and use it for ad delivery, measurement and fraud prevention. Behold does not read it, store it, or receive it. It is disclosed here, and on Behold's Play Store data-safety form and App Store privacy labels, because it leaves your device even though it never reaches us.

It is not the same identifier on each platform. On Android it is Google's advertising ID, which you can reset or delete in your device settings under Google → Ads. On iOS it is Apple's IDFA, and the ad SDK may use it only if you allow tracking when Apple's App Tracking Transparency prompt appears. Decline and no IDFA is available to it โ€” the ads become non-personalised rather than disappearing. You can change that answer at any time in Settings → Privacy & Security → Tracking. See Advertising.

4. How data is used

The on-device information is used exclusively to provide the app's features to you, on your device:

Behold never uses any of it for advertising. Nothing in the list above is passed to the ad SDK, and none of it feeds profiling, behavioural analytics or automated decision-making. Which verses you save, what you search for and what you read are not inputs to which ad you are shown. What the ad SDK does collect, it collects for itself โ€” see Advertising.

5. Device permissions

The installed app requests twelve permissions. Three are Behold's own; the other nine arrive with Google's ad SDK, Google Play Billing and the Android support libraries those depend on. The list below is read off the app's merged manifest โ€” the one Android actually installs โ€” rather than off the file we write, because a library's permissions are just as real as ours.

None of the twelve is a "dangerous" permission except POST_NOTIFICATIONS, which Android asks you about. Behold requests no access to the camera, the microphone, location, contacts, your photos, your files, or your call or message history.

Permission Why it is there
POST_NOTIFICATIONS Behold's own โ€” to show the daily verse reminder, if you switch it on. Requested at the moment you switch the reminder on, never at launch, and the app is fully usable without it.
RECEIVE_BOOT_COMPLETED Behold's own โ€” so the reminder you set survives a restart. A reboot clears pending alarms; without this the reminder would simply stop, silently.
INTERNET Behold's own, and it exists solely for ads. Scripture is bundled in the app and nothing fetches it; there is no server of ours to reach.
ACCESS_NETWORK_STATE Google's ad SDK โ€” so it can tell whether a connection exists before attempting an ad request.
com.google.android.gms.permission.AD_ID Google's ad SDK โ€” access to your device's advertising identifier. This one is a Google Play data-safety disclosure, and it is why Behold's store listing declares that an advertising ID is collected and shared.
ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS Google's ad SDK โ€” Android's Privacy Sandbox interfaces for the advertising ID, conversion measurement and interest topics. All three are data-safety disclosures too, not just AD_ID.
com.android.vending.BILLING Google Play Billing โ€” so you can buy Behold Pro. The purchase is handled entirely by Google Play; see Third-party services.
WAKE_LOCK, FOREGROUND_SERVICE Support libraries the ad SDK depends on, for background work it schedules. Behold itself schedules none.
…DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION Added by AndroidX. It is a private, app-specific permission whose only purpose is to stop other apps sending broadcasts to this one. It grants nothing and reaches nothing.

That set is pinned by a build check: the app will not build if a library update adds a thirteenth permission, so this list cannot drift out of date without someone noticing.

On iOS

iOS has no manifest permission list. An app must ask at the moment it needs something, and Behold asks for exactly two things โ€” both optional, both refusable, and neither of which stops the app working:

On both platforms Behold requests no access to the camera, the microphone, location, contacts, your photos, your files, your health data, or your call or message history.

Backups are also turned off deliberately (android:allowBackup="false"), so Android's Auto Backup does not copy your favourites or settings to your Google Drive. The trade-off is that this data does not carry over if you move to a new device โ€” it stays on the device you're using, which is consistent with Behold not syncing anything anywhere.

6. On-device storage

Everything Behold needs to show you scripture is bundled inside the app. The only thing it goes to the network for is an ad:

7. Advertising

Behold shows ads. They are how the app is funded, and they are served by Google AdMob. There are exactly two ad placements, and no others anywhere in the app:

There are no interstitials, no ads between chapters, no ads in the reader, in search or in Settings, and no ad in a notification. If an ad does not load, the space collapses and the screen looks as though advertising does not exist.

What this means for your data:

Consent in the EEA, the UK and Switzerland

If you are in a region that requires it, Behold shows Google's consent form โ€” the standard User Messaging Platform dialog โ€” before any ad is requested, and your choice is what decides whether ads are personalised, non-personalised, or not requested at all. Outside those regions no form is shown and the app proceeds under Google's ad policies. If you dismiss the form, or decline, the app carries on working exactly as before with no ads and no error message. With Behold Pro active no form is shown anywhere, because no ad will ever be requested.

Your consent choice is stored on your device by Google's SDK, and you can change it. Where the rules require a privacy entry point, Behold's Settings screen carries a Consent for ads row that reopens Google's form. The row appears only where that requirement applies โ€” everywhere else there is no stored choice to change, so no row is shown. Clearing the app's storage, or uninstalling and reinstalling it, also resets the choice and the form is shown again on the next launch. You can reset or delete your advertising ID at any time in your device's settings, under Google โ†’ Ads.

8. Third-party services

Behold involves a small number of third parties, and they are Google and Apple โ€” which ones apply depends on where you installed the app. Behold contains no analytics SDK, no crash reporter and no tracking SDK on either platform, and there is no backend operated by us.

9. Data sharing

We do not sell, rent or trade any information. We operate no server, we receive nothing from the app, and if we were ever required to disclose information by law we would have nothing to provide.

Google does receive data, and honesty requires saying so rather than hiding behind the sentence above. Showing an ad means the ad SDK sends a request from your device to Google, which can carry your advertising identifier and device information; under Play's data-safety definitions that counts as data being shared with a third party, and Behold's store listing declares it. What is not shared is anything Behold itself holds: your favourites, your reading position, your searches and your settings are never sent to Google, to us, or to anyone else.

We share nothing with data brokers, and there is no analytics provider involved at all.

10. Retention & deletion

Because the data lives on your device, you control how long it is kept. Behold retains your favourites, your reading position and your settings for as long as the app is installed. To remove everything:

Because we do not hold a copy of your data, once you remove it from your device it is gone โ€” there is nothing on our side to delete. Data held by Google as a result of ads or a purchase is retained by Google under its own policies, and is not ours to delete; the links in Third-party services are where to go for that.

11. Your rights

Depending on where you live, you may have rights under privacy laws such as the EU/UK GDPR or the California CCPA/CPRA โ€” typically the right to access, correct, delete, or port your personal data. Because Behold transmits no data to us, you can exercise these rights yourself directly on your device: all of the app's own data is local, and you can clear it or uninstall the app at any time. If you believe you still need our help, please contact us using the details in the Contact us section.

For the advertising data described in Advertising, three controls are yours and none of them needs us: your device's Google โ†’ Ads settings, where you can reset or delete your advertising ID; the consent choice you made in Google's form, which the Consent for ads row in Settings reopens where that row is required and which clearing the app's storage resets; and Behold Pro, which stops ads being requested at all. Requests about data Google itself holds go to Google under its own privacy policy.

12. Changes to this policy

We may update this Privacy Policy from time to time to reflect changes in the app or applicable law. The most recent material change was the arrival of ads, the Behold Pro purchase and the permissions that came with them, which revised the Data we handle, Device permissions, Advertising, Third-party services and Data sharing sections. Since then, Settings gained the Consent for ads row described in Advertising and readers with Behold Pro are no longer shown a consent form, which revised that section and Your rights. When we make material changes, we will update the "Last updated" date at the top of this page.

13. Contact us

If you have any questions, requests, or concerns about this Privacy Policy or Behold's privacy practices, please contact: