Privacy policy

Who is responsible

Liora is offered by Brayan Andrés Ortiz Bastidas, in Cali, Colombia. He is the person responsible for the personal data described here. Write to brayanortizbastidas82@gmail.com.

What this policy covers

This policy covers the Liora app on iPhone and Android, and this website, including the waitlist. It says what leaves your phone, what stays on it, and what you can ask us to do with a message you sent.

What stays on the phone

Liora has no account. Your library, reading progress, quotes, habit, and appearance stay on the phone. We cannot see them, restore them, or hand them back. If you delete a book, delete the app, or lose the phone, that copy is gone.

A future account or backup

A later version may offer an account or a backup of the library and the progress. Before any of that leaves the phone, we will publish the updated policy on this page and ask you in the app. We will not upload it in silence.

A purchase you have already made stays on the store account that paid. A future Liora account will not be required to keep it.

Analytics

The published app sends usage events to Firebase Analytics, a Google service, so we can see whether Liora is being used and where it fails. A development build does not.

Those events can include the minutes you chose, the part of the day, how many days you picked, the reasons you gave for reading, whether you allowed notifications, where a book was added from and whether the add succeeded, the catalog identifier of a catalog book, the seconds of a reading session, whether you moved forward in the book, whether you met the day’s goal, whether focus mode is on, and which area of the app you opened. The area name does not include the identity of an imported book.

The text of a book is not sent. The file you imported is not sent. We do not attach your name or your email to these events. Firebase adds its own app and device identifiers so it can tell one install from another.

Crash reports

The published app sends crash reports to Firebase Crashlytics. A report contains the error and a short reason, so we can fix it. It is not the text of the book. We do not attach your name or your email.

The catalog

Loading the catalog and downloading a book need a connection. The server that sends the file receives the request: the IP address, the time, the book, and the language. We use that request to deliver the catalog and the file. There is no account to attach it to.

Help messages

From Profile, Help lets you send a petition, a complaint, a claim, or a suggestion. We store it in Cloud Firestore, a Google database. The record holds the kind of message, the text (up to 2,000 characters), the platform, the language, and the time. The app cannot read, edit, or delete that record afterward.

The email is optional. If you leave one, we use it only to reply to that message. We do not add it to the waitlist and we do not use it to announce other news. If you leave no email, we still receive the message and we have no address to answer.

If you include an email, we answer within two business months. You cannot look the message up later in the app.

The waitlist

This website asks for an email if you want to know when Liora is in the App Store and Google Play. We store that address in Firebase. We use it for one notice, when the app is available. We do not use it for a newsletter or for anything else. You can ask us to remove it before that notice. After we send the notice, we delete the address.

The one-time purchase

Apple or Google charges the one-time unlock and handles the refund. Liora does not receive your card number. The store tells the app whether those features are unlocked for the store account that paid. The purchase is described in the terms of use.

Who else handles the data

Google handles analytics, crash reports, help messages, and waitlist addresses through Firebase. Apple or Google handles the purchase and the download of the app, under that store’s own terms.

We do not sell this data. We do not use it for advertising, and we do not let an ad network track you across apps.

How long we keep it

• What stays on the phone stays there until you delete it.
• A help message is kept until we have defined the response. We then delete it. You can ask us to delete it sooner.
• A waitlist address is kept until we send the one notice that Liora is available, and is then deleted. You can ask us to delete it sooner.
• Analytics and crash reports are kept by Google under Firebase’s retention settings. We do not keep a separate copy attached to your name.

Children

Liora is not directed at children under 13. Do not send us a child’s email through the waitlist or through Help. If we learn that we have personal data from a child under 13, we will delete it.

Your rights

Under Colombian Law 1581 of 2012 you can ask to know, update, and correct your data; ask for proof of the authorization you gave; be told how the data is used; revoke the authorization and ask for deletion; and see the data we hold about you, at no charge. You can also complain to the Superintendence of Industry and Commerce (sic.gov.co).

Those rights apply to data we actually hold: a help message and a waitlist address. Write to brayanortizbastidas82@gmail.com and say what you are asking for, and which address or date we should look for. The library on your phone is yours to delete there. We do not have a copy of it.

Transfers outside Colombia

Google may store Firebase data on servers outside Colombia, including in the United States. By joining the waitlist, sending a help message, or using the published app, you authorize that transfer for the purposes in this policy.

Language

This policy is published in English and in Spanish. If the two versions differ, the English version controls.

Changes

When this policy changes, the new text replaces this page and the date at the top changes. If a change would send a new kind of data off the phone, we will ask you in the app before that happens.