Privacy Policy

Browser-local Video Processing

The portrait, green-screen and background-replacement tools process selected video and audio in your browser. The GIF tool processes selected animation frames locally too. A replacement background image also stays in this browser. These workflows do not upload media, send it to an inference provider, or store it in our database. Portrait workflows download the model and runtime files from this site; color-key tools do not need a portrait model. Model telemetry and external requests from the processing worker are blocked.

The current task and output remain in page memory. Canceling stops processing; refreshing or closing the page clears the task and result. A downloaded file is saved on your device and is under your control.

Website Requests and Preferences

The hosting service receives ordinary website requests, including an IP address, browser request headers and requested URLs, to deliver the website, model and runtime files. These requests do not include selected video, audio, GIFs or replacement images. Hosting logs depend on the deployed hosting configuration.

Language and theme preferences can be stored in cookies or local storage. You can clear these using your browser settings. The public tools do not enable advertising or chat widgets. Public purchasing is currently unavailable while merchant approval and payment verification are completed; the payment handling described below applies when checkout is available.

Optional Google Sign-in

You can use the tools without an account. If you choose Google sign-in, Google shares your account identifier, name, email address, email verification status and profile image with us. We store account and session records in our PostgreSQL database hosted in Singapore. Login records can include your IP address, browser information and language. Authentication cookies keep you signed in; signing out ends that session. OAuth tokens stored for authentication are encrypted.

We request only basic identity permissions, not access to Gmail, Drive or your media. Signing in does not upload your selected files or save your editing media to your account; necessary task IDs and allowance records are linked to the account as described below. Account details shown on the site are masked from Clarity session recordings. We keep account records while your account exists and session records for authentication. To request account deletion, email contact@cutoutup.com. You can also revoke access in your Google account settings; this does not itself delete your CutoutUp account.

Purchases and Payment Records

When checkout is available and you choose to buy monthly browser access, Waffo provides the hosted checkout and payment service. To create and reconcile the purchase, we send Waffo your internal account identifier, order reference, product and quantity, price and currency, and the product binding needed to verify that purchase. We do not send your selected media, file names or media hashes to the payment provider.

Information you enter on the hosted checkout, such as payment and billing details, is handled by Waffo and its payment processors. CutoutUp does not receive or store your full card number or card security code. Our server receives payment status through signed notifications and authenticated payment queries. We store order and payment references, the account entitled to the purchased access, amounts and currency, tax and fee information returned by the provider, payment and refund status, and the associated allowance adjustments. These records let us confirm payment, activate access once, recover a purchase after signing in again, and handle refunds, disputes and support.

Necessary order, payment and entitlement histories are kept separately from optional behavior analytics. The 90-day behavior retention period does not delete those histories. They are retained as needed to provide purchased allowances, reconcile transactions, resolve refunds or disputes, and meet applicable recordkeeping obligations; this policy does not promise a fixed deletion period for financial records. For a privacy or account deletion request, contact contact@cutoutup.com. Declining optional analytics does not prevent a purchase or these necessary records.

Website Analytics

We use Google Analytics 4 (GA4) to measure website visits and tool usage only after explicit consent, regardless of location. Before consent, we do not load GA4 or send measurement requests, including cookieless requests. Microsoft Clarity also requires explicit consent. Scrolling, leaving the choice unanswered or choosing Not now does not grant permission. These services can receive sanitized public page URLs, browser and device information, approximate location and interaction data, and can use cookies or similar identifiers. All three advertising consent settings, Google signals and advertising personalization remain disabled.

The regional policy check uses Cloudflare's server-provided country code. This check does not collect, save or forward your IP address or return your country to the browser, and its response does not replace your consent. Normal hosting and authorized third-party network requests still use ordinary network transport. You can independently change GA4, Clarity and optional attribution through Analytics preference in the footer. The floating notice offers accept, decline and Not now controls. After scrolling more than one screen it collapses to a small preferences button; collapsing does not save a consent choice. Withdrawal stops subsequent tracking and clears GA cookies this site controls for its measurement ID; already transmitted data follows provider retention/deletion procedures.

Clarity also uses page layout and interactions such as clicks and scrolling to generate usage reports, heatmaps and session replays. Session replays reconstruct website interactions; they are not recordings of your selected video or audio.

Every media workbench, including file names, media details, background settings and input/output previews, is marked for Clarity content masking. We do not send selected video, audio, GIFs, replacement images, decoded frames or exported files to either analytics service. The processing worker has a separate policy that permits only downloads of first-party assets. Website analytics do not change where your media is processed.

