What information does SinceTag collect and why

Repository data

Repository names, paths, tags, commit messages, task text, categories, and GitHub credentials are used only on your Mac. SinceTag does not send this content to the analytics service. GitHub credentials are stored in the macOS Keychain.

Diagnostics and analytics

SinceTag sends static screen names, static action names, app launches, app version and build, macOS version, Mac model, preferred language, and display size to my self-hosted Umami analytics service. No repository content, action values, identifiers from your repositories, or custom event properties are sent.

When a handled error or a crash happens, SinceTag also sends a static error name together with the error’s type, domain, and numeric code. It never sends error messages, stack traces, file paths, or repository content.

The analytics client uses a random visitor identifier that stays in memory and changes at least daily. Static analytics events may be stored temporarily in a size-limited queue in Application Support while waiting to be sent. The network request includes an IP address, which Umami uses to derive coarse location.

Analytics helps me understand which parts of SinceTag are used. Umami runs on Fly.io and stores analytics in Supabase. I do not currently set an automatic deletion period. The data is not used for advertising, sold, or used to track you across apps or websites. Because none of it can be linked to you, I cannot locate or delete the data of any single person. Deleting the app stops any future collection. For privacy questions, email me at runar@hjerpbakk.com.