Humble is a daily async Bible reading app built for small groups. This policy explains what personal information we collect, why we collect it, how we protect it, and what rights you have over your data.
1. Information We Collect
Account and profile
- Phone number. Sign-in requires a US mobile phone number. We send a one-time code to verify it. Your phone number is stored in your account and on our servers.
- Display name. You choose a name during profile setup. It is visible to your group members.
- Profile photo (optional). If you add a photo, it is uploaded to Google Cloud Storage and is visible to any signed-in Humble user.
Content you create
- Audio readings. When it is your turn to read, you record yourself reading the day's Bible passage. These recordings are stored in Google Cloud Storage and accessible only to members of your group.
- Reflections. You may respond to a reading with a short audio recording or a text message. Both are stored on our servers and visible to your group members after they have submitted their own response.
- Waveform data. A compact visualization of each audio file is computed on your device and stored alongside the recording.
Usage and diagnostics
- Analytics events. We use Firebase Analytics to understand how the app is used. Events include signing in, creating a group, starting a recording, submitting a response, and opening a group thread. Event metadata may include things like recording format (text or audio), word count, or duration. The content of your reflections is never included in analytics data.
- Crash reports. Firebase Crashlytics collects crash logs and diagnostic breadcrumbs, including your user ID, to help us find and fix bugs.
Push notification token
When you grant notification permission, your device's push token is registered with Firebase Cloud Messaging so we can deliver reading reminders and group activity alerts to you.
Contact list (optional)
When you invite people to a group, the app may read phone numbers from your device's address book. Phone numbers are hashed (SHA-256) on your device — only the hashes, not the raw numbers, are sent to our servers. We use these hashes to check which of your contacts already have Humble accounts. Contact names are never sent to our servers, and we do not store your contacts' phone numbers.
2. How We Use Your Information
- To authenticate you and operate your account
- To deliver the app's core features: reading assignments, audio playback, and group threads
- To send push notifications (reading reminders, group activity)
- To let your group members recognize you by name and photo
- To match your contacts with registered Humble users (using one-way hashed phone numbers)
- To understand how the app is used and improve it (analytics)
- To identify and fix crashes (crash reporting)
3. Who Can See Your Data
| Data | Your group members | App operators | Anyone else |
|---|---|---|---|
| Display name | Yes | Yes | No |
| Profile photo | Yes (any signed-in user) | Yes | No |
| Audio readings & reflections | Yes (after they respond) | Yes | No |
| Text reflections | Yes (after they respond) | Yes | No |
| Phone number | No | Yes | No |
| Analytics & crash data | No | Yes | No |
We do not sell your data or share it with advertisers.
4. Third-Party Services
Humble is built on the following services. Each receives the categories of data described above in order to deliver the functionality they provide.
- Firebase Authentication (Google) — handles phone-number sign-in and OTP verification. Privacy policy
- Cloud Firestore (Google) — stores your profile, group data, and reflections. Privacy policy
- Firebase Analytics (Google) — collects app usage events. Privacy policy
- Firebase Crashlytics (Google) — collects crash logs and diagnostic data. Privacy policy
- Firebase Cloud Messaging (Google) — delivers push notifications to your device. Privacy policy
- Google Cloud Storage (Google) — stores profile photos and audio recordings. Privacy policy
- Google Cloud Run (Google) — hosts the Humble backend server. Privacy policy
- YouVersion / Bible.com (Life.Church) — provides Bible passage text. Scripture is fetched server-side; your identity is not shared with YouVersion. Privacy policy
- Formspree — if you submit your email on this website to be notified of the App Store launch, that email is processed by Formspree. Privacy policy
- Google Fonts — this website loads fonts from Google's servers, which may log your IP address. Privacy policy
5. Data Retention and Deletion
Your data remains in our systems as long as your account exists. We do not currently offer in-app account deletion. To request deletion of your account and all associated data — including your profile, audio recordings, and reflections — email us at charlie@charlieproctor.com. We will complete deletion within 30 days.
6. Security
All data is transmitted over HTTPS. Access to Firestore and Google Cloud Storage is controlled by security rules that restrict reads and writes to authenticated users who are members of the relevant group. Phone numbers stored server-side are salted with SHA-256 before use in contact matching. No system is perfectly secure, and we cannot guarantee absolute security.
7. Children's Privacy
Humble is not directed at children under 13 and we do not knowingly collect personal information from anyone under 13. The app requires a US mobile phone number to sign in. If you believe a child under 13 has created an account, please contact us at charlie@charlieproctor.com and we will delete the account promptly.
8. Your Rights
Depending on where you live, you may have the right to access the personal data we hold about you, correct inaccurate data, delete your data, or object to or restrict certain processing. To exercise any of these rights, contact us at charlie@charlieproctor.com.
9. Changes to This Policy
If we make material changes to this privacy policy, we will update the effective date at the top of this page. For significant changes, we may also notify you through the app or by push notification. Continued use of Humble after a change takes effect constitutes acceptance of the updated policy.
10. Contact
For privacy questions or data deletion requests: