The reader owns the deployment
Your library lives on hardware you choose. The developer has no account for you, no copy of it and no access to it.
Why it is built this way
The rules behind the reader
A personal library should work for the person reading. It shouldn't watch them, and it shouldn't be a burden on the sites and authors it reads from.
Fetching is deliberate
Subscribing and downloading are separate choices. Fiction Reader only fetches the stories you pick.
Source sites set boundaries
Requests are paced, and the app slows down when a site asks. It only reaches what your own account can already see.
No circumvention
The app doesn't solve CAPTCHAs, get round paywalls, share credentials, fake its identity or rotate proxies.
Downloaded HTML is untrusted
Downloaded pages are cleaned before they're shown, addresses are checked, and credentials are kept out of logs. The server is meant for a private network.
Nothing disappears quietly
Edited chapters are kept as versions, and deleted ones stay in your archive, marked as deleted. The author and the original link stay attached.
Cloud permission stays narrow
Google Drive sync only asks for a hidden folder of the app's own. It doesn't ask for the rest of your Drive.
Offline copies stay copies
A story saved for offline reading is copied from your library. Saving it doesn't contact the fiction site again.
It has limits
This is a personal project maintained by one person. There's no promise of support, and a site can change in a way that breaks it.
The responsibility line
You are responsible for how you use it
Fiction Reader can sign in to a site with the login you give it. That doesn't change the site's terms, copyright, account rules or technical limits. Whether and how to use the app with each site is your decision, and so are the consequences.