Effective date: November 13, 2026 Last updated: November 13, 2026
This Cookie Policy explains how Cutwise, operating Cutwise ("Cutwise," "we," "us," or "our"), uses cookies, local storage, session storage, pixels, software development kits and similar technologies when you access or use the Cutwise website and related Services.
It should be read together with our Privacy Policy and Terms of Use.
This Policy applies particularly to technologies stored on, or accessing information from, your browser, computer, phone or other terminal equipment.
Because Cutwise is operated by a company established in Romania, our use of these technologies is subject, where applicable, to Romanian and European Union law, including:
- Law no. 506/2004 regarding the processing of personal data and the protection of privacy in the electronic communications sector;
- Regulation (EU) 2016/679, the General Data Protection Regulation ("GDPR");
- Law no. 190/2018 concerning measures for implementing the GDPR;
- and other applicable Romanian and European Union legislation.
Contents
- What cookies are
- What Cutwise uses
- Page-view and product-usage measurement
- Local and session storage
- The Cutwise mobile application
- Managing cookies and similar technologies
- Changes to this Policy
- Contact
1. What Cookies Are
Cookies are small text files that a website stores in your browser or device.
Cookies can allow a website to remember information between page loads or visits.
For example, cookies may allow a website to remember:
- that you are signed in;
- your session;
- your privacy preferences;
- a checkout that you started;
- where you arrived from;
- a referral code;
- a campaign;
- your language;
- or other settings.
Cookies may be set directly by Cutwise.
These are commonly referred to as first-party cookies.
Cookies may also be set by another company whose services appear on or are used by the Cutwise website.
These are commonly referred to as third-party cookies.
Different cookies may remain for different lengths of time.
Session cookies
Session cookies normally expire when the browser session ends.
Persistent cookies
Persistent cookies remain for a defined period or until you delete them.
Not all browser storage is technically a cookie.
Cutwise may also use:
- local storage;
- session storage;
- pixels;
- SDK identifiers;
- browser identifiers;
- server-side identifiers;
- and similar technologies.
For simplicity, parts of this Policy may refer collectively to these technologies as "cookies and similar technologies."
2. What Cutwise Uses
Cutwise may use the following categories of cookies and similar technologies:
- strictly necessary technologies;
- authentication technologies;
- security technologies;
- payment technologies;
- referral technologies;
- preference technologies;
- analytics technologies;
- attribution technologies;
- advertising-measurement technologies;
- testing technologies;
- and local or session storage.
The exact technologies that apply depend on:
- which Cutwise features are currently enabled;
- which providers we use;
- whether you are signed in;
- whether you start a checkout;
- whether you arrive through a referral link;
- and the privacy choices you make.
We do not intentionally activate optional analytics, advertising or tracking cookies before obtaining consent where Romanian or EU law requires consent.
Strictly necessary technologies may operate without consent where they fall within an applicable legal exception.
Strictly Necessary Technologies
Strictly necessary cookies and storage are used where required to provide functionality that you explicitly request.
Examples may include:
- maintaining authentication;
- maintaining a secure session;
- preventing fraud;
- remembering cookie choices;
- completing checkout;
- protecting forms;
- maintaining security;
- keeping a requested application state;
- and associating an active checkout with the correct Cutwise account.
Blocking strictly necessary technologies may prevent some parts of Cutwise from working correctly.
For example, you may be unable to:
- remain signed in;
- access your account;
- complete checkout;
- manage billing;
- or securely use account functionality.
Authentication Cookies
Where Cutwise uses cookie-based authentication, authentication technologies may be used to:
- keep you signed in;
- validate your session;
- refresh authentication tokens;
- protect login flows;
- prevent unauthorized access;
- and identify the authenticated Cutwise account.
Supabase authentication
Where Cutwise uses Supabase authentication, Supabase may create authentication cookies or browser-storage entries.
Depending on the Supabase implementation, names may include values containing:
sb-followed by a Supabase project identifier and authentication-related suffixes.
Authentication data may also be split across multiple storage values where necessary because of browser size limits.
These technologies may contain:
- session information;
- access tokens;
- refresh tokens;
- code-verification information;
- or other authentication state.
Their purpose is to:
- authenticate you;
- maintain your session;
- and protect your account.
They are not intended for advertising.
Provider-managed cookie names and storage formats can change when Supabase changes its implementation.
Payment Technologies
Cutwise intends to use or may use Stripe for website payments.
When Stripe is enabled, Stripe may set cookies or use other browser technologies on:
- Stripe Checkout;
- Stripe-hosted billing pages;
- payment forms;
- customer billing portals;
- or other payment-related interfaces.
Stripe may use these technologies to:
- securely process payments;
- prevent fraud;
- authenticate payment activity;
- maintain checkout state;
- comply with financial regulations;
- and protect its infrastructure.
Stripe controls the exact names, content and duration of technologies used on Stripe-hosted systems.
You should review Stripe's own privacy and cookie information for details about Stripe-controlled technologies.
Cutwise does not need to store your full payment-card number in a Cutwise cookie in order to process your subscription.
Checkout State
Where Cutwise allows a person to begin checkout before completing account creation or before a subscription is fully linked to an account, we may use a cookie or storage value such as:
cutwise_checkoutor another implementation-specific identifier.
It may contain a random or pseudonymous reference associated with the checkout.
Its purpose may be to:
- associate a purchase with the account created afterward;
- recover an interrupted checkout;
- prevent duplicate checkout prompts;
- or connect a Stripe session to the appropriate Cutwise account.
The exact retention period should be limited to what is reasonably necessary for the checkout process.
Before publication, this section should be updated with the actual cookie/storage name and lifetime used by Cutwise.
This technology is not intended for behavioral advertising.
Referral Technologies
Cutwise provides or intends to provide a referral program.
A Cutwise user may receive a unique referral code or link.
For example:
https://usecutwise.com/?ref=TYUG3SWhen another person arrives through that link, Cutwise may store information necessary to remember who referred that visitor.
We may use a referral cookie or local-storage value such as:
cutwise_refor another implementation-specific name.
Referral information may include:
- referral code;
- referring Cutwise account;
- referral identifier;
- click identifier;
- arrival date;
- campaign;
- landing page;
- or associated referral state.
The purpose is to:
- remember the referral;
- attribute a later signup;
- attribute a qualifying subscription;
- award the appropriate referral credit;
- prevent referral fraud;
- and display the appropriate referral offer.
For example, where Cutwise offers $10 in Cutwise credit to both the referring user and the referred user after a qualifying subscription, referral information is needed to determine who qualifies for the reward.
Referral lifetime
Cutwise may use a referral attribution period such as 30 days.
If implemented, this means that a qualifying purchase completed during that period may be attributed to the referral.
The exact attribution period displayed in the referral program or applicable Referral Terms controls.
If Cutwise changes the period, this Policy and the referral disclosures should be updated accordingly.
What a Cutwise credit means
Referral credits are promotional Cutwise account balances.
Unless the referral offer expressly says otherwise:
- credits are not cash;
- cannot be withdrawn to a bank account;
- cannot be exchanged for cash;
- cannot normally be transferred;
- and may be applied only toward eligible future Cutwise subscription charges.
Specific referral terms may impose:
- expiration;
- eligibility;
- anti-fraud conditions;
- per-account limits;
- or other restrictions.
Attribution Technologies
Where Cutwise performs marketing attribution, we may record information about how a visitor reached the website.
This may include:
- source;
- medium;
- campaign;
- content;
- search term;
- landing page;
- referring host;
- timestamp;
- advertising click identifier;
- referral identifier;
- or similar information.
Cutwise may use a value such as:
cutwise_attror another implementation-specific identifier.
Where this storage is not strictly necessary, it will be activated only after any legally required consent has been obtained.
Retention should be limited to the attribution window Cutwise actually uses.
For example, a campaign attribution value may be retained for approximately 28 or 30 days where that accurately reflects the implementation.
Offer and Experiment Technologies
Cutwise may test:
- pricing presentation;
- landing pages;
- onboarding;
- calls to action;
- offers;
- referral messaging;
- plan presentation;
- or other user-interface variations.
To ensure that a person consistently sees the same test variation, Cutwise may store:
- a random experiment identifier;
- test assignment;
- variant;
- or similar value.
Possible names may include:
cutwise_experiment
cutwise_offeror another implementation-specific value.
These names should not be published as actual cookie names until they are implemented.
Where an experiment is non-essential and involves accessing or storing information in the user's terminal equipment, the experiment technology will be subject to any consent requirement that applies.
Experiment technologies should not be used to circumvent a user's analytics or advertising preferences.
Advertising-Measurement Technologies
Cutwise may advertise through platforms such as:
- TikTok;
- Meta / Facebook / Instagram;
- Google;
- or other advertising providers.
These technologies should only be included in the live version of this Policy if Cutwise actually activates the relevant provider.
In Romania and the EEA, advertising and tracking technologies that are not strictly necessary will not be activated until the legally required consent has been obtained.
Meta / Facebook / Instagram
If Cutwise uses the Meta Pixel, Meta may set technologies such as:
_fbp
_fbcand other Meta-controlled identifiers.
If a visitor arrives from a Facebook or Instagram advertisement, Cutwise may receive or store Meta advertising click information.
The Meta Pixel and related server-side conversion functionality may help us measure whether a person later:
- visits Cutwise;
- creates an account;
- starts checkout;
- begins a trial;
- subscribes;
- renews;
- or performs another conversion event.
Where enabled and permitted, server-side events may contain:
- hashed email;
- hashed name;
- account identifier;
- subscription information;
- conversion information;
- IP address;
- browser information;
- and advertising identifiers.
Hashing allows matching and should not be treated as equivalent to anonymization.
Meta may combine information with data from Facebook, Instagram and other Meta services under its own privacy practices.
Google advertising
Where Cutwise uses Google advertising or conversion-measurement products, Google may process:
- advertising click IDs;
- browser information;
- campaign information;
- conversion events;
- purchase events;
- and other attribution information.
These technologies will be subject to legally required consent.
Analytics Cookies
Cutwise may use analytics to understand:
- how people find the website;
- which pages they use;
- which features they use;
- where they encounter errors;
- whether they start checkout;
- whether they subscribe;
- how referral flows perform;
- and how the Services can be improved.
Analytics technologies that are not strictly necessary will be activated only after legally required consent.
Google Analytics
If Cutwise uses Google Analytics, technologies may include cookies whose names begin with:
_gaand related Google Analytics identifiers.
Google Analytics may distinguish:
- browsers;
- users;
- sessions;
- page views;
- and events.
Information may include:
- pseudonymous identifier;
- page;
- referrer;
- approximate geographic region;
- device;
- browser;
- traffic source;
- campaign;
- and interaction events.
Where configured, Cutwise may report events such as:
- account creation;
- pricing-page interaction;
- checkout initiation;
- subscription;
- renewal;
- cancellation;
- and refund.
Cutwise should not intentionally send through the analytics integration:
- full card numbers;
- passwords;
- uploaded videos;
- or other information that is unnecessary for analytics.
PostHog
If Cutwise uses PostHog, PostHog may store cookies and matching local-storage information.
PostHog identifiers often include names beginning with:
ph_followed by a project identifier.
PostHog may help Cutwise understand:
- website use;
- page navigation;
- feature use;
- onboarding;
- account creation;
- subscription funnels;
- processing activity;
- and experiments.
Where we associate PostHog activity with a Cutwise account, it may receive an internal Cutwise account identifier.
If session replay is enabled:
- it will be subject to any applicable consent requirement;
- sensitive inputs should be masked;
- payment data should not be intentionally captured;
- passwords should not be intentionally captured;
- and uploaded videos should not be intentionally recorded through session replay.
Masking reduces risk but cannot guarantee that no personal data will ever appear.
3. Page-View and Product-Usage Measurement
Where you have provided required consent, Cutwise may use analytics tools to measure activity across the website and application.
This may include:
- page views;
- landing pages;
- traffic sources;
- pricing interaction;
- referral page use;
- account creation;
- upload initiation;
- successful uploads;
- failed uploads;
- AI processing;
- edit completion;
- exports;
- subscription checkout;
- successful payments;
- failed payments;
- plan upgrades;
- cancellations;
- renewals;
- referral conversions;
- and other product interactions.
Google Analytics Measurement
Google Analytics may measure:
- page views;
- traffic sources;
- plan selection;
- account creation;
- checkout;
- and general engagement.
Where technically implemented, Cutwise's backend may also send certain subscription events.
Such events may include:
- plan;
- transaction identifier;
- amount;
- currency;
- purchase status;
- renewal;
- refund;
- or cancellation.
Cutwise should use pseudonymous identifiers wherever practical.
We do not intend to send Google Analytics:
- your full payment-card details;
- account password;
- uploaded videos;
- or other content unnecessary for analytics.
Vercel Web Analytics
Cutwise is hosted on Vercel.
Where Vercel Web Analytics is enabled, it may measure website traffic and page views.
Vercel's implementation may operate differently from traditional cookie-based analytics.
Whether a specific Vercel feature uses cookies or other identifiers depends on the Vercel product and configuration used by Cutwise.
Product Analytics
A product analytics provider may be used to measure Cutwise product usage.
Events may include:
- user session;
- page;
- feature interaction;
- edit workflow;
- subscription flow;
- processing performance;
- account state;
- referral flow;
- or error.
Where the user is authenticated, product activity may be connected to an internal Cutwise account identifier.
Any analytics that requires terminal storage or access will be subject to the consent rules described above.
4. Local and Session Storage
Cookies are not the only browser-storage technology used by Cutwise.
The Cutwise web application currently uses or may use local storage and session storage to remember application state.
Local storage can remain in a browser until:
- the user clears it;
- Cutwise removes it;
- browser policies remove it;
- or application logic expires it.
Session storage usually lasts until the relevant browser tab or session ends.
Current Cutwise Application Storage
Depending on the version of Cutwise that you use, local browser storage may include entries relating to:
Edit history
cutwise-edit-historyThis may store information used to display your edit history in the current browser.
It may include information such as:
- job identifier;
- video title;
- completion information;
- thumbnail or preview information;
- Trash state;
- Trash date;
- or related UI metadata.
Actual video files should not be stored directly in a normal local-storage value.
Current view
cutwise-current-viewThis may remember the edit or result that the user was viewing so that refreshing the page can return the user to the appropriate Cutwise screen.
It may contain information such as:
- application phase;
- job identifier;
- or current state.
Account profile
Cutwise may store local account-profile state, for example under a value such as:
cutwise-account-profileThis may include locally cached information such as:
- display name;
- email;
- profile-image reference;
- or related profile UI state.
The production version should not rely on local storage as the authoritative source for sensitive account authentication.
Account settings
Cutwise may store user preferences under a value such as:
cutwise-account-settingsThis may include:
- default export quality;
- default video format;
- auto-caption preference;
- silence-removal preference;
- false-start-removal preference;
- processing-notification preference;
- and other Cutwise settings.
These values allow the browser to remember preferences between visits.
Billing interface state
Cutwise may temporarily or locally store billing-interface information under a value such as:
cutwise-account-billingThis may include information displayed in the Billing UI, such as:
- plan;
- billing cycle;
- renewal date;
- billing display preferences;
- or receipt preference.
When Stripe is integrated, authoritative payment information should come from Cutwise's backend / Stripe rather than relying solely on browser local storage.
Sensitive card information should not be stored in Cutwise local storage.
Referral state
Cutwise may store:
- referral code;
- referral attribution;
- referral arrival;
- or related campaign state
to remember an active referral.
The actual name and duration should be documented once the referral backend is finalized.
Search and interface state
Cutwise may use browser storage for:
- current filters;
- UI preferences;
- feature state;
- dismissed notices;
- or similar convenience functionality.
Security of Local Storage
Browser storage is accessible to scripts running within the relevant website origin.
For this reason, Cutwise should not intentionally store highly sensitive secrets such as:
- raw passwords;
- full card numbers;
- card security codes;
- private API keys;
- or similar credentials
in browser local storage.
Authentication tokens should be handled using security controls appropriate to the authentication architecture used.
5. The Cutwise Mobile Application
If Cutwise provides a native mobile application, the application may use:
- device storage;
- secure storage;
- application preferences;
- notification identifiers;
- SDK identifiers;
- and similar mobile technologies
rather than ordinary website cookies.
A native mobile application may still open Cutwise web pages.
When a web page is opened inside:
- an in-app browser;
- embedded browser;
- browser view;
- or external browser,
website cookie and storage rules may apply to that page.
Device Permissions
Depending on the functionality offered, a mobile app may request permission for:
- photo library;
- local files;
- camera;
- microphone;
- notifications;
- or other device functionality.
These permissions are separate from website cookie consent.
You can normally manage device permissions through your iOS or Android settings.
Advertising Tracking on Mobile
If Cutwise later uses mobile advertising attribution, platform-specific requirements may apply.
For example, where Apple's App Tracking Transparency framework applies, Cutwise would request the required ATT permission before performing covered tracking.
Refusing tracking permission must not prevent use of core Cutwise editing functionality unless the tracking is genuinely necessary for the requested feature.
Core functions such as:
- authentication;
- security;
- subscription entitlement;
- video processing;
- and strictly necessary diagnostics
may operate independently where permitted by law.
6. Managing Cookies and Similar Technologies
You can control cookies and similar technologies in several ways.
Cutwise Cookie Banner / Privacy Center
Where Cutwise uses optional technologies requiring consent, we will provide a cookie banner or similar privacy-preference interface.
You should be able to choose between options such as:
- Accept all
- Reject optional
- Manage preferences
or functionally equivalent controls.
Optional categories may include:
- Analytics;
- Advertising;
- Personalization;
- or similar categories.
Strictly necessary technologies cannot generally be disabled through the cookie banner because they are necessary to provide requested functionality.
Rejecting Optional Cookies
Rejecting optional cookies should not prevent you from using the core Cutwise service.
For example, refusing analytics or advertising cookies should not prevent you from:
- creating an account;
- uploading a video;
- processing an edit;
- exporting an edit;
- purchasing a subscription;
- or managing your account,
except where a specific storage technology is strictly necessary for one of those operations.
Withdrawing Consent
You may withdraw consent for optional cookies at any time.
Cutwise should provide a persistent mechanism such as:
- Cookie Settings
- Privacy Choices
- or another comparable control
that allows you to reopen your privacy preferences.
Withdrawing consent prevents future consent-based storage or access after your preference is processed.
It does not automatically delete information already lawfully transmitted to third parties.
Browser Controls
Most browsers allow you to:
- view cookies;
- block cookies;
- delete cookies;
- clear local storage;
- clear site data;
- restrict third-party cookies;
- or delete all browsing data.
Blocking all cookies may interfere with:
- authentication;
- checkout;
- account state;
- or other essential functionality.
Clearing Browser Storage Does Not Delete Your Cutwise Account
Deleting:
- cookies;
- local storage;
- session storage;
- cached files;
- or the browser itself
does not necessarily delete information stored on Cutwise servers.
It does not delete your Cutwise account.
It does not necessarily cancel a subscription.
It does not necessarily delete a Stripe customer record.
To delete your Cutwise account, use the account-deletion process provided by Cutwise.
To cancel a subscription, use the applicable Billing cancellation functionality.
Referral Cookies
If you delete the Cutwise referral cookie or referral storage before completing a qualifying subscription, Cutwise may no longer be able to automatically associate the purchase with the original referral.
This can affect referral-credit attribution.
Where reasonable, account-linked referral information may still permit attribution even if browser storage has been cleared.
Server-Side Events
Blocking a browser script or deleting cookies does not necessarily stop processing that does not depend on that cookie.
For example, Cutwise may still need to send server-side information for:
- Stripe payment processing;
- subscription entitlement;
- fraud prevention;
- security;
- accounting;
- or another essential service.
Optional server-side advertising or analytics events will be governed by the applicable privacy choice and legal basis.
Global Privacy Control and Do Not Track
If Cutwise implements Global Privacy Control or another legally recognized browser privacy signal in the future, this Policy will be updated to explain how we respond.
Browser Do Not Track signals do not have one universal technical or legal meaning.
Where a legally binding signal applies, Cutwise will respond as required by applicable law.
7. Changes to This Policy
We may update this Cookie Policy when:
- Cutwise changes;
- new cookies are introduced;
- providers change;
- analytics change;
- advertising systems change;
- referral functionality changes;
- payment infrastructure changes;
- browser storage changes;
- or legal requirements change.
The Last updated date at the top shows the most recent version.
If we begin using an optional cookie or other tracking technology requiring consent, that technology should not be activated merely because this Policy has been updated.
Where consent is legally required, we will request consent before activating the technology.
If we materially change the purposes for which a consent-based technology is used, we will request renewed consent where required.
Change Log
The production version of this Policy may maintain a history of major changes.
For example:
November 13, 2026 — Referral functionality added Added information about Cutwise referral attribution and referral storage.
November 13, 2026 — Stripe added Added website payment and billing technologies associated with Stripe.
November 13, 2026 — Analytics added Added information concerning
November 13, 2026 — Meta advertising added Added Meta advertising measurement technologies after the corresponding consent system was implemented.
Only actual Cutwise implementation dates should be added to the published change log.
Do not copy CutAI's historical dates into Cutwise's Policy.
8. Contact
help\@cutwise.com
You may also contact us if you:
- have a question about a cookie;
- want to understand what a provider receives;
- cannot access cookie preferences;
- want to withdraw consent;
- or believe an optional tracking technology is operating contrary to your privacy choice.
See also our:
- Privacy Policy
- Terms of Use
for additional information about how Cutwise processes personal data and the rules that govern the Services.
Effective date: November 13, 2026
Last updated: November 13, 2026