Skip to content
Ajanta
Features In action Privacy Contact support

Legal

Privacy Policy

Clear choices for your reading data · Last updated July 18, 2026

On this page Overview On-device data Book and author lookups Google Drive sync Providers Retention and controls Security Your rights Changelog

Who and what this policy covers

This policy covers the Ajanta iOS app and the Ajanta.app website. “Ajanta.app” is the trade name used for the app and website by the application provider identified as the seller in Ajanta's App Store listing; “we” and “us” refer to that provider.

At a glance

  • Your library is stored on your device by default. Ajanta.app does not operate an account server or a server that stores a copy of your library.
  • Book and author lookups send search information to the providers listed below.
  • If you connect Google Drive, the app automatically synchronizes library and device-sync data to files in your own Drive.
  • Ajanta does not include advertising, behavioral analytics, or cross-app tracking, and does not sell your information.

1. Information processed on your device

Ajanta stores the information needed to run your library locally, including book and author details, ISBNs, reading years and progress, ratings, notes, summaries, cover images, dates, and app preferences. This information remains on your device unless a feature described below sends it elsewhere.

When you scan a barcode, photograph a cover, or choose an image, the app processes that input to identify the book and may keep a local cover image. Barcode recognition, text recognition, and optional Apple on-device model extraction run on the device. An ISBN, title, or author derived from the image may then be used for an online lookup.

2. Book, cover, and author lookups

Normal app use can make direct network requests for metadata and images. Depending on the lookup, Ajanta sends an ISBN, book title, author name, or Wikipedia/Wikidata identifier to Open Library, Google Books, Bookshop.org image hosting, Wikipedia, or Wikidata. Those services also receive ordinary request information such as your IP address, request time, and device/network headers.

Ajanta can also load a cover or profile image from a remote URL contained in lookup results, an imported library, or a synced record. In that case, the host named in the URL receives the same ordinary request information.

Lookup results can include titles, authors, descriptions, covers, biographies, dates, and source links. Ajanta saves the results you choose or that are used to complete a book or author record.

3. Optional Google account and Drive sync

You can use Ajanta as a guest without Google. If you choose Sign in with Google, the app receives your Google user ID, name, email address, and profile-image URL. While connected, Google's sign-in SDK stores authorization credentials on your device, and Ajanta can retain those profile fields in app preferences.

Ajanta requests the drive.file permission. This lets the app create, read, update, and delete files it creates in Google Drive; it does not give Ajanta general access to all of your Drive files. Once connected, Ajanta starts sync automatically and creates a visible Ajanta_Data folder, including a books subfolder.

Synced files can contain:

  • Book titles, authors, ISBNs, reading years and progress, ratings, notes, summaries, source URLs, thumbnails, and locally saved cover images
  • Author names, alternate names, biographies, birth and death dates, profile-image URLs, and source identifiers
  • An iOS vendor identifier, your user-assigned device name, app version, timestamps, library counts, content hashes, and sync performance/status information

The app exchanges this information directly with your Google account. Ajanta.app keeps no separate copy on a server it operates and has no operator dashboard for your Drive files. Ajanta.app uses Google information only for sign-in and user-facing synchronization—not for advertising, tracking, credit decisions, sale, or training generalized AI models.

Ajanta.app's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Before using Google information for a new or materially different purpose, Ajanta will explain the change and ask for your consent.

4. Website and support

Ajanta.app is delivered through Cloudflare Pages, and its fonts are requested from Google Fonts. Those providers receive normal web-request information such as IP address, browser headers, requested URL, and time. The site itself sets no first-party cookies, uses no browser storage, and includes no analytics or advertising code.

If you email support, your address, message, and attachments are processed by the email services involved and retained as reasonably needed to answer you, maintain support records, protect the service, or meet legal obligations. Do not send an exported library unless it is needed for your support request.

5. Providers and their policies

Ajanta sends information only as needed for the feature you use. Every third party selected and integrated by Ajanta.app to receive personal information is required to provide the same or equivalent protection described in this policy. We assess those providers through their published commitments and applicable platform terms, limit the information sent, and will stop sending information to a provider if that protection cannot be maintained. Independent services also process direct requests under their own policies:

  • Google — sign-in, Drive sync, Google Books, and web fonts
  • Internet Archive / Open Library — book, author, and cover metadata
  • Bookshop.org — cover-image requests
  • Wikimedia Foundation — Wikipedia and Wikidata lookups
  • Cloudflare — website delivery
  • Apple — App Store distribution, device services, and any device backups you enable

Ajanta does not authorize these providers to use information for Ajanta advertising or tracking. Their independent logging, retention, international transfers, and legal disclosures are governed by their policies.

A remote image host supplied by a lookup result, imported library, or synced record is not selected or controlled by Ajanta.app. Loading that image sends the URL and ordinary request information to the named host under its own policy. Avoid importing or retaining remote image URLs from a host you do not trust.

6. Analytics, advertising, and tracking

The Ajanta app contains no advertising SDK, behavioral analytics SDK, or cross-app tracking code. Ajanta.app contains no tracking pixel or analytics script. Service providers may keep operational or security logs under their own policies, as described above.

7. Retention, deletion, and your controls

  • Local library: Records remain until you delete them or remove the app. Deleting a book removes its library record and schedules deletion of its matching Ajanta-created Drive file when sync is available. Cached or orphaned image files can remain until the app is removed. Apple-controlled device backups may retain app data according to your backup settings.
  • Google Drive: Synced files remain in Ajanta_Data until Ajanta deletes a matching file during sync or you delete the files or folder in Google Drive. Shared author and library-metadata files can remain after an individual book is deleted.
  • Sign Out: Signing out removes the local Google session and saved Google profile state from Ajanta and stops new sync. It does not delete your local library, Drive files, or the Google authorization grant.
  • Disconnect Google: Settings → Sign Out → Disconnect Google removes the local sign-in state, revokes Ajanta's Google authorization, and stops data access. It does not delete local or Drive files. If Google cannot complete revocation, Ajanta keeps sync paused until you retry or complete a new sign-in.
  • Exports: Exported JSON files are independent copies. Delete them wherever you saved or shared them when you no longer need them.

To remove Ajanta's visible Drive files, delete the Ajanta_Data folder and empty Google Drive Trash if you want it removed immediately from your view. Google-controlled revisions, backups, or retention remain subject to Google's policy. You can also review or revoke access from your Google Account connections. Ajanta has no separate server account or server-held library copy to delete.

8. Security

Ajanta uses HTTPS for supported network requests and relies on iOS and Google security controls for local credentials and Drive storage. Exported and Drive library files use readable JSON, and Ajanta does not add end-to-end encryption to them. Protect your device, Google account, backups, and exported files. No storage or transmission method can be guaranteed completely secure.

9. Children

Ajanta is a general-audience reading utility and is not directed to children under 13. Ajanta.app does not knowingly operate accounts for or solicit personal information from children. If you believe a child sent information in a support request, contact us so we can address it.

10. Your privacy rights

Depending on where you live, you may have rights concerning personal information that Ajanta.app actually holds, such as support correspondence. Most library data is controlled directly through the app, your device, and your Google Drive. For a privacy question or request, visit the Support page. We may need enough information to understand and verify a request.

11. Changes to this policy

We may update this policy as Ajanta's features or providers change. The current version and effective date will remain posted here. Material changes will be highlighted in the changelog and, when appropriate, in the app.

Changelog

  • July 18, 2026 — Documented active Google Drive sync, lookup and website providers, exact data categories, retention controls, and consent revocation.
  • September 21, 2025 — Initial public version.
Ajanta

Read with abandon™

Support Privacy Terms

© 2026 Ajanta.app. All rights reserved.