LeafPort

Privacy Policy

Last updated: June 5, 2026

LeafPort is designed to move ebooks from your Android device to your e-reader using local device storage access.

Personal Data

LeafPort does not ask for an account and does not collect ebook titles, filenames, folder paths, book contents, author names, or reading data.

Local Ebook Processing

All ebook scanning, conversion, and transfer work occurs locally on your device.

LeafPort does not upload your books to external servers.

LeafPort does not send ebook titles, filenames, folder paths, book contents, author names, or reading data to external services.

Storage Access

LeafPort uses Android's Storage Access Framework so you can grant access to selected local folders and connected e-reader storage.

Those permissions are used only to scan supported ebook files and copy or delete files when you choose those actions.

Analytics

Public builds of LeafPort use Firebase Analytics to understand whether users can successfully connect an e-reader and complete transfers.

Analytics are limited to coarse events such as folder selected, device connected, destination authorized, transfer started, transfer completed, and transfer failed.

Analytics may include coarse properties such as book count, file format family, device type bucket, and failure phase. LeafPort disables Firebase Advertising ID collection and ad-personalization signals.

Public builds also use Firebase Crashlytics for crash reports. Crash reports may include technical diagnostics such as app version, device model, operating system version, and stack traces. LeafPort does not add ebook titles, filenames, folder paths, book contents, author names, or reading data to crash reports.

Contact

For privacy questions, contact Mammutträd Labs at mammuttradlabs@gmail.com.