This Cookie Policy explains how Cutflux ("we," "us" or "our") uses cookies and similar technologies (collectively, "cookies") on our websites, apps, and embedded checkouts (the "Services").

If you do not agree with this Policy, you should adjust your preferences (see Manage Your Choices, §6) or refrain from using the Services.

1. What are cookies and similar tech?

Cookies are small text files stored on your device by a website.
Local Storage / Session Storage are browser storage areas used by web apps.
Pixels/SDKs are small code snippets that help measure usage and performance.

We use these to run the Service securely, remember choices, understand performance, and (if enabled) measure analytics.

2. How we categorize cookies

We classify cookies as:

Essential (Strictly Necessary) — required for core functionality and security (e.g., sign‑in, load balancing, fraud/bot protection such as Cloudflare Turnstile). These cannot be switched off.
Preferences — remember settings like language, theme, or saved state.
Analytics & Performance — help us understand how the Service is used so we can improve reliability and speed.
Marketing (only if used) — personalize content/ads and measure campaigns.

We do not currently use targeted advertising cookies. If this changes, we will request consent where required and update this Policy.

3. Examples of cookies/storage we may use

The exact cookies depend on which features you use and your region. Typical examples include:

Name (example)	Provider	Category	Purpose	Expiry
cf_bm, cf_clearance	Cloudflare	Essential	Bot/abuse detection, challenge completion, and rate limiting to keep the Service secure and reliable.	Up to 30 minutes – 1 year (varies)
__Host-<app-session>	Cutflux	Essential	Maintains your logged‑in session (HTTP‑only).	Session / up to 30 days
csrf-token	Cutflux	Essential	Protects against cross‑site request forgery.	Session
ls_* / __stripe_* (if checkout used)	Lemon Squeezy / Stripe	Essential	Payment processing and fraud prevention during checkout.	Up to 1 year
prefs (local storage)	Cutflux	Preferences	Saves UI choices (e.g., theme/language).	Until cleared
analytics_id (if enabled)	Analytics provider	Analytics	Usage insights to improve performance and stability.	13 months or less

4. Legal basis

Where required (e.g., EU/UK/EEA), we only set non‑essential cookies (Preferences, Analytics, Marketing) with your consent. Essential cookies rely on our legitimate interests in providing a secure, functioning Service.

5. Your choices

Consent banner: On your first visit (and periodically thereafter), we present options to Accept all, Reject non‑essential, or Manage settings.
Manage Your Choices: You can change your decision at any time via the Cookie Settings link in the footer or within the app. Revoking consent will stop future setting of non‑essential cookies; previously set cookies may remain until you clear them in your browser.
Browser controls: Most browsers let you block or delete cookies. Doing so may break parts of the Service that rely on Essential cookies.
Global Privacy Control (GPC): Where applicable (e.g., California), we treat a valid GPC signal as an opt‑out of cross‑context behavioral advertising.

6. Cookie banner & preferences

Short banner copy:

We use cookies to run the site, keep it secure, and (with your consent) improve performance. Click "Accept all" to agree, "Reject non‑essential," or "Manage settings" to choose.

Categories shown in settings:

Essential — Always active (security, sign‑in, load balancing, Turnstile).
Preferences — Off by default in EU/UK unless you choose on.
Analytics — Off by default in EU/UK unless you choose on.
Marketing — Currently not used.

Buttons: Accept all · Reject non‑essential · Save choices

7. Changes to this Policy

We may update this Policy if our cookies or practices change. We will post the updated version with a new Effective date and, where required, seek consent again.

8. Contact

Questions? Email [email protected] or use our support page.

This Policy is for transparency and does not constitute legal advice. Ensure your published cookie table reflects the actual cookies/storage in use on your site and embedded checkout.