Privacy
Privacy Policy
Folio collects nothing. This is the long version of that sentence.
The short version
Folio collects nothing about you. There is no account, no server of mine, no analytics, no crash reporting, no advertising, and no tracking of any kind. Your library never reaches me, because there is nowhere for it to reach.
The rest of this page is that sentence at length, and the few places where your music or your device does talk to somebody else — always because you asked it to.
What stays on your device
Your scores, the marks you make on them, bookmarks, setlists, tags and every preference are kept in Folio's own storage on the device. They are not transmitted anywhere by Folio, and they are removed with the app when you delete it.
iCloud
If you keep your library in iCloud, copies of your scores and their annotations are stored in Folio's private iCloud container inside your Apple Account. That is Apple's storage under Apple's terms; I have no access to it and no way to enumerate who uses it. Apple's handling of it is described in their own privacy policy.
Google Drive
If you connect Google Drive, Folio asks Google for one narrow permission — drive.file — and nothing else. That permission grants access only to files Folio itself created and files you personally chose in the picker. It cannot list, read or search the rest of your Drive, and the app is written so that widening it is caught by a test rather than shipped.
The token that permits this is held in your device's Keychain. It is sent to Google, to use the permission you granted, and to nobody else. Disconnecting Drive in Folio's settings discards it; you can also revoke it yourself from your Google Account's permissions page.
Folio's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. That information is used only to provide the features you asked for, is never sold, and is never used for advertising.
Connecting two devices
When two devices act as one stand, they talk to each other over your local network or directly by Bluetooth. The score, the page position and anything else exchanged travels between those two devices. It does not pass through a server of mine, and there is no server of mine for it to pass through.
Purchases
Folio Pro is sold by Apple. Payment happens entirely inside the App Store: Folio never sees your name, your payment details or your Apple Account. What it receives back is the answer to one question — whether this device is entitled — and it keeps only that answer.
Tracking, and the absence of it
Folio contains no analytics SDK, no crash reporter, no advertising network and no third-party tracker. It does not read the advertising identifier, does not build a profile of you, and shares nothing with data brokers. This is why its App Store privacy label reads Data Not Collected.
Your data, and deleting it
There is no account to close, because there is no account. Deleting Folio removes what is on the device. Anything you put in iCloud or Google Drive lives in your own account and is deleted there, by you, at any time — without needing my permission or my involvement.
This website
This site is served by Cloudflare, which keeps the ordinary server logs any host keeps. It sets no cookies of mine and runs no analytics or scripts.
If you leave an address to hear when Folio ships, it is stored in a Google Form in my Google account and used for that one message. It is not shared, sold or added to anything else, and it is deleted once that message has gone out — or sooner, if you write to the address below and ask.
Children
Folio is for anybody who reads music, including children learning it. It is not directed at children specifically, and since it collects no personal information from anyone, it collects none from them either.
Changes to this policy
If what Folio does with your information changes, this page changes in the same release, and the date below changes with it. The page is versioned alongside the app's source, so its history is as auditable as the code it describes.
Contact
Questions about any of this go to jenny610138@gmail.com, and are answered by the person who wrote the code.
Last updated 8 September 2026.