Biblical Calendar — Privacy Policy

Effective date: 8 October 2026 · Version 3

1. Who we are

Biblical Calendar is made by PyBuilt Technologies LLC, 30 N Gould Street, Suite R, Sheridan, Wyoming 82801, USA ("we", "us"). Contact: [email protected].

2. What stays on your phone

Everything you create or choose is kept in the app's private storage on your phone, which other apps cannot read: your events, reminders and anniversaries, your journal (encrypted with its own key), the pictures you choose for days and places (the app keeps its own copy of each), your settings and looks, the place you choose, the chapters of the day, the Safe (encrypted) and the safety copies used by Restore. Nothing of this is sent to us.

Backup files in your Download folder. When you save your profile on the phone, the app writes encrypted files in Download/Biblical_Calendar: your profile and a "depot" holding your pictures, your journal, your Safe and the history of your saves, each encrypted. From Android 10 on, the app also brings these files up to date by itself each time you leave it, when something has changed. They open only with your key on paper. They are yours: they stay on the phone even after the app is uninstalled, until you delete them (in the app, Restore → Delete, or with your phone's file manager).

Files you make. A PDF of the calendar or of the anniversaries, or a file of pictures to send, is made only when you ask for it and goes only where you choose.

Error file. If the app meets an error, it writes a text file BiblicalCalendar_erori.txt in your phone's Download folder, with technical details (the app version, the place in the app, the error message, and timings when the app was slow). An error in the journal, the Safe, the keys or the profile is written without its words. The file does not contain your journal, your events or the Safe. It is never sent anywhere by the app; you may send it to us yourself if you want help.

Android's own backup. If you turned on Android's backup to your Google account, Android may copy the app's settings, events and pictures there, under Google's terms. The journal, the Safe, the keys, the PINs and the passwords are kept out of it.

3. Your Google account and Google Drive (optional)

• You may connect your Google account to keep your profile safe in your own Google Drive. The app asks Google only for access to its own hidden folder in your Drive (the drive.appdata permission); it never sees your other files, your e-mail or your contacts. The address of the account you choose is kept on your phone, only to know which account is connected.
• Sent there, each encrypted on your phone with AES-256-GCM before it leaves it: your profile (settings, events, reminders, anniversaries, looks), the pictures of your days and places (each as a file of its own), your journal (under its own key) and your Safe (under its own passwords). The app keeps the last copies of each part, for you to choose from.
• Your key on paper (26 signs, 128 bits) opens these copies anywhere; only you hold it. On your phone they also open through the phone's security chip. If you lose the key on paper, nobody — not even we — can open the copies.
• Each of your phones also leaves there a small file with the name of its model (for example "Samsung SM-A515F"), the hour of its last save and a random number made by the app, so that from another phone of yours you can erase a lost or stolen one (section 6). It stays in the app's hidden folder.
• Google stores these files under the Google Privacy Policy. We never receive them.
• Biblical Calendar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The data in the app's Drive folder is used only to save and bring back your own profile for you; it is never transferred to us or to anyone else, never used for advertising, and never read by people.
• You can remove the app's access at any time: myaccount.google.com/permissions.

4. Permissions and why they are asked

• Location (optional). To work out the hours of sunset and twilight for your place. Your position is read on the phone and kept in the app. To show the name of a place, the app asks Android's geocoder, a Google service on your phone.
• Map. When you open the map to choose a place, map pictures are downloaded from OpenFreeMap and OpenStreetMap. Like any web server, they see your internet address and the area shown.
• Microphone (optional). Only while you press "Dictate" in the journal. The words are recognised by your phone's speech service (often Google's), which handles the sound under its own policy; the app receives only the text.
• Camera (optional). Only when you photograph a card for your Safe, inside the app. The picture never goes to your gallery or to any other file: it is sealed in the Safe. The card is read on your phone by Google's ML Kit text recognition, with no internet; the picture and its text never leave the phone. ML Kit itself sends Google anonymous usage data about its own work (phone model and Android version, app name and version, a per-installation identifier that does not identify you, timings and error codes), under the ML Kit data disclosure.
• Photos and sounds. Only the pictures you choose yourself, and a song you choose as the sound of a reminder; the app keeps its own copy of each picture. It does not ask for access to your whole gallery.
• Notifications, exact alarms, starting after the phone restarts. For the reminders of your events and anniversaries.
• Display over other apps (optional). Only if you turn on the encouragements shown over other apps.
• Reading aloud. Texts are read by your phone's own speech engine (text-to-speech), chosen by you; an engine may work under its own policy.
• Fingerprint or face. Checked by Android itself; the app never receives any biometric data.
• Signs of theft, on the phone. When you turn on an erase of Section 6, the app looks on the phone for known tools that take control of a phone (for example Magisk, SuperSU, Xposed) and for a clock set by hand. This stays on the phone.
• Internet. For Google sign-in and Drive, the map, the app's fonts (downloaded from Google Fonts through Google Play services), a time check with google.com (made only when the counter of wrong tries needs a clock that cannot be set by hand, after a restart of the phone), and, when you press "Check the phone", Google's public list of revoked security certificates (android.googleapis.com). Nothing about you is sent with these requests.

