Subprocessors and service providers
Metricgram relies on specialized providers to operate the platform. This page explains the main categories and why each provider is used.
Specialized providers
Payments, email, infrastructure, authentication, Telegram, analytics, and AI workflows are handled by purpose-built services.
Limited by function
Providers receive the data needed for the service they perform, such as payment processing, email delivery, hosting, or AI assistance.
Reviewed over time
This list is updated when the product, hosting, legal, or operational setup materially changes.
Provider categories
- Hosting and storage AWS, PostgreSQL, Redis, Active Storage, and server infrastructure support application hosting, persistence, caching, queues, and file storage.
- Payments Stripe and Stripe Connect process Metricgram subscriptions, invoices, refunds, connected-account payments, and paid-community access.
- Communications Mailgun and Telegram help deliver transactional email, bot messages, group events, and community workflows.
- Authentication and analytics Google OAuth and Google Analytics may support sign-in, measurement, and product analytics according to consent settings.
- AI-assisted features OpenAI may process prompts or support context for AI chatbots, summaries, support responses, or knowledge-base workflows when those features are enabled.
How provider access is limited
Metricgram sends providers the data needed to perform their role. For example, Stripe handles payment data, Mailgun handles email delivery data, and Telegram receives bot and group interactions required for configured workflows.
Feature choices matter. If a workspace does not enable optional extraction or AI workflows, those specific data flows are not used for that workspace.
Changes to providers
Providers may change as Metricgram improves reliability, coverage, security, or compliance. Material updates are reflected in this trust center.
Questions or data requests
Contact Metricgram at info@metricgram.com