Privacy policy

Who is responsible

Lectio Daily is offered by Juan Gamarra, an individual, with address at Proviv. Res. La Esperanza, Carabayllo, Lima 15121, Perú, who is responsible for the data described here ("we" on this page). You can write to privacy@lectiodaily.com.

What we store

From the website, nothing. It has no sign-up or sign-in, asks you for no information and does not record what you read. We use no advertising or tracking pixels; Cloudflare counts visits, without cookies and without identifying you (below).

The app and your account

The app can be used without an account. What you read and mark without an account is stored only on your phone; usage metrics, below, are separate.

Your phone schedules the daily reminder, without going through our server. The time you choose only leaves it with the usage metrics, below.

When it opens, the app asks Expo, the service that updates it, whether there is a new version. That request carries a random identifier for the installation, the type of phone and the IP address.

The Bible versions you download in the app come from lectiodaily.com, delivered by Cloudflare like the website. Which version you read only leaves your phone with the usage metrics, below.

On Android, if the phone does not have the voice for a language installed, its speech engine may use a voice over the internet: the provider (usually Google) receives the Bible text being read and your IP address.

With an account, if you allow notifications, we store with it an identifier for your phone so it can receive them, and the language they arrive in. Notifications (from your groups and, in the evening, when your streak is at risk) go through Expo’s push service and Apple’s or, on Android, Google’s (Firebase Cloud Messaging), which only receive that identifier and the text of the notification. You can turn them off in Settings → Notifications or in your phone’s settings, and the identifier is deleted when you sign out or with your account.

If you create an account, with your email, with Apple or with Google, we store your name and your email. If you sign in with email, also your password, encrypted: we never store it as is. With Apple or Google we store the identifier and the access keys they give us, and with Google also the address of your profile photo; if you hide your email with Apple, we receive Apple’s relay address.

With an account we store your reading: the chapters you mark as read or listen to in full, and when, the days you read, your plans (also the ones you save for later), your saved verses, highlights, notes and prayers, your daily goal, your achievements, the days the streak protector covered, your time zone and your language. When you sign in, what you had read without an account on that phone moves to your account.

In a group, the other members see your name, your streak, how many chapters you read that week and your progress in its challenge; never your notes, prayers or saved verses. We store your groups, when you accepted their rules, whom you block and, if you report a group or someone, the report with its reason and the reported name. Reports about a member are reviewed by the person who created the group, who sees whom and why, never who reported; the rest, by us. If the person who created a group removes you without letting you back in, we store that so its code does not let you join. For a few hours we also note that they were already told you joined, so as not to repeat it. If you delete your account, your reports keep no data of yours, and the ones that mention you are deleted.

To know how many people use the app, we note which days you open it with your account and the time you first open it each day, nothing of what you read. After 13 months, it is deleted.

With an account, we also note which version of the app and of the system (iOS or Android) you use and the country you connect from (worked out from your IP address, which we do not store), to know who receives each update. It is deleted with the account.

Apple or Google charge for Premium: we never see your card. To show you the prices and validate purchases, the app talks to RevenueCat from the moment it opens, with an anonymous identifier for the installation; with an account, whether you buy or not, it also gives RevenueCat a random identifier for your account, not your name or email. RevenueCat tells us what you bought and until when: we store that with your account and it is deleted with it.

For security, each session stores the IP address and the kind of device you signed in from, and sign-in attempts are counted by IP address to stop abuse.

Everything is stored in our database, on Cloudflare, and your session, encrypted, on your phone (in the iPhone’s keychain or Android’s keystore). We only use your email to activate your account, to recover your password and to let you know if someone tries to create another account with it: we send no newsletters or advertising, and we do not sell or share your data.

So that nobody can use the app to flood someone else’s inbox, for one hour we keep which address we sent each account email to and when, and then we delete it. And so that nobody can guess a new-password code, until the end of the day we keep how many times a code was tried for each address, and then we delete it.

App metrics

To learn what gets used and to fix crashes, the app sends usage metrics to Google Firebase (Analytics and Crashlytics), which processes them on our behalf: which screens you open and what you do on them (for example, that you marked a chapter as read or listened to it and which book it was in, that you saved or highlighted a verse, that you started, saved or left a plan and which one, including those on a theme, such as anxiety or grief, which Bible version you downloaded or chose, that you searched and how many results there were, or that you opened Premium and from where), some settings (language, appearance, theme, font and text size, voice speed, sounds, daily goal, whether the reminder is on and at what time, and whether you allowed notifications), how long your streak is (in ranges, not the exact number), how many plans you follow and whether you have an account and Premium. If the app crashes, the crash report is sent with the phone model and the system version. Like any internet service, Google sees the IP address and infers the approximate country and city from it.

We never send the text of your notes or prayers, what you search for, the exact chapter you read, your name or your email. Metrics carry a random identifier for this installation, never your account; you can see it in Settings → Privacy. We do not use the phone’s advertising identifier, there are no ads, and the metrics are not combined with other companies’ data. Google keeps them for 14 months.

With metrics on, the app also checks in once a day with our own database, using that same install ID: the app and system version, the language, whether you have an account and Premium, and the country (worked out from your IP address, which we do not store). We note which days you open the app, nothing of what you read. That is how we know how many people use it, including without an account. If you are signed in, we also note in our database which account checks in from this installation, with the first and last time, so we can see which phones each account uses. Google never receives it. It is deleted with the account, or when you turn metrics off. Everything is deleted after 13 months without opening the app. If the app or an account connects from Google’s or Apple’s networks (their reviewers and test robots), or the app runs on a simulator, we mark it as a test one to leave it out of our figures.

They are on by default and you can turn them off in Settings → Privacy → Share usage metrics: from then on nothing else is sent, and what we keep about this installation is deleted at once. To have us delete what was already sent, write to privacy@lectiodaily.com with your install ID.

Cookies and data in your browser

We use no cookies, which is why you will not see a cookie banner. Your browser keeps your reading preferences on your device only: light or dark theme, and text size and font. They never leave your device and disappear if you clear your browser data.

Who serves the website

The website is delivered by Cloudflare. Like any hosting provider, it processes technical data from each visit, such as your IP address, to serve the pages and protect them from attacks. We do not store that data. The website also uses Cloudflare Web Analytics: without cookies or storing anything in your browser, it counts how often each page is opened, where visitors come from, the type of browser and device, the country and how fast the page loads. It identifies no one, and we only see totals.

How to delete your data

For the website, there is nothing to delete on our side. Your reading preferences can be cleared from your browser settings.

If you have an account in the app, you can delete it with everything it stores in Settings → Delete account, or write to privacy@lectiodaily.com from its email and we will delete it. An account created with an email that is not confirmed within 7 days is deleted automatically. What the app keeps without an account is deleted when you uninstall it.

What is deleted stays for 30 days in the database’s automatic backups, which are only used to recover it after a failure. The steps, what is deleted and what is kept are at lectiodaily.com/en/delete-account.

Children

Lectio Daily is intended for people aged 13 and over. We do not ask for your age and the account is optional. If someone under that age created an account, write to privacy@lectiodaily.com and we will delete it.

Changes to this policy

If what the website or the app does changes, this page changes at the same time, with its updated date.

Contact

For any privacy question: privacy@lectiodaily.com