Last updated: March 16, 2026
Prody uses a limited number of third-party service providers ("sub-processors") to help deliver our product analytics service. Each sub-processor listed below may process Customer Data as part of their role in supporting the Service.
We evaluate the security practices of every sub-processor before engagement. We will update this page whenever a sub-processor is added or removed, and will notify customers with active Data Processing Agreements at least 30 days before engaging a new sub-processor.
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Anthropic | AI processing - generates Prody Signal explanations (batch), powers the Ask Prody assistant (interactive chat), and runs the Correlation Discovery engine | Aggregated event metadata, analytics context, and natural language queries. No raw PII is sent unless included in event properties by the customer. | United States |
| Railway | Cloud hosting - application servers and PostgreSQL database infrastructure | All Customer Data (events, users, accounts, health scores, metadata). Encrypted at rest and in transit. | United States |
| Resend | Transactional email - verification emails, welcome emails, and account notifications | Recipient email addresses and email content. No product analytics data is sent to Resend. | United States |
| Cloudflare | DNS management and marketing site hosting (Cloudflare Pages) | DNS queries and static marketing site assets. Cloudflare does not process Customer Data from the application. | United States (global edge network) |
| Slack (Salesforce) | Notification delivery - sends signal alerts and discovery notifications to customer-configured Slack channels via Slack's API | Signal titles, severity levels, account/user names referenced in signals, and recommended actions. Only transmitted when the customer enables the Slack integration. Bot tokens are stored per tenant. | United States |
Customers can configure generic webhook URLs to receive structured JSON payloads when signals, health drops, or discoveries are generated. Webhook endpoints are chosen entirely by the customer. Prody transmits signal metadata (titles, severity, entity names) to those endpoints via HTTPS POST. Prody is not responsible for data handling at customer-configured webhook destinations.
Prody does not use any third-party analytics services (Mixpanel, Amplitude, Segment, Google Analytics), advertising networks, data brokers, or customer data platforms. Your data stays between Prody, its hosting provider, Anthropic (for AI features), and any integrations you explicitly configure (Slack, webhooks).
If we add a new sub-processor, we will update this page and notify all customers with active DPAs at least 30 days in advance. If you object to a new sub-processor, you may terminate your agreement as described in our Terms of Service.
For questions about our sub-processors or data processing practices, contact us at [email protected].
For our full privacy practices, see our Privacy Policy. For security details, see our Security page.