Перейти к содержанию
LEGAL

Sub-processors

Last updated: 2026-08-27

Rapoport Studio uses the following infrastructure sub-processors to deliver its services. Each vendor has an executed Data Processing Agreement (DPA) or equivalent legal instrument. Telegram operates as a joint controller.

VendorServiceData categoryRegionDPA
AnthropicClaude APIAI model inputsUS2026-05-14
CloudflareCDN, Workers runtimeHTTP trafficGlobal / EU2026-05-14
FinExpert SRLSRL accounting services and Moldova IT Park residency supportStudio financial records, employee payroll data, banking detailsMDpending
GitHubCode hostingSource code, project dataUS2026-05-14
Google Ireland Limited and Google LLCGoogle Analytics 4 and Google Ads conversion attributionOnline identifiers, device and usage data, conversion eventsEU and United States2026-08-27
InfisicalSecrets managementTechnical secrets (no PII)US2026-05-14
LinearProject managementTask data, commentsUS2026-05-14
n8n CloudWorkflow automationMessaging payloadsEU2026-05-14
OpenAIOpenAI APIAI model inputsUS2026-05-14
Plausible AnalyticsCookieless web analyticsAggregated HTTP request metadata (no PII)EU (Estonia / Germany)pending
Stripe (Stripe Payments Europe, Ltd. / Stripe, Inc.)Payment processing — Discovery checkoutName, email, payment card data (entered on Stripe-hosted page; never stored on Studio systems), billing details, transaction metadataEU (Ireland) with US sub-processing (DPF / SCCs)pending — owner to record SSA acceptance date
SupabaseDatabase, AuthUser data, authenticationEU (eu-central-2)2026-05-14
TelegramClient communicationsMessage contentGlobaljoint controller
WhatsApp BusinessClient communicationsMessage contentEU (via EU-BSP)2026-05-14

Telegram is listed as a joint controller — no formal DPA is available. Telegram and Rapoport Studio independently determine the purposes and means of processing messages on the Telegram platform.