How Folio handles your information.
Folio runs on your own computer. It has no backend, no hosted component and no user accounts. Its author operates no service and receives no data from it.
Once you authorise it, Folio can read:
spreadsheets.readonly and documents.readonly permissions;Folio requests no Google Drive permission. It cannot list, search or browse a Drive; it can only open a document you have identified, and only if your account may already read it. It cannot create, modify or delete anything in your Google account.
One thing: an OAuth refresh token, written to a file in your home directory with owner-only permissions, so you are not asked to sign in on every run. Nothing else is kept. Document contents are held in memory for the length of a single request and are not cached, logged or written to disk.
Folio returns what it reads to the program on your computer that asked for it, and to nowhere else. It performs no analytics, sends no telemetry and shares nothing with any third party.
What happens to a document after Folio hands it over is determined by whatever you run it with, and by your own choices. If you are reading material that belongs to an employer or client, their rules on where that material may be sent apply to you.
Folio's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Information obtained through Google APIs is used only to provide the function described above. It is never sold or transferred, never used for advertising, and never used to train any model.
You can revoke Folio's access at any time at myaccount.google.com/permissions. Deleting the token file removes the stored credential from your machine. Either takes effect immediately, and no copy exists anywhere else.
Questions about this policy: contact@trungvq.com