Last updated · September 21, 2026
Honest Dev LLC ("we", "us", "our") uses the following third-party service providers to operate the PilotPM platform and Site. Each is a "sub-processor" under California Consumer Privacy Act (CCPA/CPRA) terminology and is bound by contract to use information only to provide services to us and to protect it under standards consistent with our Privacy Policy.
This list is canonical — we update it whenever we add, remove, or materially change a sub-processor. The list is referenced from §5.1 of the Privacy Policy and §6.6 of the paid-tier Master Service Agreement.
These process Customer Data to run the platform. A feature-gated entry is engaged only when you turn that feature on.
| Sub-processor | Purpose | Data scope | Region |
|---|---|---|---|
| Amazon Web Services (AWS) | Application hosting, managed Postgres database, object storage, email receiving and sending (SES), AI model inference (Amazon Bedrock, Anthropic Claude models), logging and monitoring | All Customer Data, encrypted at rest (sensitive fields additionally encrypted at the application layer) | United States (us-east-2, Ohio) |
| Anthropic | Large language model API (Claude) for AI-drafted replies and related AI features | Prompts derived from Customer Data; no training on Customer Data | United States |
| OpenAI | Embeddings (text-embedding-3-small) for knowledge-base retrieval and clustering of customer signals | Message and knowledge-base excerpts; no training under contract | United States |
| ElevenLabs | Speech-to-text and text-to-speech for the Genie voice companion (only when Genie voice is enabled) | End-user voice audio and transcripts; zero-retention mode, not stored by us | United States |
| Hostinger | Operations server: off-site copy of the production database backup; hosting of this website | Database backup copy, sensitive fields still application-encrypted (rolling ~8-day window); website access logs | United States (Arizona) |
| Clerk | Authentication and identity management for workspace users | Email, name, OAuth identity, session metadata | United States |
| Stripe | Payment processing for paid-tier subscriptions | Billing name, address, payment method (card numbers stored at Stripe, not by us) | United States |
| Postmark | Fallback transactional email path (primary sending is Amazon SES; being retired) | Recipient email, message body | United States |
These integrate ONLY when a workspace owner explicitly connects them on /integrations, usually with the customer's own account or credentials. The data scope is bounded by that grant.
| Sub-processor | Purpose | Data scope |
|---|---|---|
| Google (Workspace APIs, Firebase Cloud Messaging, Google Play) | Gmail/Drive/Sheets connections, push delivery, Google Play review ingest | Email, documents and sheet rows you connect; push tokens; review text |
| Slack | Channel ingest, notifications, and replies in your connected Slack | Messages, channel metadata for the connected workspace |
| Meta (WhatsApp Business, Instagram, Messenger) | Inbound and outbound on the respective channels | Messages, sender profile ids, phone numbers |
| Twilio | WhatsApp and SMS through your Twilio account | Messages, phone numbers |
| LINE | LINE Official Account messaging | Messages, LINE user id and display name |
| Zalo | Zalo Official Account messaging | Messages, Zalo user id and display name |
| Pancake | Social-inbox aggregation for connected pages | Messages, sender metadata |
| HubSpot | CRM context (companies, deals, contacts, tickets) | Records as scoped by OAuth |
| Jira (Atlassian) | Engineering-issue sync and escalation | Issue metadata for the connected project |
| Zoho CRM | Read-only contact lookups | Contact records you expose |
| ChurnZero | Ticket and event push | Ticket metadata, account identifiers |
| Airtable | Read-only record lookups | Records in the connected base |
| Shopify | Order-status lookups | Order and customer records in the connected store |
| Gong | Call-summary and risk-signal sync | Call metadata and summaries |
| Sentry | Read-only lookup of your own error events | Error events and user context in your Sentry org |
| PagerDuty | Incident webhooks for known-issue context | Incident metadata |
| Apple (App Store Connect, Apple Search Ads) | Review ingest and replies, sales reports, Search Ads management | Review text and nicknames; aggregate metrics |
| GitHub | Code grounding and issue/release sync for repositories you connect | Repository content and issue metadata |
| Snowflake | Customer data warehouse joins (read-only, your warehouse) | Query results limited to the role you grant; we never write |
| Freshdesk / Zendesk / Intercom / Help Scout | Import of existing helpdesk history during migration or dual-tool periods | Tickets, conversation history and help-centre articles per your credentials |
| Braze | Campaign import and stats | Campaign definitions, aggregate stats, attributes you sync |
| PayPal | Operator-approved refunds through your PayPal credentials | Transaction ids, refund amounts |
Every material sub-processor is chosen by these criteria, in this order:
When a sub-processor is added, removed, or materially changed:
The "Last updated" date at the top of this page reflects the most recent change.
Questions about this list or our sub-processor selection process:
Honest Dev LLC
Attn: Privacy
support@pilotpm.ai
This page is informational. The contractual obligations governing sub-processors live in the Privacy Policy for users of the Site and other no-charge services, and the Master Service Agreement (linked at checkout) for subscribing customers.