Data Minimization

Our privacy-first stance means: we treat processing as a purpose-bound technical operation, not as an invitation to analyze your content.

No content analysis

We do not analyze documents or chat messages. Not for LLM training, not for advertising, not for profiling, and not for product analytics. When data is processed, it is processed for the function you are using.

No readable chat history on the server

We do not store chats as readable server history. This includes user messages and LLM responses. The chat state remains local on your device.

Temporary data instead of permanent storage

Server-prepared document and RAG data is stored only as long as needed for the concrete function. It is deleted afterwards. This temporary storage enables work with large documents, but it is not permanent document storage.

Metadata

A service cannot operate entirely without technical metadata. Depending on use, account ID, timestamps, file sizes, status values, quotas, error states, or expiration times may be processed.

We keep this data as purpose-bound as possible. It supports operation, security, quota accounting, and deletion, not content analysis of your chats or documents.

Your choice

You can combine functions according to your task: local document processing and optional server processing for large documents. The more confidential the content, the more strongly you should prefer local processing.

For documents with personal data, Pseudonymization adds an additional protective layer.