Subprocessors


Last updated February 10, 2026

This page lists the third-party subprocessors that GrowPanel engages to process personal data on behalf of our customers, in accordance with our Data Processing Agreement (DPA) and Privacy Policy.

We will update this page whenever a subprocessor is added or removed. If you have questions, contact us at [email protected].

1. Infrastructure

SubprocessorPurposeData processedLocation
CloudflareApplication hosting (Workers, Queues, Durable Objects, KV), CDN, DDoS protectionAll service data in transit and at restGlobal (edge network)
SupabasePostgreSQL database for account configuration, user accounts, and settingsAccount data, user profiles, data source configurationEU (Frankfurt)
LeasewebDedicated ClickHouse cluster for analytics data (customers, MRR movements, transactions)Customer billing data, MRR movements, transactions, plansNetherlands

2. Email and communications

SubprocessorPurposeData processedLocation
SendGrid (Twilio)Transactional email delivery for reports, notifications, and system emailsEmail addresses, report content, notification contentUS
MailerLiteMarketing email campaigns and drip sequencesEmail addresses, account plan statusEU (Lithuania)
HelpScoutCustomer support chat and help deskEmail addresses, support conversationsUS

3. Billing integrations

These subprocessors are only engaged when the customer connects the respective billing source. GrowPanel reads data from these platforms but does not write customer data back to them.

SubprocessorPurposeData processedLocation
StripeBilling data source (OAuth integration)Customer names, emails, subscription data, invoices, chargesUS
ChargebeeBilling data source (API integration)Customer names, emails, subscription data, invoicesUS
RecurlyBilling data source (API integration)Customer names, emails, subscription data, invoicesUS
Google SheetsData source for manual/custom data importCustomer data as provided by the userUS

4. AI and analytics

SubprocessorPurposeData processedLocation
AnthropicConversational analytics (Claude Sonnet 4.6) and chat title generation (Claude Haiku 4.5)Aggregated metrics only (MRR, subscriber counts, movement summaries). No personally identifiable information is sent.US
OpenAIAI-generated email report summaries and plan-group suggestions (GPT-5-mini)Aggregated metrics only (MRR, subscriber counts, movement summaries). No personally identifiable information is sent.US

5. Authentication providers

These are used only when the user chooses to log in via a third-party provider.

SubprocessorPurposeData processedLocation
GoogleOAuth login (Google Sign-In)Email address, nameUS
MicrosoftOAuth login (Microsoft Sign-In)Email address, nameUS

6. Analytics and product improvement

SubprocessorPurposeData processedLocation
PostHogProduct analytics and feature usage trackingAnonymized usage events, page viewsEU (Frankfurt)
MouseflowSession recording for UX improvementSession recordings, anonymized interaction dataEU (Denmark)

User-initiated AI integrations (NOT GrowPanel subprocessors)

GrowPanel offers an MCP server at mcp.growpanel.io that lets users connect external AI assistants (e.g. Claude.ai, ChatGPT, Cursor, Windsurf) to their GrowPanel account via OAuth.

These AI providers are not GrowPanel subprocessors. When a user authorizes an external AI assistant via the MCP server, the user is the controller of that data flow: they choose the AI provider, accept the AI provider's own privacy and data-handling terms, and decide what data gets queried. GrowPanel acts only as the API relay between the user's chosen AI assistant and the GrowPanel REST API.

The data that flows when an MCP connection is active depends on what the AI assistant requests, but can include any field exposed by the GrowPanel REST API — including customer names, email addresses, subscription details, and payment metadata. We do not redact PII on this path; the user has explicitly granted the AI access on their own behalf.

Connections can be reviewed and revoked at any time from Settings → Integrations. For full details see Privacy Policy § 3.2.6.


See also: Privacy Policy | Data Processing Agreement | Security