Beacon
Privacy Policy
Effective date: March 19, 2026
What this covers
This policy explains how Beacon - Daily Bible Encouragement ("Beacon") collects, uses, and protects personal information.
Information we collect
We collect information you provide directly and information needed to operate the app, including:
- Account information, such as your name, email address, and profile image when you sign in.
- Faith rhythm and check-in inputs you choose to share in the app, such as preferences, reflections, and encouragement settings.
- Technical information needed to run the service, such as push token identifiers and basic diagnostic logs.
Google Sign-In and OAuth data use
- If you choose Google Sign-In, Beacon uses Google OAuth only for authentication and account setup.
- Beacon does not request access to Gmail, Google Drive, Google Photos, or other Google user content.
- Beacon does not sell personal information or Google user data.
- Beacon's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
How we use information
- Authenticate your account and keep your session secure.
- Provide personalized encouragement, prayers, and reminders.
- Operate core features, including notification delivery.
- Maintain service reliability, safety, and abuse prevention.
How information is shared
We may share data only when necessary to run Beacon, such as with:
- Authentication, hosting, database, and push-notification providers.
- Authorities when required by law or valid legal process.
Retention and deletion
We retain personal data for as long as your account is active or as needed to operate the service and comply with legal obligations. You can request account and data deletion using the support contact listed in the app store listing.
Security
We use reasonable technical and organizational safeguards designed to protect personal information.
Policy updates
We may update this policy from time to time. Material changes will be reflected by updating the effective date on this page.