Legal

Sub-processors

Legal

Sub-processors

MOVEMENT SUB-PROCESSORS

Movement Platform Pty Ltd (“Movement”) uses the third-party sub-processors below to deliver its Services. Each one processes personal data on Movement’s behalf, under written data protection terms that are no less protective than our Data Processing Agreement.


Current sub-processors

Last updated: October 31 2026


Sub-processor

Purpose

Personal data processed

Location

Transfer basis

DigitalOcean, LLC

Application servers, primary database, Redis and automated backups

All customer personal data stored in the production database

Singapore

DigitalOcean DPA (SCCs)

Amazon Web Services, Inc.

File storage and delivery for uploads and published app bundles

Uploaded media and files

Sydney, Australia; Singapore

EU–U.S. DPF / AWS DPA (SCCs)

Cloudflare, Inc.

CDN, DNS, security, edge hosting, media cache and AI gateway

Web traffic, authentication tokens, cached images, AI chat content

Global edge network / USA

EU–U.S. DPF / Cloudflare DPA (SCCs)

Mux, Inc.

Video and audio upload, transcoding and streaming

Video and audio content, playback data

USA

EU–U.S. DPF / DPA

Twilio Inc. (SendGrid)

Transactional and customer-composed email

Email addresses, names, email content, delivery data

USA

Twilio DPA

Pusher Ltd (a Bird company)

Real-time chat updates and push notifications

Chat message text, participant names, avatars, push tokens

Asia-Pacific

Bird DPA (SCCs)

Google LLC (Firebase)

Web and Android push notifications

Push tokens, notification content, device identifiers

USA / Global

EU–U.S. DPF / Google DPA

650 Industries, Inc. (Expo)

Push notifications for native iOS and Android apps

Push tokens, notification content

USA

EU–U.S. DPF / DPA

Google LLC

Sign in with Google; analytics in member web apps (under cookie consent)

Google account ID, name, email; page view and device data

USA / Global

EU–U.S. DPF / Google DPA

OpenRouter, Inc.

Routing for optional AI features and spam detection

AI conversations, member context

USA

OpenRouter DPA (SCCs)

Anthropic PBC

AI models for the app builder and optional member AI assistant

AI conversations and member context

USA

Anthropic DPA (SCCs). No training on customer data

OpenAI, L.L.C.

Search embeddings and selectable AI models

Customer content, member search queries, AI prompts

USA

OpenAI DPA (SCCs). No model training on customer data

Google LLC (Gemini)

Selectable AI models, via OpenRouter

AI prompts and member context

USA

Via OpenRouter DPA (SCCs)

Svix, Inc.

Webhook delivery to customer-configured integrations (e.g. Zapier)

Member IDs, names, emails, activity and form data

USA

EU SCCs + UK Addendum / Swiss addendum (DPA signed)

New Relic, Inc.

Application performance monitoring

Diagnostic traces and logs

USA

EU–U.S. DPF / New Relic DPA

Better Stack, Inc.

Centralised application logging

System logs and request metadata (sensitive fields removed)

Frankfurt, Germany; Singapore

Better Stack DPA (SCCs)

Everapi GmbH (ipbase.com)

IP address geolocation

Member and visitor IP addresses

Germany (EU)

DPA in progress

Stripe, Inc.

Payment processing on the customer’s connected Stripe account

Names, emails, billing records, Stripe IDs

USA / Global

EU–U.S. DPF / Stripe DPA (SCCs)


Services configured by our customers

Some integrations are switched on and controlled by our customers in their own accounts. Examples include Apple sign-in and in-app purchases, Zapier, Vimeo, YouTube, Meta video embeds, Google Analytics and Tag Manager, Rewardful and Meta Pixel. These aren’t Movement sub-processors. They act on the customer’s instructions or as independent controllers. See Annex III, Part B of our DPA for details.


Changes to this list

We’ll give customers at least 14 days’ notice before a new or replacement sub-processor starts processing personal data. We do this by updating this page and emailing the account owner’s registered email address.

In urgent cases, for example to protect security or keep the service running, we may need to replace a sub-processor sooner. If so, we’ll notify customers as soon as reasonably practicable.


Objecting to a change

Customers can object to a new sub-processor on reasonable data protection grounds by emailing hello@movement.so within the 14-day notice period. The process is set out in clause 7 of our DPA.


Questions

Contact our privacy team at hello@movement.so.