Lock In Bible — Privacy Policy
Last updated: 16 October 2026
Hapiga Vietnam Company Limited, also known as Hapiga Studio ("Hapiga", "we", "us", "our"), provides Lock In Bible, an app that keeps the apps you choose blocked each day until you read the Bible. This policy covers the Android app. It explains what information we collect, why, who receives it, how long we keep it, and your choices and rights. We are the data controller for this information.
Questions: support@hapiga.com.
1. Summary
- Your Bible reading progress, highlights, streak, schedule and blocking settings are stored on your device.
- To block apps, Lock In Bible uses Android usage access, display over other apps and, only if you turn on Strict mode, an Accessibility service. These check which app is open on screen so the reading screen can appear. We do not send the history of apps you open, or anything you see or type in other apps, off your device.
- We do send the following to our service providers: a user ID, the answers you give in the introduction questions (including your religion, if you agree), the names of the apps you choose to block, how you use Lock In Bible, purchase records, crash reports, device and advertising identifiers, and approximate location derived from your IP address.
- Your religion answer is sensitive data. We only send it with your explicit consent. You can choose "Prefer not to say" or withdraw consent at any time.
- Firebase Remote Config uses a Firebase installation ID to send feature settings to your device. We do not record your screen or replay your app sessions.
- We do not sell your personal information, and Lock In Bible shows no ads.
2. Information we collect
2.1 Information stored on your device
| Information | Why |
|---|---|
| Reading progress, streak, reading length, Bible translation, highlights and saved verses | To run the reading experience and the home-screen widget |
| Blocking schedule, pauses, mode (Standard or Strict) and the list of apps to block | So blocking works, also when Lock In Bible is closed |
| Your answers to the introduction questions | To show your selections and estimate phone time in the introduction |
| Notification and permission states | To show which settings still need to be turned on |
The app keeps this information in its private storage. Some of it is also shared with service providers, as described below. Lock In Bible disables Android backup for its app data. Uninstalling Lock In Bible or clearing its storage removes it from the device.
2.2 Information about your apps
- List of apps on your phone. To let you pick apps to block, Lock In Bible reads the apps that appear in your launcher (name and icon). The full list stays on your device.
- Apps you choose to block. The names and package IDs of the apps you select are sent to Google Analytics for Firebase with your user ID, so we can learn which apps people want help with.
- The app on screen. Usage access (Standard mode) or the Accessibility service (Strict mode) tells Lock In Bible the name of the app in the foreground, only to decide whether to show the reading screen. The Accessibility service is set up so it cannot read screen content or what you type. We do not store or send a live history of the apps you open. We send daily blocking counts and the package ID of your most-blocked selected app to Google Analytics for Firebase.
2.3 Information you give us
- Introduction questions: your goals, how familiar you are with the Bible, how often you read Scripture, your religion, your gender, your age range, your average screen time and how you heard about Lock In Bible. These answers go to Google Analytics for Firebase with your user ID; your religion answer is sent only if you give explicit consent.
- Account: if you sign in with Google, we receive your Google account email address and a Google account identifier through Firebase Authentication.
- Messages to support: if you email us, we receive your email address and your message.
2.4 Information collected automatically
| Information | Collected by | Purpose |
|---|---|---|
| Account user ID (including an anonymous Firebase ID created on first launch) | Firebase Authentication; used by analytics, subscription and attribution providers | Link your data across our services; restore purchases |
| App interactions (introduction screens, answers, reading started and finished, blocking settings, permission results, paywall views, purchases) | Google Analytics for Firebase | Analytics and product improvement |
| App-instance ID, advertising ID, device model, OS version, language, app version | Firebase, Adjust, RevenueCat, Meta SDK | Analytics, install attribution, fraud prevention |
| Approximate location (country, region, city from your IP address) | Google Analytics for Firebase, Adjust | Analytics and attribution |
| Crash logs and diagnostics | Firebase Crashlytics | Find and fix errors |
| Firebase installation ID | Firebase Remote Config | Select the feature settings sent to your device |
| Campaign information (which ad led to your install) | Adjust, Meta install referrer | Measure our marketing |
| Purchase and subscription records (product, price, currency, dates, renewal state, store transaction ID) | Google Play, RevenueCat | Provide Premium and manage your subscription |
We do not collect your precise location, contacts, photos, microphone, camera, messages or payment card numbers.
3. Sensitive information: your religion
The question "What is your religion?" collects information about your religious beliefs. This is special-category data under the EU and UK GDPR, and sensitive personal information under some US state laws. Other answers, and using a Bible app at all, can also suggest religious interest.
- Legal basis: your explicit consent, which you give on the religion question before your answer is sent.
- Use: to understand product use in aggregated reports. This answer does not change the reading schedule.
- You can refuse: choose "Prefer not to say". The app works the same.
- You can withdraw consent in Privacy → Religion analytics. This stops further sharing and clears the current Analytics religion property. To request deletion of past events, email support@hapiga.com. We process deletion as described in Section 7.
- We never use it for advertising, and we never send it to Adjust or Meta.
4. How we use information and legal bases
| Purpose | Information | Legal basis (EEA/UK) |
|---|---|---|
| Provide the app: blocking, reading, widget, notifications | Device data, permissions | Contract |
| Accounts and restoring purchases | User ID, account email | Contract |
| Subscriptions and billing support | Purchase records | Contract; legal obligation (tax and accounting) |
| Analytics and product improvement | App interactions, answers, blocked-app names, device data, approximate location | Consent where the law requires it, otherwise legitimate interests |
| Religion answer | Religion | Explicit consent |
| Feature settings | Firebase installation ID | Consent where the law requires it, otherwise legitimate interests |
| Install and campaign attribution | Device and advertising IDs, campaign data, purchase events | Consent where the law requires it, otherwise legitimate interests |
| Crash reporting, security and fraud prevention | Crash logs, diagnostics, IDs | Legitimate interests |
| Support and legal requests | Emails | Legitimate interests; legal obligation |
Where we rely on legitimate interests, you can object (Section 8).
5. Who receives your information
We share information with the service providers below, who process it for us, and where the law requires. We do not sell personal information.
| Provider | What it does for us | Information | Privacy policy |
|---|---|---|---|
| Google Firebase (Authentication, Analytics, Crashlytics, Remote Config) and Google Cloud (BigQuery) | Sign-in, analytics, crash reports and feature settings; BigQuery exports are not enabled | User ID, account email, events, answers including religion (with consent), blocked-app names, device data, IP-based location, crash logs, Firebase installation ID | Firebase · Google |
| RevenueCat | Subscription management and attribution matching | User ID, purchase records, Adjust ID, advertising ID, device model, IP address | RevenueCat |
| Google Play | Payment processing | Your Google account and payment details (we never see card numbers) | |
| Adjust | Install attribution and marketing measurement | User ID, Adjust ID, advertising ID, device data, IP address, install and purchase events | Adjust |
| Meta Platforms (Facebook SDK) | Install attribution for our Meta ads | Advertising ID, device data, install referrer data | Meta |
5.1 Advertising measurement
We advertise Lock In Bible on other platforms. Adjust and the Meta SDK tell us which ad led to an install or a purchase, using your device's advertising identifier. Under some US state laws this can count as "sharing" for cross-context advertising. You can reset or delete your advertising ID in Android Settings → Privacy → Ads, or email us to opt out.
5.2 Other disclosures
We may disclose information to comply with law or a valid legal request, to protect rights and safety, or as part of a merger, acquisition or sale of assets, under the protections of this policy.
6. Retention
| Information | Kept for |
|---|---|
| Data on your device | Until you delete it, clear app storage or uninstall |
| Firebase Authentication account | Until you delete your account or ask us to delete it |
| Google Analytics for Firebase (user-level data) | [PLACEHOLDER: 2 or 14 months] |
| Analytics export in BigQuery | Not enabled; no exports are currently stored |
| Crashlytics crash reports | 90 days before Google starts removal from live and backup systems |
| Firebase Remote Config installation ID | Until deletion is requested through the Firebase API; Google then removes it from live and backup systems within 180 days |
| Adjust attribution data | [PLACEHOLDER: period] |
| Purchase records | As long as needed for your subscription, then as tax and accounting law requires |
| Support emails | As long as needed to answer your request, resolve disputes and meet legal obligations |
The Analytics retention setting applies to user-level and event-level data used in explorations and funnel reports. It does not set a deletion period for standard aggregated reports.
7. Deleting your data and your account
Our Data Policy explains every way to delete your data. In short:
- By email: write to support@hapiga.com with the subject "Lock In Bible data deletion" and the email address of your account or your user ID.
- We answer within 30 days and tell you if a law requires us to keep something, such as purchase records for tax.
- Deleting your data does not cancel your subscription. Cancel it in Google Play.
- Uninstalling Lock In Bible deletes data on the device but not data already sent to our providers.
8. Your rights
Depending on where you live, you may have the right to access a copy of your personal information and receive it in a portable format; correct it; delete it; restrict or object to processing; withdraw consent at any time (without affecting earlier processing); and complain to your data protection authority. We do not make decisions based solely on automated processing that have legal effects on you.
California and other US states: you can ask to know, delete or correct your information, opt out of its "sale" or "sharing", and limit the use of sensitive personal information. We do not sell personal information. We use your religion answer only to provide and improve the service. We will not discriminate against you for using your rights. You may use an authorized agent.
To use any right, email support@hapiga.com. We may need to verify your request, for example with your user ID or account email.
9. International processing
Hapiga is based in Vietnam. Our providers process information in the United States and other countries, where protections can differ from those in your country. When we transfer personal data from the EEA, the UK or Switzerland, we rely on the Standard Contractual Clauses (and the UK Addendum) offered by our providers, or on the EU-US Data Privacy Framework where a provider is certified. Contact us for details. EU representative: [PLACEHOLDER]. UK representative: [PLACEHOLDER].
10. Security
Data is encrypted in transit (HTTPS/TLS) to all our providers. Data on your device is kept in the app's private storage. Access to provider consoles is limited to staff who need it. No system is fully secure; please tell us if you find a problem.
11. Children
Lock In Bible is for people aged 13 or older, and 16 or older in the EEA and the UK (or the lower age of digital consent your country sets). It is not directed to children under 13, and we do not knowingly collect information from them. Users under 18 should have a parent's or guardian's permission. A parent or guardian who believes a child has given us information can email support@hapiga.com, and we will delete it.
12. Changes
We will post changes on this page and update the date at the top. If a change is significant, we will tell you in the app and ask for consent again where the law requires.
13. Contact
Hapiga Vietnam Company Limited
34/521 Nguyen Trai, Thanh Xuan District, Hanoi, Vietnam
Email: support@hapiga.com
Website: hapiga.com