Data and privacy — development preview

Data handling in the current GengReader development build.

GengReader is being developed and tested locally. It is not a launched commercial service. The operating entity, contact details, retention periods and provider agreements must be confirmed before launch.

Books, text, notes and conversations are scoped to the signed-in account. Files use authenticated private endpoints. Passwords are handled by the authentication system using password hashing. API keys stay on the server.

Only user-initiated AI discussion, analysis, OCR or portrait requests send relevant content to configured providers. Reading and notes work without an AI provider. Review the chosen provider's terms before enabling it.

Book deletion revokes access and cancels work immediately, with physical file cleanup performed by the worker. Non-content metering records may be retained. Unsynced progress and notes may remain in browser storage; sign out and clear site data on shared devices.

This describes the development implementation. A final privacy policy must be reviewed before public operation.