Leafmark — Privacy Policy

Last updated: October 23, 2026

Leafmark is built on a simple principle: your books, highlights, and reading habits belong to you — and to no one else, including us.

What we collect

Books, highlights, notes and reading habits stay on your device or in your own iCloud. From version 1.20, Leafmark sends a few anonymous events about the path to purchase (Firebase Analytics) and purchase records (RevenueCat). Both are described below.

• No account. You never sign up, log in, or give us an email address.
• No reading-behavior tracking or advertising. Leafmark never sends which books you open, what you read, or what you highlight, and it does not track you across apps or websites.
• No Leafmark cloud. Leafmark has no server. Your books, highlights, notes, reading positions, and reading statistics are stored on your device, in plain files you can inspect. Some of them are also synced through your own iCloud (see iCloud sync below).
• No reading content is sent to us. Core reading features work offline. Apple and RevenueCat handle purchase-service requests, and Firebase Analytics receives the purchase-funnel events below.

What stays on your device

• Imported EPUB files (stored in the app's Documents folder, included in your own iCloud/iTunes device backup if you have backups enabled — that backup is managed by Apple under your Apple account, not by us)
• Highlights and notes (a local JSON file, exportable as Markdown at any time)
• Reading positions and appearance settings
• Reading statistics (local sessions history)

Deleting the app deletes all of this from your device. Copies already synced to iCloud stay in your iCloud account. We could not recover any of it even if you asked us to, because we never had it.

iCloud sync

• When you are signed in to iCloud with iCloud Drive turned on, Leafmark automatically copies your highlights (with their text and notes), bookmarks, reading positions, and the title and author of each book in your library to the app's folder in your iCloud Drive, so your other devices can pick them up.
• There is no switch for this in the app. Signing out of iCloud or turning off iCloud Drive stops it, and the app keeps working on its own.
• EPUB files, reading statistics, imported fonts, and appearance settings are not synced.
• The transfer is done by iOS, and the data is stored in your iCloud account. None of it is sent to us.

Third parties

Leafmark uses the open-source Readium Swift Toolkit to render EPUB files. It runs entirely on your device and sends nothing anywhere.

Purchase-funnel analytics with Firebase Analytics

From version 1.20, Leafmark uses Google's Firebase Analytics to learn how many people reach the Leafmark Pro screen and how many of them buy. The app sends only these four events:

• The Leafmark Pro screen was shown
• The one free Markdown export was used
• The purchase button was tapped
• A new purchase was completed (restores are not counted)

The screen, button and purchase events carry a fixed label for where the Leafmark Pro screen was opened from (for example, the export limit or the library menu).

Firebase Analytics also records its standard app events, such as first launch and the start of a session, together with an app-instance identifier generated by Firebase, the device model, OS and app versions, language, and a general location that Google derives from the network IP address. It measures App Store purchases, including the product and price. Firebase Installations also sends diagnostic data used to keep the analytics service working.

The app does not send book titles, authors, file names, book text, highlights, notes, reading positions or statistics. It does not send your name, email address or any account. The advertising identifier (IDFA) is not used, identifier-for-vendor collection is turned off, advertising personalization and ad-network registration are turned off, and screens are not recorded automatically. These events are not linked to your identity and are not used for advertising or tracking. Only the App Store version sends these events: development builds, TestFlight builds and the copies used for App Review send nothing. See Google's Privacy Policy and how Google uses information from apps that use its services.

Purchase processing with RevenueCat

From version 1.20, Leafmark uses RevenueCat's purchase service for receipt validation, fraud prevention, purchase reliability, and purchase analytics.

The SDK automatically sends past and new Apple purchase records, including product and transaction identifiers, purchase dates and status, and renewal, expiry or revocation information where applicable. It also uses a randomly generated anonymous app user ID. RevenueCat receives request information such as app and operating-system versions, locale, currency and network IP address. Purchase records may include purchases from earlier versions and both production and Sandbox transactions.

The app does not add your name, email address, advertising identifiers or a custom cross-app identity to RevenueCat. Automatic device-identifier collection is disabled. App-created content is not sent to RevenueCat. See RevenueCat's Privacy Policy.

Apple StoreKit continues to determine purchase ownership and eligible Family Sharing access. Existing purchases, prices and free features are unchanged, and this migration does not require a repeat purchase. Uninstalling the app removes local app data but does not delete Apple's purchase history or RevenueCat purchase records. Manage subscriptions through Apple and send privacy or deletion requests privately to andphoto.co@gmail.com. Do not post receipts or transaction identifiers in public issues.

Changes

This policy describes the Firebase Analytics events and RevenueCat purchase processing in version 1.20 and later. Other future changes will be documented here before activation.

Contact

Privacy questions or deletion requests: andphoto.co@gmail.com. Do not post receipts or transaction identifiers in public issues.