LibafileYour library, in a file you own.
Libafile privacy policy
Libafile is made by AnchorKite LLC. Last updated November 2, 2026.
The short version
Libafile has no server that receives your library. Your books, borrowers and loans are kept in a library file that you own and choose where to store, plus a working copy and backups inside your own browser. AnchorKite never sees them unless you choose to send them to us.
What Libafile stores, and where
- Your library file, wherever you save it: your computer, a USB drive, or a cloud folder such as Google Drive or OneDrive. If you use a cloud folder, that provider's terms and your organization's agreement with them apply to the file.
- A working copy and up to 30 backups in this browser's storage on this device, so closing the tab never loses work. Clearing your browser data removes them.
- Dated copies in a backup folder, if you choose one. They stay in that folder and go nowhere else.
- Borrower records hold a display name and an optional group only. When you add borrowers, Libafile refuses entries that look like email addresses or ID numbers. We suggest first name and last initial.
- Your display choices, such as theme and book view, in this browser's storage.
Lost libraries
AnchorKite holds no copy of your library, so we can't recover it if it is lost. Keeping your file safe is up to you. See what can be recovered.
What leaves your device
- Book lookups (optional). When you look up a book by ISBN, Libafile sends that ISBN to Open Library (openlibrary.org), a project of the Internet Archive. No borrower or library data is included. Like any website, Open Library receives standard request data such as your IP address.
- Book covers. When you are online, cover images load from the address saved with each book. That is usually covers.openlibrary.org, but a book imported from another app can use a different website. Each website that serves a cover receives standard request data and can tell which image was requested. Covers are kept in this browser where possible, so they load faster and work offline.
- The app itself is downloaded from our web host, Netlify, when you first visit and when it updates. Like any website, the host receives standard request data such as your IP address. No library data is sent. We use Netlify's server-side traffic statistics, such as page views, visitor counts and countries, to see whether Libafile is being used. They come from those same requests: no script runs in the app, no cookies are set, and we only see totals.
- Email to us. If you write to us, we receive your email address and whatever you include, and we use them only to reply. Please don't attach your library file.
Libafile has no analytics, advertising or tracking inside the app, and no accounts.
Borrower data, including children's data
Because borrower names stay in your file and browser, AnchorKite does not collect, process or store borrower information, and does not act as a data processor for your organization. Your organization's own policies decide where the library file may be kept, and it decides whose names go in it.
Changes
If a future version changes what leaves your device, this page and the app will say so before it happens.
Contact
Questions: support@anchorkite.com