Privacy

CakeCut privacy

Daniel Duma operates CakeCut (formerly CloudCap) and is responsible for this privacy notice. It covers the CakeCut website and mobile apps. Editing can use storage on your device; signing in, cloud processing and purchases also involve CakeCut servers and the services described below.

Your account and projects

CakeCut stores account identifiers, your name and email, sign-in records, project and media metadata, processing status, and billing and credit records to operate your account. Server-backed projects can also contain caption text and timing. If you choose Google or Apple sign-in where available, that provider supplies the identity information needed to sign you in; CakeCut does not receive your Google or Apple password.

Media on your device

Device-local projects keep working video, audio and other local files in the app or browser's storage. Choosing a file does not mean every feature runs offline: transcription and translation can send the material they need for processing. Clearing app or site data, uninstalling, changing browser profiles or moving to another device can make local media unavailable. Account deletion does not remotely erase these device-local files.

Face retouch

Face retouch processes your selected video on this device. Face observations and masks stay in browser-owned or app-private storage and are never uploaded or sent to analytics. Prepared data is excluded from native backup and is deleted when you choose Remove face retouch, delete the local project or media, or replace its main video. Switching the effect off keeps the prepared data for reuse. Treatment settings can be saved with your project. This feature does not request camera access.

Cloud transcription and translation

Transcription sends extracted audio to CakeCut's processing service, including its Parakeeper gateway. Groq can process audio as a configured transcription provider or fallback. Translation sends caption text and language instructions to OpenAI or Google Gemini, depending on the enabled feature and provider configuration. A fallback can receive the same material when the first service cannot complete a request.

CakeCut keeps processing status and results needed for your project. Cloud-storage and other media-processing features can also transfer the media required by that feature. Processor-side storage and deletion are separate from files kept on your device; using a local editor is not a promise that no data leaves it.

Clean voice and behind-the-subject captions

Clean voice (background noise removal) sends the audio of the clip you clean to CakeCut's processing service through its Parakeeper gateway and returns the cleaned audio to your project. Voice polish and auto level run on your device and send nothing.

Behind-the-subject captions prepare person masks on your device on computers and in the CakeCut apps. In mobile browsers, sampled frames from the parts of the video that need masks are sent to CakeCut's own processing host, which returns the masks; the frames are written to temporary storage on that host and deleted when the job finishes.

Automatic editing and the edit assistant

Automatic edits and the edit assistant send transcript text with word timings, a summary of your project's clips, cuts and graphics, and your request to TypeSafe, which runs CakeCut's Jev decision model. Requests that need a language model also go to Anthropic. Visual checks, such as choosing the cover frame or the best take, send small downscaled frames to Cloudflare's Workers AI decision models; frames aren't stored. These features never send the video file or its audio. Using them is covered by the terms you accept when you create your account.

The assistant keeps its conversation with your project: on CakeCut servers for cloud projects, and in your browser's storage for device-local projects. Deleting the project deletes its conversation.

Android subject separation

The Android app includes Google ML Kit for subject separation. It processes the images on the device and does not send the input images or resulting masks to Google. ML Kit does send performance and usage metrics to Google and can contact Google to obtain models or updates. These SDK communications are separate from CakeCut's product analytics.

Purchases

Google Play handles Android in-app payments, Apple handles iOS in-app payments, and Stripe handles web payments. The payment provider receives the payment details. CakeCut receives purchase identifiers or tokens, product, subscription status and billing dates to verify purchases, provide paid access or credits, restore eligible purchases and handle billing disputes. CakeCut does not receive your full card details through these store or hosted-checkout flows.

Hosting, email and support

CakeCut uses Hetzner for server hosting and Cloudflare for website delivery and protection. Those services handle network information such as IP addresses and request details. Cloud media uses the configured storage service. When Resend email delivery is enabled, Resend receives the recipient address and message needed to send account emails. Messages you send to support contain your email address and anything you choose to include; avoid sending passwords, purchase tokens or private media.

Analytics and diagnostics

When enabled, PostHog receives product events and diagnostics, such as actions, device or browser information, account identifiers and error categories. CakeCut filters these events to exclude raw media, caption text, credentials and provider request bodies. Session replay is a separate configuration: it can record masked interface interactions, with private media and editor areas excluded. Availability and capture depend on the release configuration. Hosting and security logs, and ML Kit metrics, are separate from this setting.

Retention and deletion

Device-local files stay under your device or browser's storage controls. CakeCut account and project records remain while your account is active, unless you remove them sooner. After a deletion request, server cleanup is a separate operation; signing out does not mean it has finished.

Limited purchase and deletion records can remain to prevent duplicate credit grants, reconcile store transactions and handle accounting or legal obligations. Support messages, service-provider records and backup copies can also outlast the active account. CakeCut retains these records only for as long as reasonably needed for the stated operational, security, accounting or legal purpose. Providers and backup systems apply their own retention and rotation rules. No fixed deletion or retention deadline is promised. Ask the contact below about your data or a request's status.

Your choices and requests

Use Account → Delete account in the app, or follow /account-deletion on the website. You can also email [email protected] for access, correction, deletion or other privacy requests, including if you cannot sign in. We may need to verify that the account is yours. Deleting a CakeCut account does not cancel an Apple or Google Play subscription; manage that subscription with its store separately.

See also Contact and Support.