Sub-processors
Last updated: 2026-05-15
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.
| Vendor | Service | Data category | Region | DPA |
|---|---|---|---|---|
| Anthropic | Claude API | AI model inputs | US | 2026-05-14 |
| Cloudflare | CDN, Workers runtime | HTTP traffic | Global / EU | 2026-05-14 |
| FinExpert SRL | Бухгалтерское обслуживание SRL + сопровождение резидентства Moldova IT Park | Финансовая документация студии, персональные данные сотрудников (зарплата), банковская реквизитика | MD | [contract effective date to be inserted at Phase 2] |
| GitHub | Code hosting | Source code, project data | US | 2026-05-14 |
| Infisical | Secrets management | Technical secrets (no PII) | US | 2026-05-14 |
| Linear | Project management | Task data, comments | US | 2026-05-14 |
| n8n Cloud | Workflow automation | Messaging payloads | EU | 2026-05-14 |
| OpenAI | OpenAI API | AI model inputs | US | 2026-05-14 |
| Plausible Analytics | Cookieless web analytics | Aggregated HTTP request metadata (no PII) | EU (Estonia / Germany) | pending — gated on Pavel-external account provision |
| Supabase | Database, Auth | User data, authentication | EU (eu-central-2) | 2026-05-14 |
| Telegram | Client communications | Message content | Global | joint controller |
| WhatsApp Business | Client communications | Message content | EU (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.