Plain language. No hedging. What we do and don't do with your information.
Most privacy policies are written for lawyers. This isn't one. This is what we actually believe and how we actually operate.
The organizational knowledge inside your Hive is one of the most sensitive things you entrust to any software platform. It reflects your strategy, your decisions, the way your team thinks and works. We take that seriously, not as a compliance matter, but as the foundation of any honest relationship between us.
Below is exactly where we stand. No exceptions hidden in footnotes.
The work your team creates inside HiveBoss (your messages, your Bee outputs, your context graph, your Marching Orders) is yours. We do not read it, scan it for insights, or mine it for any purpose. HiveBoss processes your content to run the platform on your behalf. That is not the same as reading it. We don't.
Your data is not a product. Full stop. We do not sell it, license it, package it for advertisers, or share it with third parties for their commercial use. Our business model is subscription revenue. Your data is never part of what we sell.
Your organizational knowledge (the context graph you build, the Marching Orders you write, the HiveReports your Bees generate) is never used to train AI models, including our own. What's yours stays yours, and it doesn't become someone else's model weights.
Every Bee runs from versioned Marching Orders you can read and edit. Every task produces a HiveReport: what was requested, what was done, what it cost, what was learned. Every Honey transaction is logged. You can audit everything your AI has done at any time.
Your data is encrypted in transit and at rest. Access controls are enforced at the node level in your context graph, the same permission model your team sets is the permission model we enforce. We do not share your data between organizations.
You can export your context graph, your HiveReports, and your account data at any time. If you close your account, your data is deleted. We don't hold it as a hedge or an asset. It leaves when you do.
We receive requests for user information from time to time. Our position is simple: we require a signed legal warrant before we will disclose any user content or account data to any government or law enforcement entity.
A request is not a warrant. A subpoena is not a warrant. We will challenge legally challengeable demands. A warrant (signed, issued by a court of competent jurisdiction, meeting all legal requirements) is what it takes.
When we receive a valid warrant and are legally permitted to notify you, we will tell you before we comply, so you have the opportunity to seek legal counsel. If we are legally prohibited from notifying you, we will comply with the warrant and note that notification was legally restricted.
We do not have a back door. We do not participate in bulk data collection programs. We are not in the business of making law enforcement's job easier at the cost of your privacy.
HiveBoss routes work through AI providers (including Anthropic's Claude API and others). When a Bee runs, content from your context graph may be sent to those providers as part of the request. Those providers have their own privacy policies, which govern how they handle that content.
We choose providers whose API data-handling policies do not allow training on API inputs by default. We will always be transparent about which providers your Bees use and what their policies are. If you bring your own API key (BYOK), the provider relationship is directly between you and them.
We use cookies and session data to run the platform: to keep you logged in, to route you to the right Hive, to remember your preferences. We use aggregate, anonymized analytics to understand how the product is being used so we can improve it. We do not use third-party advertising trackers. We do not build behavioral profiles for sale.
If you have a question about how we handle your data that isn't answered here, ask us. We will answer. Privacy questions: privacy@hiveboss.ai. Legal requests should be directed to our registered legal address, available at that same address.
This document is not the full legal Privacy Policy, which governs our relationship with you in the event of a legal dispute. This is what we actually believe and practice. Both are true.