Selected folders
Commitick
Privacy
Commitick Privacy
Last updated: June 2, 2026
This page explains how Commitick handles selected folders, local snapshot records, configured Git remotes, support email, and diagnostics.
Privacy
How Commitick handles project data
Commitick is designed around local folder access, local snapshot history, and user-controlled Git remotes.
Folder access
macOS permissions may be required.
Commitick may need folder access permission to monitor selected folders. If access changes, the app may ask you to reselect a folder.Local records
Project status and rules may be stored locally.
Commitick may keep local app records for selected folders, monitoring state, rules, ignore settings, snapshot state, and project status.Snapshots
Snapshot history is Commitick-managed.
Commitick keeps source-folder work separate from Commitick-managed snapshot history and does not rewrite your source working tree during normal monitoring.Source privacy
No Commitick-operated source upload.
Source files and diffs are not uploaded to Commitick-operated services. Commitick does not require you to send source code to Hazybyte Studio for normal monitoring.Push
Configured Git remotes are your choice.
If you choose to push, snapshot history goes to the Git remote you configure. That remote is governed by the provider, account, and access settings you choose.Support email
You decide what to send.
The support page prepares an email in your email app. Include only the details needed to understand the issue, and do not attach private source files unless support asks later.Diagnostics
Share intentionally.
Diagnostics or logs, if requested, should avoid private code, private diffs, sensitive file paths, and full folder listings unless you intentionally choose to send them.Choices
Privacy questions
For privacy questions about Commitick, use support or email Hazybyte Studio directly.