Privacy Policy
Last updated: March 2026
Overview
Section titled “Overview”modelBridge.ai is designed with privacy as a core principle. The plugin operates primarily on your local machine, and your data stays under your control.
What We Collect
Section titled “What We Collect”From the Plugin
Section titled “From the Plugin”modelBridge.ai collects minimal data necessary to operate:
- License validation — your email address and subscription status are checked against our license server to verify your subscription is active
- Pricing data — the plugin fetches curated pricing information from a remote source to display cost estimates (no user data is sent)
What We Do NOT Collect
Section titled “What We Do NOT Collect”- No analytics or usage tracking
- No telemetry about which models you use
- No generation history or prompts
- No media files or content
- No crash reports (unless you explicitly send them)
Where Your Data Lives
Section titled “Where Your Data Lives”API Key
Section titled “API Key”Your fal.ai API key is stored in two places, both on your local machine:
- The CEP panel’s
localStorage(browser storage within Premiere Pro) - A local file in the extension’s data directory
Your API key is never sent to modelBridge.ai servers. It is transmitted only between your machine and fal.ai’s API for generation requests.
Generation History
Section titled “Generation History”All generation history, including prompts, parameters, cost records, and result metadata, is stored locally on your machine in localStorage and local data files. This data never leaves your computer unless you explicitly export it.
Media Files
Section titled “Media Files”When you generate content:
- Source media (images, video frames) is extracted locally from Premiere Pro
- The media is uploaded directly from your machine to fal.ai’s servers for processing
- Generated results are downloaded from fal.ai to your machine
- fal.ai processes and stores media according to their own privacy policy
modelBridge.ai does not route your media through any intermediate server. The upload goes directly from your machine to fal.ai.
Learned Constraints
Section titled “Learned Constraints”The self-learning validation system stores model constraint data (dimensions, duration limits, file size limits) locally on your machine. This data is derived from fal.ai error messages and is not personal information.
Your Media and Data
Section titled “Your Media and Data”Your source clips and generated results never pass through modelBridge servers:
- Source media is uploaded directly from your machine to fal.ai for processing — modelBridge’s local server handles the extraction and upload, but the data goes straight to fal.ai
- Generated results are downloaded directly from fal.ai to your local machine
- Your API key is stored locally and transmitted only to fal.ai for authentication — never to modelBridge
- Prompts and parameters are sent directly to fal.ai for generation — modelBridge does not log, store, or transmit this data to any other destination
- No analytics or tracking — modelBridge does not collect usage data, telemetry, or behavioral information of any kind
All user data — installed models, settings, generation history, cost logs, learned constraints — lives on your machine and stays on your machine.
Third-Party Services
Section titled “Third-Party Services”fal.ai
Section titled “fal.ai”modelBridge.ai communicates directly with fal.ai’s API. When you generate content, the following is sent to fal.ai:
- Your fal.ai API key (for authentication)
- Source media (images, video, audio) when required by the model
- Text prompts and generation parameters
- Your IP address (standard HTTPS communication)
fal.ai’s handling of this data is governed by fal.ai’s privacy policy. modelBridge.ai has no control over how fal.ai processes or retains your data.
License Server
Section titled “License Server”modelBridge.ai contacts its license server to validate your subscription. Only your account email and a license identifier are transmitted. No generation data, media, or usage patterns are shared.
Data Deletion
Section titled “Data Deletion”Since all generation data is stored locally, you can delete it at any time by:
- Clearing the extension’s
localStoragein Chrome DevTools (localhost:8089) - Deleting the extension’s data directory files
- Uninstalling the extension (removes all local data)
To delete your modelBridge.ai account, contact support.
Changes to This Policy
Section titled “Changes to This Policy”We will update this page if our data practices change. The “Last updated” date at the top reflects the most recent revision.
Contact
Section titled “Contact”For privacy questions or data requests, contact us at support@modelbridge.app.