Last updated on
What do we mean by “personal information?”
For us, “personal information” means information which either directly identifies you (like your name or email address) or can be reasonably linked or combined to identify you (like an account identification number or IP address). We’ll always tell you what personal information we’re collecting from you.
We consider any other information “non-personal information.”
If we store your personal information with information that is non-personal, then we will consider the combination as personal information. If we remove all personal information from a set of data, then the remaining set is non-personal information.
What information do we collect?
We don’t collect any personal information other than what you explicitly share with us through the Lectionary.app. Unless you contact us to tell us you’ve used the Lectionary.app, we have no way of knowing.
How do we use information we collect?
When you give us information, we will use it only in the ways for which you've given us permission. Generally, we use your information to communicate directly with you.
What information do we share?
Whenever you share personal information with us through the Lectionary.app, we will not share that information with anyone apart from your knowledge and without your explicit permission.
What if we want to share information we collect?
Before sharing any personal information you’ve shared with us through the Lectionary.app, we will seek your permission directly. First, we will contact you by e-mail, phone, or private message through a common social media platform, or some other mutually beneficial communication method. We will ask you if and how we may share specific personal information you have shared with us through the Lectionary.app. Then, only after you have given us your explicit permission, will we share any of that information.
What if we change this policy?
Contact the Lectionary.app team
Attn: The Lectionary.app
633 S Plymouth Ct, #703
Chicago, IL 60605
For technical support, please visit our GitLab repository.