Overview

This policy describes Treeish for macOS, developed by Sergii Khliustin (ioapps). Treeish is a Git client that works with repositories you choose. A Treeish account is not required for local repository workflows.

Repository data stays on your device

Treeish reads and changes selected repository files and Git metadata to perform the operations you request. This may include source code, file paths, commit messages, branch names, and commit author names and email addresses. Treeish does not intentionally send repository contents, Git credentials, commit messages, or custom Git-operation events to ioapps as telemetry. Standard crash reports may contain runtime or exception metadata; please see the diagnostics section below.

Git commits can contain your configured name and email address. When you push commits, their contents and metadata are sent to the remote Git server you selected and may be visible to people who have access to that repository.

Local app data and recovery

Treeish stores app preferences, repository references, permission bookmarks, window state, and supported operation history locally on your Mac. Supported recovery workflows may also create local patches or other recovery artifacts containing repository changes. These records and artifacts are not uploaded to ioapps.

Remote Git services and authentication

Clone, fetch, pull, and push communicate with the Git servers configured for your repositories. Automatic fetch may also contact a configured remote when that feature is enabled. Those servers receive the information needed for the operation and handle it under their own privacy policies.

Authentication follows your Git configuration and the selected server’s requirements. Git credential helpers may store credentials according to their own settings. Password or token responses entered through Treeish’s authentication prompt are transient; Treeish does not persist these responses or send them to ioapps.

Links opened from Treeish in a web browser are handled by the destination website. App Store downloads, updates, and any diagnostics you share with Apple are handled by Apple under its policies and your system settings.

Usage analytics and crash diagnostics

The release app uses Google Firebase Analytics and Firebase Crashlytics. Collection is enabled automatically to help us understand app use and investigate crashes. Analytics measures standard app lifecycle and session events and includes a generated app-instance identifier, app and device information, operating-system information, and approximate country information derived by the service from a masked IP address. Treeish does not use Apple location services for this purpose.

Crashlytics collects crash reports, stack traces, exception or runtime metadata, app and operating-system information, and diagnostic identifiers. Standard Analytics events may appear as crash breadcrumbs. Treeish does not set an account identifier, custom user properties, or custom repository-related events in these services. Crash and exception metadata can nevertheless contain information about the running process; we do not promise that every crash report is free of paths or other incidental runtime details.

These services process data for ioapps through Google Firebase. Data is kept according to the Firebase and Google Analytics project settings and provider policies. You can contact us with privacy questions or requests. The current version does not provide an in-app switch for Analytics or Crashlytics.

Treeish does not contain ads. Advertising identifiers and Apple IDFV collection are disabled, and advertising-storage, advertising-user-data, and advertising-personalization consent are denied in the app. We do not use this telemetry for cross-app advertising tracking.

Information you send to support

If you contact us by email, we receive your email address, message, and any attachments you choose to send. We use this information to respond to your request and investigate the issue. Please remove credentials and private repository content before sending logs, screenshots, or files. Support information is kept only as needed to handle your request and any related obligations; you can contact us to request deletion.

Your choices

You choose the repositories Treeish can access and the remote services they use. You can change automatic fetch preferences in the app and manage access through macOS settings. Removing a repository from Treeish’s library does not delete the repository’s files or its Git history. Manage those files, remote data, and credentials through the relevant file system, Git service, or credential helper. Contact us if you need help locating local Treeish data.

Changes to this policy

We will update this page and its date when Treeish’s data practices change. Data collection is described here and reflected in the App Store privacy information.