Last updated
Privacy policy
TinyPrune is an open-source project maintained by Mihir Khandekar in Singapore. This policy explains the supported macOS app and this website. The distinction matters: the app has no telemetry, while the homepage uses third-party analytics.
- The app: local cleanup, no account, no app telemetry.
- Update checks: on by default, optional in Settings, and use the network.
- The homepage: Google Analytics and PostHog measure visits and interactions.
Data stays local in the app
Core cleanup works without an account or internet access. It reads filesystem metadata, not the contents of your files. TinyPrune does not upload your files, folder inventory, cleanup rules, or activity history to the maintainer and does not include app telemetry.
You choose and authorize managed folders. The macOS app stores security-scoped bookmarks for those grants so its background agent can access the selected locations. Access remains subject to macOS permissions; suggested template folders do not themselves grant access.
Technical detail: what the app stores
To apply and explain your rules, TinyPrune processes names and paths, filesystem identifiers, file types, sizes, timestamps, and project-activity metadata. Its local SQLite database stores managed folders and bookmarks, rules, overrides, observations, scheduled deadlines, and audit events such as cleanup decisions, safety skips, failures, and moves to Trash. On macOS the agent database is stored at ~/Library/Application Support/TinyPrune/state.sqlite3. Preferences are also stored locally, and explicit item overrides can be written as filesystem extended attributes.
Paths and audit details can reveal personal information, including your username, project names, and folder names. Treat database copies, configuration exports, screenshots, and diagnostic output as potentially sensitive. This policy does not promise that removing a rule, removing a folder grant, or uninstalling the app erases all local records.
Cleanup moves eligible items to macOS Trash, rather than permanently deleting them. TinyPrune does not empty Trash. Items remain subject to your actions and macOS Trash settings; TinyPrune is not a backup or a secure-erasure tool. Preview does not move files.
Update checks use the network
Check for new versions is on by default. Turn it off in Settings to stop automatic update checks. You can still request a manual check. Update installation requires your confirmation.
Where requests go
Key-enabled direct-download macOS copies use Sparkle to request the update feed at tinyprune.com/updates/appcast.xml, release notes, and update downloads. Homebrew copies and copies without an update key use the public GitHub Releases API to check for a newer version, then offer a release link or a Homebrew upgrade command. The GitHub notifier sends the app version in its User-Agent header, not your file paths or rules.
These requests reach Cloudflare, which serves this site and its update feed, and GitHub or its download-delivery services when you access releases or downloads. As with other HTTPS requests, the receiving services can process connection information such as your IP address, request time, requested URL, and client headers. These network checks are separate from local cleanup; no app files or cleanup rules are included in them.
Website analytics are separate
The TinyPrune homepage loads Google Analytics and PostHog to measure visits and interactions. Google Analytics uses measurement ID G-EERWCSKWF4. PostHog is configured with the endpoint https://us.i.posthog.com and person_profiles: 'identified_only'; this setting is not a claim that anonymous activity is not collected.
What analytics can collect
The homepage explicitly sends PostHog events for link clicks, including the link label and destination, and for selecting a sample folder in the interactive demo. Analytics services can also collect page and browser information and use cookies or browser storage to recognize visits, subject to their SDK and service settings. Requests to these services expose connection information such as your IP address. The demo uses sample data and never accesses files on your device.
The checked-in website configuration does not explicitly enable or disable PostHog session recording. Provider-side settings are not established by that source, so this policy does not claim that session recording is disabled or specify an analytics retention period. This privacy page itself does not load the analytics scripts.
Your browser controls
You can use browser privacy controls to restrict cookies, clear site storage, or block analytics requests. This is not an in-site consent or opt-out mechanism. For the providers' own practices and controls, see Google's privacy policy, PostHog's privacy policy, and Cloudflare's privacy policy. Their services and policies govern their own processing; no regional-hosting or fixed-retention guarantee is made here.
Support, contact, and information you share
If you open a GitHub issue, you voluntarily share the issue text, attachments, and GitHub profile information with the project and, for public issues, everyone who can view the repository. Review and redact logs, paths, filenames, screenshots, configuration, and database information before sharing. Do not post sensitive information in a public issue.
For privacy questions or requests, contact the maintainer through the project's GitHub issue tracker, initially describing the concern without personal or sensitive details. The maintainer can discuss information shared with the project, but cannot access or erase your local app database remotely. GitHub handles information you share on its platform under GitHub's privacy statement.
Changes to this policy
This policy may change as the app or website changes. The date above identifies the latest revision. Revisions are published on this page, and the open-source repository's page history records changes.