Privacy Policy

What We Keep, and What We Keep Not

Chapter 1 Of what we gather

When thou enterest, we receive thine email and thy name from Apple, from Google, or from thee, and if thou wilt, a likeness and how the child calleth thee. When thou makest a Bible we keep its name and cover, the words of its dedication, and, if thou givest it, the child's birthday, that we may prompt thee at the right seasons. All that thou puttest in a Bible, the ink, the notes, the letters, the recordings, the pictures, the record of the family, we keep, for that is the whole purpose. We keep also whom thou hast named to receive it, whom thou hast invited, what thou hast bought, and the token of thy device for messages, if thou allowest them. If our own service fall, it reporteth the fault to us, without thy writing in it. If the app fall upon thy device, Apple may tell us of it, and only if thou hast allowed Apple to share such reports with them that make apps.

In plain words. We collect: your account email and display name (from Apple, Google, or you), an optional profile photo and relationship label; each Bible's title, cover, dedication, and the child's optional birthday; everything you put in a Bible (ink, notes, letters, highlights, recordings, photos, Family Record entries); the recipient and backup adult you name; invites and contributors; purchase records; push notification tokens if you allow notifications; error reports from our own service, which don't include Bible content; and Apple's crash reports for the app, only if you've allowed Apple to share them with developers. The app has no crash-reporting tool of its own. We don't collect your contacts, location, or advertising identifiers.

Chapter 2 Of what stayeth upon thy device

Thy voice is written out into words upon thine own device, and thy handwriting is read into words upon thine own device, that thou mayest search them. The sound and the strokes go not forth to any machine of ours for that purpose; only the words that come of it are kept with the mark, and marked as made by a machine, and thou mayest mend them.

In plain words. Transcription of recordings and recognition of handwriting run on your device, using Apple's or Google's on-device frameworks. Audio and strokes never leave your device for that. Only the resulting text is stored with the mark, labeled as machine-generated and editable by you. It's used for search and in exports.

Chapter 3 Of why we keep it

We keep these things to show thee thy Bible on every device thou hast, to show it to them thou hast invited and to none else, to make it whole again if a device be lost, to carry it out as a book when thou askest, to prompt thee if thou hast asked to be prompted, to send thee the emails the app requireth (the invitation, the handing down, the warning before a deletion), to honor thy purchases, to answer thy claims, and to find and mend what is broken. For no other end.

In plain words. We use your data to sync Bibles between your devices, show them to the people you invite, back them up, render exports and prints, send prompts you opt into, send transactional email (invites, hand-downs, deletion notices, claim updates), process purchases, handle bereavement claims, and fix bugs. Nothing else.

Chapter 4 Of what we do not

We sell not thy data, nor lend it, nor trade it. We set no advertisements before thee. We follow thee not across the web nor across other apps, and we use no tool that doth so. We read not what thou writest, save where the law compelleth or thou hast asked our help upon it. We make no marketing unto children. We use no machine that writeth or draweth or speaketh in thy stead.

In plain words. No data sales, no ads, no cross-app or cross-site tracking, no third-party analytics SDKs, no advertising identifiers. We don't read your content except when the law requires it or you ask for support on a specific item. No child-directed marketing. No generative AI in the product.

Chapter 5 Of them that help us keep it

We keep thy words and thy pictures with these, each under a covenant that it serve us alone: Supabase for the database and the sign-in, in the eastern United States; Cloudflare for the recordings and the pictures; Fly.io, where our own service runneth; Resend, which carrieth our emails; Sentry, which receiveth the reports when our service falleth; Apple and Google, which take payment within the app; Paddle, which taketh payment upon this website; and, if thou order a printed book, a store and a printer that have thy shipping address and thy book. Thy data abideth in the United States. If thou art elsewhere, know that it crosseth the sea to be kept.

