Cookies and browser storage help Kreotar work like a workspace.

Cookies are small pieces of data stored by your browser. Browser storage technologies, including LocalStorage, SessionStorage, IndexedDB, Cache Storage, and similar mechanisms, can store more structured information in the browser.

Kreotar may use these technologies to support sessions, language, interface preferences, local drafts, studio state, recent actions, security checks, and user-requested workflows.

Essential storage is necessary for the service to work. This may include authentication sessions, security tokens, locale settings, interface preferences, cloud workspace state, and technical state needed to move between tools and studios.

If you block all essential cookies or browser storage, parts of Kreotar may fail to load, lose state, sign you out, or become unable to save or reopen work.

Kreotar may use browser storage to support local drafts, tool-to-studio handoff, recently opened files, editor state, and temporary workflow data. This helps a quick task continue into a studio without unnecessary friction.

Local browser storage is stored on your device and can be cleared through your browser. If you clear it, local drafts or preferences may disappear.

Kreotar may use analytics to understand page performance, feature adoption, error patterns, route quality, and user experience issues. This helps improve the ecosystem and identify pages or workflows that need repair.

Analytics should be used to improve the product, not to sell private files. We aim to limit analytics to product and technical signals that help the service operate and improve.

Kreotar may use advertising technologies to support free public tools. Advertising partners may use cookies or similar identifiers to deliver, measure, or personalize ads according to their own policies and your consent settings where required.

Advertising should not require Kreotar to sell your private files or workspace content. You can manage ad personalization and cookie behavior through browser settings, consent tools where available, and provider controls.

Some services may set their own cookies or use their own storage when you interact with them. This can include authentication providers, cloud import providers, analytics providers, advertising partners, or media and infrastructure providers.

Kreotar does not control all third-party storage behavior. You should review the privacy and cookie policies of third-party providers when you connect accounts, authorize imports, or interact with embedded third-party services.

You can manage cookies and browser storage through your browser settings. You can clear cookies, block third-party cookies, delete site data, or use private browsing modes. These choices may affect login, KreoCloud, local drafts, preferences, and handoff workflows.

If a feature stops working after blocking storage, you may need to allow essential site storage or use a different workflow.

Kreotar's storage model may evolve as new tools, studios, and KreoCloud features are added. We may update this policy when storage behavior changes in a meaningful way.

The goal is to keep the policy aligned with the real implementation. If a workflow begins using a different technical path, public documentation should reflect that change.