Os cookies essenciais mantêm a sua sessão iniciada; as estatísticas apenas com o seu consentimento. Consulte a nossa Política de Privacidade.
Last updated: July 30, 2026
This page lists the third-party companies ("sub-processors") that Monqez AI uses to process personal data on your behalf when you use the platform. We share data with them only as needed to run the features you actually enable, and only under contracts that require them to protect it.
Running an AI customer-service platform means depending on specialists. The AI models that write replies, the messaging networks that carry them, the infrastructure that stores your data and the processor that takes card payments are each built by companies that do that one thing at scale. Building substitutes in-house would make the product slower, more expensive and less secure, not more private.
What we do control is scope. Each provider below receives only the data its feature needs, only while that feature is switched on for your account, and under terms that forbid using your content to train public models.
The Gemini AI models that generate replies, answer from your knowledge base and power the Test-AI sandbox; Google Sign-In (optional); and Google Analytics (loaded only after you consent).
Data: Content and prompts submitted to the AI; your name and email (Google Sign-In only); anonymised usage analytics (consent-gated).
Location: Global (Google infrastructure)
Drafting Sales outreach emails; non-Arabic voice features (speech-to-text and text-to-speech); and the optional CRM summary that condenses a customer’s conversation history into a short brief for you.
Data: The text and audio submitted for those features. For a CRM summary this includes recent messages exchanged with that customer, which may contain whatever they wrote to you. Processed under enterprise API terms that prohibit training on your data.
Location: United States
Arabic voice features (speech-to-text and text-to-speech), including the native dialect voices.
Data: The audio and transcripts submitted for those features.
Location: United States / global
Vector memory for the AI knowledge base — the long-term memory that lets the AI answer from your own documents.
Data: Numeric embeddings derived from your knowledge-base content, plus the passage text needed to return an answer. Not the original files.
Location: Cloud region (EU available)
Delivering and receiving messages on the WhatsApp, Instagram and Facebook Messenger channels you choose to connect.
Data: The messages exchanged on those channels, plus the sender name and ID that Meta provides.
Location: Global
Delivering and receiving messages on a connected Telegram channel.
Data: The messages exchanged, plus the sender information Telegram provides.
Location: Global
Cloud hosting, database and file storage. The platform — including our self-hosted automation engine (n8n) — runs on this infrastructure.
Data: All platform data at rest, held in our isolated environment. Sensitive credentials are encrypted with AES-256-GCM before storage.
Location: European Union — Frankfurt, Germany
The scrapers behind lead and creator search. Used only while a search feature is enabled for your account, and only on the terms you type in.
Data: Your search terms, and the publicly available business or creator results returned.
Location: EU / global
Sending transactional and account email — verification, receipts and notifications.
Data: Recipient email address and the content of the message.
Location: EU / global
Processing payments for paid plans and purchases. Active once online billing is enabled for your account.
Data: Billing details are handled by Stripe directly. We never receive or store full card numbers.
Location: Global
Every provider above is engaged under a written agreement that binds them to confidentiality and to security measures at least as protective as our own. Where a transfer leaves the EEA or the UK, it relies on Standard Contractual Clauses or an equivalent lawful mechanism.
Your platform data is held in the European Union (Frankfurt). Connected-channel credentials are encrypted at rest with AES-256-GCM, access to production is limited to authorised personnel, and administrative actions are recorded in an internal audit log.
For the AI providers, we do not permit your content to be used to train their public models. We do not sell your data, and we never train shared models across customers.
Your own email provider is not our sub-processor. When you connect your own mailbox — Gmail, Outlook, Hostinger, Zoho, SendGrid or another — to send outreach, that provider is yours, and your mail is sent through it from your own domain.
We keep this list current as part of shipping. Where the law requires it, we will notify affected customers before a new sub-processor that handles their personal data begins processing, so there is a genuine opportunity to object on reasonable data-protection grounds.
To object, or to ask anything about this list, email support@monqezai.io.
For how we use this data and your rights over it, see our Privacy Policy. For business customers who need a signed data-processing agreement, see our Data Processing Agreement.