We use a small number of trusted third-party providers ("subprocessors") to run ManyRequests and deliver our service. These providers only process data on our behalf and under data protection obligations.
Last updated: October 2026
What is a subprocessor?
A subprocessor is a third-party service that processes personal data as part of providing ManyRequests, for example hosting, payments or email delivery.
Current subprocessors
Subprocessor | What we use it for | Data it processes |
Amazon Web Services (AWS) | Hosting, databases, file storage and background processing | All data stored in your portal: accounts, requests, comments, files, invoices |
Stripe | Payment processing for your ManyRequests plan, and for the payments your clients make when you connect Stripe | Names, email addresses, billing addresses, payment details |
Postmark | Sending transactional emails (notifications, invitations, account emails) and receiving email replies | Names, email addresses, email content |
Microsoft Clarity | Session recording and product analytics, to understand how the app is used and fix problems | Pages viewed and interactions, user name, email address, portal domain |
Google (Gemini API) | AI features: rewriting comments and messages when you ask it to, and suggesting services from your agency website during setup | Your draft and, for context, the request or conversation details and its last five comments or messages with the names and roles of who wrote them; your agency website content during setup |
OpenAI | AI screening of outgoing emails for spam and phishing | Sender, subject and body of outgoing emails |
Pusher | Real-time updates and browser push notifications | User IDs, notification content |
Intercom | In-app support chat for portal admins and admins | Name, email address, role, support conversations |
Featurebase | Product feedback and announcements widget for admins | Name, email address, portal name |
Bento | Product and account emails to portal owners | Portal owner name, email address, plan and account events |
Flare | Error tracking, so we can find and fix bugs | Technical error details, which can include request data and user IDs |
Cloudflare | DNS, SSL certificates and traffic routing for custom portal domains | Domain names, IP addresses, network traffic |
hCaptcha | Bot protection on sign-up and checkout forms | IP address, browser and device information |
Brandfetch | Fetching your logo and brand colors from your agency website when you sign up | Your agency website domain |
Plausible | Cookieless, aggregate website analytics on our sign-up pages | Page views (no cookies) |
Want Microsoft Clarity session recording turned off for your portal? Contact support and we'll switch it off for you.
Integrations you choose to enable
Some services only receive data when you connect them yourself in Settings > Integrations or add them as extensions, for example Slack, Google sign-in, Zapier, Hubstaff, Mailchimp, Loom, Rewardful, Tapfiliate and live chat widgets. For these, you decide what to connect, and the provider's own terms apply.
How we work with subprocessors
All subprocessors are:
Carefully selected for reliability and security
Required to process data only on our instructions
Bound by data protection agreements
Data transfers
Some subprocessors may process data outside the EU/UK. When this happens, we use appropriate safeguards such as Standard Contractual Clauses (SCCs).
Updates
We may update this list as we improve our infrastructure. The date at the top of this page shows when it last changed, and we will take reasonable steps to inform customers of significant changes.
Related
Questions
If you have any questions about our subprocessors, contact our support team through the chat in your portal.