In plain words. Our processors: Supabase (database and auth, US East), Cloudflare R2 (media storage), Fly.io (our keepsake service), Resend (transactional email), Sentry (our service's error reports), Apple and Google (in-app purchases), Paddle (web purchases, as merchant of record), and for printed books, Shopify and Lulu (payment, printing, and shipping). Each is bound by a data-processing agreement. Data is stored in the United States. If you're outside the US, your data is transferred there to provide the service.

Chapter 6 Of the children

No child under thirteen hath an account here. A parent may make a layer for such a child, with a passcode, under the parent's own account; whatsoever the child writeth there is the parent's to keep and the parent's to delete. The child's name and birthday are written by the parent, and we use them only within that family's Bible and to time the prompts. We gather nothing from a child that the parent hath not set before us.

In plain words. Accounts are 13+. Child mode is a layer under a parent's account, created and controlled by the parent, who can delete it. A child's name and birthday are entered by the parent and used only inside that Bible and for prompt timing. We don't knowingly collect personal data from children except what a parent provides, and a parent can review or delete it any time by email or in the app.

Chapter 7 Of them thou hast invited

They that thou invitest see what is in the Bible, every layer save the sealed letters before their day, and the names and likenesses of them that wrote. Thy child, when the Bible is handed down, seeth all that was written for him. What a contributor writeth is given to the child and remaineth with the child, labeled with the name he bore, unless he ask at his leaving that it be taken away.

In plain words. Contributors you invite can see the Bible's content (except unopened sealed letters) and the names and photos of other contributors. After a hand-down, the child sees everything written for them. A contributor's marks stay in the Bible after they leave, attributed by display name, unless they choose to remove them when deleting their account.

Chapter 8 Of the claim upon a death

He that claimeth a Bible after a death sendeth us the certificate of death, his own government papers, and proof of kinship or of the estate. These lie in a locked place where every opening is written down, and they are destroyed thirty days after the claim is closed.

In plain words. Bereavement claims require a death certificate, the claimant's government ID, and proof of relationship or estate papers. They're stored in a private, access-logged bucket, seen only by the reviewer, and deleted 30 days after the claim closes.

Chapter 9 Of how long we keep it

We keep thy Bible as long as thou keepest thine account, for that is the promise. A Bible cast out lieth thirty days and is then destroyed. An account closed sleepeth fourteen days and is then blotted out: the sign-in, the profile, the likeness, the recordings and pictures of the Bibles it owned, the exports, unused gift codes, the claim papers, the device tokens; and we tell Apple to revoke the sign. The copies we lay up each night roll away within thirty days more. Of purchases we keep what the tax law biddeth, with thy name taken out. And we keep one sealed token, a salted hash of thy store identity and nothing else, that the free first Bible be not claimed again and again.

In plain words. Content is kept for as long as your account exists. Deleted Bibles are purged 30 days after deletion. Deleted accounts are hard-deleted 14 days after the request: auth identity, profile, avatar, media of owned Bibles, exports, unused gift codes, claim documents, push tokens, and we revoke the Sign in with Apple token. Backups roll off within 30 days after that. Anonymized purchase records are kept as long as tax and accounting law requires. A salted hash of your store identity is kept so the free first Bible can't be farmed by deleting and recreating accounts. It contains nothing else.

Chapter 10 Of thy rights

Thou mayest see all that we hold of thee, for the export giveth it all. Thou mayest mend thy name and thy likeness in the app, and the words a machine made of thy voice or thy hand. Thou mayest delete a Bible, or thine account, as is written in the terms. Thou mayest ask us by email for a copy, a correction, or a deletion, and we shall answer within thirty days, or sooner where the law of thy land requireth. We shall not treat thee the worse for asking. If thou art in Europe or in California, the laws there give thee these rights by name, and we honor them; thou mayest also complain unto thine own authority.

In plain words. Access: export gives you everything. Correction: edit your profile and machine-generated text in the app. Deletion: delete a Bible or your account in the app or at fathersbible.com/account/delete. Or email us for access, correction, deletion, or portability and we reply within 30 days (sooner where required). No discrimination for exercising rights. GDPR and CCPA rights apply where you live, including the right to complain to your local authority. We don't sell or share personal data for advertising, so there is nothing to opt out of.

Chapter 11 Of how we guard it

All that passeth between thy device and us is sealed in transit. The database itself refuseth to show one family's Bible to another, by rules written into it and not only into the app. Thy sealed letters are kept shut upon our side until their day. Few of us can reach the stores, and every reaching is written down. Yet no vault is perfect; if a breach touch thee we shall tell thee as the law requireth.

In plain words. TLS in transit. Row-level security in the database enforces who can see which Bible. Sealed letters are enforced server-side. Access to production is limited and logged. No system is perfectly secure; if a breach affects you we'll notify you as the law requires.

Chapter 12 Of changes, and of reaching us

If we change these words in more than a small way, we shall tell thee in the app or by email before the change taketh hold. Write unto us at hello@fathersbible.com, and a person shall answer.

In plain words. Material changes are announced in the app or by email before they take effect. Contact: The Byte Quill LLC, [TODO: mailing address], hello@fathersbible.com. See also the terms of service.