Asks Subprocessors
Asks is an AI customer support and customer experience platform that answers, books, sells, and resolves customer inquiries across WhatsApp, Instagram, Messenger, Telegram, Slack, and website chat.
- Subprocessors
- 19
- Locations
- 6
- Categories
- 11
- Last scanned
| Name | Category | Purpose | Location | Data processed |
|---|---|---|---|---|
| DigitalOcean, LLC | Cloud Infrastructure | Cloud hosting for the Asks backend |
 United States
|
All platform data in transit through our API |
| Supabase, Inc. | Database | Managed PostgreSQL database | United States (us-east-1) | Account data, workspace data, conversations, customer records |
| Google LLC (Google Cloud) | Cloud Infrastructure | File storage for uploads and attachments |
United States
|
Files, images, documents, and avatars you or your customers upload |
| Vercel, Inc. | Cloud Infrastructure | Hosting for our website, dashboard, and hosted chat pages |
United States
global edge
|
Web requests and technical logs |
| Redis, Ltd. | Database | Caching, rate limiting, and job queues |
United States
|
Transient conversation state and technical counters |
| OpenAI, L.L.C. | AI | Large language model powering the AI Agent — responses, transcription, document understanding, and quality checks |
United States
|
Conversation messages, knowledge base content, attachments, and voice notes |
| MongoDB, Inc. (Voyage AI) | Database | Embedding and reranking for knowledge retrieval (the search index itself is stored in our primary database) |
United States
|
Knowledge base content (as text chunks) and customer questions |
| Firecrawl, Inc. | AI | Website crawling for knowledge base ingestion |
United States
|
Publicly available content from websites you choose to sync |
| Meta Platforms, Inc. | Social Media | WhatsApp, Instagram, and Facebook Messenger channels |
United States
global
|
Message content, phone numbers / user handles, media |
| Slack Technologies (Salesforce, Inc.) | Communications | Slack channel |
United States
|
Message content and Slack workspace/user identifiers |
| Telegram FZ-LLC | Communications | Telegram channel |
 United Arab Emirates
global
|
Message content and Telegram user identifiers |
| Discord Inc. | Communications | Discord channel |
United States
|
Message content and Discord user identifiers |
| Resend (Plmr, Inc.) | Email sending and the inbound email support channel |
United States
|
Email addresses, subject lines, message bodies, attachments | |
| Stripe, Inc. | Payment Processing | Payment processing and subscription billing |
United States
global
|
Billing name, email, and payment details (held by Stripe, never stored by Asks) |
| Shopify Inc. | E-commerce | Billing and commerce data for Shopify-connected workspaces |
 Canada
United States
|
Shop domain, billing status, order and customer lookups you enable |
| PostHog, Inc. | Analytics | Product analytics for the Asks dashboard; website analytics for asks.app, docs.asks.app and demo sites (without cookies unless the visitor consents) |
United States
|
Usage events tied to account identifiers; anonymous website events (the IP address only feeds a daily-changing count hash and is not stored) |
| Functional Software, Inc. (Sentry) | Error Tracking | Error and performance monitoring |
United States
|
Error reports and technical context (emails and IPs are scrubbed before sending) |
| Langfuse GmbH | AI | AI quality observability — tracing what the AI Agent did and why |
United States
|
AI prompts and responses, including conversation content |
| Google LLC (Google Identity) | Authentication | Optional “Sign in with Google” |
United States
global
|
Account email, name, and avatar |
No subprocessors match your filters.
No changes recorded yet. Changes will appear here after the next scan detects updates.