Last updated: September 5, 2026
Biblely, developed and operated by Jason ("we", "our", or "the app"), is a faith, fitness, and productivity companion for iPhone, available at biblely.uk. Your privacy matters to us. This policy explains what data the app handles, where it goes, who we share it with, and your rights.
Biblely has no social features. There is no feed, no friends list, no messaging between users, and no leaderboard. Nothing you create in the app is shown to other users.
Biblely requires an account. When you create one we collect your email address, a username, a display name and a password. Sign-in is by email or username plus password, handled by Firebase Authentication. We do not use Sign in with Apple, Google sign-in, or any social login.
During setup you can also choose a preset avatar, a country from a list (we do not use your location for this), a theme, a Bible translation, your weight and height units, and a language. You may be asked how you heard about Biblely and what you want to get out of it. These choices are saved to your account record.
Your account record also holds whether your email is verified, whether two-factor sign-in is turned on, your referral details (the username that referred you and how many people you have referred), and the dates you joined and were last active.
We do not ask for your age or gender when you create an account. Age and gender are only asked for in the Nutrition body profile (see Section 1.3), and only if you use that feature.
Content you create inside the app, including:
This content is stored on your device. When you are signed in, the following is also saved to your account in Firebase (see Section 3.3) so it follows you across devices: prayers, their schedules and completion history; prayer boards; journal entries, verse notes, bookmarks, highlights, saved verses and recent Bible searches; to-do items, scheduled tasks and task descriptions; visions and their reflections; habits, check-ins and relapse notes; reminders; workout logs, workout templates and folders, and split plans; food logs and favourite meals; and Guide chat history.
A subset of this is also backed up to your iCloud (see Section 3.4): verse notes and highlights, saved verses, journal entries, reading streaks, achievements, highlight names, to-dos and completed to-dos, stats (points and level), Bible version, units, prayer history and completions, your profile, app settings, and the onboarding flag.
Day templates, custom exercises, available equipment, and Coach chat history stay on your device only. Biblely does not sync them to Firebase or back them up to iCloud.
Habit check-ins and relapse notes can be sensitive. They are handled like the rest of your content and are never shown to anyone else.
Workout history and exercise logs (sets, reps, weights), split plans (training days, muscle groups, exercise counts), available equipment, and physique scores. Physique scores (per-muscle scores, balance suggestions, training frequency) are calculated on your device from your workout history.
If you use Nutrition, you can enter a body profile: gender, age, height, weight, body fat percentage, target weight, goal, and activity level. From this the app works out daily calorie and macronutrient targets and body composition estimates (BMI, body fat, muscle mass, visceral fat, body water, and body age) using formulas on your device. Your food log stores what you ate and its calories and macronutrients.
Weigh-ins are typed in by hand. Biblely does not connect to Bluetooth scales and does not read or write Apple Health.
The Guide chat and the Coach chat accept typed text, voice input from your microphone, and photos. Other features (verse simplification, prayer reflections, task scoring, smart workout generation, physique coach feedback, nutrition plans, and the "Make it fit" replanner in My Week) also send text to outside AI services to generate a reply. Section 4 lists each service, what is sent, and where it goes.
Streaks, points, level, achievements, and counters such as prayers completed, workouts completed, tasks completed, quizzes taken, verses read, Bible characters read, timeline eras viewed, and maps visited. These are stored on your device and, if you are signed in, in your account record so your progress follows you across devices. We also count how many AI requests you make each day, per feature, to enforce fair-use limits.
Prayer reminders, task and habit reminders, workout reminders, the Saturday weigh-in reminder, achievement alerts, and streak reminders are scheduled by the app on your device as local notifications. They do not go through a server. You control them in Settings and in iOS notification settings.
When you sign in, the app also requests an Expo push token and stores it in your account record. We do not currently send any remote push notifications, so this token is not used to message you. The app checks whether it is running on a real device before requesting the token. We do not collect device identifiers for tracking.
If you choose to use the camera or photo library, images are used as follows:
If you allow calendar access, My Week, the day timeline, and day templates read events from your iPhone calendars (all event calendars, including those from other apps) to show them next to your Biblely items and let you move them. This reading happens on your device. Calendar events are not uploaded to our servers.
If you turn on calendar sync in Settings, the app creates a "Biblely" calendar and a "Biblely Work" calendar on your iPhone and writes your prayers, reminders, tasks, workouts, and day template blocks to them, with the default alarm you choose. Turning sync off deletes the Biblely and Biblely Work calendars and the events Biblely wrote to them.
If you use "Make it fit" in My Week, the titles and times of the items on that day, which can include your calendar events, are sent to the text AI providers in Section 4.3 to suggest a new order. You review the suggestion before anything changes.
My Week can show a weather line. If you type a city name, that name is sent to Open-Meteo to look up its coordinates, and the coordinates are then sent to Open-Meteo for the forecast. The city you typed is stored on your device only. Biblely never uses your device location.
Your theme (from 25+ themes), wallpaper, app icon, loading and streak animations, tab bar and card layout, notification toggles and alert style, notification sound, calendar sync setting, units, Bible translation, language, reading voice, and referral status. These are stored on your device. Some of these (theme, dark mode and wallpaper, loading and streak animations, notification preferences, prayer preferences, Bible translation, reading progress, recent Bible searches, units and country) are also saved to your account record in Firebase. Only your Bible translation and units are also backed up to iCloud. Your app icon, tab bar layout, and card order stay on your device.
The Daily Verse, Habits, Body Composition, Tasks, Add Task, My Week, Fuel Tracker, and Vision widgets read a copy of your data from a shared container on your device. Widgets do not use the network.
The app reads your device language and region to pick a locale, and checks whether it is running on a physical device. It does not request your location, contacts, Bluetooth, motion data, or Apple Health, and it does not use the advertising identifier.
Your data is stored on your device so the app works offline. Completed tasks, prayer completion history, quiz history, food logs and workout history older than 90 days are removed automatically, on the device and in the cloud. The exercise library is bundled inside the app and is not downloaded.
When you are signed in, your data, including your Guide chat history, is saved to Google Firebase (Firestore and Cloud Storage) on servers located in the United States so it can follow you across devices. Cloud data is kept for as long as your account exists. When you delete your account, all of your cloud data is permanently removed.
If your iPhone is signed in to iCloud, Biblely automatically backs up part of your app data to your private iCloud container (iCloud Drive files and iCloud key-value storage): verse notes and highlights, saved verses, journal entries, reading streaks, achievements, highlight names, to-dos and completed to-dos, stats (points and level), Bible version, units, prayer history and completions, your profile, app settings, and the onboarding flag. The rest of your content syncs through Firebase only (Section 3.3) or stays on your device (Section 1.2). This happens whenever iCloud is available; there is no separate switch inside the app. You can manage iCloud for Biblely in iOS Settings. iCloud data is governed by Apple's Privacy Policy, and Biblely removes it when you delete your account.
We use the following services to run the app. Requests go directly from your device to each service. We do not run a server in between. Apart from Guide chat history, which is saved to your account record so it syncs across devices (see Section 1.2), we do not keep copies of what is sent to the AI, speech, or OCR services. Data shared with each service is limited to what the feature needs.
Used for account sign-in (email and password), the cloud database that stores your synced data, file storage for profile photos and prayer board images, and small server functions that email your codes, handle two-factor sign-in, roll back referrals on account deletion, and count daily AI usage. Data is stored on servers in the United States.
iCloud for automatic backup (Section 3.4), the iPhone Calendar for My Week and calendar sync (Section 1.8), Photos for saving and picking images, Apple Maps for the Bible maps (with location turned off), WidgetKit for home screen widgets, and the App Store review prompt.
To generate text replies, the app sends your request to one of the following providers, chosen automatically based on which one is available at that moment. If one is busy or out of capacity, the app moves to the next.
Depending on the feature, the request can include: your chat messages and recent conversation, your display name (used to greet you), Bible verse text and references, your prayer text, task text, the titles and times of your day's items for "Make it fit", nutrition profile numbers (gender, age, height, weight, body fat percentage, target weight, goal, activity level), calorie targets, workout summaries and exercise names, physique scores, and body composition estimates. We never send your email address, password, or sign-in tokens.
Each provider processes the text to produce a reply and handles it under its own privacy policy. Some providers may keep requests for abuse monitoring or, on free tiers, to improve their models, according to their terms. We do not control that. Apart from Guide chat history, which is saved to your account record so it syncs across devices (see Section 1.2), we do not store the requests or replies on our servers.
Important: DeepSeek is operated by a company based in the People's Republic of China. Text sent to DeepSeek may be processed on servers in China. By using AI features you acknowledge that your request may be handled by any provider in this list.
Used for food photo nutrition estimates, Coach gym photo analysis, and custom profile photo moderation. Only the photo and a fixed analysis instruction are sent to Google; any caption you type is sent to the text providers in Section 4.3 together with Gemini's description. If you type a food name instead of taking a photo, that text is sent to Google Gemini to estimate its nutrition. We do not store these photos on our servers. Google handles them under its privacy policy and the Gemini API terms linked above.
When you use the microphone in the Guide or Coach chat, the app records a short audio clip and sends it to the first available provider in this order: Groq (Whisper), Mistral AI (Voxtral), Google Gemini, then Google Cloud Speech-to-Text. The provider returns the transcript, which is then sent to the text providers in Section 4.3 as your message. The audio clip is not kept by us. Each provider handles the audio under its own policy (see the links in Section 4.3 and Google Cloud Speech-to-Text data logging).
Used to read verses, prayers, and chat replies aloud with the cloud voices in the voice picker. The text is sent to Google Cloud for speech synthesis and the audio is cached on your device. Bible character audio stories are pre-recorded files downloaded from GitHub, or, if a file is missing, generated from the story text by Google Cloud Text-to-Speech. They are not generated from your data. The app can also use the built-in iOS voices, which stay on your device.
Google Cloud Text-to-Speech data logging, Google Cloud Privacy Notice
Used to read text from photos you attach in the Guide chat. The image is sent to OCR.space and the extracted text is returned.
Used for barcode food lookup. Only the barcode number is sent. Open Food Facts is a free, open database of food products.
Used for the weather line in My Week. The city name you type is sent to look up coordinates, and the coordinates are sent to fetch a 7-day forecast. No account details are sent.
Bible translations, quiz questions, Bible character profiles, and character audio stories are downloaded from GitHub. Your device fetches these files directly. No account details or content of yours is sent to GitHub.
Used to email your 6-digit codes for email verification, password reset, and two-factor sign-in, from noreply@biblely.uk. Your email address and the code are shared with Resend for this purpose only.
The app is built with Expo. When you sign in, it requests a push token from Expo's push service and stores it in your account record. We do not currently send push notifications, so no notification content is shared with Expo.
The exercise library offers tutorial links. When you tap one, your device opens YouTube (the app or website) with a search for the exercise name. The app sends nothing to YouTube itself. Your use of YouTube is governed by YouTube's own policies.
YouTube (Google) Privacy Policy
If you also have EyeCandy, another app by the same developer, installed, the two apps can pass a request between them on your device using app links (for example, EyeCandy asking Biblely to move a reminder). Biblely asks you to confirm before it changes anything. This happens entirely on your device; nothing is sent over the internet.
Your data may be processed in countries outside your country of residence, including:
Other providers in Section 4 may process data in further countries under their own policies. Where data is transferred internationally, we rely on the data protection practices of our service providers and their compliance with applicable frameworks. For AI providers we limit what is sent to what the feature needs and never send account credentials or sign-in tokens.
We do not sell, rent, or share your personal data with third parties for marketing or advertising. Data is only shared with the services listed in Section 4, solely to provide app features. Your content is never shown to other Biblely users. We do not sell your personal information as defined under the California Consumer Privacy Act (CCPA) or any other applicable privacy law.
We do not use any analytics, crash reporting, advertising, or tracking SDKs. We do not track you across apps or websites, and no advertising identifier is collected. The only usage counting we do is the per-day AI request count in your account record, used to enforce fair-use limits.
If you are located in the European Economic Area, the United Kingdom, or Switzerland, you have additional rights under the General Data Protection Regulation (GDPR) and the UK GDPR:
If you are a California resident, you have the following rights under the California Consumer Privacy Act (CCPA):
Categories of personal information we collect: identifiers (email address, username, display name), health and fitness data (workouts, physique scores, nutrition profile and food logs, weigh-ins, body composition estimates), content you create (prayers, prayer boards, journal entries, verse notes, tasks, visions, habits and relapse notes, reminders, day templates, chat messages), audio (voice input, sent for transcription only), photos (when you choose to use the camera or photo library), calendar events (read on your device), and device information (push token, locale).
"Do Not Sell My Personal Information": Biblely does not sell, and has never sold, the personal information of its users to any third party for money or other valuable consideration.
Biblely is not directed at children under 13. We do not knowingly collect personal data from children under 13. If we learn that we have collected data from a child under 13, we will promptly delete it from our servers. If you believe a child under 13 has provided us with personal data, please contact us at biblelyios@gmail.com so we can act.
We use Firebase Authentication for sign-in, encrypted connections (HTTPS/TLS) for all traffic, and optional two-factor sign-in by emailed code. Passwords are hashed by Firebase; we cannot see them. All data sent to the services in Section 4 travels over encrypted connections. No method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.
We may update this privacy policy from time to time, including when we add or remove a service provider. We will notify you of significant changes through the app or by updating the "Last updated" date at the top of this page. Please review this policy periodically.
If you have questions about this privacy policy, your data, or wish to exercise any of your rights, contact us at:
Email: biblelyios@gmail.com
Website: biblely.uk