Privacy is part of Kreotar's product architecture.

You may provide information when you create an account, contact support, upload or import a file, save a file in KreoCloud, use a studio, submit feedback, or interact with a form. The exact information depends on the feature you use.

Account and support information may include an email address, authentication identifiers, support messages, and technical context needed to respond to your request. File and workspace information may include file names, file metadata, saved project records, timestamps, and content you intentionally save or import.

Many Kreotar tools are designed to perform work inside your browser. This can include file reading, conversion preparation, editing, compression, formatting, preview generation, and other client-side operations powered by browser APIs and local runtime capabilities.

When a workflow is fully browser-side, the file can remain on your device during that workflow. However, not every feature has the same technical path. Some workflows may require cloud storage, server endpoints, authentication, third-party imports, or external resources. Kreotar's product language should reflect those differences.

KreoCloud is the workspace layer for saved files and ongoing projects. If you use KreoCloud, your chosen files and related records may be stored so you can access them later, organize them, reopen them in studios, or continue work across sessions.

KreoCloud is optional for many quick tasks. You can use many public tools without saving files to a cloud workspace. When you do use KreoCloud, the data is used to provide the workspace functionality you requested.

Kreotar may support importing files from external providers such as cloud storage services. These actions are initiated by you. The provider may require its own authentication flow and may apply its own privacy policy and terms.

Kreotar only needs access necessary to complete the import or workflow you request. We do not claim control over third-party provider practices, availability, security incidents, or account decisions.

Kreotar may use essential cookies and browser storage for authentication, security, preferences, language, workspace state, and product functionality. These technologies help the site work reliably.

Kreotar may also use analytics and advertising technologies to understand product performance, improve pages, and support free access. Advertising partners may use cookies or similar technologies according to their own policies and your consent settings where required.

We use information to operate Kreotar, provide tools and studios, maintain account and workspace features, respond to support requests, protect the service, debug issues, improve usability, and comply with legal obligations.

We do not use your private files to build a profile for sale. We do not sell your personal files or workspace content. We may process limited technical data to keep the service secure and functional.

Kreotar applies reasonable technical and organizational measures for the nature of the service. No online service can guarantee absolute security, but we design the product to minimize unnecessary data transfer and to separate public pages from private app surfaces.

Retention depends on the data type. Browser-local data can remain on your device until you clear it. KreoCloud data can remain while your account or saved workspace items exist. Support records may be retained as needed for operational, legal, or security purposes.

Depending on where you live, you may have rights to access, correct, export, delete, or restrict certain personal information. You can contact Kreotar to request help with account or privacy matters.

You can also control many items directly: clear browser storage, delete KreoCloud files, manage cookie settings, avoid optional imports, or use quick tools without signing in when a workflow supports it.