Reach the team behind the Kreotar workspace ecosystem.

Contact us if a tool, studio, KreoCloud workflow, import, export, save action, or mobile interface does not behave as expected. A useful support request includes the route, the feature name, browser, device type, whether you were signed in, and the smallest set of steps that reproduces the issue.

For file-related issues, describe the file type and approximate size. Do not attach confidential files in an initial message. If we need a sample, we will ask for a non-sensitive reproduction file or another safe way to understand the problem.

Use the contact channel for privacy questions, account deletion assistance, data access questions, or clarification about how a workflow handles files. We may need to verify account ownership before acting on account-specific requests.

If your question is about cookies, analytics, advertising, browser storage, KreoCloud, or third-party imports, mention the relevant feature so the response can be precise.

Bug reports are most useful when they are reproducible. If a button does not work, a mobile bottom sheet overlaps a bar, a translation key appears on screen, or a studio fails to open, include the exact path and what you clicked.

Kreotar covers many surfaces, so precision matters. A report that says 'PDF is broken' is hard to investigate. A report that says 'on /en/cloud, tapping a PDF card opens a bottom sheet but the mobile nav remains visible' gives us a real path to fix.

If a public page contains outdated information, unclear wording, wrong route behavior, inaccurate privacy language, or a broken link, contact us. Public trust pages and SEO pages should match the real product.

We especially welcome reports where a page describes a workflow too broadly. Kreotar should not claim browser-only processing for a feature that uses cloud storage, an API, or a third-party provider.

Kreotar is a growing ecosystem, and partnership conversations should be relevant to privacy-first productivity, browser tools, workflow automation, document productivity, education, developer workflows, or cloud workspace improvements.

We do not accept irrelevant link schemes, misleading SEO proposals, or outreach that would weaken user trust. Partnership messages should clearly explain the value for Kreotar users.

If you believe you found a security issue, contact us with a clear, responsible report. Do not exploit, access, modify, delete, or exfiltrate data that does not belong to you. Do not perform disruptive testing against production systems.

A responsible report includes the affected route or feature, a concise explanation, reproduction steps, and the potential impact. We appreciate careful disclosure that protects users.