Privacy summary · launch draft

Collect less. Keep it bounded.

This summary describes the intended first-release data boundary and must receive final legal review before live commerce is enabled. Public checkout currently uses Stripe test mode and creates no real charge.

Open-source downloads

No account is required. ldgr does not phone home to validate a license. Aggregate site analytics are cookieless and exclude repository URLs, identity data, license IDs, and demo findings.

Demo sessions

The demo accepts public repositories only. A disposable checkout and result workspace are retained for the active session and deleted two hours after completion. Qualifying cache entries for well-known public repositories may be retained for up to 30 days without reuse, keyed to an exact commit.

Accounts and purchases

When commerce is enabled, Google identity, Stripe customer references, entitlements, and audit records are stored server-side. Signed license files contain opaque customer and license IDs rather than email addresses.

Experience donation

Experience donation is separate and disabled by default. LDGR instructs agents to remove credentials, secrets, and PII before writing ledger records. After explicit opt-in, Core sends only those model-sanitized LDGR work records. Direct Pi conversations, prompts, tool events, reasoning, images, and sessions are not donated. Disablement stops future capture and deletes unsent work episodes.

Launch notifications

Email is used only for the adapter notifications selected at signup. Consent records include the selected products, time, and policy version. Every notification includes an unsubscribe path.

Contact

contact@hydradynamix.com · HYDRA DYNAMIX INC. · Vancouver, British Columbia, Canada.