Lock In Bible — Privacy Policy
Last updated: 5 November 2026
SISYMUS PTE LTD ("Sisymus", "we", "us", "our") provides Lock In Bible (formerly My Bible), a Bible reading app for iPhone and iPad. Reading is free; App lock needs a Lock In Bible Premium subscription. This policy explains what information the app handles, who receives it, and your choices.
Questions: admin@sisymus.com.
1. Summary
- Lock In Bible has no account. We do not ask for your name, email or password.
- Your highlights, notes, chosen Bible edition, downloaded Bible text and settings are stored on your device. We do not receive them.
- Search runs on your device, over the chapters you have downloaded. Your search words are not sent anywhere.
- The app shows no ads. To measure which of our ads bring people to the app, it uses Adjust, which shares install and campaign data with ad networks such as Meta. It reads your device's advertising identifier only if you allow tracking when iOS asks (section 2.6).
- The app sends usage events and crash reports to Google Firebase so we can see how the app is used and fix errors. They are not linked to your name or email (section 2.5).
- The app checks with Expo for app updates and with Firebase Remote Config for settings such as the lowest supported version.
- To download Bible text, the app connects to the Digital Bible Platform.
- If you buy or restore Lock In Bible Premium, Apple processes the payment and RevenueCat verifies the purchase. We never see your card details.
- We do not sell your personal information.
2. Information we handle
2.1 Information stored on your device
| Information | Why |
|---|---|
| Highlights, highlight colours and notes | To show them back to you |
| Chosen language, Bible edition, book and chapter | To reopen the app where you left off |
| Downloaded Bible text, book lists and the list of editions | To read and search without loading them again |
| Display settings (reading surface, font, line spacing, text size, app language) | To keep your preferences |
| App lock: the apps and categories you chose (as Apple's opaque Screen Time tokens) and whether the lock is on | To block the chosen apps until you have read |
This information stays on your device. We do not receive it. Deleting the app deletes it.
2.2 Information sent when the app downloads Bible text
| Information | Who receives it | Why |
|---|---|---|
| The language list, edition list, book list or chapter requested; your IP address and standard connection details | Digital Bible Platform (Faith Comes By Hearing) | To deliver Bible text to the app |
The app sends these requests only to download text it does not already have. The World English Bible, King James Version and Berean Standard Bible are built into the app, so reading them sends no chapter requests. It does not send your highlights, notes or search words.
2.3 Sharing a passage
When you tap share, the app opens your device's share sheet with the passage text and a link to the app's App Store page. The app you choose receives that text and handles it under its own policy. Copy places the text on your device's clipboard.
2.4 Legal pages
This policy and our Terms of Use are hosted on Google Firebase Hosting. When you open them, Firebase Hosting processes the IP address of the page request.
2.5 Usage events, crash reports and app settings
| Information | Who receives it | Why |
|---|---|---|
| App interactions: finishing setup; the paywall being shown, a plan being picked, the paywall being closed or having no plans; a purchase starting, completing, being cancelled or failing, and restores; the Screen Time permission being asked for and its answer; how many apps and categories you chose for App lock (a count, not which apps); App lock being turned on or off; and reaching the daily reading goal | Google Analytics for Firebase | To understand how the app is used and improve it |
| Whether Premium is active, whether App lock is on, how many apps and categories it blocks, and the reading time you chose | Google Analytics for Firebase | To compare how different groups use the app |
| App-instance ID, device model, iOS version, language, app version, and approximate location (country, region or city, derived from your IP address) | Google Analytics for Firebase | Analytics and diagnostics |
| Crash logs and diagnostics (for example the app version, device model and the code that failed) | Firebase Crashlytics | To find and fix errors |
| Firebase installation ID, app and device information | Firebase Remote Config | To send settings to the app, such as the lowest app version that is still supported |
The app is built without Firebase's advertising identifier support, so Firebase does not receive your device's advertising identifier. We do not set a user ID, so these records are not linked to your name or email. Development builds of the app, which only we use, send no usage events or crash reports.
Google Analytics for Firebase may also record automatic events, such as the first time the app is opened and app sessions.
2.6 Ad measurement (Adjust and Meta)
We advertise Lock In Bible on networks such as Meta (Facebook and Instagram). To learn which ads bring people to the app, the app uses Adjust, a measurement service.
| Information | Who receives it | Why |
|---|---|---|
| An Adjust device ID, app installs and sessions, finishing setup and the paywall being shown, device model, iOS version, language, app version, IP address, and Apple's SKAdNetwork install reports | Adjust | To tell which ad campaign, if any, led to the install |
| Your device's advertising identifier (IDFA), only if you allow tracking | Adjust | To match the install to an ad you saw |
| Install and campaign results, matched to an ad | Meta and other ad networks, via Adjust | To report and improve the performance of our ads |
| The Adjust device ID and the ad network, campaign, ad set and ad that led to the install | RevenueCat | To see which campaigns lead to Premium purchases |
| Premium trials and purchases (product, price, date), sent by RevenueCat | Adjust | To measure which campaigns lead to purchases |
When you first open the app, iOS asks whether Lock In Bible may track you. If you choose Ask App Not to Track, the app does not read your advertising identifier, and installs are measured only through Apple's privacy-preserving SKAdNetwork reports and the other information above. You can change your answer at any time in iOS Settings > Privacy & Security > Tracking. Adjust does not receive your highlights, notes, reading or App lock choices. Development builds of the app, which only we use, report to Adjust's test environment, not to live campaigns.
2.7 App updates
| Information | Who receives it | Why |
|---|---|---|
| Your IP address, platform, app runtime version, update identifiers, and update request or error records | Expo (EAS Update) | To check for and download updates to the app |
2.8 App lock and Screen Time
App lock is part of Lock In Bible Premium. If you turn on App lock, iOS asks for Screen Time permission. Apple identifies the apps and categories you choose with opaque tokens, so the app does not learn which apps they are. Your selection and the lock state stay on your device, and we do not receive them.
2.9 Purchases and Lock In Bible Premium
| Information | Who receives it | Why |
|---|---|---|
| Your Apple Account and payment details | Apple | To charge for and manage your subscription. We never see your card details. |
| An anonymous app user ID created by the app, product and transaction details, the App Store receipt, subscription status, app and device information, and your IP address | RevenueCat | To verify purchases, restore them, and tell the app whether Premium is active |
The app contacts RevenueCat when you open the paywall, buy or restore, and when it checks whether Premium is still active. The anonymous ID is not linked to your name or email, and the app sends RevenueCat none of your highlights, notes, reading or App lock choices. Through RevenueCat we can see purchase and subscription records, linked to that anonymous ID and to the ad campaign data in section 2.6.
2.10 What we do not collect
We do not collect your name, email, contacts, photos, precise location, payment card details, or the names of the apps you choose for App lock. We read your advertising identifier only if you allow tracking (section 2.6).
3. How we use information
The requests in section 2.2 are used only to deliver Bible text to the app. Usage events and crash reports in section 2.5 are used only to understand how the app is used, improve it and fix errors. Ad measurement information in section 2.6 is used only to measure and improve our own advertising of Lock In Bible. Update requests in section 2.7 are used only to deliver app updates. Purchase information in section 2.9 is used only to provide, verify and restore Lock In Bible Premium, to handle refunds and support requests, for accounting, and to see which campaigns lead to purchases. The app shows no ads, and we do not sell your information.
4. Sharing
The Digital Bible Platform receives the requests described in section 2.2 and handles them under its own policy: faithcomesbyhearing.com/privacy-policy. RevenueCat processes purchase information for us as described in sections 2.6 and 2.9, under revenuecat.com/privacy. Google provides Firebase Analytics, Crashlytics and Remote Config (section 2.5) and Firebase Hosting for our legal pages, under policies.google.com/privacy and firebase.google.com/support/privacy. Adjust measures ad campaigns for us (section 2.6) under adjust.com/terms/privacy-policy. Meta receives campaign results from Adjust and handles them under facebook.com/privacy/policy. Expo delivers app updates (section 2.7) under expo.dev/privacy. Apple provides the App Store and handles your download and payments under apple.com/legal/privacy.
We may also disclose information if the law requires it, to protect our rights or users' safety, or as part of a sale or transfer of the app.
5. Retention
Information on your device is kept until you remove it in the app or delete the app. The Digital Bible Platform keeps request logs according to its own policy; we do not receive them. Purchase records are kept in RevenueCat with no automatic expiry, and Apple keeps its own records of your purchases. Google Analytics for Firebase keeps event data for at most 14 months, the longest retention Google Analytics allows; aggregated reports are not affected. Crashlytics keeps crash reports for 90 days before Google starts removing them from live and backup systems. Remote Config keeps the Firebase installation ID until deletion is requested through the Firebase API; Google then removes it from live and backup systems within 180 days. Adjust keeps measurement data according to its own retention policy. Meta keeps campaign results under its own policy. Expo keeps update request records according to its own policy.
6. Your choices and rights
- Remove a highlight with Remove highlight, or edit or clear a note, in the app.
- Allow or stop tracking at any time in iOS Settings > Privacy & Security > Tracking.
- Turn off App lock in the app, or remove Lock In Bible's Screen Time access in iOS Settings.
- Cancel Lock In Bible Premium in iOS Settings > your name > Subscriptions. Deleting the app does not cancel it.
- Delete the app to remove everything it stored on your device.
- Depending on where you live, you may have the right to access, correct, delete or object to the processing of your personal information. Because the app has no account and sets no user ID in Firebase, we cannot find your usage events or crash reports from your name or email. Deleting the app resets its Firebase app-instance and installation IDs, so new records are not linked to old ones. The only record we can find from information you give us is a purchase record in RevenueCat, if you bought Premium. To ask about it, email admin@sisymus.com with the order ID from Apple's purchase receipt so we can find the record, and we will respond as the law requires.
7. Security
The app connects to the Digital Bible Platform, RevenueCat, Google Firebase, Adjust and Expo over encrypted (HTTPS) connections. Information on your device is protected by your device's own security. No method of storage or transmission is completely secure.
8. Children
Lock In Bible is rated 4+ and is suitable for all ages. It has no account and shows no ads. Its usage events, crash reports and ad measurement data (sections 2.5 and 2.6) are not linked to anyone's name or email, and we do not knowingly collect personal information from children under 13. If you believe a child has sent us information, for example by email, contact us and we will delete it.
9. Changes
We may update this policy. We will publish the new version here with its date, and give notice of significant changes where the law requires it.
10. Contact
SISYMUS PTE LTD
9 Raffles Place, #29-05, Republic Plaza, Singapore 048619
Email: admin@sisymus.com
Website: sisymus.com