Abide Privacy Policy

Effective date: February 21, 2026

This policy explains what data Abide accesses, how Abide uses that data, and how users can manage or delete their data.

1) Data Controller

Abide is operated by the app developer for personal devotional use by end users.

2) Data Accessed

2.1 Data you provide in the app

Abide stores user-provided devotional content, saved devotion entries, journal entries, selected pastors/teachers, app settings (including appearance and Bible translation), and reminder preferences.

2.2 Google account data (only when you choose Google Sign-In)

When you connect your Google account, Abide requests OAuth scopes that allow the app to:

• Read your basic profile information: name, email address, and profile photo (openid email profile).
• Create, read, and update files that Abide creates in your Google Drive (https://www.googleapis.com/auth/drive.file).

2.3 Files in Google Drive used by Abide

Abide creates and manages files in a folder named abidefaith-docs, including:

• abide-devotions.json (saved devotion snapshots and related metadata)
• abide-journals.json (journal entries and prompts)
• abide-ask-chats.json (saved Ask the Bible conversations and summaries)
• abide-settings.json (settings metadata such as selected pastors, appearance, translation, and app preferences)
• Optional share files created only when you use devotional sharing (for example, abide-share-*.json)

3) How Data Is Used

• To render and personalize devotional content in the app experience.
• To sync your devotions, journals, saved Ask the Bible chats, and settings across your devices when you explicitly connect Google Drive.
• To create Google Drive share links when you explicitly use sharing features.
• To provide scripture search and devotional generation features through configured third-party API providers.
• To maintain app functionality such as streaks, day/session progress, and reminder preferences.

4) Data Storage and Retention

• Local device storage: App state is stored in your browser storage on your device.
• Google Drive storage: If connected, synced files are stored in your Google Drive until you delete them.
• No mandatory cloud account: Abide can be used without Google Sign-In.

5) Data Sharing and Disclosure

• Abide does not sell personal data.
• Abide does not share Google user data with data brokers or advertisers.
• Data is shared only with third-party services needed to provide app functionality that the user invokes (for example Google Drive APIs and configured AI/scripture providers).

6) Security

Abide uses OAuth 2.0 for Google authorization and uses HTTPS for production endpoints. No guarantee of absolute security is made, but reasonable steps are taken to reduce unauthorized access risk.

7) User Controls and Deletion

• You can disconnect Google Sign-In within the app.
• You can delete synced files directly from your Google Drive folder abidefaith-docs.
• You can clear local app data from app settings/browser data controls.

8) Children

Abide is not directed to children under 13 and is intended for general devotional use.

9) Changes to This Policy

This policy may be updated periodically. Updates will be posted at this URL with an updated effective date.

10) Contact

For privacy questions, contact the developer at: mail@matthewmccoy.info

Back to Abide