Português

Privacy Policy

Updated: 19/10/2026

Bibly (the iPhone app and the usebibly.com website) is operated by I H F ALVES LTDA, Brazilian company registration (CNPJ) 66.498.316/0001-63. Contact: app@usebibly.com.

Scope

This policy covers the Bibly iPhone app and the usebibly.com website. It explains what personal data we handle, why, who we share it with and how you exercise your rights under Brazil’s General Data Protection Law (LGPD).

Data you give us in the app

• Account: using Bibly requires signing in with Apple, Google or e-mail with a code. We keep the account identifier, the e-mail, the name the provider shares and which provider you used. With Apple, the e-mail may be a private relay address.
• Profile: the name you choose and, if you want, a photo (from the camera, your library or your Google account photo).
• What you create: reading plans, daily progress, answers to questions, reflections, notes, highlights, saved passages, devotional photos, reading history, streak and achievements.
• Getting-started answers: what you are looking for in reading, how much time per day, and the books and reminders you choose.
• Religious tradition (optional): if you choose to answer, we keep your answer and when you gave it. It is sensitive personal data: the acceptance at sign-in includes your consent to keep it if you answer, it is not used in analytics or shared, and you can remove it at any time in Profile > Account data.

This data stays on your device and is synced with your account on our servers, so you don’t lose it and can use it on another device.

Data that stays on your device

• Focus Mode: the apps you choose to pause are stored by Apple as codes not even Bibly can read, and they never leave the device.
• Reminders: local notifications scheduled on the iPhone itself.
• Note dictation: microphone audio is turned into text on the device and is neither stored nor sent. Only the text becomes a note.
• Preferences: language, appearance, text size, Bible version and similar choices.

Subscription (Bibly+)

If you subscribe to Bibly+, payment is made and processed by Apple in the App Store; we do not receive your card details. To know whether your account has Bibly+, we use RevenueCat, which receives the purchase information from Apple (the product, purchase, renewal and expiration dates, whether a free trial, coupon or offer was used, the store country) and links it to your Bibly account identifier, never to your e-mail or name. RevenueCat also receives technical device data (model, system and app version, language) and the connection’s IP address. When you sign in with another account or sign out, the link follows the account.

Usage data and screen recordings

When you sign in, you accept that Bibly records how the app is used so we can improve it: which screens and features are opened (for example starting or finishing a day, opening a chapter, starting Focus Mode), the language and the plan being read, and recordings of how you move through the app. In recordings all text and images are hidden, and the screens with what you wrote or your profile details are covered. This data is linked to your account’s identifier, never to your e-mail or name. We also send, without identifying you, which plans and days are finished and whether answers were right, to improve the content. You can turn all of this off at any time in Profile > Privacy and terms > Usage data.

Crash reports

When the app crashes or an operation fails, we send a technical report (error type, app version, language, the last screens opened) to fix the problem. It does not include your name, e-mail, account identifier, reading content, notes or photos.

Bible text

Bible text comes from the ABíbliaDigital service. The app sends it the requested version, book and chapter and, when you search, the search terms; the service also receives the connection’s IP address.

The usebibly.com website

The website does not ask you to sign in and does not receive your app data. Vercel hosting receives technical data needed to deliver and protect the pages, such as IP address, URL and browser. Demonstrations use libraries from jsDelivr and photos from Unsplash, which receive the connection data. With your permission in the cookie notice, PostHog measures visits and clicks and records browsing on the site, with what you type masked; sent URLs keep only the path and campaign (utm) parameters. See the cookie policy.

Why we use it and on what basis

• Creating and keeping your account, syncing and storing what you create, and unlocking Bibly+ for subscribers: performing the service you signed up for.
• Religious tradition: your consent, given in the sign-in acceptance and by choosing to answer.
• Usage data and recordings in the app, and website analytics: your consent (at sign-in in the app; in the cookie notice on the site), which you can withdraw.
• Crash reports, security and abuse prevention: our legitimate interest in keeping the service working and safe.
• Answering your requests and meeting legal obligations.

We do not sell personal data, show ads or track you across third-party apps or websites.

Who we share it with

We use providers that process data on our behalf, only for the purposes above:

• Supabase: account, database and files (photos), on servers in the United States.
• Apple and Google: sign-in, when you choose one of them.
• Resend: sending the e-mail with your sign-in code.
• RevenueCat: Bibly+ subscription status (United States).
• Apple: payment and subscription management in the App Store.
• PostHog: usage data and recordings (United States).
• Sentry: crash reports (United States).
• ABíbliaDigital: Bible text.
• Vercel, jsDelivr and Unsplash: the website.

When you share a card or an achievement, the image goes only to the destination you pick (for example Instagram or WhatsApp), which has its own policy. We may also provide data when the law or a competent authority requires it.

International transfers

Some providers store data outside Brazil, mainly in the United States. These transfers follow the LGPD, are made to perform the service and rely on the providers’ contractual safeguards.

How long we keep it

We keep account data while the account exists. In Profile > Account data > Delete account you delete your account: deletion starts right away and removes from our servers the account, plans, progress, achievements, notes and photos. If you signed in with Apple, a record used to revoke Apple access may last up to 7 days. Usage recordings are kept for up to 30 days. Subscription purchase records may be kept for as long as tax and consumer laws require. To also erase usage and crash data linked to you, write to app@usebibly.com. Providers’ backups may take longer to expire.

Your rights

You can ask for confirmation of and access to your data, correction, anonymization, blocking or deletion, portability, information about who we share it with and review of decisions, and you can withdraw consent at any time. Much of this is in the app itself (edit profile, account data, turn off usage data, delete account). For the rest, write to app@usebibly.com. You can also complain to Brazil’s National Data Protection Authority (ANPD).

Device permissions

The app asks for a permission only when you use the feature: camera (devotional or profile photo), microphone and speech recognition (dictating notes, on the device), notifications (reminders) and Screen Time (Focus Mode). The photo library opens through the system picker, which hands over only the chosen photo. Bibly does not ask for your location or the advertising identifier.

Security

Data travels encrypted, your session is kept in the iPhone Keychain and each account can reach only its own data on the servers. No system is completely immune; if a relevant incident happens, we will notify as the law requires.

Children and teenagers

Bibly is not intended for children. People under 18 should use the app with the guidance and permission of a parent or guardian.

Changes

If this policy changes in a relevant way, we will tell you in the app or on the site before the change applies. The update date is at the top of the page.

See also the terms of use and the cookie policy.