Privacy Policy

Last updated: 2026

1. Introduction

Welcome to Kensa. We respect your privacy and are committed to protecting your personal data.

2. Data We Collect

We collect information you provide directly to us when you create an account, generate videos, or contact support.

3. How We Use Your Data

We use your data to provide and improve our services, including generating AI videos and maintaining your transaction history.

We email you about your account, such as sign-in links, and about getting started with Kensa, such as tips, reminders and offers; every getting-started email has an unsubscribe link, and you can also ask [email protected] to unsubscribe you.

4. Data Security

We implement appropriate security measures to protect your personal information.

5. Cookies and Analytics

We use four analytics services to understand how Kensa is used and to fix problems:

  • PostHog (product analytics): page views and product events, for example starting a video generation, a download or a checkout.
  • Microsoft Clarity (session replay and heatmaps): records how pages are used, such as clicks, scrolling and page layout. It does not record admin pages.
  • pvuv.ai (visit statistics): counts page views and visitors, with the referring site, campaign tags, screen size, language, time zone and browser type. It sets its own cookies (_pv_id and _pv_uid, about 13 months) to recognise a returning browser and, once you sign in, your internal account ID. It does not count admin pages.
  • Umami (privacy-friendly visit statistics): counts page views with the referring site, campaign tags, browser, device type, screen size, language and country. It sets no cookies and does not count admin pages.

When you are signed in, PostHog, Clarity and pvuv.ai receive an internal account ID, not your email address; Umami receives no account information. When a payment completes, our server reports it (amount, product and country, with the account ID) to PostHog and pvuv.ai. Each service sets its own cookies and browser storage to recognise a returning browser and visit. Analytics events also carry the traffic source of your visit (channel, referring site, landing page and campaign tags), which we keep in your browser's storage.

Kensa also keeps, in your browser's storage, a list of the Kensa pages you viewed in the last 30 days and how long each was on screen (page paths only, up to 60 pages). When you first sign in on a browser and when you start a checkout, we save that list and the traffic source of your first visit with your account, together with your country and device type, so we can see which pages lead people to buy. Signing out clears the list from the browser.

Kensa itself sets these cookies:

  • better-auth.session_token (7 days, extended while you keep using Kensa): Keeps you signed in (the sign-in session cookie). On HTTPS the name starts with __Secure-.
  • better-auth.session_data (5 minutes): A short-lived, signed copy of your sign-in session, so pages do not look it up on every request.
  • better-auth.state (Removed when you return from Google): Set only while you sign in with Google, to check that the sign-in response belongs to your browser.
  • kensa_ref (30 days): Referral cookie. Set when you open an invite link (a link with ?ref=) or type an invite code when signing up. It holds only the invite code, so a new account can be linked to the person who invited you.
  • kensa_touch (365 days): First-party attribution cookie. It holds only channel names: how this browser first reached Kensa and how it arrived on the current visit (for example search, social or an AI assistant, plus the assistant's name). No referring address, page URL or personal data. It is read when you create an account, so we can count sign-ups by channel.
  • NEXT_LOCALE (Until you close the browser): Remembers the site language.
  • shopify_oauth_state (10 minutes): Set only while you connect a Shopify store to Kensa, to check that Shopify's install response belongs to your browser.

6. Contact Us

If you have questions about this policy, please contact us at [email protected].