Workspace data stays on your host.

01Scope

Who provides the extension

Ameyon Labs Inc., based in Edmonton, Alberta, Canada, develops BranchHarbor. This policy covers the extension. The website privacy policy covers visits to ameyonlabs.com.

02Information used

Repository and feature records

The extension reads repository locations, Git metadata, branch and revision information, worktree registrations, and file status to create, reopen, and check feature worktrees. Git checks out repository files into new worktrees.

• Repository catalog: repository names, local or remote-host paths, Git common-directory paths, internal identifiers, and Common or Optional selections.
• Feature records: the feature name, selected repositories, branch names, starting revisions, storage paths, creation time, operation status, and errors. Errors may contain file paths or Git diagnostic text.
• Generated files: Git worktrees containing checked-out repository content and .code-workspace files containing folder references and a window-title setting.
• Operation lock: a temporary record of the host name, process ID, and operation start time, used to prevent conflicting operations. An interrupted process can leave this file behind.

03Storage

On the machine running the workspace

The catalog is stored as a JSON file in the extension’s VS Code global storage. Worktrees and workspace files default to a workspaces folder there, or a folder you choose with Choose Worktree Storage Folder. Changing that folder affects new features only. The catalog is not registered for VS Code Settings Sync.

With Remote SSH or a development container, the extension runs on that workspace host and stores files there, not necessarily on your desktop. Host administrators, filesystem permissions, backup tools, and any synchronization you configure can affect access to these files. The extension does not add its own encryption or cloud backup.

04Collection and network access

No developer-operated data service

Version 0.1.0 has no account system, backend connection, telemetry, analytics, advertising, or crash-reporting integration. The extension itself does not send repository contents, catalog records, or usage data to Ameyon Labs or another service.

Managed Git commands disable checkout hooks and filesystem-monitor hooks and do not fetch or push. However, Git content filters configured on your machine, such as an installed Git LFS filter, may run other programs or use the network. Only use repositories and Git configuration you trust. Other extensions, VS Code, remote-host services, and the Visual Studio Marketplace operate independently under their own settings and policies.

05Retention and removal

You control the files

Catalog and feature records remain on the workspace host until removed. Manage Repositories → Forget repository removes that catalog entry only; existing feature records and files remain. Remove Feature Worktrees removes eligible clean worktrees and, on successful completion, their feature record. Git branches and commits remain. Saved workspace files and extra files in the feature folder are deliberately preserved.

After preserving your work and removing managed worktrees through the extension, you can remove remaining workspace files and extension storage yourself. Do not delete a catalog or worktree directory as a substitute for Git-aware cleanup. Uninstalling the extension is not a guarantee that all generated files or backups are removed. Contact support if you need help locating the correct storage. Ameyon Labs cannot remotely access or delete these local or remote-host files.

06Support

Information you choose to send

If you email us, we receive your email address and the message, attachments, and diagnostics you provide. We use that information to respond and handle the related support correspondence. Support information is separate from the extension’s local catalog. Redact secrets, access tokens, proprietary source, personal information, and confidential repository names or paths before sharing a report. Ask us about access to or deletion of support correspondence using the contact below.

07Policy changes

Keep this policy aligned with the extension

We will update this page when the extension’s information practices change. The effective date identifies this version. Consult the policy and license supplied with the version you install.

08Contact

Privacy questions