Sub-processors
3. Subprocessors
The Company engages the following subprocessors to provide the Service.
| Subprocessor | Role | Region |
|---|---|---|
| Vercel Inc. | Frontend and API hosting | United States (Washington D.C. region; edge network is global) |
| Supabase Inc. | Database, authentication, file storage | eu-west-1 region, Ireland, European Union |
| Railway Corp. | Background workers (BullMQ), Redis, Playwright browser | ams region, Amsterdam, Netherlands, European Union |
| Upstash Inc. | Background job queue | eu-west-1 region, Ireland, European Union |
| Resend Inc. | Transactional email | United States |
| Functional Software Inc. (Sentry) | Error monitoring | United States |
| OpenAI OpCo LLC | ChatGPT queries, base engine | United States |
| Perplexity AI Inc. | Perplexity queries, base engine | United States |
| Google LLC | Google AI Overviews, base engine; Gemini API as a paid add-on | United States |
| Anthropic PBC | Claude API as a paid add-on; model powering the Observatory browser agent | United States |
3.1. Paddle.com Market Ltd (United Kingdom) is not a subprocessor of the Company and acts as an independent controller, as Merchant of Record, in respect of the User's payment data. Paddle's processing of such data is governed by Paddle's own privacy policy.
3.2. GitHub is used solely for storing the Service's source code, no personal data of Users is processed there, and it is not a subprocessor within the meaning of this Policy.
3.3. The automated engines Yandex Alice, GigaChat (Sber), and DeepSeek are present in the Service's codebase as additional modules but are not used in plans offered to Users outside the Russian Federation and are not included among the subprocessors for the international version of the Service.
3.4. The Company may change the composition of its subprocessors, including replacing an existing subprocessor with a new one performing an equivalent function, and may change the location of data processing within the limits described in Section 8 of this Policy, upon notice to the User by publishing an updated version of this Policy on the Service website at least 14 days before the change takes effect. Re-execution of this Policy or the User's separate consent to such a change is not required, unless otherwise expressly provided by applicable law.