Privacy Policy — Branches for Vault

1. What we do NOT send to third parties

Branches for Vault is an on-premise, in-Vault tool. It does not transmit your design files, file contents, geometry, properties, or branch data to Avant Leap or any third-party service at runtime. All branch, diff, and merge operations happen between the Vault Client and your own Vault server.

There is no telemetry, no analytics, and no cloud component in the core product.

2. What the product stores, and where

• Branch metadata (registry): stored inside your Vault at $/Branches/_bfv/registry.json — i.e., on your own server, under your own Vault permissions and backups.
• Local cache + logs: a registry cache, an audit trail (audit.jsonl), and a debug log (debug.log) are written to %ProgramData%\AvantLeap\BranchesForVault\ on the local machine. These contain operation metadata (file names, versions, actions, timestamps, user name) — not file contents. They never leave the machine.
• Lineage properties (UDPs): written onto branched files inside your Vault.

3. Licensing

If a license activation mechanism is enabled, the product may transmit a license token and a machine identifier to the Avant Leap license service over HTTPS solely to validate entitlement. No design data is included in that request.

4. Data retention and deletion

All product data lives either in your Vault or in the local %ProgramData% folder. You control retention and deletion entirely; removing the add-in and that folder removes all local data. Branches created in Vault remain as ordinary Vault folders/files under your control.

5. Contact

Questions about this policy: privacy@avantleap.com