LogKitty

Privacy Policy

Last updated: June 23, 2026

LogKitty (“the app”) is an on-device Android log viewer. It overlays the system logcat output so you can read your device’s logs in real time. This policy explains what data the app accesses, what stays on your device, and the limited cases where data leaves it.

The short version: LogKitty has no account system, no analytics, and no servers of its own. Your logs are read and shown locally and are never uploaded by the app. The only data that can leave your device comes from third‑party components (downloadable fonts) and from optional features you trigger yourself, all described below.

Who is responsible

LogKitty is developed by HereLiesAz. For any privacy question or request, contact: hereliesaz@gmail.com.

Data the app accesses on your device

LogKitty reads several kinds of data locally, on your device, in order to function. None of it is collected by the developer or sent to a LogKitty server (there is no LogKitty server).

• System logs (READ_LOGS). The app reads the device logcat stream and displays it. Logs are generated by the operating system and other apps and may incidentally contain personal information (e.g. identifiers, content, or errors that other apps write to the log). LogKitty keeps the log only in memory (and a bounded in‑memory buffer you can size in Settings) for display. It does not transmit the log anywhere on its own.
• Installed app information. Used to let you pick an app to monitor and to classify log sources (user / system / Play Store / category). LogKitty does not request the broad QUERY_ALL_PACKAGES permission: it sees launchable apps via a scoped <queries> launcher filter, and on rooted devices lists the rest via pm list packages. This lookup happens on‑device and is not transmitted.
• Usage access (PACKAGE_USAGE_STATS). Used, where available, to identify the foreground app for context filtering and, in the optional Developer Stats module, to read per‑app network usage. Processed on‑device only.
• App preferences. Your settings (colors, font, filters, monitored apps, prohibited tags, etc.) are stored locally in the app’s private storage.

Permissions and why they are used

Permission	Purpose
READ_LOGS	Read the system log to display it (granted via ADB or root).
SYSTEM_ALERT_WINDOW	Draw the floating log overlay over other apps.
FOREGROUND_SERVICE / FOREGROUND_SERVICE_SPECIAL_USE	Keep the log capture running with a persistent notification.
POST_NOTIFICATIONS	Show the persistent silent control notification.
PACKAGE_USAGE_STATS	Detect the foreground app for context filtering; read per‑app network usage in the Developer Stats module.
INTERNET	Required by the components below (fonts, GitHub Actions, optional crash reporting).

You can review the live grant status of these permissions in Settings → Permissions.

When data leaves your device

LogKitty itself does not upload your logs. Data leaves the device only in these cases:

Fonts (Google Fonts)

Code fonts are fetched on demand from Google’s downloadable‑fonts provider. When a font is requested, the request is handled by Google Play services and is subject to Google’s privacy policy (linked above). No LogKitty user data is attached to these requests.

GitHub Actions (optional, only if you configure it)

If you use the optional GitHub Actions feature, the app talks to the GitHub REST API (api.github.com) to show workflow runs, jobs, and logs for the repository you configure. To do this you provide a Personal Access Token (PAT), which is stored encrypted on your device (Android Keystore, AES/GCM) in a backup‑excluded store — it is never included in settings backups/exports and is sent only to GitHub to authenticate your own requests.

On‑demand feature modules

Developer Stats and GitHub Actions ship as optional modules downloaded from Google Play the first time you use them. Fetching a module is a request to Google Play, governed by Google’s privacy policy (linked above).

Saving or sharing logs (only when you choose to)

If you explicitly save, copy, or export logs or preferences, that content goes wherever you send it (a file you pick, the clipboard, or another app you share to). This only happens on your action.

Crash reports (optional, build‑dependent)

Some builds can file a crash report to the project’s issue tracker to help fix bugs. A report contains the exception type and message, the stack trace, and basic device metadata (Android version, SDK level, device manufacturer and model) — it does not include logcat or any of the log content you were viewing. The report is stored locally and only uploaded if the build was configured with a reporting token; if it is not configured, no crash data is sent.

Data retention

LogKitty does not retain your logs after they leave the in‑memory buffer or the app is stopped. Preferences persist locally until you clear them or uninstall the app. The developer does not store any of your data, because none is sent to the developer.

Children’s privacy

LogKitty is a developer/debugging utility and is not directed at children.

Your choices

• Revoke any permission in the Android system settings at any time; the related feature will stop working but the rest of the app continues.
• Uninstalling the app removes all locally stored preferences.

Changes to this policy

This policy may be updated as the app changes. Material changes will be reflected by updating the “Last updated” date above and committing the revised policy to the project repository: https://github.com/HereLiesAz/LogKitty

The current policy is published at https://hereliesaz.github.io/LogKitty/privacy/.

Contact

Questions or requests: hereliesaz@gmail.com

This site is open source. Improve this page.