Urdu Novels Library · Legal information
Privacy Policy
Your reading life belongs to you. Reading progress and offline library data stay on your device; the service does not create reader accounts or keep a server-side reading history.
Last updated October 22, 2026
Who and what this policy covers
This policy applies when you use the Urdu Novels mobile app, its public catalog API, or this website. The service is operated by Urdu Novels Library, based in Pakistan. “We” means that operator. This policy describes the current app and backend; it will be updated if the service adds features that change how information is handled.
Information the service handles
The reader app does not ask you to create an account, and the backend has no reader profile, bookmark, reading-progress, or download-history records. We do not receive your locally saved reading position or the list of books you have downloaded for offline reading.
The app stores information on your device so its reading and offline features work. Depending on how you use the app, this includes:
- Reading progress: a book identifier, current and total page numbers, and the time the position was saved.
- Offline library records: a book identifier, download status, file location and integrity metadata, book details needed to display your library, and download timestamps.
- Local download quota records: book identifiers, local dates, timestamps, and the device time zone used to apply the app's daily limit.
- Cached catalog responses and related app state used to make browsing more reliable.
The PDF files you choose to download are saved in app-managed storage on your device. These records and files are not synced to our backend. Anyone with access to your unlocked device or its backups may be able to access locally stored app data.
Information sent when you use the service
When the app loads the catalog, searches, opens a book, or reads a PDF online, it sends the relevant request to our backend so we can return the requested content. Search terms are processed to find matching results and are not saved to the application backend or associated with a reader profile. Our application backend does not store or log API requests or search history. Hosting and network providers handle technical information such as IP addresses, request times, requested resources, and response status to route and deliver requests; their own processing and retention settings may apply. We do not use search requests to build reader profiles.
These requests can reveal which catalog or file endpoint a device requested to the systems that handle that request. They do not send the app's local reading position or local offline-download database to us. The backend also records actions by authorized catalog administrators for security and accountability; those records concern administration, not reader activity.
Cookies and similar technologies
The public website runs on Laravel's standard web session and may use a first-party session cookie for basic session and security behavior. It is not currently used by us to track reading activity or serve advertisements. The cookie's settings and lifetime depend on the deployment configuration. We do not currently add advertising or analytics cookies to these pages.
Device storage and deletion
Progress, cached catalog data, download records, and completed offline files remain in app storage until you delete them using available app controls, clear the app's data, or uninstall the app. Exact behavior can vary by operating system and device backup settings. Deleting a local record or uninstalling the app does not delete server logs that were already created from service requests.
Analytics, advertising, and third parties
The app displays banner and interstitial ads through Google AdMob. The Google Mobile Ads SDK automatically collects and shares data such as IP address, app interactions (including launches, taps, and video views), diagnostics, and device or account identifiers for advertising, analytics, and fraud prevention. IP address may be used to estimate general location. Google states that SDK data is encrypted in transit. Ads may be personalized depending on consent and the choices available in your region. The app presents consent notices and privacy choices where required. Google and other advertising partners handle information under their own privacy policies.
The app communicates with the catalog backend to provide its features, and normal hosting or network logs may record technical request data as described above. Mobile platform services and libraries needed to run or distribute the app may also process information under their own terms.
We may rely on hosting, storage, delivery, and security providers to operate the service. Those providers process information needed for their services. We do not sell reader profiles; the backend does not maintain reader profiles.
Retention and your choices
You can manage locally stored progress and downloads through the app and device settings. If you contact us, we use the information you provide to respond and keep it only as long as needed for the request, safety, or legal obligations. Technical logs are retained according to the configured operational and security needs of the service.
You may contact us to ask about personal information connected with a request or to raise a privacy concern. We may need enough information to locate the request and verify that we are responding to the right person. Rights and response timelines depend on the law that applies to you.
Children and changes
The service is a general reading library and is not designed to collect personal information from children through reader accounts; it has no reader account system. If you believe a child has sent personal information to us, contact us so we can review the matter.
We may revise this policy as the app or its providers change. The updated date at the top identifies the version currently published here. Material changes will be reflected on this page before or when they take effect, subject to applicable law.