Privacy notice
Local data, optional browser analytics and your choices in Bee Team.
Who this notice concerns
This notice describes the official Bee Team website and browser interface maintained by Philippe Ferreira Assis Tecnologia da Informação LTDA, trade name Philtech, CNPJ 59.845.514/0001-90. Contact us about privacy at beeteam@runvibe.dev.
Independent forks, separately operated instances and third-party harnesses may have different practices. Check the notices of the operator and providers you choose.
Your work data and the local service
By default, the Bee Team service stores task and team records locally in SQLite. You can configure another supported database, backups or exports. The browser reads and updates that service through the API, and your harness may access it through MCP according to your setup.
Task text, plans, comments, chats, attachments and other authored content are not analytics inputs. Using a local service does not by itself upload its database to the official website. What a connected harness or model provider receives depends on the permissions and service you use; consult that provider's privacy notice.
Requests needed to deliver the interface
Opening the hosted website sends ordinary requests to its hosting infrastructure, including Cloudflare. Such requests expose network information such as your IP address, browser information and the requested resource to the receiving infrastructure. Installation can also request release metadata and packages from GitHub. These delivery requests are separate from optional Google Analytics.
A locally served interface reads its own local service. Loading the public website, an external link or a download still contacts that destination. Local storage does not make every network request private or anonymous.
Optional Google Analytics
If you accept analytics, the browser interface can send basic usage measurements to Google Analytics to help us understand which product areas are used and improve Bee Team. This applies to the hosted interface and to a locally served browser interface when you opt in there. Starting only the native API or MCP service does not load browser analytics or report its startup to Google Analytics.
Measurement uses an isolated, static frame rather than giving Google Analytics access to the app's task views or navigation history. Only approved screen categories and basic interface events are supplied to that frame. The tracking configuration excludes authored content, private route identifiers and query strings.
- No task titles, specifications, plans, comments, chats or attachment contents are sent as analytics parameters.
- No team, agent or task names, private slugs, search text or full application URLs are supplied as analytics parameters.
- Google may receive device/browser information and identifiers used by its tag, as well as network information needed to process the request. This notice does not describe those requests as anonymous.
Accept, refuse or change your choice
Analytics is off until you choose to accept it. You can reject analytics and continue using Bee Team. You can reopen Analytics preferences to change your choice or withdraw consent. Refusing or withdrawing consent prevents further optional measurement from that interface; it does not automatically erase data that Google already received.
Your browser stores the versioned consent choice for the origin where you made it. The public website and a local address have separate choices; changing browsers, using another origin or clearing browser storage may require choosing again. A material change to what the consent covers requires a new choice.
The browser also stores functional preferences such as language and theme. If analytics is enabled, Google's tag may use cookies or similar identifiers for measurement. Our tag requests measurement cookies on metrics.getbee.team with an expiry of up to 180 days, without extending that expiry on each visit; your browser may shorten or block them. This cookie lifetime does not define how long Google retains previously received events. Advertising storage, advertising personalization and Google Signals are disabled in our tag configuration. Rejecting analytics does not disable functional preference storage.
Google's processing
Google processes the analytics requests it receives under its applicable service and privacy terms, and processing may take place outside your country. Google explains the information used by Analytics and the choices available to users in its own documentation. Optional consent here applies to Bee Team's browser measurement, not to every Google service you may use.
Retention and control
You control the local Bee Team records and backups held in your installation or configured database. Deleting browser storage does not delete that database. Data received by hosting providers or Google follows the applicable service settings and processing arrangements; this notice does not promise a particular retention period or automatic deletion of all prior requests.
You can contact beeteam@runvibe.dev to ask about the applicable retention settings or request information about data held by the official operator. Include only the information necessary to explain your request, and do not send task content, secrets or credentials unless a suitable secure channel has been agreed.
Questions and privacy requests
Where applicable, you may request confirmation of processing, access, correction, information about sharing or deletion of personal data, and withdraw consent. Contact beeteam@runvibe.dev so the operator can assess your request and any identity information reasonably needed to handle it. Public GitHub issues are not a private channel for personal or confidential information.
The date above identifies this version of the notice. Review the updated notice when the service or its measurement practices change.