Privacy Policy
Last updated:
This policy has not been reviewed by a lawyer. It was written by the people who built Folio, to describe exactly what the software does today. Have it checked by a qualified adviser before relying on it.
It explains what Folio collects, why it is allowed to, who else sees it, how long it is kept and how to get rid of it. It covers the Folio app and the Folio service, and it forms part of the Terms and Conditions.
1. Who is responsible, and where your data sits
- Who decides what happens to your data. Folio is built and run by one independent developer, not by a company. "Folio", "we" and "us" below mean that person.
- Contact for anything in this policy. folioink.app@gmail.com. That mailbox is the way to reach us: write there to see, correct, export or delete your data, to withdraw a consent, or to complain. There is no postal address to write to.
- Where your data is held. On one rented server in Finland, in the European Union. Your account, your reading history, the books you upload and the audio generated for them are all on that machine and its backups. Some of the text you read is additionally sent to Google for processing, as section 4 describes.
2. What Folio stores about you
Your account.
- the email address you registered with, or the verified email address from your Google account if you signed in with Google;
- your password, held only as a salted PBKDF2-HMAC-SHA256 hash at 600,000 iterations. We cannot read it, and for a Google sign-in we never receive a password at all;
- the username and native language you chose, and your daily reading goal.
What you read and learn.
- which books are in your library, where you are in each one, and your bookmarks;
- how many seconds you read or listened on each day, and the streak that follows from it;
- the words and sentences you saved, with their translations and the review schedule that your answers build;
- the XP, levels, quests and achievements that follow from all of the above;
- any rating or review you leave on a catalogue book. Other readers see the rating and the text, never who wrote it: the service returns reviews with no identity attached.
What you upload. The book file itself and the text extracted from it, so you can read it on any device you sign in to. Uploads are private to your account; the Copyright Policy says what that means in practice.
Your installs. For each install signed in to your account: platform, timezone, locale, app version, and your reminder settings. Reminders are scheduled by the app on your own device, so Folio does not collect a push notification token.
Your subscription. Whether you are on a trial, subscribed or lapsed, when a trial ends, and the events our store provider sends when that changes. We never see your card details: payment happens inside Apple's or Google's store.
Logs. The proxy in front of our API records each request: your IP address, the time, and the path requested. For a catalogue search or a word pronunciation that path contains the text you searched for or asked us to speak. Logs exist to run and debug the service and to investigate abuse, and are used for nothing else.
One further record is kept against a device rather than against you. Section 6 is about that record, because you would not otherwise guess it exists.
3. Why we are allowed to hold it
Under the GDPR, every use of your data needs a lawful basis. Ours are these three.
- To provide what you signed up for (Article 6(1)(b), performance of a contract): your account, library, reading progress, bookmarks, saved vocabulary, translations, audio, XP and subscription state. Without this data the product does not function.
- To keep the service from being farmed (Article 6(1)(f), our legitimate interests): the once-per-device trial record, per-account request quotas and the access log. Our interest is that a free trial and a paid translation budget cannot be taken repeatedly by a script. The data used for it is the minimum that works, and none of it is used to profile you.
- With your consent (Article 6(1)(a)): notifications, which happen only if you grant the permission your operating system asks for. Withdraw it in the app or in system settings at any time; nothing else about your account changes if you do.
4. What leaves Folio, and to whom
Folio is not self-contained. Four kinds of text leave our server for Google, which processes each request and returns a result.
- Words and sentences you tap to translate, with enough of the surrounding sentence for the translation to make sense, go to Google's Gemini API.
- Text to be spoken goes to Google Cloud Text-to-Speech: a page you ask to have read aloud, or a single word you ask to hear. If the server cannot produce the audio, your device's own speech engine reads the text instead, under the rules of your operating system rather than ours.
- Every search you type in the catalogue goes to Google's Gemini embedding API, which is how a search matches a book by meaning instead of by exact words.
- The title and author of a book you upload go to that same embedding API, in the background, moments after the upload finishes, so that your own books answer the same search. For books we add to the catalogue ourselves, the title, author and genre go the same way.
What does not leave: the text of a book you uploaded is never sent for indexing, only its title and author. We do not send your email address, your username, your account id or your reading history to any of these services, and nothing in a request tells Google which Folio user it belongs to.
Three other companies are involved.
- RevenueCat keeps subscription state for us. It receives your internal Folio account id and tells us whether that account is entitled to use the paid features. It receives neither your email address nor anything you read.
- Apple and Google take the payment under their own privacy policies. We receive the entitlement, never the payment details.
- Google, once more, if you sign in with Google: the app obtains an identity token from Google and our server checks it against Google's published keys. We keep the verified email address and derive a username from it. We do not store your Google account id.
Google, RevenueCat, our hosting provider and our database provider act as our processors. They may use what we send only to deliver the service to us.
5. Processing outside the EU
Google runs the services in section 4 on its own infrastructure, which is not confined to the EU or the EEA, so the text in those requests is transferred out of the EU and processed there. Those transfers rely on the data protection terms Google publishes for these APIs, which incorporate the European Commission's standard contractual clauses. Everything else - your account, your library, your uploads, your vocabulary - stays in the region named in section 1.
6. The free-trial record that outlives your account
Registration grants one free trial per device. For "per device" to mean anything the server has to remember that a device has had its trial, because otherwise deleting an account and registering again would hand out another one.
What is stored is not your device's identifier. The app generates a random value the first time it runs - not a hardware identifier, and replaced if you reinstall - and the server keeps only a keyed hash of it: HMAC-SHA256 under a secret that never leaves our server. Alongside the hash it stores the internal id of the account that claimed the trial, and the date. The hash cannot be reversed into the original value, and it is attached to nothing about you: not your name, not your email, not a single thing you read.
That record is deliberately kept when you delete your account. It is the one piece of data that survives deletion, and we keep it for exactly one purpose: so that the trial stays once per device. Once the account is gone the id stored beside the hash points at nothing, and what is left is an unreadable hash and a date.
7. How long we keep things
- Your account and everything attached to it - as long as the account exists. Delete the account and it goes, as section 8 describes.
- Translation and audio caches - a translated sentence and a synthesised page are cached and reused for anyone who reads the same text, because the providers charge per request. A cache entry is keyed by a hash of the text and holds the text with its translation or its audio. It records neither who asked for it nor which book or upload it came from, so there is nothing in it attached to you, and nothing in it to delete when you leave.
- The free-trial device record - kept indefinitely, by design. Section 6.
- Store webhook events - we keep a log of the subscription events our store provider sends: an event id, the account id it concerned, and a timestamp. It exists so that a duplicate or out-of-order delivery cannot flip a subscription back. These rows are not removed when an account is deleted; what remains is an event id, the id of an account that no longer exists, and a time.
- Access logs - kept while they are useful for running the service and investigating abuse, and used for nothing else.
8. Deleting your account
Open Account -> Delete account in the app. It takes effect immediately and there is no grace period and no backup copy kept for later. It deletes your user record and login, your library and reading progress, your bookmarks, your saved vocabulary and its review history, your ratings and reviews, your daily reading totals, your XP, quests and achievements, your audio spending record, your registered installs and their reminder settings, the books you uploaded, and the uploaded files themselves in storage.
It does not delete the two records named in section 7: the free-trial device record and the store webhook log. Neither holds anything that identifies you once the account is gone.
Deleting your account does not cancel a subscription, because Apple and Google own that relationship. Cancel in the store, as the Terms explain.
9. Your rights
If you are in the EU or the UK, or anywhere with comparable law, you have the right to:
- see what we hold about you, and be told what we do with it;
- correct it. Your email address, username, native language and daily goal are editable in the app;
- have it erased. Delete account does this yourself, immediately; or ask us;
- take it with you. Ask and we will send you a machine-readable copy of your account data;
- restrict or object to the processing we base on our legitimate interests, which is the trial record, the quotas and the access log;
- withdraw consent to notifications at any time, which does not affect anything else;
- complain to your data protection authority. In the EU that is the authority where you live or work; in the UK it is the Information Commissioner's Office. You may complain to them without asking us first, though we would rather hear from you.
Write to the address in section 1. We will answer within one month, and we do not charge for any of this.
10. Security, and one thing you should know about it
- Traffic between the app and our server runs over HTTPS. The API refuses to start with an unsafe configuration, which is checked on every deployment.
- Your password is stored only as a salted hash, as described in section 2, and changing it invalidates every existing session on every device.
- The device identifier behind the trial is stored only as a keyed hash, as described in section 6.
- Uploaded files are private to the account that uploaded them. No other account can list them, open them, or confirm that they exist.
The disclosure. The codes we generate to confirm a password change or an email change are, at the time of writing, written into our server log instead of being emailed, because no email sender is configured yet. Anyone with access to that log can read them, so those two flows are not safe to rely on until an email provider is in place. No other part of your account is handled that way. If this paragraph is still here, it is still true.
11. Children
Folio is not directed at children, and nothing in it is designed to appeal to them. The Terms require you to be at least 16, or the age of digital consent where you live if that is higher. We do not knowingly collect personal data from a child under 13, or under 16 in the EU and the EEA.
If we learn that an account belongs to a child below that age we delete the account and everything attached to it, as section 8 describes, and we keep no copy. A parent or guardian who believes their child has an account can write to the address in section 1; we will delete it and confirm that we have.
12. What Folio does not do
- No advertising. There is no advertising or analytics software in the app, and nothing in it tracks you across other apps or websites.
- No selling or renting your data, and no sharing it beyond the processors named in section 4.
- No training on what you read. We do not use your uploads, your vocabulary or your reading history to train any model, and we do not license them to anyone who would.
- No device fingerprinting. The identifier behind the trial is a random value the app generates for itself, never a hardware identifier the stores would refuse.
13. Changes to this policy
We may update this policy. If a change materially affects what we collect or who receives it, we will say so in the app or by email before it takes effect, and the date at the top of this document will change.
14. Contact
Everything here is answered at the address in section 1: questions about this policy, requests about your data, and complaints.