5. What we do not do

• We do not collect your personal data on any server of ours, because we have none.
• We do not sell, rent or share your data, and we show no advertising.
• We use no analytics, no crash-reporting service, no tracking and no advertising identifiers. (Google's ML Kit, which reads the cards of the Safe, sends Google its own anonymous usage data: see section 4, Camera.)
• We do not access your Google account beyond the app's hidden folder in your Drive.

6. How your data is protected

• Profile, pictures, journal and Safe are encrypted on your phone (AES-256-GCM) under keys of 256 bits. The key on paper has 128 bits of chance. PINs and passwords are made slow to try (Argon2id) and bound to your phone's security chip, so they are useless away from it.
• The window of the Safe and the window of the key cannot be captured in screenshots.
• After 10 wrong PINs or passwords, no more can be tried for 24 hours from the first of them, counted on a clock that cannot be set by hand. After 100 wrong tries in a row, the Safe and the journal are erased from this phone (their copies in your Drive and in your backup files stay). The Safe locks itself as soon as you leave the app.
• Erasing a phone that is lost or stolen — each only if you turn it on, all off at first: an erase after a number of days without any opening or at signs of theft; an erase command left from another phone of yours; an erase when Google no longer lets this phone into your account for 24 hours. They erase only what is on this phone; what is in your Drive and in your backup files stays and opens with your key on paper. Log out saves to Drive first, then removes everything of the app from this phone.
• The journal, the Safe, the keys and the PINs are not included in Android's own backup.
• No protection can make a weak password strong: choose a strong one and protect your Google account with 2-step verification.

7. Keeping and deleting your data

Your data stays until you delete it. You can:

• delete any event, picture or journal page in the app;
• delete the profile, its pictures, the journal and the Safe from your Drive: in the app, Profile → Delete my profile from Drive;
• erase the Safe for ever: hold the Safe for 5 seconds → Burn;
• remove everything of the app from this phone: Profile → Log out, or uninstall the app;
• delete the backup files of Download/Biblical_Calendar: in the app (Restore → Delete) or with your phone's file manager — uninstalling the app does not delete them;
• in Google Drive on the web: Settings → Manage apps → Biblical Calendar → Options → Delete hidden app data;
• remove the app's access to your Google account: myaccount.google.com/permissions.

We cannot delete your data for you, because we never have it; write to us and we will guide you.

8. Children

The app is meant for people aged 13 and over. We do not knowingly collect data from children, and we collect none from anyone.

9. Your rights

Wherever you live (including under the GDPR in the European Union and the laws of California), you have rights over your personal data. Because we hold none of it, you exercise them directly in the app: you can see, change, export (an encrypted file of your profile) and delete everything yourself. For any question, write to [email protected].

10. Changes to this policy

If this policy changes, the new version will be published here with a new date, and an important change will be shown in the app.

11. Contact

PyBuilt Technologies LLC · 30 N Gould Street, Suite R, Sheridan, Wyoming 82801, USA · [email protected]