Privacy
The short version is the whole version.
TMEject collects nothing. There is no account, no analytics, no telemetry, and no server of ours for anything to be sent to.
What it does on your Mac
TMEject watches Time Machine’s state — a backup starting, writing, finishing — and when a backup completes successfully, it ejects the drive. All of that happens locally, on your Mac.
It reacts to the state of a backup, never its contents. Nothing inside your backups is read, indexed, or sent anywhere — TMEject treats the drive as a volume to eject, not as files to look at. Your settings live locally on your Mac too.
The one network call
TMEject keeps itself up to date with Sparkle, the standard open-source updater for Mac apps, and that is the app’s only network activity. Periodically it fetches the update feed at dakshgargas.com/apps/tmeject/appcast.xml, and when a new version exists it downloads it from GitHub releases.
The requests go to this site’s host and GitHub’s servers, which see the standard metadata any web request carries — your IP address and a user agent. The app attaches no identifier of yours to either request, because it has none to attach.
That is the whole list. If TMEject is making a network connection, it is checking for an update.
What it never asks for
- No account. There is nothing to sign in to, so it never asks for an email, a name, or anything else about you.
- No analytics or crash reporting of ours. How you use the app is not measured, counted, or phoned home.
- No look inside your backups. It acts on the drive as a whole — eject, verify, retry — and has no business with what’s on it.
Changes
If this policy ever changes, the date at the top changes with it. Should TMEject ever collect anything — it does not today, and there is no plan for it to — we would say so here before it happened, not afterwards.
Getting in touch
Questions about any of this, or anything else about the app: see the support page.