Q, Hive, and HiveMind are designed to run inside your own cloud account, against your own repos and CI. Here is exactly what that means, what data moves where, and what never leaves your environment.
What lives in your infrastructure. What touches Hiventiq's cloud. Nothing more.
| Data type | Your infrastructure | Hiventiq cloud |
|---|---|---|
| Source code | ✓ | No |
| Tickets / requirements | ✓ | No |
| Pull requests | ✓ | No |
| HiveMind recall data | ✓ | No |
| License validation | N/A | ✓ |
Telemetry, where enabled, is limited to anonymous product-health signals and never includes source code, ticket content, or recall data.
Two halves, separated by intent. The left half handles your work. The right half handles the business of running the software.
Your code, tickets, and recall data never cross the wire to Hiventiq. License validation crosses the wire with a license key and account identifier — nothing about your codebase.
Q and Hive call the LLM providers you configure. This is your choice, made explicit in setup, not a default we pick for you.
You choose where agent requests go — Anthropic, OpenAI, or another provider you configure. Your API key lives in your own environment and the request goes directly to the provider you picked. Hiventiq is not in the path. We do not proxy, log, or see the request.
This mirrors how Bzz handles optional AI rewrite — the model call is yours to route, not ours to intercept.
Because Q, Hive, and HiveMind run inside your own infrastructure, your source code and ticket data never leave your environment to reach Hiventiq. That reduces the surface area your compliance program has to cover.
What that means in practice:
Important. Hiventiq does not currently sign Business Associate Agreements or equivalent regulated-data agreements. Customers remain responsible for their own compliance programs, including access controls, audit logging, and any third-party AI providers they choose to configure with Q, Hive, or HiveMind.
If you're evaluating Q for a team with specific infrastructure or compliance requirements, we'd rather have a direct conversation than send you to a generic FAQ.
