Afsana Get the app

Privacy policy

Effective 28 August 2026 ยท Last updated 7 November 2026

In plain language: Afsana works without an account. Imported books and reading activity stay on your device unless you deliberately use an online feature or enable private backup. We do not sell personal data and Afsana contains no advertising SDK.

Who operates Afsana

Afsana is operated by Faiz Iqbal. Questions and privacy requests can be sent to faiziqbal733@gmail.com.

Information kept only on your device

Without cloud backup, Afsana stores imported EPUB files, covers, reading position and history, bookmarks, highlights, notes, saved words, reader preferences, reading statistics, AI response caches, and book-chat history in app-private storage on your device. This information is removed when you delete it in Afsana or clear/uninstall the app, subject to Android device behavior.

Optional account information

If you sign in with Google, we receive the Google account identifier and may receive your name, email address, and profile image. We also keep device/session identifiers and session times so sign-in, token refresh, session revocation, and account security work. Afsana never receives your Google password.

AI features

When you request an explanation, summary, book insight, or chat response, the text needed for that request is sent over encrypted HTTPS to the Afsana backend and then to Anthropic, which provides the Claude AI models. For "Ask this book", that text is the part of the book you have read so far (never anything past your reading position), your question, and the conversation in that chat. When you turn on chapter artwork, a short scene description derived from the chapter is sent to OpenAI to create the image. Under these providers' commercial API terms, the content is not used to train their models; they may keep it for a limited time for safety and abuse monitoring under their own policies. The Afsana server records a pseudonymous actor key, model name, time, and token counts for limits, cost control, and abuse prevention; it does not store the prompt or generated text in the AI-usage table. Responses may be cached locally on your device.

Optional private backup and sync

Cloud backup is off by default. If you enable it after signing in, Afsana uploads the EPUB files you choose to keep, book metadata, reading positions and sessions, bookmarks, highlights and notes, saved vocabulary, preferences, and progression data to the Afsana server. These records are tied to your account and are used only to provide backup and synchronization.

Feedback

When you send feedback from Afsana, the server stores your message, a random identifier created for this installation of the app, and the time. It also stores an email address only if you enter one or keep the one your signed-in account fills in, and device details (app version, phone model, Android version, and reader settings such as font and page style) only if you leave "Include device details" on. Feedback never includes the text of your books. If you are signed in, the report is linked to your account and is deleted with it; otherwise it is anonymous and you can ask for its deletion by email. Feedback is used only to fix problems, improve Afsana, and reply when you asked for a reply.

The optional "Enjoying Afsana?" prompt is decided on your device and sends nothing by itself. Choosing to rate opens Google Play's in-app review, which Google provides under its own terms.

Usage counts

Afsana sends a few anonymous counts so we can see what helps people read, such as "opened a book", "used Simplify", "turned reminders on" or "tapped a reminder". Each count carries only the event name, a time, the app version, a random identifier created for this installation, and small details like which AI action was used. It never includes your books, what you read, your account, your name or your email, and it is not linked to your account. Counts are used only to improve Afsana. You can turn them off in Profile, under Privacy.

Reading reminders

Reminders are optional and off until you turn them on. They are created on your phone from your own reading (your book, chapter and streak) and nothing about them is sent to a server. You can change the time or turn them off in Profile, or in Android's notification settings.

Tips

"Support Afsana" lets you leave an optional tip. Payment is handled entirely by Google Play, under Google's terms. Afsana never receives your card, UPI, or bank details; Google Play tells the app only whether a tip went through. Tips unlock nothing and are not stored on the Afsana server.

Other network services

These services may receive ordinary connection information such as IP address, time, and user agent. Their own policies govern their independent processing.

How information is used

We use information only to provide reading, sign-in, AI, backup, sync, feedback, account support, security, quota enforcement, troubleshooting, service operation, and improving the app from anonymous usage counts. We do not sell personal information, use it for behavioral advertising, or share it with data brokers.

Security and retention

Network traffic uses HTTPS. Account credentials are stored as rotating hashed tokens; private EPUB downloads require authentication. Server data is retained while your account exists or as needed to provide the requested service. Limited security and request logs are rotated. Disaster recovery backups are access-restricted and expire on a rolling schedule. No internet service can guarantee absolute security.

Your choices and deletion

Successful account deletion removes account information, active sessions, synchronized reading records, feedback sent while signed in, and private EPUB backups from the live service. Recovery copies expire with the backup schedule and are not used except to restore the service after a disaster. Local books remain on your device unless you delete them separately.

Account deletion options

Children

Afsana is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Contact us if you believe a child has provided account information.

Changes to this policy

Material changes will be reflected on this page with a new effective date and, where appropriate, communicated in the app.