@@ -40,18 +40,15 @@ go—and, importantly, where they don't.
4040 We retain telemetry only as long as needed for product analytics and debugging.
4141 Telemetry does ** not** collect your code or AI prompts, and you can opt out at
4242 any time through the settings.
43- - ** Zoo Code Observability (All Authenticated Users ):** If you sign in to
44- Zoo Code, Zoo Code will send LLM usage telemetry to the Zoo Code backend
45- (zoocode.dev). This includes task ID, AI provider name, model name, token
46- counts (input/output/cache), and estimated cost. This data is linked to your
47- authenticated Zoo Code account and is retained for up to 90 days as
48- metadata-only API request logs , as described in the
43+ - ** Zoo Gateway usage logs (Zoo Gateway only ):** The extension does ** not **
44+ send LLM usage telemetry to zoocode.dev for bring-your-own-key (BYOK)
45+ providers. If you choose ** Zoo Gateway ** as your AI provider while signed in,
46+ your requests are processed through zoocode.dev and we record metadata-only
47+ API request logs on our servers (model used, token counts, timestamps,
48+ estimated cost) for billing and dashboard analytics , as described in the
4949 [ zoocode.dev Privacy Policy] ( https://www.zoocode.dev/legal/privacy ) . Free
50- plan users can view their telemetry in the dashboard for the most recent 7
51- days; Pro and higher plan users can view the full 90-day window. You can
52- stop this collection at any time by signing out via the Zoo Code badge in
53- the chat area, and you may request deletion of your data at any time per
54- the privacy policy.
50+ plan users can view gateway usage in the dashboard for the most recent 7
51+ days; Pro and higher plan users can view the full retention window.
5552- ** Marketplace Requests** : When you browse or search the Marketplace for Model
5653 Configuration Profiles (MCPs) or Custom Modes, Zoo Code makes a secure API
5754 call to Zoo Code's backend servers to retrieve listing information. These
0 commit comments