Overview
This Privacy Policy explains how Mocut handles information when you visit mocut.app, use editor.mocut.app, create an account, edit projects, upload or generate media, use AI tools, manage billing, or contact us.
Mocut combines local browser editing with cloud-backed features. Some project data may stay in your browser unless you choose or trigger a cloud feature. Other features require Mocut servers and third-party providers to process account, billing, media, prompt, and generation data.
When you sign in, Mocut automatically saves project changes and project-associated chat history to your account. Media backup depends on your plan, available storage, and successful upload; some source files can remain only on your device. Using an AI feature can send relevant content to a provider even when the source media or search index is stored locally.
This policy explains data processing; accepting the Terms or reading this policy is not blanket consent to every use of personal information.
Information we collect
The information Mocut collects depends on how you use the service.
- Account information, such as email address, authentication identifiers, sign-in provider details, and account status.
- Project and media information, such as project metadata, uploaded files, generated assets, captions, transcripts, audio, video, images, filenames, asset references, and editor state.
- AI task information, such as prompts, chat messages, timeline context, scripts, voice settings, voice samples and consent recordings, microphone recordings for voice typing, reference media, search queries and indexes, generation parameters, model choices, job status, provider task ids, account-linked chat identifiers, costs, and credit usage.
- Billing information, such as plan, subscription status, Stripe customer and subscription ids, billing portal activity, transaction metadata, and records needed for accounting and support. Mocut does not store full payment card numbers.
- Usage and device information, such as API requests, feature and credit usage, logs, errors, diagnostics, browser and device details, IP address and the approximate location it indicates (country, region and city), security signals, and timestamps. Our infrastructure providers also receive network information needed to deliver and secure the service.
- For signed-in assistant use, bounded diagnostic copies of the message you send and the assistant reply, the turn outcome and reason, timing, model, tool counts, and any thumbs-up or thumbs-down feedback. We also collect browser error messages and stack traces, page paths without query strings, and application build information to investigate editor failures. These reports do not include attachment files or project snapshots.
- First-visit information, such as the landing-page address, referring site, campaign tags, time of arrival, browser family, and device category. The landing address excludes its query and fragment, and the referrer is reduced to its origin; campaign tags are recorded separately. This information can be associated with your account when you sign up.
- Export events, such as format, resolution, approximate duration category, success or failure, browser and device category, and your account identifier when signed in. These records help us understand export use and reliability.
- Product milestones for signed-in accounts: whether and when you first and last opened the editor, added or recorded your own media, started an export, viewed plans, or started a checkout, and a count of how often each happened. These records contain no file names, media, or project content.
- Communications, such as feedback, support requests, bug reports, admin messages, and email delivery metadata.
Information stored locally
Editing data, media, project state, chat history, and settings can be stored in your browser using local storage, IndexedDB, or similar browser storage. Local data can remain until you use the relevant deletion controls, clear site data, or your browser removes it. Signing out ends your session but does not erase local projects, media, or settings.
Clearing browser data does not by itself delete cloud copies, provider records, or your account. Likewise, a cloud deletion request does not erase files you have downloaded or copies on other devices.
Local browser storage is not a backup. If you need to keep important media or projects, export or back them up separately.
How we use information
- Provide the editor, project sync, asset storage, exports, AI tools, credits, billing, account features, and support.
- Send prompts, reference media, transcripts, scripts, and job data to AI providers when needed to complete requested generation or analysis tasks.
- Process payments, manage subscriptions, prevent duplicate checkout, grant credits, reconcile usage, and detect billing or provider failures.
- Secure the service, verify sessions, prevent abuse, enforce limits, investigate errors, detect fraud, and protect users and providers.
- Improve Mocut by debugging, measuring reliability, understanding feature usage, and prioritizing product work.
- Understand how people first find Mocut by connecting first-visit and campaign information with signups.
- Understand where new accounts stop getting started, by counting how many reach each product milestone after signing up.
- Send transactional emails such as signup confirmations, password resets, billing notices, support replies, and service alerts.
- Comply with legal obligations, enforce terms, and respond to lawful requests.
Legal bases for processing
Where the GDPR or similar law applies, our legal basis depends on the purpose. Information needed for an account, payment, or requested AI task is necessary to provide that part of the service; if you do not provide it, that feature may be unavailable.
- Contract: processing necessary to provide your account, save projects, perform requested editing and AI tasks, manage subscriptions, and provide related support.
- Legitimate interests: keeping the service secure, preventing fraud and abuse, diagnosing failures, understanding feature use and how people find the service, measuring reliability, and handling disputes, where those interests are not overridden by your rights and consent is not required.
- Legal obligations: maintaining required financial records and responding to legally binding requests.
- Consent: optional marketing or other processing where consent is required. You can withdraw consent at any time; withdrawal does not affect the lawfulness of earlier processing.
AI providers and generated media
When you use AI features, Mocut may share the inputs needed for that task with model or media providers. Inputs can include prompts, selected project context, uploaded or generated media, image references, video frames, audio, transcripts, scripts, captions, and generation settings.
Provider processing is required for features such as agent chat, image generation, image editing, video generation, voiceover, music, sound effects, transcription, voice typing, video or audio analysis, and AI media search. Requests can pass through an AI gateway or routing service to the selected model host. Task references and account-linked user or chat identifiers may accompany requests for operation, usage accounting, and conversation continuity.
When you activate voice typing, a microphone recording is sent to ElevenLabs for transcription. The returned text can be edited and sent as a chat message. When the assistant analyzes video or audio, selected media excerpts or a prepared preview can be sent to an analysis model through OpenRouter.
Reference images, audio, and video can be uploaded to a generation provider or made available through temporary media links. Media search can send queries, filenames, descriptions, generation prompts, and transcript excerpts to an AI provider to create search representations. Those indexes may be stored in your browser or in cloud storage; local index storage does not mean the indexing is performed entirely on your device.
Provider policies, contractual terms, account settings, retention, and safety rules can differ. This policy does not promise that every provider offers zero retention or excludes every input from model training. Contact support before submitting content that requires a specific processing or confidentiality arrangement.
Custom voices and recordings
Creating a custom voice sends the requested voice description or sample recordings, and where required a spoken consent recording, to the selected voice provider. The provider can store the resulting voice for later speech generation. Mocut stores details such as the voice name, description, provider identifier, and account association.
Only submit recordings and personal information you are authorized to use. Voice cloning requires the applicable rights confirmation and any provider consent or verification steps. These recordings may identify the speaker and can contain other personal information.
Deleting a saved custom voice removes its active association in Mocut and, where applicable, queues deletion from the provider after the last active association is removed. Failed provider deletion requests are retried. Provider deletion is separate, can take longer, and does not delete audio already generated with that voice. Contact support@mocut.app for erasure requests covering recordings, provider-held voice data, or generated files.
Retention
Mocut keeps information for as long as needed to provide the service, maintain accounts, store projects and assets, process billing, resolve disputes, comply with legal obligations, enforce terms, secure the service, and keep operational records.
The cleanup periods below describe when files become eligible for removal, not a guarantee that every copy is erased at that instant. Scheduled processing, active references, provider dependencies, failures, caches, and backups can affect timing. Provider-held copies follow the applicable provider arrangements.
Account records and project documents are kept while needed for your account and requested service. Job, usage, billing, accounting, security, support, and legal records may outlast deletion of a project or media file where needed to settle charges, investigate failures or abuse, resolve claims, or meet legal obligations. Their retention depends on that purpose and the applicable recordkeeping requirements.
- Unsaved generation previews, temporary provider-reference files, and voice-preview audio normally become eligible for cleanup after 24 hours when no longer protected by required references. Unreferenced temporary asset thumbnails can be cleaned up after seven days.
- Uploads, generated outputs, and exports more than 30 days old can become eligible for unused-media cleanup when unreferenced and not protected by library saving or retention rules. Unkept generated outputs can qualify even if their originating project still exists.
- When paid cloud-storage access ends, existing uploads, generated outputs, and exports are normally retained for three months after the applicable paid-access end date. After that, cleanup can remove them even if older projects reference them. Resuming paid access before cleanup removes this expiry; explicit deletion can remove them earlier.
- Ordinary user-deleted cloud assets normally become eligible for physical removal after a one-hour delay; temporary or expired assets can be removed sooner. Removing a clip does not necessarily delete its source media or project-history copies. Deleting a project can schedule its associated assets for removal, while assets still used by other projects are preserved.
- Projects exceeding a plan's active-project limit can be archived and scheduled for deletion, normally after three months or at the existing paid-storage retention deadline. The product shows the deletion date. Archived projects can be downloaded, and a paid plan with capacity can restore them before deletion.
- Content-bearing inputs and results of completed jobs normally become eligible for redaction after 30 days. Active reservations, pending completion work, and other settlement dependencies can delay cleanup. Limited billing, usage, status, and duplicate-request prevention records can remain after content is removed.
- Stored system-error records are scheduled for cleanup after 90 days and export-event records after 365 days. Account deletion removes account-linked export records and removes the account association from retained system-error records.
- Assistant diagnostic copies, reply feedback, and browser-error reports are scheduled for deletion 90 days after collection and are removed when the associated account is deleted. This diagnostic retention period is separate from chat history saved as part of your projects.
- Product milestone records are scheduled for deletion 90 days after the milestone last occurred and are removed when the associated account is deleted.
- Local browser data remains subject to your deletion controls and browser storage management. Deleting local data and deleting cloud data are separate actions.
Security
Mocut uses technical and organizational safeguards designed to protect information, including authentication checks, access controls, rate limits, provider-key isolation, service-role boundaries, and operational monitoring. No online service is perfectly secure, and Mocut cannot guarantee absolute security.
You are responsible for securing your account, browser, devices, exports, and any files you download or publish.
Your choices and rights
Depending on your location and the applicable conditions, you may have rights to access, correct, delete, receive a portable copy of, restrict, or object to processing of your personal information. You can withdraw consent where processing relies on consent and object to direct marketing at any time. You may complain to your local data protection authority, including where you live or work in the EU or EEA.
You can delete projects or assets, manage saved voices, clear local browser data, and manage billing using the relevant product controls. The account menu offers permanent account deletion, which cancels active subscriptions, removes account content, and clears this browser's account data after successful completion. Canceling a subscription or signing out alone does not delete your account. Contact support@mocut.app for help or other privacy requests, preferably from your account email.
Account deletion can finish in stages. Cloud-file cleanup and provider-voice erasure may continue in the background. Stripe retains past payment and invoice records, and limited deletion, security, and required financial records may remain; retained operating-cost records are anonymized where applicable. Downloaded exports and copies on other devices are not erased by the account-menu action.
We may request information reasonably necessary to verify your identity and locate the relevant data. We respond within the period required by applicable law, generally one month for GDPR requests, and will explain any permitted extension or reason we cannot fully comply. Do not send passwords or payment-card details with a request.
Marketing communications
Mocut may send product updates or marketing emails if you sign up for them or if allowed by law. You choose this with an optional checkbox when you create your account, and we record when you made the choice. You can unsubscribe at any time using the unsubscribe link in any such email, the Product emails switch in your account menu, or by contacting us. Transactional messages, such as account, security, billing, or service emails, may still be sent when needed.
Children
Mocut is not directed to children under 13 or people below a higher minimum age required in their location. The Terms also require users to be able to enter a binding contract. Where consent is the legal basis, a child's ability to consent depends on local law; age 13 is not a universal consent threshold. If you believe a child has provided personal information without the required eligibility or authorization, contact support@mocut.app so we can review and take appropriate action.
International processing
Mocut and its providers may process information in countries other than where you live, including where the selected model host or infrastructure provider operates. Those countries may have different data protection laws. International transfers are subject to applicable data-protection requirements. Contact support@mocut.app for information about the destinations and transfer safeguards applicable to the feature you use.
Changes to this policy
Mocut may update this Privacy Policy as the service changes. If changes are material, we will provide notice through the product, website, email, or another reasonable method. The "Last updated" date shows when this policy was last revised.
Contact
Questions, requests, or privacy concerns can be sent to support@mocut.app.