Summary
Cloudflare and Supabase support core delivery and account data. Firebase supports analytics, crash reporting, and notifications. AI, search, and payment providers process data only when the corresponding route is used or enabled.
Core service providers
| Provider | Purpose | Data involved |
|---|---|---|
| Cloudflare | CDN, static site, Workers/API execution, network protection, observability, image or workflow services | Requests, IP and device metadata, API payloads, operational logs, generated images when used |
| Supabase | Authentication, Postgres database, sessions, workspace data, row-level access controls | Account identity, sessions, memberships, workspace content, settings, usage, billing and request records |
| Google Firebase / Google Analytics | Web and mobile analytics, Crashlytics, Cloud Messaging | App and device identifiers, page and feature events, crash diagnostics, push tokens, platform and locale |
AI providers
| Provider or route | When used | Data involved |
|---|---|---|
| OpenAI or OpenAI-compatible endpoint | As the verified platform AI endpoint, or when an eligible account configures it in LabRat Local | Prompts, selected workspace context, source material, model settings, generated output |
| Anthropic Claude | Only when independently connected through an eligible LabRat Local configuration | Prompts, selected workspace context, source material, model settings, generated output |
| Google Gemini | Only when independently connected through an eligible LabRat Local configuration | Prompts, selected workspace context, source material, model settings, generated output |
| Local Runtime provider | When the user selects a model running on an authorized device or local endpoint | Prompt and selected context on the device; returned output is sent to the cloud workspace |
The operator of a custom OpenAI-compatible endpoint is determined by the endpoint chosen by the user. LabRat cannot list or control an independently configured provider.
Web-search providers
| Provider | When used | Data involved |
|---|---|---|
| AI provider native search | When the selected model and account support native web search | Search prompt, relevant workspace context, source results and citations |
| You.com | When a workspace configures and selects You.com search | Search queries, necessary context, returned results and URLs |
| Tavily | When a workspace configures and selects Tavily search | Search queries, necessary context, returned results and URLs |
Payment provider
| Provider | When used | Data involved |
|---|---|---|
| Paddle | Only when Paddle checkout or subscription management is enabled and selected | Billing contact, plan, checkout, transaction and subscription identifiers; payment details are handled by Paddle |
Changes and questions
Providers may change as LabRat adds features, replaces infrastructure, or enables a payment route. This page will be updated before or when a new material provider begins processing customer data, as appropriate. Business customers whose agreement incorporates the DPA receive the material-core-provider notice and objection process described there.