Legal transparency
Sub-processors
Kitrus uses infrastructure, AI, billing, analytics, and optional integration providers to operate the service. This page lists providers that may process personal data for Kitrus and the boundaries we apply to each one.
DRAFT — final wording review before live
Provider roles describe the implemented service paths, including optional paths. Agreement assumptions are identified below and still need account-specific confirmation. This draft does not certify signed agreements, permission to process health data, or provider retention settings.
Last updated: October 23, 2026
Core service providers
| Provider | Role | Data processed | Boundary |
|---|---|---|---|
| Supabase | Database, authentication, and file storage | Account data, user-entered health data, uploads, chat records, causal maps, and audit records | Durable system of record with row-level security and server-side ownership checks. Draft assumption: agreement coverage applies to the operating entity and projects; account-specific terms and any required health-data arrangements remain unverified. |
| OpenRouter | AI gateway for Ask, analysis, extraction, report narration, and service-quality analysis | Selected health context, chat messages, uploaded document content, and generated health-analysis outputs | Requests exclude model endpoints that collect prompts for storage or training. |
| Answering model provider (for example OpenAI, Anthropic, or Google) | Model inference selected through OpenRouter; a configured direct OpenAI route may also be used | The selected context and content needed to answer | Provider identity and retention can vary by request; no universal 30-day deletion claim applies. Draft assumption: terms cover each selected gateway, provider, account and endpoint; that coverage remains unverified. |
| OpenAI (direct voice transcription) | Transcribes voice recordings when a direct OpenAI route is configured | Voice recordings | OpenRouter does not receive voice recordings for transcription. Draft assumption: direct OpenAI terms cover the configured account and transcription endpoint; coverage and retention controls remain unverified. No Zero Data Retention guarantee is made. |
| Vercel | Application hosting, serverless runtime, cron, logs, and performance analytics | Application requests, including health content processed in server functions, coarse runtime metadata, and redacted operational logs | Kitrus policy forbids PHI in logs. Draft assumption: terms cover the operating team, plan and services; account-specific coverage and any required health-data arrangements remain unverified. |
| Customer.io | Transactional and lifecycle email | Email address, account identifiers, and coarse lifecycle events | Health details must not be sent in lifecycle or marketing payloads. |
| Sentry | Error and performance monitoring | Redacted error context, stack traces, route categories, and user ids where needed for debugging | PHI scrubbers run across client, server, and edge telemetry. |
Billing and app-store providers
| Provider | Role | Data processed | Boundary |
|---|---|---|---|
| RevenueCat | Native iOS and Android subscription adapter | App user identifiers, receipts, product ids, and subscription state | No health data is intentionally sent. Draft assumption: subscription processing is covered by the applicable account agreement; account-specific acceptance and terms remain unverified. |
| Whop | Web checkout and web subscription lifecycle | Billing identity, email, plan id, membership, payment, refund, and cancellation state | No health data is intentionally sent. Draft assumption: applicable terms cover the web billing relationship; account-specific processing roles and contractual coverage remain under final review. |
| Apple and Google | App distribution, app-store billing, Sign in with Apple/Google, HealthKit or Health Connect where authorized | Store account, receipt, sign-in, device, and user-authorized health-source data depending on the feature used | Health-source access is controlled by the user through the operating system permissions screen. |
Analytics and attribution providers
| Provider | Role | Data processed | Boundary |
|---|---|---|---|
| Google Analytics / GA4 | Site and campaign measurement | Coarse page, conversion, and device-event metadata | No biomarkers, medications, symptoms, lab values, uploads, or chat content. |
| TikTok | Ad attribution and conversion measurement | Coarse conversion events and click identifiers when enabled | Marketing payloads must not include health data. |
| Ad attribution and conversion measurement | Coarse conversion events and click identifiers when enabled | Marketing payloads must not include health data. | |
| PropellerAds | Telegram Mini App campaign attribution where enabled | Coarse attribution and conversion metadata | Marketing payloads must not include health data. |
Optional integrations and inactive fallback providers
- Oura
- WHOOP
- Fitbit
- Withings
- Telegram
- PayPal
Tavily — inactive web-search fallback. This search provider is currently inactive. Draft assumption: any future use would send deidentified research queries and receive public search results. Applicable account terms, data handling and approval must be reviewed before reactivation; inactive status does not establish historical compliance.
Optional integrations process data only when you connect or use that feature. Inactive fallback providers do not receive production data unless Kitrus deliberately re-enables that path.
Change notices
Sub-processor change notices
Signed-in users can subscribe to email notices before Kitrus adds a new sub-processor that materially changes how personal data is processed.
Checking your preference...
Questions or objections
Contact hello@kitrus.ai for privacy questions. See the Privacy Policy for the full description of data rights, retention, international transfers, and user controls.