AIMER uses a small number of carefully selected service providers ("subprocessors") to deliver the service. The table below reflects the providers that actually process AIMER customer data in production today. We update this page whenever a subprocessor is added, changed or removed.
| Provider | Purpose | Data processed | Region |
|---|---|---|---|
| Emergent (hosting & infrastructure) | Application hosting, database infrastructure and deployment platform.ProcessorSCCs / provider DPA (verify before launch)Not used for AI training | All application data (encrypted in transit; access-controlled). | EU/US |
| OpenAI (via Emergent LLM gateway) | Generates AI Employee chat responses.SubprocessorSCCs / EU-US DPF (verify before launch)API data NOT used to train models (OpenAI API terms) | Conversation messages and the business’s own knowledge base content. | US |
| Resend | Transactional email delivery (signup, password reset, team invites, system notifications).SubprocessorSCCs (verify before launch)Not used for AI training | Recipient email address and email content. | US/EU |
| Stripe (payments) | Subscription billing and hosted checkout (Starter and Professional plans).Subprocessor / payment processorSCCs / EU-US DPF (Stripe terms)Not used for AI training | Billing contact details and subscription/transaction metadata (plan, amount, status). Card data is entered on Stripe-hosted checkout and is never stored by AIMER. | US/EU |
| Google (Google Calendar API) | Calendar availability and booking sync — only when a business actively connects Google Calendar.Independent controller / API providerSCCs / EU-US DPF (Google terms)Not used for AI training | Calendar events and booking details for the connected calendar. | EU/US |
This list reflects the providers in active production use today. Payment card data is handled solely by Stripe on its hosted checkout and is never stored by AIMER.
Questions about our subprocessors or data processing? Contact us at hello@getaimer.ai.