Skip to main content

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

Kitrus does not sell personal data. Marketing and analytics providers must not receive health details such as lab values, medications, symptoms, diagnoses, uploads, or chat content.

Core service providers

ProviderRoleData processedBoundary
SupabaseDatabase, authentication, and file storageAccount data, user-entered health data, uploads, chat records, causal maps, and audit recordsDurable 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.
OpenRouterAI gateway for Ask, analysis, extraction, report narration, and service-quality analysisSelected health context, chat messages, uploaded document content, and generated health-analysis outputsRequests 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 usedThe selected context and content needed to answerProvider 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 configuredVoice recordingsOpenRouter 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.
VercelApplication hosting, serverless runtime, cron, logs, and performance analyticsApplication requests, including health content processed in server functions, coarse runtime metadata, and redacted operational logsKitrus 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.ioTransactional and lifecycle emailEmail address, account identifiers, and coarse lifecycle eventsHealth details must not be sent in lifecycle or marketing payloads.
SentryError and performance monitoringRedacted error context, stack traces, route categories, and user ids where needed for debuggingPHI scrubbers run across client, server, and edge telemetry.

Billing and app-store providers

ProviderRoleData processedBoundary
RevenueCatNative iOS and Android subscription adapterApp user identifiers, receipts, product ids, and subscription stateNo health data is intentionally sent. Draft assumption: subscription processing is covered by the applicable account agreement; account-specific acceptance and terms remain unverified.
WhopWeb checkout and web subscription lifecycleBilling identity, email, plan id, membership, payment, refund, and cancellation stateNo 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 GoogleApp distribution, app-store billing, Sign in with Apple/Google, HealthKit or Health Connect where authorizedStore account, receipt, sign-in, device, and user-authorized health-source data depending on the feature usedHealth-source access is controlled by the user through the operating system permissions screen.

Analytics and attribution providers

ProviderRoleData processedBoundary
Google Analytics / GA4Site and campaign measurementCoarse page, conversion, and device-event metadataNo biomarkers, medications, symptoms, lab values, uploads, or chat content.
TikTokAd attribution and conversion measurementCoarse conversion events and click identifiers when enabledMarketing payloads must not include health data.
PinterestAd attribution and conversion measurementCoarse conversion events and click identifiers when enabledMarketing payloads must not include health data.
PropellerAdsTelegram Mini App campaign attribution where enabledCoarse attribution and conversion metadataMarketing 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.