Subprocessors

Effective Date: May 8, 2026

ConvRadar engages the following third-party service providers (“subprocessors”) to operate the Service. We require each provider to maintain confidentiality and security obligations consistent with our Privacy Policy and applicable data-protection laws (GDPR, UK GDPR, CCPA). Where a provider is located outside your country, transfers of personal data are governed by the European Commission's Standard Contractual Clauses (Module 2: Controller-to-Processor) and, for UK data subjects, the UK International Data Transfer Addendum.

We will update this page when our stack changes. Material changes will also be reflected on the Privacy Policy page with an updated effective date.

Direct subprocessors

Supabase

Purpose: Primary database, authentication (passwordless magic link), and OAuth credential storage.
Categories of data: Account email, hashed session tokens, GA4 property metadata, aggregated GA4 metrics, hypotheses, verifications, change journal.
Hosting region: United States (AWS us-east-1) by default; EU regions available on request.
Data Processing Agreement / Privacy reference: https://supabase.com/legal/dpa

Render

Purpose: Hosting for the ConvRadar web application and the remote MCP connector server.
Categories of data: Request logs (timestamp, path, status code, tenant ID hash). No tenant content beyond what is needed to serve the request.
Hosting region: United States (Oregon).
Data Processing Agreement / Privacy reference: https://render.com/dpa

Google APIs (GA4 Data API)

Purpose: Read-only access to your Google Analytics 4 data via OAuth 2.0 (analytics.readonly scope).
Categories of data: Aggregated metrics and dimensions (sessions, conversions, revenue, source, medium, device, geography). No raw user IDs or IPs.
Hosting region: United States; transfer governed by Google Cloud DPA + Standard Contractual Clauses.
Data Processing Agreement / Privacy reference: https://cloud.google.com/terms/data-processing-addendum

Resend

Purpose: Transactional email delivery for passwordless magic-link sign-in and account notifications.
Categories of data: Account email address and email message contents we generate (sign-in link, audit completion notice).
Hosting region: United States; EU sending regions available.
Data Processing Agreement / Privacy reference: https://resend.com/legal/dpa

Stripe

Purpose: Subscription billing for paid plans, where you choose to subscribe.
Categories of data: Account email, billing name and address, payment method tokens (handled by Stripe; ConvRadar never sees raw card numbers), subscription status, invoices.
Hosting region: United States and Ireland (EU).
Data Processing Agreement / Privacy reference: https://stripe.com/legal/dpa

ScreenshotOne

Purpose: Server-side screenshot capture of public pages on your own site that you ask the Service to verify (e.g. PDP audit).
Categories of data: URLs of public pages you submit for verification, plus the rendered HTML/screenshot output.
Hosting region: United States.
Data Processing Agreement / Privacy reference: https://screenshotone.com/security-compliance/

Browserless

Purpose: Headless-browser fallback for fetching pages that ScreenshotOne cannot render (auth-walled pages are not bypassed).
Categories of data: URLs of public pages you submit for verification, plus the fetched HTML.
Hosting region: European Union.
Data Processing Agreement / Privacy reference: https://www.browserless.io/privacy-policy

Google Tag Manager

Purpose: Website analytics on the marketing site convradar.com (not on the MCP connector).
Categories of data: Anonymised page views, interaction events, basic device/browser metadata.
Hosting region: United States; transfer governed by Google Cloud DPA + Standard Contractual Clauses.
Data Processing Agreement / Privacy reference: https://business.safety.google/processorterms/

Telegram (Bot API, internal alerts only)

Purpose: Internal operator alerts to the operator (Ivan Pika) — for example, error notifications and deploy events.
Categories of data: Aggregated, non-PII operational events (e.g. “sync run failed” + tenant ID hash). No personal data of end-users is sent.
Hosting region: Multi-region (Telegram global infrastructure).
Data Processing Agreement / Privacy reference: https://telegram.org/privacy

Indirect processors (your choice of AI assistant)

When you choose to access ConvRadar through Claude or ChatGPT, the AI assistant's operator is the controller of your conversation. ConvRadar does not control how Anthropic or OpenAI process your prompts, memory, or chat history; please refer to their respective privacy policies. ConvRadar itself never reads, stores, or transmits the content of your conversations beyond the specific tool arguments the assistant sends to us.

Anthropic (Claude)

Role: When you choose to use ConvRadar through Claude as an MCP connector, Claude (operated by Anthropic) is the conversational interface. ConvRadar passes responses back to Claude in your turn.
Data they process: The MCP tool calls and responses for your session. Anthropic is responsible for handling your conversation according to its own Privacy Policy.
Region: United States.
Their privacy policy: https://www.anthropic.com/legal/privacy

OpenAI (ChatGPT)

Role: When you choose to use ConvRadar through ChatGPT as an MCP connector or App, ChatGPT (operated by OpenAI) is the conversational interface.
Data they process: The MCP tool calls and responses for your session. OpenAI is responsible for handling your conversation according to its own Privacy Policy.
Region: United States.
Their privacy policy: https://openai.com/policies/row-privacy-policy/

Questions

If you have questions about how a specific subprocessor handles your data, or you wish to be notified before we add a new subprocessor, see our Contacts page or email .