MultiLipi Subprocessors
Last updated: 10 September 2025
MultiLipi engages the following third-party Subprocessors to provide the Services. We conduct due diligence on the security and privacy practices of our Subprocessors to ensure the protection of Customer Data.
On this page
1) Current Subprocessors
| Subprocessor | Purpose | Categories of personal data | Location(s) | Transfer mechanism |
|---|---|---|---|---|
| Cloudflare, Inc. (CDN/WAF/Workers) | Edge CDN, DNS, network security (WAF/DDoS), TLS; Workers used to fetch client‑site assets for localization. | IP addresses, request headers/URLs, limited logs/diagnostics; transient cached copies of assets. | Global edge network | SCCs/UK Addendum where applicable |
| Microsoft Corporation (Azure) | Cloud infrastructure: hosting/compute, databases, object storage, backups. | Customer content (incl. translation assets), account metadata, logs. | Regions selected by MultiLipi (incl. India/EU/US) | SCCs/UK Addendum where applicable |
| Microsoft Azure Cognitive Services (Translator) | Machine translation for languages you enable. | Text you send for translation and related metadata. | Azure regions selected by MultiLipi | SCCs/UK Addendum where applicable |
| Google Cloud Platform (GCP) | Cloud infrastructure used for specific components. | Customer content (feature‑dependent), account/project metadata, logs. | Regions selected by MultiLipi | SCCs/UK Addendum where applicable |
| Google Cloud Translation (Vertex/Translation API) | Machine translation for languages you enable. | Text you send for translation and related metadata. | Google Cloud regions selected by MultiLipi | SCCs/UK Addendum where applicable |
| Stripe, Inc. | Payments processing, subscription billing, invoicing. | Billing contact, email, company, transaction metadata. Card data handled by Stripe; not stored by MultiLipi. | EU/US (per Stripe) | SCCs/UK Addendum where applicable |
| PushlapGrowth | Affiliate portal and referral tracking. | Affiliate account details, referral IDs, payout metadata. | Per vendor (EU/US) | SCCs/UK Addendum where applicable |
| Google Workspace (Gmail) | Support‑related email communications. | Email addresses, message metadata, support correspondence. | Per Google (regional storage options) | SCCs/UK Addendum where applicable |
| Azure Communication Services | Transactional email delivery (alerts, notifications). | Email addresses, message metadata, delivery logs. | Azure regions selected by MultiLipi | SCCs/UK Addendum where applicable |
| Google Analytics (GA4) | Product/website analytics (consent‑based where required). | Pseudonymous identifiers, page views, events, device/browser data; IP and geodata per GA4 configuration. | Global (per Google service) | SCCs/UK Addendum where applicable |
Links and detailed vendor terms are available upon request. The MultiLipi DPA governs our processor obligations.
We provide at least 15 days’ advance notice of any intended subprocessor changes and an opportunity to object (see DPA and SCCs Clause 9 — general authorization).
Feature‑dependent vendors: AI/translation providers (e.g., Google Cloud, Microsoft Azure) receive only the content necessary to provide the requested feature. You can disable these features in your project settings to prevent such transfers.
2) Change notifications
We will provide reasonable advance info before we add or replace a subprocessor that may process Customer Personal Data. Notices will be updated on this page.
3) How to object
If you have a reasonable, documented objection related to data protection risks posed by a new or replacement subprocessor, you may object by emailing privacy@multilipi.com within the notice period. We'll work with you in good faith to address concerns. If unresolved, you may suspend or terminate the affected Services, with a prorated refund of prepaid fees for the terminated portion, as described in our DPA.
4) International transfers
Where a subprocessor is located outside your region, MultiLipi ensures appropriate transfer safeguards (e.g., EU Standard Contractual Clauses, UK Addendum) and binds subprocessors to equivalent obligations as set out in our DPA.
5) Change log
2025‑09‑10: Initial publication of public subprocessor list template.
6) Contact
Questions or objections? Email privacy@multilipi.com.