Privacy Policy

Files you convert on this website are read and converted inside your browser. The file contents are never uploaded to our servers. What reaches us is metadata about each conversion — file names, sizes, detected formats, conversion warnings and error messages, and timing — sent over an encrypted (HTTPS) connection to operate quotas, debug failures, and understand which converters matter. Optional review sharing is described below. Our MCP/API endpoint has no browser to convert in; files sent there are processed on our servers in memory and are not stored after the result is returned.

Local editor projects and source media remain on your device unless you explicitly share them. Creating a shared rough-cut project uploads its text, source filenames and details, and edit decisions to our Convex backend. Invited, signed-in members can access it according to their role. We store revisions, comments, suggestions, memberships and expiring invitations to provide this service. When an owner enables simultaneous editing, applied edits sync immediately to invited members; saving a review checkpoint is separate. We retain edit operations for recovery and share account presence, selection and playhead position with project members.

Uploading review media requires a separate choice. Your browser creates full-source video or audio proxies, including material outside the selected timeline cuts. Hosted proxies are delivered through authenticated requests to project members. We measure stored and delivered bytes and client-reported processing time. Shared projects, feedback and proxies expire after 30 days; owners can delete them sooner. Expiry or revocation blocks subsequent access immediately, with stored content removed by scheduled cleanup. Members may retain copies already downloaded.

To resume interrupted uploads, completed proxies are cached in IndexedDB on your device. Expired cache entries are cleared on a later cache operation. You can delete a source proxy and its local cached copy in the shared workspace, or clear this site's browser storage. In single-editor review mode, unpublished drafts stay in the open tab; download a backup before leaving. In simultaneous mode, a pending request and attempted edit are saved in that tab’s session storage for retry after a reload, scoped to your account and project. Clear its recovery record or close the tab to remove it; expired records are removed when the project is reopened. Shared project media is separate from the original files on your disk.

Selects review links upload a fixed transcript and selection snapshot for anyone with the link to read. Signed-in reviewers may comment. These snapshots also expire after 30 days; their video packages are downloaded locally for you to send separately.

Without an account:a randomly generated anonymous identifier stored in your browser, a coarse first-touch attribution record (referring site, landing page, UTM parameters, browser language region, and timezone), and the conversion metadata above. Conversions made through our MCP/API endpoint are metered by a one-way hash of the caller's IP address; the IP itself is not stored.

With an account: additionally your email address, name, and sign-in method (email/password or Google), and your plan and usage balances.

Your recent conversion results (the output files, for a one-click re-download) are kept only in your own browser's storage on your device. They are never sent to us, and clearing your browser data or the "Clear history" link removes them.

Before checkout, queued files and conversion settings are saved in IndexedDB on your device so the job can be restored on return. They are removed after restoration; expired recovery copies are cleared on a later visit after one hour. Clearing this site's browser data also removes them. Delivery presets remain in your local browser or panel for Premiere Pro until you clear that storage. Preset exports contain settings, not your files. We also record offer views and checkout starts with your browser identity to measure purchases and completed jobs. Only verified Stripe payments count toward revenue reporting.

We do not use third-party advertising or cross-site tracking.

Billing runs through Autumn and Stripe. Your payment card details go directly to Stripe and never touch our servers; we see your plan, purchase history, and billing status. Stripe's handling of your data is covered by the Stripe Privacy Policy.

We use a small set of infrastructure providers to run the service: Convex (backend and database), Fly.io (hosting), Stripe and Autumn (billing), Resend (transactional email, such as password resets), and Google (optional sign-in). Each receives only what it needs to perform its function. We do not sell your data or share it with anyone for marketing.

Conversion metadata and account data are retained while the service operates or your account exists. To delete your account and its associated data, email us and we'll handle it promptly.

Questions, deletion requests, or anything unclear: [email protected]. More about who runs CutConvert is on the About page.