Clarity may use first-party and third-party cookies and similar browser storage to associate visits and interactions, subject to browser settings and applicable consent requirements. You can block or clear cookies and site storage in your browser. Browser tracking protection and content blockers can also limit analytics collection. For provider details, see Google's privacy policy, Microsoft's privacy statement and the Clarity data collection documentation.

Your Control

You choose whether to select a file, start processing or download an output. You can stop processing at any time. Close or refresh the page to clear the local task. Downloaded files must be managed on your device; this site cannot delete them for you.

Policy Changes

We will update this page and its date when the preview's data handling changes.

Contact

For questions about this preview's data handling, email contact@cutoutup.com.

Necessary allowance and business records

A necessary signed random browser cookie identifies the allowance subject. Server records store task IDs, allowance usage, account ownership and purchase balances. These records are needed to run the service, prevent duplicate consumption and fulfill purchases. They do not depend on optional analytics permission. File reselection identifiers stay in device sessionStorage; accounts do not save your videos. Necessary records do not contain selected media, file names or media hashes.

Task start and outcome records may be shown as aggregate business statistics. A browser-reported successful outcome is not independent verification of the exported media. Orders, verified payments, refunds and grants remain separate authoritative business records. Declining analytics, Do Not Track (DNT) or Global Privacy Control (GPC) does not disable necessary allowance, payment or entitlement records.

First-party basic statistics

Basic statistics measure public page visits, file selection, processing start, success, failure or explicit cancellation, and download clicks. They are separate from GA4, Clarity and optional visitor tracking, and require their own explicit basic-statistics permission on public pages. An unanswered or deferred choice does not enable collection. Basic collection can also be disabled entirely. You can decline or stop basic statistics independently of optional analytics. DNT and GPC suppress basic collection.

Basic records use a random identifier held in the current document's memory to connect the steps of that visit. Document and task references are pseudonymous technical identifiers, not a claim that the records are entirely non-personal or impossible to associate with other records. Basic events do not store an account identifier or the necessary allowance cookie. Processing and download events reuse the existing random task ID, so authorized administrators can associate them with necessary task and account records when those records exist. Task IDs do not grant access to another user's task or media. Reloading, opening another page or another tab can create a new document session. Document sessions do not independently identify unique people or cross-device users.

We accept only public page paths, restricted source and medium categories, operator-allowlisted campaign labels, reduced referral categories, coarse browser and device categories, tool and task references, duration and resolution buckets, and fixed error or stage codes. To diagnose failures, we may also record fixed categories for processing operations, exceptions, processing mode, engine, background type, output format and Detailed-mode retries; raw exception text and stack traces are not recorded. We do not send selected video, audio, GIFs, images, decoded frames, file names, raw user-agent strings or raw IP addresses as analytics fields. Ordinary transport requests still reach the hosting service. A short-lived, rotating keyed digest of the transport IP may be used solely for abuse rate limiting; it is not a visitor identifier and is removed with short-lived rate-limit records.

Basic events are kept in memory for sending and retries. After explicit basic-statistics permission, a bounded pending-event queue may also use device sessionStorage for up to 24 hours to retry failed requests. This queue is not enabled solely by an exemption mode, and stopping basic statistics clears pending events. Pending records expire from use after 24 hours and are removed when the queue is next checked. The target retention period for basic event records is 30 rolling days. When the internal daily retention schedule is enabled, expired records are removed in bounded batches with retries and failure monitoring; collection cleanup and authenticated maintenance remain fallbacks. Records awaiting a retry or backlog cleanup can remain longer. Business histories are stored separately and are not deleted by this analytics retention period. Delivery is best effort and a failed statistic never blocks processing, downloading or purchasing.

Optional analytics preferences

GA4, Clarity, longer-lived first-party visitor identifiers and optional attribution require explicit permission. Existing explicit declines remain effective; you may later reauthorize each service. Basic-statistics permission never enables GA4 or Clarity. DNT and GPC suppress both third-party services. Each service's loading failures are independent and do not authorize additional first-party collection. Public pages require basic-statistics permission even if a legacy server configuration specifies an exemption mode.

Optional first-party behavior records use restricted attribution, device/browser categories and error codes. Their target retention period is 90 rolling days; the enabled internal daily schedule or authenticated maintenance performs deletion, and records awaiting a retry or cleanup can remain longer. Optional browser identifiers can be stored on your device only when that preference allows them. Any account identifier sent to GA4 while signed in also requires optional attribution permission; GA4 permission alone does not enable it. You can change preferences using the controls on public pages and can clear browser storage in your browser settings. Previously collected third-party records are subject to the providers' retention and deletion processes. Necessary financial and entitlement histories are not erased by withdrawing analytics permission.