Cookie Policy

1. What cookies are

Cookies are small text files a website stores on your device. They let the site recognise your browser on the next request: keep you signed in, protect forms and remember your interface language.

Alongside cookies we use browser storage (localStorage and sessionStorage). It is not sent to the server with every request, but we describe it here as well so the picture is complete.

What follows is what the service actually sets. If the list changes, this page changes with it.

2. Strictly necessary cookies

The service does not work without these files: they carry sign-in, request security and correct rendering of the interface. They cannot be switched off selectively — you can only block cookies entirely in your browser, and then signing in becomes impossible.

• Session and authentication. The sign-in and session-renewal cookies (accessToken, refreshToken) are not readable by JavaScript (httpOnly flag). An additional auth_session file is read by the interface and holds only your identifier, username and role — no email or other contact details.
• Cross-site request forgery protection (csrf_token): confirms that an action was initiated by you on our site.
• External sign-in protection (google_oauth_state_srv, yandex_oauth_state_srv): short-lived files that prevent tampering with the identity provider's response.
• Anti-bot check. Our sign-in and sign-up forms run a Cloudflare Turnstile check. It loads from challenges.cloudflare.com and may set its own technical files to tell a person from an automated sign-up. We use that service purely as an anti-bot check; it does not deliver our site or media files.
• Interface language (clipia_locale): remembers the language you selected so you do not have to switch it on every visit.
• Offer consistency (clipia_trial_ab): a technical key that keeps the pricing offer you see identical before and after registration. It contains no information about you.

The interface theme is not stored in a cookie but in browser storage under the clipia-theme key. It is never sent to the server and is removed together with the site data.

3. Analytics: Yandex.Metrica and Webvisor

Our primary analytics tool is Yandex.Metrica (Yandex LLC, Russia). It shows which pages people use, where journeys break and which sections are slow.

The counter has Webvisor — session recording — enabled. That means cursor movement, clicks, scrolling, interaction with the interface and the sequence of screens are recorded and replayed as video. Recordings are used only to diagnose interface problems and errors. Webvisor does not record the contents of password fields, and payment forms are rendered by the payment provider, so they stay out of the recording.

Metrica sets _ym_uid, _ym_d, _ym_isad and the Webvisor service file _ym_visorc. The analytics provider defines its own terms for the data its counter collects.

4. Google Analytics and Google Ads — outside Russia only

For audiences outside Russia we additionally use Google Analytics 4 and Google Ads to evaluate traffic sources and record advertising conversions. These services set _ga, _ga_<identifier> and _gcl_au.

For users located in Russia the foreign counters are not loaded at all: the Google Analytics and Google Ads scripts are not injected and their cookies are not set. Analytics for the Russian audience relies on Yandex.Metrica, and the initial recording of Russian citizens' personal data takes place in databases located in Russia.

5. Payment provider cookies

We neither process nor store card details. Payment happens on the payment provider's side, and those providers set their own cookies under their own rules:

• CloudPayments — primary rouble payments for Russia. The form opens on top of our site; the files are set by the provider's domain.
• Robokassa — backup rouble payments for Russia. Payment is completed on the provider's own site after you leave our page.
• Stripe — international payments, completed on a secure Stripe page. Your prompts, uploaded files and generation results are never passed to payment providers.

6. Site and media delivery

Images and video are delivered through the Amazon CloudFront content delivery network from media.clipia.ai. No cookies are used to load them.

7. Cookie table

Browser storage additionally holds clipia-theme (interface theme) and clipia-analytics-consent (your choice in the consent banner, if it was shown).

8. Managing cookies

8.1 Browser settings

You can delete stored files and block new ones:

• Chrome: Settings → Privacy and Security → Cookies
• Firefox: Settings → Privacy & Security → Cookies and Site Data
• Safari: Settings → Privacy → Manage Website Data
• Edge: Settings → Cookies and site permissions

Blocking strictly necessary files makes signing in impossible.

8.2 Do Not Track and Global Privacy Control

We honour browser privacy signals. If Do Not Track (DNT) or Global Privacy Control (GPC) is enabled, no analytics script is loaded at all — neither Yandex.Metrica nor Google Analytics nor Google Ads. Strictly necessary files keep working.

8.3 Consent banner for the EEA, the UK and Switzerland

Visitors from the European Economic Area, the United Kingdom and Switzerland see a consent banner. Until you press "Accept", no analytics script is loaded. Your choice is stored in browser storage; to change it, clear the site data in your browser.

8.4 What the service does not offer

There is no separate cookie-category control panel in your account settings, and we do not show a category-selection banner to users in Russia. The available controls are described in sections 8.1–8.3.

9. What changes if you disable cookies

• Strictly necessary: signing in and paying become impossible
• Language and theme: you will have to choose them on every visit
• Analytics: your visits stay out of our statistics; the service itself is unaffected

10. Policy updates

We update this page whenever the set of cookies or connected services changes. For material changes we will notify you in the site interface or by email.

11. Related documents and contacts

• Privacy Policy — what data we collect and on what legal basis
• International Data Processing & Transfers — recipients outside your country and the safeguards applied
• Consent to Personal Data Processing — the scope of consent and how to withdraw it

Questions about cookies and privacy: privacy@clipia.ai. Data protection contact: dpo@clipia.ai.