Subprocessors

1. Authentication

MotionLab may use authentication providers to manage sign-in, sessions, account identity, and access control.

• Clerk: User authentication and session management.

2. Payments

MotionLab may use payment processors or merchant-of-record services for checkout, billing, invoices, taxes, payment status, subscriptions, and refunds.

• Dodo Payments: Merchant of record and payment processor.

3. Hosting and Databases

MotionLab may use hosting and database providers to run the website, APIs, databases, workers, admin tools, and backend services.

• Railway: Application hosting and primary databases.

4. Storage and Delivery

MotionLab may use cloud storage and delivery providers to store uploads, generated outputs, thumbnails, previews, public assets, and downloads.

• Cloudflare & Cloudflare R2: Asset delivery (CDN) and media storage. File-link access is explained in our Uploaded Assets Privacy policy.
• esm.sh and jsDelivr: Browser library delivery for Motion Studio and browser exports. Resource requests include ordinary browser network information.

5. GPU and AI Processing

MotionLab may use GPU infrastructure and AI model providers to process prompts, uploaded assets, generation settings, and outputs.

• RunPod: GPU infrastructure and model rendering containers.
• fal.ai: Creative AI model execution providers.
• Kie AI: API routing and processing for supported image, video, audio, and enhancement models. The underlying model operator depends on the selected route.
• OpenRouter: LLM routing and text model processing. Requests are routed to the underlying model operator (for example, Anthropic for Claude models).
• Groq: Language model inference for prompt tools and chat-based features.
• NVIDIA (hosted model APIs): Language and vision model inference for chat-based features and input safety checks.

Only providers relevant to the feature and processing route receive the request. Input files, accessible media links, prompts, settings, and relevant chat or project context may be sent for processing. Retention and permitted data use vary by provider and account settings; this list is not a promise of zero retention or identical terms across models.

6. Realtime Updates

MotionLab may use realtime infrastructure for job progress, queue status, notifications, and dashboard updates.

• Pusher: Realtime visual notifications and queue state sync.

7. Email

MotionLab may use email providers for account messages, receipts, support, transactional emails, and service notices.

• Resend: Transactional and administrative email routing.

8. Analytics, Logging, and Security

MotionLab uses first-party visitor analytics and operational logging on its service infrastructure. Our Cookie Policy describes visitor tracking; our Privacy Policy describes retention.

Site administrators may connect Google / YouTube to publish their own eligible public videos on MotionLab's official channel. This does not connect an ordinary user's Google account or automatically send their private work to YouTube. Independent AI assistants connected by users are separate services with their own privacy terms.

9. Changes to Subprocessors

MotionLab may add, remove, or replace subprocessors as the Service evolves. Subprocessors are used only as needed to operate, secure, support, and improve MotionLab.