Trust & compliance
Subprocessors
Effective Date: July 8, 2026
MotionLab uses third-party service providers and subprocessors to operate the Service. This page lists categories of subprocessors that may process account data, uploaded assets, prompts, outputs, logs, billing metadata, or usage data depending on how you use MotionLab.
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.
- LemonSqueezy: 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: Static asset delivery (CDN) and secure media storage.
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.
- 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.
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 may use analytics, diagnostics, logging, monitoring, and abuse-prevention providers to keep the Service reliable and secure.
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.