Legal

Cookie Policy

How KreaTivLab uses cookies, browser storage and similar technologies.

Effective September 2, 2026Last updated September 2, 2026

Overview

This Cookie Policy explains how KreaTivLab, a product of XtraLynk Technologies LLC ("KreaTivLab," "we," "us," or "our"), uses cookies, browser storage and similar technologies when you use our website and Services.

Read it together with our Privacy Policy.

1. What cookies and browser storage are

Cookies are small data files a website stores on your device or browser. They can be used for authentication, security, preferences, session management, analytics, performance and functionality.

KreaTivLab relies mostly on browser-storage technologies that are not technically cookies — primarily localStorage — plus a small number of first-party cookies and third-party technologies set by payment and account providers.

2. Strictly necessary technologies

Strictly necessary technologies are required for the Services to work at all. In KreaTivLab these are:

  • your authentication session, stored in localStorage, which keeps you signed in and authorizes access to your workspace
  • short-lived state used to complete a Google/YouTube authorization securely
  • technologies set by Stripe when a checkout or billing surface is loaded

These cannot be switched off through a preference control, because without them you cannot sign in, stay signed in, connect a channel, or pay.

3. Functional storage

Functional storage remembers your preferences. Verified functional entries are your theme preference, your interface language, whether you dismissed the install-to-home-screen prompt, whether you completed an in-app guided tour, and whether the app sidebar is expanded (the only first-party cookie we set).

Clearing these does not sign you out; it simply resets those preferences to their defaults.

4. Analytics, performance and error monitoring

KreaTivLab does not load a browser analytics provider such as Google Analytics, and does not set analytics or telemetry cookies in your browser.

Product and usage analytics you see inside KreaTivLab are produced server-side from your own account activity and from metrics retrieved from platforms you connected, and creator analytics such as YouTube metrics are fetched by our servers rather than by a browser tracker.

Error and performance diagnostics are captured server-side from application logs. No third-party browser error-monitoring script is loaded on our pages.

KreaTivLab does not currently use advertising, retargeting or cross-site behavioral advertising cookies, and does not load advertising pixels.

5. Stripe and payments

KreaTivLab uses Stripe for subscription and credit-pack payments, and loads Stripe's embedded checkout and billing surfaces inside the app.

Stripe may set its own cookies and browser storage for payment processing, fraud prevention, security and transaction integrity. Those technologies are set and controlled by Stripe under Stripe's own privacy and cookie policies; KreaTivLab does not control them, and card details are never handled by KreaTivLab.

6. Google and YouTube

When you connect a Google/YouTube account, the authorization happens on Google's own domains, where Google may use its own cookies and authentication technologies under Google's policies. KreaTivLab does not control those.

KreaTivLab stores only what is needed to complete the authorization securely and to keep the connection working afterwards; connection tokens are held encrypted on our servers, not in your browser.

KreaTivLab does not currently embed YouTube players, social widgets or other third-party media embeds on its marketing pages.

7. Browser storage in the app

Beyond the entries listed below, KreaTivLab's editors keep working state on our servers rather than in your browser: Creative Studio generations and Clips projects are saved server-side, including autosave.

Some processing, such as media preview and audio analysis used by Beat Sync, happens in your browser memory during the session and is not written to persistent browser storage.

KreaTivLab does not use IndexedDB for its own data, and does not use sessionStorage for its own preferences.

8. PWA and service workers

KreaTivLab can be installed to your home screen using a web app manifest. Installation is a browser feature and does not itself require cookies.

The published app may register a service worker, which browsers use to cache application files in Cache Storage to improve loading. Cache Storage and service workers are not cookies and are not used to identify or track you. Service workers are not registered in preview or development environments, and appending ?sw=off to a page URL unregisters the app service worker.

9. Cookie and storage table

The table below reflects the technologies verified in the current production build. Names of third-party technologies are set by those providers and can change.

sb-<project>-auth-token

Provider
KreaTivLab (authentication service)
Category
Strictly necessary
Purpose
Keeps you signed in and authorizes requests to your workspace.
Storage
localStorage
Duration
Until sign-out, token expiry, or you clear browser storage
Required
Yes

kreativ-theme

Provider
KreaTivLab
Category
Functional
Purpose
Stores your light / dark / system theme preference.
Storage
localStorage
Duration
Until removed
Required
No

kreativlab.locale

Provider
KreaTivLab
Category
Functional
Purpose
Stores your selected interface language.
Storage
localStorage
Duration
Until removed
Required
No

kreativlab.install-prompt.dismissed

Provider
KreaTivLab
Category
Functional
Purpose
Remembers that you dismissed the install-to-home-screen prompt.
Storage
localStorage
Duration
Until removed
Required
No

kreativlab.tour.*

Provider
KreaTivLab
Category
Functional
Purpose
Remembers which in-app guided tours you have already completed.
Storage
localStorage
Duration
Until removed
Required
No

sidebar_state

Provider
KreaTivLab
Category
Functional
Purpose
Remembers whether the app sidebar is expanded or collapsed.
Storage
First-party cookie
Duration
About 7 days
Required
No

Stripe checkout / billing technologies

Provider
Stripe
Category
Strictly necessary (payments)
Purpose
Payment processing, fraud prevention and transaction integrity when a Stripe checkout or billing surface is loaded.
Storage
Third-party cookies and storage set by Stripe
Duration
Set and controlled by Stripe
Required
Yes, to complete a payment

Google account technologies

Provider
Google
Category
Third-party
Purpose
Authorizing your Google/YouTube account during the connection flow, on Google's own domains.
Storage
Cookies and storage set by Google on Google domains
Duration
Set and controlled by Google
Required
Yes, to connect a Google/YouTube account

10. How long these technologies last

Session technologies expire when the browser session ends. Persistent technologies remain until they expire or are removed. Browser storage such as localStorage and Cache Storage persists until the application, you, or your browser removes it.

Where a duration is controlled by a third party such as Stripe or Google, that provider sets the lifetime, not KreaTivLab.

11. Your choices

You can control these technologies through your browser: block or delete cookies, block third-party cookies, clear site data and browser storage, or use private browsing.

Clearing strictly necessary storage will sign you out of your workspace, and blocking Stripe or Google technologies may prevent payment or channel connection from completing.

KreaTivLab does not currently display a cookie-consent banner or a cookie preference center, because it does not run optional advertising or third-party browser-tracking technologies. If optional tracking is introduced in the future, consent controls will be added before it is enabled.

12. Selling and targeted advertising

KreaTivLab does not sell personal information, does not share personal data for cross-context behavioral advertising, and does not currently use cookies for cross-site behavioral advertising or retargeting.

13. AI features and browser tracking

AI features call providers from our servers, not from your browser. Using an AI feature does not place third-party AI-provider cookies on your device. See the AI Disclosure for how AI processing works.

14. Changes to this policy

We may update this Cookie Policy when website technologies, analytics tools, payment integrations, consent mechanisms or laws change. The "Last updated" date identifies the current version.

15. Contact

Questions about this policy can be sent to:

  • XtraLynk Technologies LLC — KreaTivLab
  • Email: kreativlab@xtralynk.com
  • Website: https://kreativlab.dev