Legal
Subprocessors
Vendors that may process personal data for the QUBE Chatbot Payment App and Remittance Backend.
Last updated: September 11, 2026
Qube (“Qube”, “we”, “us”) uses the service providers below to operate remittance, identity verification, messaging, notifications, and infrastructure. This list covers processors used by the QUBE Chatbot Payment App and Remittance Backend. It does not replace our Privacy Policy or Terms of Service.
We update this page when vendors are added or removed. For questions, contact hello@qubeus.com.
| Subprocessor | Purpose | Data categories | Location |
|---|---|---|---|
| Bridge | Custodial wallets, transfers, virtual accounts, bank rails, and hosted KYC / terms flows | Contact email, KYC verification flow, bank account fields, amounts, wallet and transfer identifiers | United States (Bridge API and hosted flows) |
| Persona (via Bridge) | Identity verification inquiry inside Bridge’s hosted KYC WebView | Government ID images, selfie / liveness capture, and related verification data as configured by Bridge | United States (Persona / withpersona.com hosts) |
| Sentry | Application crash, error, and performance monitoring | Device and diagnostic data; QUBE Chatbot Payment App ties events to an opaque install device id only (not phone or email) | United States (Sentry US ingest) |
| Expo (and Apple APNs / Google FCM) | Remote App Push delivery | Push tokens, notification titles and bodies, deep-link payload fields | United States / vendor push infrastructure |
| Twilio | SMS one-time codes (Verify) and administrative email when enabled | Phone number (E.164); admin email and invite content | United States (Twilio) |
| Meta | WhatsApp and Messenger Messaging Channel delivery | Chat text, recipient identifiers, media | United States (Meta Graph / media) |
| Telegram | Telegram Messaging Channel bot delivery | Chat text and file attachments | Telegram infrastructure |
| Discord | Discord Messaging Channel bot and open-chat | Direct message text, OAuth and channel identifiers | United States / Discord infrastructure |
| DeepSeek / Groq / Alibaba DashScope | Optional channel intent extraction and voice transcription (configuration-dependent) | Redacted chat transcripts and/or audio for ASR | Vendor API regions as configured |
| Polygon / Privado ID | Decentralized identity credential issue and holder prove | Identity protocol and chain-query payloads | Public Polygon Amoy RPC and RHS hosts |
| Amazon Web Services | Hosting, database, encryption keys, and secrets for Remittance Backend | Application data at rest and operational secrets | AWS region of the production deployment |
Notes
- Bridge may open Persona and related CDN hosts inside the in-app identity WebView; those loads are part of Bridge’s KYC path.
- Messaging Channel vendors (Meta, Telegram, Discord) process chat content only when you use that channel.
- Analytics SDKs that are not active in the product build are not listed here.