METRICRM
FeaturesIndustriesAIPricingResources
//
Talk to us
METRICRM
ProductPricingFeaturesAll modulesIndustriesAIIntegrations
ResourcesUser GuideContact
LegalTerms of ServicePrivacy NoticePDPA NoticeData Processing AgreementSub-processorsCookie PolicyDelete your account
© 2026 Webbalances Solution (003096168-D). All rights reserved.Version 4.68.0
Terms of ServicePrivacy NoticePDPA NoticeData Processing AgreementSub-processorsCookie PolicyDelete your account

Sub-processors

The service providers that process customer personal data for us, and how we tell you about changes.

Last updated October 19, 2026

This document is available in English, Bahasa Melayu and Chinese. The English version is the most accurate version and prevails if there is any inconsistency.

1. About this list

This page lists the sub-processors that Webbalances Solution (003096168-D) uses to provide MetriCRM, as described in section 7 of the Data Processing Agreement. Each one is bound by data protection terms no less protective than the Data Processing Agreement.

2. Current sub-processors

  • Neon (database hosting) — Singapore.
  • Vercel (application hosting and encrypted file storage) — Singapore, with a global edge network for delivery.
  • Stripe (payments and invoicing) — billing data only.
  • Inngest (background job scheduling) — job metadata, not message content.
  • AI providers the Customer enables: Anthropic, OpenAI and Google (AI features) — only content sent to AI features.
  • Our email hosting provider (system emails such as sign-in links and notifications) — the recipient address and the notification only.

3. Changes

We give at least 30 days' notice before adding or replacing a sub-processor. We update this page and email the owners and billing administrators of every workspace. If you object on reasonable data protection grounds and we cannot resolve the objection, you may terminate the affected service and receive a refund of prepaid fees for the unused period.

4. Services you connect

Services your organisation connects to its workspace (for example Google, Microsoft, Meta, Twilio, Stripe, Billplz or LHDN MyInvois) are not our sub-processors: your organisation instructs us to exchange data with them, and its own agreement with each service governs that service's processing.